Front matter
- Title page in the department format
- Bonafide certificate signed by your guide and head of department
- Declaration of originality
- Acknowledgement
- Abstract — 200 to 300 words covering problem, method, result
- Table of contents, list of figures, list of tables, list of abbreviations
Chapter 1 — Introduction (6 to 10 pages)
- Background of the problem domain
- Problem statement, stated as a problem rather than as a solution
- Objectives, three to five, each measurable
- Scope: explicitly what is included and what is not
- Organisation of the report, one line per chapter
Chapter 2 — Literature survey (8 to 15 pages)
This chapter fails when it becomes a list of paper summaries. What the panel wants is a comparison: what approaches exist, what each achieved, what each left unsolved, and where your work fits into that gap.
- Six to twelve papers or existing systems reviewed
- A comparison table across method, dataset or scale, and limitation
- An explicit statement of the gap your project addresses
- Current citations — a survey built entirely on pre-2015 work reads as stale
Chapter 3 — System analysis and design (12 to 20 pages)
- Existing system and its specific drawbacks
- Proposed system and how it addresses each drawback
- Feasibility study: technical, economic and operational
- System architecture diagram with a written walkthrough
- ER diagram, table structures and normalisation level
- UML diagrams: use case, sequence, activity and class as applicable
- Hardware and software requirements
Chapter 4 — Implementation (15 to 25 pages)
The longest chapter, and the one that most often goes wrong by becoming a code dump. Include only the code fragments worth explaining, and explain them rather than reprinting them.
- Module-wise description of what each module does and how
- Key algorithms explained in words or pseudocode
- Important code fragments with commentary, never entire files
- Screenshots of each module with captions
- Integration approach and how the modules communicate
- Deployment details if the system is hosted
Chapter 5 — Testing and results (8 to 15 pages)
- Testing strategy: unit, integration and system testing
- Test case table with expected and actual results
- For AI projects: metrics, confusion matrix and a baseline comparison
- For IoT projects: calibration data and reliability observations
- Performance measurements where relevant, such as response time or throughput
- Discussion of what the results mean, not just the numbers
Chapter 6 — Conclusion and future scope (3 to 5 pages)
- What was achieved, mapped back to the objectives in chapter one
- Honest limitations — this section builds credibility rather than costing marks
- Future enhancements, specific enough to be actionable
- A short closing paragraph on the value of the work
Back matter
- References in the format your department specifies, IEEE style in most engineering programmes
- Appendix with sample code, the dataset description, or the full test log
- Publication or certificate copies where applicable
Page count reality check
Undergraduate engineering reports typically run 60 to 90 pages, and MCA reports 70 to 120. If you are far below that, the usual culprits are a thin literature survey and an implementation chapter that describes what the system does rather than how it was built.
If you are far above it, you have probably pasted whole source files into the implementation chapter. Move them to the appendix and keep the chapter readable.