Chapter 3 in Thesis Writing for IT/CS Students

Chapter 3
Chapter 3

Chapter 3

(Design and Methodology)

Generally, this chapter will describe how you will create and develop your analysis section. The section describing measurement techniques should include some test of validity and reliability. In addition, the who, what, when, and where of data collection procedure will be used.

Another, the researcher will discuss and present the description, features, research design employed, the instruments used in the gathering of data, the course of action followed in the gathering of data, and the analysis of the gathered data in relation to the specific objectives of the study and procedures.

Any data collected describing the samples are not results. They should be included in this chapter rather than in the results chapter.

  1. Research Design
    • It shows the function and structure of the system, tables, diagrams and other tools to make a clearer vision about the study.
    • In some studies, this part already includes the pilot study to readily validate the effectiveness of the instruments and the system.
  2. Participants/Respondents
    • The number of participants requires sample size which is based on the total number of potential participants and is determined by a power analysis.
    • Use the alpha level and the population effect size which is the estimated effect of the independent variable within the target population, this is to estimate the number of participants needed to demonstrate and existing effect.
  3. Instrumentation
    • There are two kinds of instruments used to collect data, one is created by the researcher and the other is based on an existing instrument.
    • If the instrument is researcher created, the process used to select questions should be described and justified. If an existing instrument is used, the background of the instrument is described. Also, if a Likert scale is used, the scale should be described. If the study involves interviews, an interview protocol should be made for data collection.
  4. Procedure
    • This section is itemized, starting with letters of permission to conduct the study until the end of the testing process. In other words, this section will detail when and how the data were collected.
  5. Data Processing and Statistical Treatment
    • In both qualitative and quantitative studies, the precise method of how the data were processed and analyzed is described.

Capstone chapter writing checklist

Structuring a BSIT capstone chapter correctly saves rework and eases the defense. Follow this checklist for consistent quality across all 5 chapters.

  • Draft the outline first. Every section header first, then fill in the content.
  • Write the methodology before the introduction. Chapter 3 (methodology) forces you to think through the system; Chapter 1 becomes easier after.
  • Include diagrams early. UML diagrams in Chapter 3 clarify what you’re building.
  • Cite sources as you write. Do not defer citations. Use Zotero or Mendeley to track sources.
  • Get adviser feedback per chapter. Do not write all 5 chapters then ask for review.
  • Number figures and tables. Figure 3.1, Table 4.2, etc. Panels reference these numbers.
  • Follow the school template exactly. Font, margins, spacing — do not deviate.

Common capstone mistakes to avoid

  • Copying without attribution. Panels use Turnitin. Cite everything you did not write yourself.
  • Over-scoping the project. A well-executed simple system beats a poorly-executed ambitious one.
  • Deferring documentation. Documentation quality is a big part of the grade.
  • Skipping user testing. Panels ask about user feedback. Have real data.
  • Ignoring adviser feedback. Advisers know what the panel will ask.

Recommended free tools for capstone projects

  • draw.io / diagrams.net. UML diagrams for Chapter 3.
  • Google Docs. Collaboration + version history + adviser comments.
  • Zotero or Mendeley. Reference management + auto-formatted citations.
  • GitHub. Version control for the source code (also earns E-E-A-T signal on your CV).
  • Grammarly. Language + tone check on the documentation.
  • Turnitin. Plagiarism check before submission (some schools provide access).
  • ChatGPT or Claude. For outline scaffolding — not for writing the actual content.

Where to get more capstone resources

  • Capstone project ideas. Browse itsourcecode.com/topics/fyp/ for 140+ tested capstone concepts.
  • Working source code. itsourcecode.com/topics/free-projects/ has 1,000+ downloadable projects.
  • UML diagrams. itsourcecode.com/uml/ has 300+ free UML examples for Chapter 3.
  • ER diagrams. itsourcecode.com/topics/uml/erd/ for database schemas.

Frequently asked questions

How many pages should a BSIT capstone chapter be?

Chapter 1 (Introduction) is typically 8-12 pages. Chapter 2 (RRL) is 15-25 pages. Chapter 3 (Methodology and System Design) is 15-30 pages depending on diagram count. Chapter 4 (Results) is 10-20 pages. Chapter 5 (Conclusions) is 5-10 pages. Total: 60-100 pages for the whole capstone.

What order should I write the chapters in?

Recommended order: Chapter 3 first (system design and methodology — most concrete), then Chapter 1 (introduction with the problem statement), then Chapter 2 (RRL to justify Chapter 1), then Chapter 4 (results — after implementation), then Chapter 5 (conclusions). This avoids rewrites and speeds up defense readiness.

What formatting style should I use for the capstone documentation?

Most Philippine BSIT programs require IEEE or APA 7th edition. Confirm with your adviser first. Use Times New Roman 12pt, double-spaced, 1-inch margins, and page numbers. Reference all sources properly and use consistent citation style throughout.

How many references do I need per chapter?

Chapter 1: 5-10 references. Chapter 2 (RRL): 20-40 references. Chapter 3: 10-15 references. Chapter 4-5: minimal, mostly self-referential. Recent sources (last 5 years) are strongly preferred over older ones.

What tools help write the capstone chapters?

Zotero or Mendeley for reference management, Grammarly for language check, Turnitin for plagiarism scan, Google Docs for collaboration with adviser, LaTeX (Overleaf) for advanced formatting, and ChatGPT or Claude for outline scaffolding (not for writing the actual content).

Joken E. Villanueva


Founder & Lead Developer at PIES IT Solution

Founder of PIES Information Technology Solutions, a software company building production-grade applications for institutions across the Philippines. Over 8 years of hands-on full-stack development experience, currently leading the development of ClinicAI, an AI-powered clinic management platform.

Expertise: PHP · MySQL · JavaScript · AI Integration · SaaS Architecture · VB.NET · Database Design · Capstone Documentation · Java
 · View all posts by Joken E. Villanueva →

Leave a Comment