PROJECT REPORT CHAPTERS HIERARCHY

Project Report Format (Report should be maximum of 120 pages and minimum of 70 pages)

Cover Page

Title Page

Glass sheet

ii. Certificate

iii. Acknowledgement

iv. Abstract
v. Table of Contents

vi. List of figures

vii. List of tables

viii. List of abbreviations (should be alphabetic orders)

1. Introduction

            1.1 Purpose

            1.2 Scope

2. System analysis

            2.1 Existing system (should include the disadvantage of existing system)

            2.2 Proposed System

                        2.2.1 Features of proposed system

            2.3 Proposed SDLC model

            2.4 Feasibility study

                        2.4.1 Technical feasibility

                        2.4.2 Economical feasibility

                        2.4.3 Operational feasibility

                        2.4.4 Social feasibility

            2.5 Gantt Chart (Diagram with detailed description)

            2.6 Cost Estimation

3. System Requirement Specification

            3.1 Functional Requirements

            3.2 Non functional Requirements

            3.3 Hardware Requirements

            3.4 Software Requirements

            3.5 Other Requirements (If any)

4. System Design

            4.1 System Overview

            4.2 System Architecture (if any)

            4.3 Modules

                        4.3.1 Module 1: Description (name the module and give description)

                        .                       .

                        .

            4.4 Algorithms used (if any)

            4.5 UML diagrams (contains minimum 4 UML diagram)

                        4.5.1 First UML diagram name (eg: Class diagram)

                                    a) Purpose

                                    b) Diagram

                                    c) Description (should provide detailed description)

                        4.5.2 Second UML diagram name (eg: Use case  diagram)

                                    a) Purpose

                                    b) Diagram

                                    c) Description (should provide detailed description)

/* The order of UML diagrams should be Class diagram, Object diagram, Use case diagram, Sequence diagram, Collaboration diagram, Activity diagram, State transition diagram, Component diagram, Deployment diagram */

                        .

                        .

            4.6 Data Flow Diagram

                        4.6.1 Purpose

                                    level 0 diagram

                                    level 1 diagram

            4.7 Database tables (should be normalized)

            4.8 ER diagram (if any)

5. Implementation

            Provide the overview of implementation

            5.1 Language used (should include the features of language)

            5.2 Installation and deployment

            5.3 Screenshots ( Each screen shot should be supported with detailed description)

6. Testing

            Provide an overview of testing and goal of testing

            6.1 Code testing

            6.2 Unit Testing

                        6.2.1 Black box testing

                                                 Black box testing with derived test cases and output result of each                                                             test cases as a table

                       

6.2.2 White box testing

White box testing with derived test cases and output result of each                                                 test cases as a table

            6.3 Integration Testing

Describe the integration approach applied with the help of structure chart

            6.4 Validation Testing

            6.5 Output Testing

6.6 System testing

            6.7 Test reports

7. Conclusion

8. Future Scope

9. References (minimum 10)

Appendix

A: Sample Program Code (Maximum 5 Pages)

Index