Académique Documents
Professionnel Documents
Culture Documents
on
<Name of discipline>
By
<Student Name1 (Roll no.)>
<Student Name2 (Roll no.)>
<Student Name3 (Roll no.)>
<Student Name4 (Roll no.)>
Name of Guide
< Guide Name >
A Project Report
on
<Name of discipline>
By
STUDENT
<Student Name1 (Roll no.)>
<Student Name2 (Roll no.)>
<Student Name3 (Roll no.)>
<Student Name4 (Roll no.)>
Name of Guide
< Guide Name >
CERTIFICATE
Date:
REPORT
ENTITLED
<TITLE
OF
<Name of Guide>
(Asst. Professor, <Dept>)
<NAME OF COORDINATOR>
(Project Coordinator)
<NAME OF HOD>
(HOD, <Dept>)
ACKNOWLEDGEMENT
PAGE INDEX
1.
2.
:
:
:
:
:
N-1
N.
Topic
ABSTRACT
TITLE OF CHAPTER ONE
1.1
HEADING
1.2
HEADING
TITLE OF CHAPTER TWO
2.1
HEADING
2.2
HEADING
CONCLUSION
BIBLIOGRAPHY
APPENDIX A POWER POINT SLIDES
APPENDIX B USER MANUAL
APPENDIX C
Page No.
TABLE INDEX
Table
1.1
1.2
Table 1 About
Table 2 About
2.1
2.2
:
:
:
N
Table 3 About
Table 4 About
:
:
:
Table N About
Page No.
FIGURE INDEX
Figure
1.1
1.2
Figure 1 About
Figure 2 About
2.1
2.2
:
:
:
N
Figure 3 About
Figure 4 About
:
:
:
Figure N About
Page No.
REFERENCES
[1] G.K.Patnaik and M. M. Gore, Design of Compiler for Mobile
Environment and its formalization using Evolving Algebra ,
proceedings of 3rd
:
Top
Bottom
Left
Right
3. Line Spacing:
:
:
:
:
1
(1 inch=2.54cm)
1
1.5
1
1.5 lines
4. Title of Chapter
Font
: Times New Roman (Bold face)
Size
: 18 point
Alignment : Right Alignment
One thick line ( 2 point weight) after the name of chapter.
5. Headings
First Order Heading: (for example 1.
INTRODUCTION)
Font
: Times New Roman (Bold Face)
Size
: 16 point
One blank line before the heading. (12 points)
Second Order Heading: (for example 1.1. Evolution)
Font
: Times New Roman (Bold Face)
Size
: 15 point
One blank line before the heading. (12 points)
Third Order Heading: (for example 1.1.1. Image
Processing)
Font
: Times New Roman (Bold Face)
Size
: 14 point
One blank line before the heading. (12 points)
6. Text
Font
: Times New Roman
Size
: 14 point
Line Indent : First line of every paragraph should be
indented
by 1 cm. ( Except first paragraph *)
For Example:
[1]
G. K. Patnaik and M. M. Gore, Design of Compiler for Mobile
Environment and its formalization using Evolving Algebra ,
proceedings of 3rd IEEE International Conference on Mobile Data
Management, Singapore, January 2002, PP 159-160.
[2] Author Guidelines, http://.computer.org/cspress/instruct.htm
[3] William Stallings, Cryptography and Network Security: Principles
and Practices, Pearson Education, Third Edition
Note :
1. Project Report must be Black colored Hard Bounded & Golden
Embossed lettering (ONLY FOR CSE STUDENTS) &. Brown
colored Hard Bounded & Golden Embossed lettering (ONLY
FOR IT STUDENTS).
2. Two copies of the report should be submitted to the college (One
for University, One for Central Library). Copy to the respective
guide is optional. Every student of the group may have their own
additional copy. (All the project copies must include CD/DVD
attached with all the documentation, coding, PPTs, Research
Papers and each and every thing related to project)
3. Personal copy of the students must contain their own name only in
Cover page, First page, Certificate and in Acknowledgement.
4. Report must be written in your own English language.
5. Synopsis should be of Two Pages only. Abstract should be not
more than One Page.
6. Report must be submitted at the time of presentation (Three
copies).
7. Cover Page, First Page, Specimen Copy are only for students
instruction, they are not be printed in the report.
8. Matter written inside <..> must be change by the students
accordingly.
First Page
Certificate
Acknowledgement
Synopsis
Page Index
Table Index
Figure Index
Abstract
Theory
Conclusion
Bibliography
Appendices
Introduction
Need for the New system
Detailed Problem Definition
Viability (Feasibility) of the System
Presently Available Systems for the same
Future Prospects
Analysis
Detailed Requirement Analysis
Proposed System [Hint-According to Modules]
Design
Software Requirements Specification
Risk Assessment
Algorithm Design (* If using your own algorithm)
System Modeling
UML Diagrams (DFD, Flow chart, class diagram, object
diagrams as applicable)
(* In brief)
Database Design (E/R Diagram)
Coding
Hardware Specification
Programming Languages Used
Software Tools Used
Coding of at least one module.
Snapshots of each module
Testing
Formal Technical Reviews
Test Plan
Test cases and Test Results
Conclusion
8.
9.
References
CHAPTER 2