MEERUT INSTITUTE OF TECHNOLOGY, MEERUT

Guidelines for the preparation of project report

Follow the guidelines given below for preparing your Project Report.

Order of the contents

1. Front page
2. Certificate
3. Acknowledgement
4. Abstract
5. Table of Contents
6. List of figures, abbreviations, symbols & tables
7. Main text Chapter Wise
8. Appendices
9. Bibliography or list of references

Paper: Standard paper size A4 (297x210mm) should be used for the print outs.

Page number: Page should be numbered consecutively and clearly. No page number
should be indicated on title page. From title page to just before the main text, roman
numbers in lower case should be used. From main text to end of report, Indian numerals
should be used. All typing should be on right hand pages only. Page number should be
typed in bottom with center alignment.

Margin: Top 1.0”, Bottom 1.0” Left 1.5” Right 1.0”

Line spacing: 1.5
Paragraph spacing: 2.0
Text:
Font: Times new roman, black, size 12 for text, larger font size 16 for major headings &
14 for subheadings.
Heading should be bold. Text should be justified. Before producing the final copies of a
project report the candidate should ensure that all the spelling, grammar, punctuation and
bibliography is complete and exact.
Chapter headings must begin with new page and must be typed in upper case letters.

Snapshots: 15-20 snapshots should be there in report...Snapshots must be labeled as

Figure <chapter no>.<snapshot no.>: Title of the snapshot.
The label should appear below the snapshot.

DVD-ROM: All reports should include soft copy on DVD-ROM accompanied with the
following:
1) Software used in project (For eg. Apache Tomcat/JDK etc).
2) Code of complete project.
3) Complete documentation.
4) Scanned copy of certificate.
5) Running Software
6) There must be another file named "READ.ME".Which must contain the name of each
project group member along with the Supervisor's name and abstract of the project.

Abstract:
The abstract is to be in fully-justified text.
Use the word “Abstract” as the title, in 16-point Times, bold type, center aligned, initially
capitalized.
The abstract is to be in 12-point.
It should succinctly summarize the reason for the work, the main findings, and the
conclusions of the study.
The abstract should be no longer than 250 words.
Do not include art work, tables, elaborate equations or references to other parts of the paper
or to the reference listing at the end.
Figures: All figure and diagrams must be clearly explained. Name of diagram must be in
Times new roman, black, size 16 for text. The text other than name should be Times new
roman, black, size 12. Abbreviations used in the figures must be explained in the list of
Abbreviations page. Figure label will appear below the figure as:
Figure <chapter no.>.<figure no.>: Title of the figure

Tables: All tables should be properly numbered and labeled as below.

Table <chapter no.>.<Table no.>: Title of the table
Label of the table will appear above the table.

Reference: All the references should be arranged alphabetically or serially as the case
may be for quoting in text.
Books
[1] Roger.S.Pressman, “Software engineering”, Tata McGraw Hill Publications, New
Delhi, Edition 2003.
Websites
[1] www.mitmeerut.ac.in, <date of retrieval>

Print-outs: Title page and snapshots should be colored. Remaining pages should be black
and white hand-outs.

Project report preparation & binding;

 Before taking the final printout, the approval of the concerned guide(s) and project
report evaluator (if assigned) is mandatory and suggested corrections, if any, must
be incorporated.
 The total number of reports to be prepared is : 1) One copy for the department , 2)
One copy for the university 3) Individual copy for each candidate in group

 Once the print outs are taken, it should be duly examined by guide before final
binding.
 After the final approval of the guide, the report should be book bound.
 The front cover color coding is navy blue with golden engraved letters.
 <TITLE OF THE PROJECT>
A project report submitted in partial fulfillment of the requirements for the

Award of degree of

Bachelor of Technology

in

Computer Science and Engineering

By

<Name of the Candidate> (<University Roll No.>)

<Name of the Candidate> (<University Roll No.>)
<Name of the Candidate> (<University Roll No.>)
<Name of the Candidate> (<University Roll No.>)

