Final Year Project Report Chapters: What Goes in Each One

By Vivek Singh · 28 September 2026 · 2 min read

In short

A final year project report usually has seven chapters: Introduction, Survey of Technologies, Requirements and Analysis, System Design, Implementation and Testing, Results and Discussion, and Conclusion. Each has standard sections, and examiners expect the diagrams and tables that belong to them.

Key takeaway

A final year project report has seven standard chapters, moving from why (introduction) to what (requirements) to how (design and implementation) to proof (testing and results) and reflection (conclusion). Each chapter has expected sections and diagrams, listed below.

Chapter 1: Introduction

1.1 Background: the problem area and why it matters
1.2 Objectives: 4–6 specific, measurable goals
1.3 Purpose, scope and applicability: what the system does and does not do, and who uses it
1.4 Achievements: what you delivered
1.5 Organisation of the report: one line per chapter

Chapter 2: Survey of Technologies

One section per major technology in your stack (for example React, Node.js, MongoDB). For each, cover what it is, why you chose it and which alternatives you considered.

Chapter 3: Requirements and Analysis

Problem definition
Requirements specification: functional requirements (FR1, FR2 …) and non-functional requirements (performance, security, usability)
Planning and scheduling: a Gantt chart
Software and hardware requirements: as tables
Conceptual models: a use case diagram

Chapter 4: System Design

Basic modules and what each does
Data design: schema tables (field, type, constraint) and an ER diagram
Procedural design: activity and sequence diagrams, plus key algorithms as numbered steps
Class diagram
User interface design and security considerations

Chapter 5: Implementation and Testing

Implementation approach
Coding details: one or two short, representative code snippets with explanation
Testing approach: unit, integration and user (beta) testing
Test cases: a table with test ID, description, input, expected result, actual result, status

Chapter 6: Results and Discussion

Test reports: pass rates and what failed and why
User documentation: step-by-step instructions with screenshots

Chapter 7: Conclusion

Conclusion and significance
Limitations: honest, specific constraints
Future scope: 5–8 concrete enhancements

Common mistakes examiners notice

Chapters that describe a generic system, not your project
Diagrams that contradict each other (for example, entities in the ER diagram that the class diagram lacks)
Test cases that all "pass" with no discussion
Future scope copied from another report

Write the chapters faster

The BlackBook AI Blackbook Maker drafts all seven chapters from your project details, including the Gantt, use case, ER, class, activity and sequence diagrams, in the structure above. You edit every section with Ask AI and export when it is right. Formatting rules are in the Blackbook format guide.

Frequently asked questions

How many chapters are in a final year project report?

Usually seven: Introduction, Survey of Technologies, Requirements and Analysis, System Design, Implementation and Testing, Results and Discussion, and Conclusion. Some colleges merge or rename chapters.

Which chapter has the ER diagram?

The ER diagram belongs in System Design, usually under data design, along with the class, activity and sequence diagrams.

Where do test cases go in a project report?

Test cases go in the Implementation and Testing chapter, normally as a table with test ID, description, input, expected result, actual result and status.

Written by

Vivek Singh

Founder of BlackBook

University of Mumbai graduate and software engineer. He built BlackBook so students can put their time into studies and exams, not months of formatting. More about BlackBook