The document provides guidelines for preparing a project report, including required sections like introduction, analysis, design, coding, testing, and security. It specifies the report should be 100-125 pages excluding coding, printed single spaced on A4 paper with numbered pages, tables, and figures. One copy of the report and CD containing the project files must be submitted and one photocopy retained for the viva.
The document provides guidelines for preparing a project report, including required sections like introduction, analysis, design, coding, testing, and security. It specifies the report should be 100-125 pages excluding coding, printed single spaced on A4 paper with numbered pages, tables, and figures. One copy of the report and CD containing the project files must be submitted and one photocopy retained for the viva.
The document provides guidelines for preparing a project report, including required sections like introduction, analysis, design, coding, testing, and security. It specifies the report should be 100-125 pages excluding coding, printed single spaced on A4 paper with numbered pages, tables, and figures. One copy of the report and CD containing the project files must be submitted and one photocopy retained for the viva.
The document provides guidelines for preparing a project report, including required sections like introduction, analysis, design, coding, testing, and security. It specifies the report should be 100-125 pages excluding coding, printed single spaced on A4 paper with numbered pages, tables, and figures. One copy of the report and CD containing the project files must be submitted and one photocopy retained for the viva.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
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) Certificate of Originality (ii) Acknowledgement (iii) Contribution of the student in the project (iv) Project documentation. (v) A CD consisting of the executable file(s) of the complete project should be attached on the last page of the project report. In no case, it should be sent separately. 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, State Diagrams/Sequence diagrams, Entity Relationship Model, Class Diagrams/CRC Models/Collaboration 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 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) & documentation 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. Only one copy of the original project report in the bound form along with the CD (containing the executable file(s) & documentation of the project should be enclosed in the last page) is to be submitted in the department. One photocopy of the same Project Report and the CD containing the executable file(s) & documentation must be retained by the student, which should be produced before the examiner at the time of viva-voce.
5. Student should be involved in each and every phase of Project Development. If it is found that student is not involved in any phase for example coding phase, it may lead to the rejection/disqualifying of the project at any stage.
