Minor Project Format

SEQUENCE IN PROJECT FILE
1. COVER PAGE
2. FRONT PAGE
3. CERTIFICATE
4. ACKNOWLEDGEMENT
5. TABLE OF CONTENTS
TOPIC
A Minor Project Report
Submitted to
Department of
INFORMATION TECHNOLOGY
BANSAL INSTITUTE OF SCIENCE AND TECHNOLOGY
BHOPAL (M. P.)
2 0 1 8 -2 0 1 9
Submitted By
NAME (Enrollment Number)

Under The Guidance of
Prof. Name of Guide

(Designation)
BANSAL INSTITUTE OF SCIENCE AND TECHNOLOGY
BHOPAL (M. P.)
(Affiliated to Rajiv Ghandhi Prodyogiki Vishwavidhyalaya, Bhopal)
(Session 2018-2019)
Department of Computer Science & Engineering
CERTIFICATE
This is to certify that …………………..…………..……students of VI

semester in Bansal Institute of Science and Technology have completed their
Minor Project on “PROJECT NAME”, as per the syllabus and has submitted
a satisfactory report on this project as a partial fulfillment towards the award
of degree of Bachelor of Engineering in Information Technology under
Ragiv Gandhi Proudyogiki Vishwavidyalaya, Bhopal.
Prof. Kiran Agrawal Prof. Name of Guide

H.O.D., IT Dept. Project Guide
TABLE OF CONTENTS
CHAPTER TOPIC PAGE NO.
Chapter-1 Introduction
1.1 Overview and issues involved

1.2 Problem definition
1.3 Proposed solution(It must also include the brief
working of your project that would be developed
in 8 -10 lines also justify that how it is better than existing
solutions of the market.)
Chapter-2 Literature Survey
2.1 Methodology (Description of Conceptual Requirements for

understanding your project for example What is a Web
service? Requirements for a Web Service etc.)
2.2 Technologies and Tools used with a very short description

of each
2.3 Other requirements(if any)
Chapter-3 Analysis
3.1 Software Requirements
3.2 Hardware Requirements
3.3 Use Case Model
3.4 Use Case Description
3.5 DFD
Use case description of each use case in the use case model must
be there and it must be properly numbered and according to
the format. In a particular use case description don’t simply
write the Preconditions, Post conditions and Special
Requirements as none before analyzing the particular use
case in detail.
Chapter-4 Design
4.1 Technology Selection (Clearly specifying the reasons behind choosing a particular
technology used in your project)
4.2 Class Diagram (With relationships, name of the attributes and their return types and
methods of each class)
4.3 Database Design (Complete E-R diagram with cardinalities and relationships, It must also
include the snapshot of each table structure with all its fields and a short description of the
content of the table under it .)
Chapter - 5 Implementation and Testing
5.1 Subsystem and Their Dependencies (A diagram showing subsystem elements and their
Dependencies)
5.2 Class diagram explanation in detail. (What is the purpose of class. Then explain the working of
methods of the class with the parameter it takes.)
5.3 It must also include the short description of testing techniques used by you and major possible
screen snapshots indicating user input and application output.
Each snapshot must include along with it the following things:-
(a) A short description about the snapshot.
(b) All possible test cases used to test the snapshot ie for correct and incorrect input
Test 01 : Test case for successful Login
Login ID :arpit_agrw
Password : ABCD0
System Output: Successful Login
Test 02 : Test case for incorrect password
Login ID: arpit_agrw
Password: ABD
System Output: Incorrect Password
Test 03 : Test case for incorrect ID
Login ID: arpit_aw
Password: ABD
System Output: Incorrect ID
Chapter – 6 Conclusion
It should include your learning and achievements from the project, limitations of the project,
future expansions.
APPENDIX-A REFERENCE
First write name of all books then research papers(if any) then websites.
For books use this format:-
Authors, Book Name(Edition No), Publisher Name , Year of publication
For research papers use this format:-
Authors Name, Title of the paper, Journal or Conference Name, Vol No, Issue No , Month
&Year
APPENDIX-B GLOSSARY
APPENDIX-C SCREEN SHOTS
APPENDIX-D CLASSES AND FUNCTIONS USED IN CODING
APPENDIX-E USER MANNUAL

Department of Information Technology
Instructions for VI B.E students doing project work

