Capstone HOME
The Capstone Manuscript guide is a structural and writing companion for BSIT and BSIS undergraduate researchers. It explains what each section of your manuscript exists to do, how to write it, and what the panel will look for when you defend it. Use it as a daily reference while you draft, revise, and prepare for your final defense.
Capstone manuscript - the 16-part map
A reusable academic reference for BSIT and BSIS programs. First Edition, 2026. Authors: Arnel C. Maghinay, Ph.D.; Alfonso D. Sales, Jr., Ph.D.; Ryan J. de la Gente, Ph.D. Carlos Hilado Memorial State University.
What this guide is
Every section of a BSIT or BSIS capstone manuscript has a predictable purpose, a predictable structure, and a predictable set of panel questions. Once you understand those three dimensions for a section, writing it becomes mechanical.
The 16 parts in order
Part 1 Preliminary Pages (title, approval, abstract) Part 2 Chapter I - Introduction Part 3 Chapter II - Literature Review Part 4 Chapter III - Methodology Part 5 Chapter IV - Results Part 6 Chapter V - Summary and Conclusion Part 7 Writing the References Section Part 8 Appendices Part 9 Writing Stronger Paragraphs - Before and After Part 10 A Second Case Study for BSIS Researchers Part 11 For Research-Only Capstones Part 12 How to Defend Each Section Out Loud Part 13 Common Panel Questions Part 14 Month-by-Month Timeline Checklist Part 15 Rubric Decoder Cross-Reference Part 16 Sample Appendix Content
Recommended writing order
You do not write in the printed order. Drafting follows the logic of the project:
- Chapter III (Methodology) - design the system before building it.
- Chapter I (Introduction) - frame the problem the methodology solves.
- Chapter II (Literature) - position your work against existing systems.
- Chapter IV (Results) - report what the prototype actually does.
- Chapter V (Summary) - close the loop and recommend next work.
- Preliminary pages + Abstract - last, when the chapters exist.
- References + Appendices - compiled throughout; finalised at end.
The title is the first thing the panel reads
A strong capstone title names the platform, the scope, the distinctive feature, the client, and the locale - in that order. Example:
Weak: Online Ordering System
Improved: Web-Based Ordering and Inventory Management System with SMS
Notification for Sample Bakery Shop in Sample City
The improved version lets a panel member assess scope-fit before opening the book - which is exactly what you want.
The abstract is six sentences
Sentence 1 Problem context - what is happening in the field/client? Sentence 2 Purpose - what did this project set out to do? Sentences 3-4 Methodology - SDLC model + data gathering + tools Sentence 5 Results - what the system does + acceptance score Sentence 6 Conclusion / Recom. - what this proves and what comes next
Defense reality check
Panels ask three families of questions for every section:
- Why this scope? (Why not bigger? Why not smaller?)
- Why this method? (Why this SDLC? Why these respondents?)
- Why this result? (How do you know the system works?)
If you can answer those three for every chapter, you will pass.
How to use this site
Each part of the printed guide maps to a section in this track. Open the section you are writing today. Read the worked example, copy the structure, substitute your own project specifics, and run the panel defense checklist before you submit.
Important: every worked example uses a fictional demonstration project (Sample Bakery Shop). Replace it with your own project before submitting.
Discussion
Loading…