A capstone document follows a standard five-chapter structure. Knowing exactly what belongs in each chapter is half the battle — it turns a daunting blank page into a checklist. Here is the complete structure used by most IT, Computer Science and Software Engineering programmes, with guidance on what each section should contain.
Front matter
Title page, approval sheet, abstract (a one-paragraph summary of the problem, method and result), acknowledgements, and the tables of contents, figures and tables.
Chapter 1 — Introduction
- Background of the study — the context and why the topic matters.
- Statement of the problem — the general problem plus specific sub-problems as questions.
- Objectives — general and specific, measurable objectives.
- Scope and limitations — what the system will and will not do.
- Significance of the study — who benefits and how.
- Definition of terms.
Chapter 2 — Review of Related Literature & Systems
Summarise existing research and similar systems, then state your synthesis: how your project is different or better. Always connect each source back to your problem rather than just listing them.
Chapter 3 — Methodology
- Development model — Agile, Waterfall, RAD, etc., and why you chose it.
- Requirements — functional and non-functional.
- System design — ER diagram, data flow diagrams, use-case and the database schema.
- Tools — languages, framework, database, hardware.
- Testing plan.
Chapter 4 — Results & Discussion
Present the finished system with screenshots, the results of testing, and how it answers each sub-problem from Chapter 1. Discuss what worked and what was hard.
Chapter 5 — Summary, Conclusions & Recommendations
Summarise the project, state your conclusions against the objectives, and recommend future improvements.
Back matter
References (in your required citation style), and appendices: source code excerpts, the user manual, survey instruments and the like.
Practical tips
- Write Chapter 1 first, then 3, then 2 — it flows more naturally.
- Keep your objectives, sub-problems and Chapter 4 results aligned one-to-one.
- Build the system in parallel with the document; don’t leave writing to the end.
Next: How to write Chapter 1 · ER diagram examples · project ideas with source code.