0% found this document useful (0 votes)
5 views

Project Report Format

The document outlines essential points for preparing a project report, including required components such as the approved project proposal, originality certificate, and a CD with executable files. It specifies the structure and content needed in the documentation, emphasizing the importance of project-specific details and avoiding generic information. Additionally, it provides guidelines on formatting, page numbering, and consistency in project titles and signatures.

Uploaded by

prathamy831
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views

Project Report Format

The document outlines essential points for preparing a project report, including required components such as the approved project proposal, originality certificate, and a CD with executable files. It specifies the structure and content needed in the documentation, emphasizing the importance of project-specific details and avoiding generic information. Additionally, it provides guidelines on formatting, page numbering, and consistency in project titles and signatures.

Uploaded by

prathamy831
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT

1. Project Report Formulation:


The project report should contain the following:
(i) Original copy of the Approved Project Proposal (Synopsis).
(ii) Certificate of Originality Project documentation.
(iii) A CD consisting of the executable file(s) of the complete project should be attached on the
last page of the project report. The student needs to retain the identical copy of the CD that
should be carried while appearing for the viva-voce along with the project report.

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.

 Table of Contents/Index with page numbering


 Introduction/Objectives
 System Analysis
 Identification of Need
 Preliminary Investigation
 Feasibility Study
 Project Planning
 Project Scheduling (PERT Chart and Gantt Chart both)
 Software requirement specifications (SRS)
 Software Engineering Paradigm applied

 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

 Data integrity and constraints

 Database design, Procedural Design/Object Oriented Design

 User Interface Design

 Test Cases (Unit Test Cases and System Test Cases)

 Coding

 SQL commands for (i) database creation (along with constraints), (ii) data insertion in
tables and (iii) access rights for different users.

 Complete Project Coding

 Comments and Description of Coding segments


 Standardization of the coding

 Code Efficiency

 Error handling

 Parameters calling/passing

 Validation checks

 Testing

 Testing techniques and Testing strategies used

 Testing Plan used

 Test reports for Unit Test Cases and System Test Cases

 Debugging and Code improvement

 System Security measures (Implementation of security for the project developed)

 Database/data security

 Creation of User profiles and access rights

 Cost Estimation of the Project along with Cost Estimation Model

 Reports (sample layouts should be placed)

 Future scope and further enhancement of the Project

 Bibliography

 Appendices (if any)

 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.

You might also like