Capstone documentation chapters 1 to 5: what goes in each chapter

Most Philippine computing programs use a five-chapter manuscript for capstone projects and theses. The headings vary a little between schools, so your own capstone manual always wins. This guide explains what each part is for, so you write the right things in the right place the first time.

Preliminary pages

The front matter usually runs six to ten pages. It includes the title page, the approval sheet with the panel’s signatures, the abstract, the acknowledgement, the table of contents, and the lists of figures, tables, and appendices. Write the abstract last. It should state the problem, the system, the method, the evaluation result, and the conclusion in about 150 to 250 words.

Chapter 1: Introduction

Chapter 1 explains the problem and what the project will do about it. Typical length is 2,500 to 4,000 words.

• Project context or background of the study: the setting, the current process, and why it needs a system.
• Purpose and description: what the system is and what it does, in plain terms.
• Objectives: one general objective and three to six specific objectives, each one measurable and each one matched to a feature you will actually build.
• Scope and limitations: what is inside the system, what is outside it, and the constraints you accept.
• Significance of the study: who benefits and how.

Panels read the specific objectives closely. If an objective says the system will “generate reports”, Chapter 4 must show that report working.

Chapter 2: Review of related literature and studies

Chapter 2 shows that you know what already exists. It is usually the longest chapter at 5,000 to 8,000 words.

• Related literature: concepts, technologies, and standards your system relies on.
• Related studies: local and foreign systems that solved similar problems, with what they did and what they lacked.
• Synthesis: a short section that ties the sources together and points to the gap your system fills.
• Conceptual or theoretical framework: often an input-process-output diagram or a framework diagram that shows how the system works.

Use APA 7th edition for citations unless your manual says otherwise. Most schools now run manuscripts through a plagiarism checker, so paraphrase and cite.

Chapter 3: Methodology

Chapter 3 explains how you built and evaluated the system. Typical length is 2,000 to 3,500 words, plus diagrams.

• The software development model you followed, such as Agile, Scrum, or a modified waterfall, and why it fits the project.
• Requirements analysis: how you gathered requirements, with interview or survey instruments in the appendices.
• System design: use case diagram, entity relationship diagram, data flow diagram or activity diagrams, and the system architecture.
• Development tools: languages, frameworks, databases, and hosting.
• Testing: unit testing, integration testing, and user acceptance testing, with the test plan.
• Evaluation instrument: many programs use the ISO 25010 software quality characteristics with a Likert scale questionnaire, and some add a statistical treatment such as weighted mean.

Chapter 4: Results and discussion

Chapter 4 presents the finished system and the evaluation results. Typical length is 3,000 to 5,000 words, much of it figures and tables.

• Screenshots of each major module, with a short description of what the user does on that screen.
• Test results, including what failed in testing and how it was fixed.
• Evaluation results per criterion, in tables with the weighted mean and the verbal interpretation.
• A discussion that connects every result back to the specific objectives in Chapter 1.

Chapter 5: Summary, conclusions, and recommendations

Chapter 5 is short, usually 1,500 to 2,500 words.

• Summary: the problem, the system, the method, and the main results in a few paragraphs.
• Conclusions: one conclusion per specific objective, stating whether it was met and on what evidence.
• Recommendations: improvements for the system and suggestions for future researchers, each one realistic.

References and appendices

References follow the citation style in your manual, usually APA 7th edition. Appendices typically include the endorsement or request letters, interview and survey instruments, the evaluation questionnaire, test cases, the user manual, source code excerpts if required, and the curriculum vitae of each member.

Mistakes that get manuscripts returned

• Objectives in Chapter 1 that have no matching feature in Chapter 4.
• A Chapter 2 that lists sources without a synthesis.
• Diagrams in Chapter 3 that do not match the system that was built.
• Evaluation tables with no statistical treatment or no verbal interpretation.
• Conclusions that are opinions rather than statements tied to results.
• Inconsistent formatting: fonts, margins, spacing, and heading styles that drift between chapters.

Where we fit in

Karakoa builds the system and supports the documentation that describes it. Diagrams, test plans, and the technical sections of Chapters 3 and 4 come straight from the working system, so the manuscript and the code match on defense day. The writing stays yours, and we never submit a paper on a student’s behalf.