Following instructions are to be strictly followed while preparing project thesis failing which the
thesis is likely to be rejected.
Do’s: -
Number of copies of thesis = Number of students in the group + 2
Don’t forget to take the sign of External Examiner, Project Guide, Internal Examiner, sign or
seal of Director in all copies.
Project Guide signs at two places in every thesis.
1. [FONT TYPE: Times New Roman]
Main heading size=14, sub heading size=13, All text size=12
Alignment should be justified for text.
Line Spacing - 1.5 between running text.
2 between two paragraphs.
2 between title and text.
In all pages leave left margin more then right margin otherwise there will be
problem in binding.
2. Page number should be there on bottom of each page centrally aligned.
The first page of the chapter should include Chapter number and Chapter Name centrally
aligned. A Chapter should start with new page.Utilize the full page space with text or
figures i.e. don’t leave half or more then half page empty in a chapter.
3. The User manual section should be included in the appendix.
4. All figures and tables should be named and numbered.
5. Spacing should be uniform between paragraphs throughout the thesis.Paragraphs

should be justified.Utlilize each page fully.
6. Index should be prepared with appropriate numbering.
7. One copy of CD should be prepared one for guide :-( Take more then one CD if the
material does not come in one CD).
The CD should contain the following:-

a) The soft copy of project report.
b) The software’s needed to run the project.
c) The project source code.
Write the Names of group members, Roll Numbers, Project Title, Name of the guide on
the CD.
8. Name of the guide and their post can be seen from their name plate outside the cabin.
Write it correctly in your thesis.
Don’ts:-
1. Don’t assign a chapter no. to bibliography and appendix.
2. Don’t write any abbreviations anywhere write the full form.
3. No page border and shading on any page of thesis.
4. Don’t put section / subsection as last line of the page.

Minor Project Format

Uploaded by

Copyright:

Available Formats

Minor Project Format

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Minor Project Format

Uploaded by

Copyright:

Available Formats

SEQUENCE IN PROJECT FILE

NAME (Enrollment Number)

Under The Guidance of

Prof. Name of Guide

(Affiliated to Rajiv Ghandhi Prodyogiki Vishwavidhyalaya, Bhopal)

Department of Computer Science & Engineering

This is to certify that …………………..…………..……students of VI

Prof. Kiran Agrawal Prof. Name of Guide

CHAPTER TOPIC PAGE NO.

1.1 Overview and issues involved

Chapter-2 Literature Survey

2.1 Methodology (Description of Conceptual Requirements for

2.2 Technologies and Tools used with a very short description

2.3 Other requirements(if any)

3.1 Software Requirements

3.2 Hardware Requirements

3.3 Use Case Model

3.4 Use Case Description

Chapter - 5 Implementation and Testing

Each snapshot must include along with it the following things:-

(a) A short description about the snapshot.

Test 01 : Test case for successful Login

System Output: Successful Login

Test 02 : Test case for incorrect password

Login ID: arpit_agrw

System Output: Incorrect Password

Test 03 : Test case for incorrect ID

Login ID: arpit_aw

For books use this format:-

Authors, Book Name(Edition No), Publisher Name , Year of publication

For research papers use this format:-

APPENDIX-C SCREEN SHOTS

APPENDIX-D CLASSES AND FUNCTIONS USED IN CODING

APPENDIX-E USER MANNUAL

Instructions for VI B.E students doing project work

Number of copies of thesis = Number of students in the group + 2

Project Guide signs at two places in every thesis.

1. [FONT TYPE: Times New Roman]

Main heading size=14, sub heading size=13, All text size=12

Alignment should be justified for text.

Line Spacing - 1.5 between running text.

2 between two paragraphs.

2 between title and text.

2. Page number should be there on bottom of each page centrally aligned.

3. The User manual section should be included in the appendix.

4. All figures and tables should be named and numbered.

5. Spacing should be uniform between paragraphs throughout the thesis.Paragraphs

6. Index should be prepared with appropriate numbering.

The CD should contain the following:-

b) The software’s needed to run the project.

c) The project source code.

1. Don’t assign a chapter no. to bibliography and appendix.

2. Don’t write any abbreviations anywhere write the full form.

3. No page border and shading on any page of thesis.

4. Don’t put section / subsection as last line of the page.

You might also like