Project Report Format
Project Report Format
2. The project documentation may be about 100 to 125 pages (excluding coding). The project
documentation details should not be too generic in nature. Appropriate project report documentation
should be done, like, how you have done the analysis, design, coding, use of testing
techniques/strategies, etc., in respect of your project. To be more specific, whatever the theory in
respect of these topics is available in the reference books should be avoided as far as possible. The
project documentation should be in respect of your project only. The project documentation should
include the topics given below. Each and every component shown below carries certain weightage in
the project report evaluation.
Data models (like DFD), Control Flow diagrams, Entity Relationship Model, Class
Diagrams/Use-case Diagrams/Activity Diagrams depending upon your project
requirements
System Design
Modularisation details
Coding
SQL commands for (i) database creation (along with constraints), (ii) data insertion in
tables and (iii) access rights for different users.
Code Efficiency
Error handling
Parameters calling/passing
Validation checks
Testing
Test reports for Unit Test Cases and System Test Cases
Database/data security
Bibliography
Glossary.
Should attach a copy of the CD containing the executable file(s) of the complete project.
3. The project report should normally be printed with single line spacing on A4 paper (one side only).
All the pages, tables and figures must be numbered. Tables and figures should contain titles.
4. Through out the project report, the title of the project should be the same as per the approved
synopsis. Signature of the Project Guide in the Certificate of Originality should match with the
signature in the Project Proposal also.