Chapter 2 in Thesis Writing for IT/CS Students (with Samp...

Chapter 2 (Review of Literature and System)

Is a proof that no one studied the gap in the knowledge outlined in chapter 1. Hence, his will state the previous study that is also related to your study to build more foundation.

Take note that the format of the study vary from one school to another or one course to any course so better finishes first the chapter 1 before proceeding to this chapter.

In this chapter, you must start with a brief introduction about the investigations of the researcher on the review literature and system about the problem.

Here, you must get your data from any book, magazines and much more. Most of all, label your published material with local or foreign sources.

Things to consider in writing chapter 2:

First, include only those references that have immediate connections or relevance for the study and to the system.
Second, be explicit in stating the relevance of all cited literature and system.
Third, the review should be in the form of an assimilated presentation of all materials.
Next, it must not contain a simple listing (annotated bibliography).
Also, when comparing and summarizing studies, be sure to note possible differences between samples, measurement techniques and much more, summarize only those truly comparable sources.
Then, it is best that your sources is updated and is finished in the most recent years. Probably, more effective if the material should not be older than 5 years.
Another, to construct a literature review consider the following issues:
- the selection of the problem
- delimiting the scope of the problem
- demonstrating the relationship of the study to previous knowledge
- indicate the contribution of the study, and
- examine the tools and methods in investigating the problem.
In addition, the researcher must be selective with respect to the quality of the sources cited.
Finally, this chapter may contain both conceptual and research literature and system.

You Can download the Chapter 2 Example CHAPTER-2

Note: Chapter 2 is encrypted with a password. Send me an email for the password.

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.

Official references

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 →