What is a final year project report?
A final year project report is the comprehensive document you submit alongside your working project. It describes everything about your project — from the problem you are solving to how you built the solution, tested it, and what results you achieved. Evaluators at Indian universities typically allot 40-60% of the total project marks to the report and presentation combined.
Most universities require reports to be 50-100 pages long for major projects and 30-50 pages for mini projects. The report should be your own work — copied reports are easily detected with plagiarism tools that universities now routinely use.
Standard chapter-wise format
The following structure is accepted by nearly all Indian universities for computer science and IT projects:
Preliminary pages
These pages come before Chapter 1 and are numbered separately (i, ii, iii):
- Title page — project title, student names, enrollment numbers, guide name, university name, month and year of submission
- Certificate page — signed by your guide and head of department, confirming that the work is original
- Acknowledgment — thanking your guide, department, family, and anyone who helped
- Abstract — a 150-250 word summary of the entire project. Write this last, after completing all other chapters
- Table of contents — auto-generated from Word headings. Include page numbers.
- List of figures — all diagrams, screenshots, and charts with page numbers
- List of tables — all tables with page numbers
- List of abbreviations — technical abbreviations used (API, REST, CRUD, ML, CNN, etc.)
Chapter 1: Introduction
This chapter sets the stage for your entire report. It should be 5-8 pages and cover:
- Background — explain the domain. What is the current state of the field?
- Problem statement — what specific problem does your project solve?
- Objectives — 3-5 measurable goals of your project
- Scope and limitations — what does your project cover and not cover?
- Organization of the report — one paragraph describing what each chapter contains
Chapter 2: Literature review
Review 5-10 existing systems, research papers, or projects related to your domain. For each, describe what they do, what technology they use, and their limitations. End with a comparison table showing how your project differs from existing work. This chapter demonstrates that you understand the research landscape.
Use IEEE-format citations. Example: "Smith et al. [1] proposed a sentiment analysis system using LSTM networks that achieved 87% accuracy on the IMDB dataset."
Chapter 3: System analysis and design
This is where you describe the architecture of your system. Include:
- System requirements — hardware and software requirements (minimum RAM, OS, Python version, etc.)
- Functional requirements — what the system should do (user login, data upload, prediction, report generation)
- Non-functional requirements — performance, security, usability, scalability
- System architecture diagram — high-level block diagram showing frontend, backend, database, and external services
- Data Flow Diagrams (DFDs) — Level 0 (context diagram) and Level 1 showing data flow between processes
- ER diagram — entity-relationship diagram showing database tables and their relationships
- Use case diagram — UML diagram showing user interactions with the system
- Class diagram — for object-oriented projects, showing classes and their relationships
Chapter 4: Implementation
Describe how you built the system module by module. For each major feature:
- Explain the logic and algorithm used
- Include relevant code snippets (not the entire codebase — just key functions)
- Show screenshots of the working feature
- Describe any challenges faced and how you resolved them
This chapter is typically the longest (15-25 pages). Use clear subheadings for each module.
Chapter 5: Testing
Explain your testing strategy. Include:
- Test cases — at least 10-15 test cases in a table format (Test ID, Description, Input, Expected Output, Actual Output, Status)
- Types of testing — unit testing, integration testing, system testing, user acceptance testing
- Testing tools — pytest, JUnit, Selenium, Postman, or manual testing
- Test results — show that all test cases pass
Chapter 6: Results and discussion
Show the final output of your project. Include:
- Screenshots of every major screen and feature
- Performance metrics (accuracy, response time, throughput) if applicable
- Comparison with existing solutions
- Discussion of results — what worked well, what could be improved
Chapter 7: Conclusion and future scope
Summarize what you built and what you achieved. Then describe 3-5 ways the project could be extended in the future. Example: "Future work could include integrating real-time data from IoT sensors, adding support for multiple languages, and deploying the system on a scalable cloud infrastructure."
References
List all cited works in IEEE format. Typically 10-20 references for a major project. Include research papers, books, and official documentation.
Appendices
Include additional material like full source code listings, user manual, installation guide, or survey forms.
Formatting guidelines
Follow these formatting rules unless your university specifies otherwise:
- Font: Times New Roman, 12pt for body text, 14pt bold for headings
- Line spacing: 1.5
- Margins: 1.5 inches on the left (for binding), 1 inch on all other sides
- Page numbers: bottom center, starting from Chapter 1
- Paper size: A4
- Headings: use Word's built-in heading styles (Heading 1, Heading 2, etc.) for automatic table of contents
Download our free project report template
Our template includes all chapters with placeholder text, proper formatting, auto-generated table of contents, and example diagrams. It follows the format accepted by AKTU, VTU, Mumbai University, Anna University, and most other Indian universities. Fill in the form below to download.