You are on page 1of 5

Mini Project Final Report Format

The report should be bound with gold colored cover and text should in black
ARRANGEMENT OF CONTENTS:
The sequence in which the project report material should be arranged and bound should
be as follows:
Cover Page & Title Page
Bonafide Certificate
Abstract
Acknowledgement
Table of Contents
List of Figures
List of Abbreviations
1. Introduction
2. Literature Survey
3. Hardware and Software Specifications
4. System Analysis and Design
5. Implementation
6. Testing Strategies
7. Results
8. Discussion
9. Conclusion
10. Future Enhancement
11. References
12. Appendices
The final report should include:
a) Title Page
b) Bonafide Certificate
c) Abstract
This should be a one page synopsis of the project report. It should summarize

The statement of the problem

Procedure or Method

The major results

Conclusion

d) Acknowledgement
This should not be more than a single page in length and should be brief .
e) Table of Contents

The table of contents should list all material following it as well as


any material which precedes it. The title page and Bonafide
Certificate will not find a place among the items listed in the Table
of Contents. One and a half spacing should be adopted for typing
the matter under this head.
f) List of Figures
The list should use exactly the same captions as they appear below
the figures in the text. One and a half spacing should be adopted for
typing the matter under this head.
g) List of Abbreviations
One and a half spacing should be adopted or typing the matter
under this head. Standard symbols, abbreviations etc. should be
used.
h) Introduction
This should give brief overview of the problem and the purpose for conducting the
work. A discussion on contemporary approaches, what is novel about the attempted
approach, salient results etc.
This section should be limited to a maximum of 5 pages.
i) Literature Survey
This section contains the background information to acquaint the reader with the
problem being addressed. The details of the related works should also be included in
this section.
j) Hardware and Software Specifications
This should give the hardware and software specification. This section should be
limited to a maximum of 2 pages.
k) System Analysis and Design
This section should include details on

Existing system

Requirement Analysis

Proposed System

It should also contain the details on system design

Module Division

DFDs / UML Diagrams

Pseudocode/Algorithm

l) Implementation
Discuss the process by which the problem was approached.
m) Testing Strategies
This section should include the major test cases of the work.
n) Results
Describe the results of your work. The screenshots in this section should be limited
to a maximum of 5 pages, each page containing at least 2 screenshots.
o) Discussion
A discussion that highlights reasons behind differences, if any, between target
specifications presented in the preliminary and design reports and the final
implementation (if applicable)
p) Conclusion
No new material should be presented here. The contents should be based upon the
results discussed. The section should be related directly to the purpose, criteria and
specifications of the problem. It should specify the level of success achieved.
q) Future Enhancement
This section should include comments for further work and for improving the work
completed.
r) References
This section should list significant literature sources. Cite references in the body of
the report. The references should be in IEEE format.
[1] Ajith K.J., Babita Sharma, A.K. Bhattacharjee, S.D. Dhodapkar, S. Ramesh:
Detection of Runtime Errors in MISRA C Programs: A Deductive Approach, LNCS
4680, Springer Berlin / Heidelberg, pages 491-504, September 2007.
s) Appendices
Appendices are provided to give supplementary information.

Appendices should be numbered using English alphabets,


e.g. Appendix A, Appendix B, etc.

In this section you can include the DFDs & UML Diagrams
of other modules of your project.

Structural Details
The preferred font is Times Roman. Use 12pt for normal text. Sections should be
numbered using a standard scheme (e.g 1, then 1.1, then 1.1.1 for a three-level structure).
The report should be printed one-sided. Use one inch margins all around. Spacing for
normal text should be 1.5 spaced. Use fully justified alignment.
Main Headings (Chapter Names)

Main headings numbered such as 1., 2., etc. must obey the following rules:

They must begin in a new page.

Omit period at the end of the heading.

Main headings must be typed in bold face and must be in capital letters and in 16
points.

The number of the headings will be followed by a period and two spaces.

They must precede the following text material or second heading by three 1.5
spacing.

Second Headings
Second headings numbered such or 2.1., 2.2., etc. must obey the following rules:

They must be typed in 14 points, bold face and title case letters; i.e., the first letter
of each word must be a capital letter.

Omit period at the end of heading.

The number designation of the second heading will be followed with a period and
two spaces.

Second headings must be two 1.5 spacing below preceding text and two 1.5
spacing above of succeeding text.

First Subheadings
First subheadings numbered such as 2.1.1., 2.1.2., etc. must obey the following rules:

They must be typed on separate lines beginning at the left margin line of the text,
but need not begin a new page.

They must be typed in 12 points, bold face and with title case letters.

The number designation of the heading will be followed by a period and two
spaces.

Omit period at the end of the heading.

First subheadings must be separated from the preceding and succeeding text by
two 1.5 spacing.

Second Subheadings
Second subheadings numbered such as 2.1.1.1., 2.1.1.2., etc. must obey the following
rules; however, second subheading, should be avoided if possible.

They must be typed in 12 points, bold and italic face and with title case letters.

The number designation shall be followed by a period and two spaces.

Second subheadings must be separated from the preceding and succeeding text by
two 1.5 spacing.

You might also like