Under the supervision of

<Name of the Supervisor>

<Designation>

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

MEERUT INSTITUTE OF TECHNOLOGY, MEERUT

Affiliated to

DR. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY,

LUCKNOW
April, 2019
 Certificate

I hereby declare that the work which is being presented in the project report entitled,
“<Project Title>”, in partial fulfillment of the requirements for the award of degree of
Bachelor of Technology submitted in Computer Science and Engineering of Meerut
Institute of Technology, Meerut, is an authentic record of my own work carried out under
the supervision of <Name of supervisor> and refers other researcher’s works which are
duly listed in the reference section.

The matter presented in this Project has not been submitted for the award of any other
degree of this or any other university.

(Name of Candidate)

This is to certify that the above statement made by the candidate is correct and true to the
best of my knowledge.

(Name of Supervisor)
<Designation>
Meerut Institute of Technology,
MEERUT.

Countersigned by

<Name of Project Coordinator> <Name of HOD>

Assistant Professor Assistant Professor
Project Coordinator HOD, Department of CSE
Department of CSE Meerut Institute of Technology,
Meerut Institute of Technology, Meerut
Meerut
 TABLE OF CONTENTS

CERTIFICATE i
ACKNOWLEDGEMENT ii
ABSTRACT iii
LIST OF TABLES iv
LIST OF FIGURES v
LIST OF SYMBOLS vi
LIST OF ABBREVIATIONS vii
CHAPTER 1 INTRODUCTION (Background of the problem, Statement of the
problem etc.)
< Page no.>
1.1.
1.2
CHAPTER 2 SOFTWARE REQUIREMENT SPECIFICATION(User Interface,
Hardware specification, Software Specification) < Page no.>
2.1
2.2
2.3
CHAPTER 3 FEASIBILITY STUDY (Technical, Operational etc) < Page no.>
3.1
3.2
3.2.1.
CHAPTER 4 SYSTEM DESIGN
(Use Case Diagram, ER, DFD, Activity Diagram) < Page no.>
CHAPTER 5 TESTING (About testing, test cases for each module) < Page no.>
5.1
CHAPTER 6 SNAPSHOTS < Page no.>
CHAPTER 7 CONCLUSION < Page no.>
(Limitations of the project, Future scope of the project)

APPENDIX (User manual, Data Dictionary, Table Structure, etc) < Page no.>
REFERENCES < Page no.>
 (Example of Acknowledgement)

ACKNOWLEDGEMENT

It gives us a great sense of pleasure to present the report of the B. Tech Project undertaken
during B. Tech. Final Year. We owe special debt of gratitude to Mr./Ms. <Name of
Supervisor>, and Mr./Ms. <Name of Project Coordinator> Department of Computer
Science & Engineering, Meerut Institute of Technology, Meerut for his constant support
and guidance throughout the course of our work. Their sincerity, thoroughness and
perseverance have been a constant source of inspiration for us. It is only their cognizant
efforts that our endeavors have seen light of the day.

We also take the opportunity to acknowledge the contribution of Mr.< Name of HOD>,
Head, Department of Computer Science & Engineering, Meerut Institute of Technology,
Meerut for his full support and assistance during the development of the project.
We also do not like to miss the opportunity to acknowledge the contribution of all project
co-coordinators and faculty members of the department for their kind assistance and
cooperation during the development of our project. Last but not the least, we acknowledge
our friends for their contribution in the completion of the project.

Signature: Signature:
Name: Name:
Roll No.: Roll No.:
Date: Date:

Signature: Signature:
Name: Name:
Roll No.: Roll No.:
Date: Date:
 (Example of Abstract)

ABSTRACT

An Abstract is required for every project report; it should succinctly summarize the reason
for the work, the main findings, and the conclusions of the study. The abstract should be no
longer than 250 words. Do not include artwork, tables, elaborate equations or references to
other parts of the paper or to the reference listing at the end. The reason is that the Abstract
should be understandable in itself to be suitable for storage in textual information retrieval
systems.