Major Project Guidelines

Bachelor of Technology in Computer

Science Engineering (B.Tech CSE)

Computer Science Engineering

Department
HMR Institute of Technology and Management
affiliated to Guru Gobind Singh Indraprastha University

2020-2025
This document gives a set of guidelines on the format of the major project report. Its
purpose is to help students prepare and turn in a professional document. These guidelines
include complete descriptions of the organization, general considerations and the submission
of the report.
1. Introduction

It is recommended that students meet their guide regularly during the course of the
project, and maintain a record of discussions with guide, and of literature survey
details, derivations etc. Such a system will allow easy and quick access to the details and
chronology of work. The final responsibility for producing an error-free report lies with
student’s personal interest, and not their guide!
It is recommended for the students to read the guidelines carefully and make it sure that
the project report should strictly conforms to the specifications and looks like a
professional document. “Keep it simple”. In general keep in mind that the maximum
“Simplicity is the mother of beauty”.
2. Organization

The project report must be organized as follows. Seek clarification where necessary.
2.1. Top cover

Title of the project, name(s) of all student(s) in the team, HMRITM LOGO, Department
name, and year of graduation. The Major Project report is to be hard bound, cloth
covered in the color maroon. See Exhibit 1.
2.2. Title page

Black & white only on regular paper. See Exhibit 2.

2.3. Certificate

Black & white only from their respective Department. This is page number (i), the
beginning of the small case Roman numeral page numbers. The certificate will be signed
by the Faculty Supervisor(s) before the viva-voce after verifying the format and by the
chairperson of the Department after review with the Supervisor (s) at a later date.
See Exhibit 3.
2.4. Declaration

This is page (ii). The report declares various aspects related to the creation and submission
of the document. This page must be signed by all the members of the Project group .See
Exhibit 4.
2.5. Acknowledgements

This is page (ii). Thank your Supervisor(s) and anyone else who has been helpful in the
Project. Keep this brief and avoid syrupy language like “We want to thank our beloved
…”. See Exhibit 5.
2.6. Abstract and Keywords

This is page (iii). See Exhibit 6. The abstract (about 150 words) should contain the
context/relevance of the problem at hand, a description of what was done and a gist
of the significant observations/results. The keywords (maximum 6) are a hint at what is
contained in the report.
2.7. Contents

The table of Contents should be titled just Contents (not Table of Contents). Starts on
page (iv). Include above items, titles of all chapters, bibliography, appendices,
drawings, program listings and CD ROMs. The table of contents gives a bird’s eye view.
Try to fit it into one or two pages. See Exhibit 7.
2.8. List of Figures & List of Tables

On separate pages. Each list should give, in tabular form, the figure or table number,
its title/caption and its page number.
2.9. Nomenclature and Abbreviations

All symbols that appear in the report should be listed alphabetically. First give all
Roman symbols, then Greek symbols.
Subscripts and superscripts should be listed separately if these are not an intrinsic part
of the variable name. Example: for a symbol such as Vai where i refers to a running
index (identifying, for instance, a particular location or time), enter Va as a symbol
(treating a as an intrinsic part of the symbol) and enter i in the list of subscripts. Also
 kpx should follow kp.
Note the ordering sequence:
1) Upper case symbols followed by lower case ones.
2) Unscripted variables preceding superscripted and subscripted ones.
3) Superscripted variables followed by subscripted ones.
2.10. The Chapters

Each chapter should begin with an Introduction and end with a Conclusion (a summing
up) and, where applicable, a lead-in to the next chapter. The page on which chapter 1
starts is page 1.
One chapter should follow immediately after another. Do not use an intervening blank
or title page between chapters.
The chapter title is the first-order heading. A chapter may be divided into sections each
of which has a section title (second-order heading). For example, in Chapter 3, the
sections will be numbered 3.1, 3.2, etc. If at all possible do not further subdivide a section.
Use subsections (third-order headings) only if unavoidable. For instance, in section 3.2,
the subsections will be numbered 3.2.1, 3.2.2, etc. Do not further subdivide beyond this
point. For example, subsection 3.2.2 may not be further divided into sub-subsections
3.2.2.1, 3.2.2.2 etc.
See Exhibits 7-10 for examples of chapter organization.

2.11. Appendices

Number the Appendices A, B, etc. Figures, tables and equations in an appendix are
numbered as in the case of a chapter with the appendix letter taking the place of the
chapter number. Examples: Figure A.2, Table B.3, Equation C.1. See Exhibit 12.

3. General considerations

3.1. Number of pages, font, spacing, color

Keep the total number of pages (of the chapters) between 70 and 100, not exceeding
100 in any case. This does not include the page count of the appendices. For text please
note:
 ✓ Margins All text, drawings, tables, etc., must be positioned on an A4 sheet
with 1 in. margin on the top, bottom and right side and 1½ in. margin on the
left side.
✓ Pages should be numbered at bottom center (including pages that contain
only figures or tables).
✓ Font style and size: Times New Roman, 12 pt.
✓ For font size of chapter, section and subsection headings see Exhibit 7.
✓ Line Spacing: 1.5
✓ Typing: Back to back
✓ Color: Black on white
3.2. Figures and Tables

Each sketch, drawing, graph and photograph should have a figure number and title
below the figure etc. Numbering should be sequential, chapter wise. For instance,
if there are 24 figures chapter 3 spread over all of its sections the figure numbers run
from Figure 3.1 through Figure 3.24. In figures experimental data should typically be
represented by centered symbols, and theoretical data by continuous curves.
Each table should have a table number and caption above the table. Numbering
should be sequential, chapter wise, as in the case of Figure numbers. For instance, if
there are 18 tables in chapter 3 the table numbers run from Table 3.1 through Table
3.18.
Make sure that figures and tables are complete in other respects such as
legends, references (if any) and coordinate labels with units. Each figure and table
must be explicitly referred to in the text and located where its first reference
occurs, preferably after the reference.
3.3. Drawings

✓ All engineering drawings must conform to relevant Standards and should

include a title block.
✓ If drawings are large they should be included at the back of the report in a
separate pocket.
 3.4. Equations

The numbering of equations should be sequential, chapter wise. Numbered

equations must be explicitly referred to in the text.
3.5. Readability

In general it will help to have someone else read your report and critique it. Make a
checklist of their questions and comments and resolve each one.
✓ The report must be complete, error free and referable. All references, figures,
tables, equations, etc. which are referenced in the text should be locatable in
the report with the specified number or reference. Conversely, all references,
figures, tables, equations, etc. must be cross-referenced in the text.
✓ Use of spelling and grammar software is strongly recommended. “Spell-check”
cannot identify correctly spelt words in the wrong context. For example, typing
“he” in place of “the” may alter the meaning of the sentence but the spell-
check will not indicate this.
✓ Except for acronyms do not use ALL CAPITALS.
✓ Do not use underlining.
✓ Use italics for emphasis or if the phrase is non-English.
3.6. Program listings

All computer programs developed should be presented in the report in the

following manner:
✓ Source code listing with complete coding.
✓ A CD ROM with program source code, executable files, and data files etc.
✓ User’s manual giving details of how to use the programs [including flow charts]
and the system requirements to be bound with the Project Report.

4. Submitting the Report

For the purpose of the viva voce exam, plan on one hard copy each for the students
and Faculty Guide(s). All hard copies must be identical from cover to cover. Students
should be prepared to exchange, with the Supervisor, drafts in both hard- and electronic
copy form before they defend their project. Students should follow these steps:
✓ Submit the draft according to schedule.
✓ Make corrections, revisions and extensions as suggested by the University
Examination committee before turning in Department’s final copy.
 Exhibit 1: Top Cover Sample

MAJOR PROJECT
ON
“IN-VEHICLE INFORMATION SYSTEM TO SUPPORT
DRIVERS’ SITUATION AWARENESS” (18, TNR)

Submitted in Partial Fulfillment of the Requirements

for the Degree of (14)
Bachelor of Technology
In
Computer Science Engineering (16)

GUIDE: SUBMITTED BY:

Mr. /Ms. ZZZZ XXXXXXXX (00100000000)
Asst. Professor YYYYYYYY (01000000000)
Dept. Of CSE

HMR INSTITUTE OF TECHNOLOGY & MANAGEMENT (16, Bold)

HAMIDPUR, DELHI 110036 (16, Bold)

Affiliated to
GURU GOBIND SINGH INDRAPRASTHA UNIVERSITY
SECTOR – 16C DWARKA, DELHI – 110075, INDIA (16, Bold)
2020-2024(16, Bold)
 Exhibit 3: Certificate Sample

CERTIFICATE

This is to certify that this project report entitled ‘In-vehicle Information System to Support
Drivers’ Situation Awareness by Prince Gupta (Roll No. 999) and Kartike Malhotra (Roll No.
100), submitted in partial fulfillment of the requirements for the degree of Bachelor of
Technology in Computer Science Engineering of the Guru Gobind Singh Indraprastha
University, Delhi, during the academic year 2020-24, is a bonafide record of work carried
out under our guidance and supervision.
The results embodied in this report have not been submitted to any other University or Institution
for the award of any degree or diploma.

(Supervisor)

The B.Tech Project viva-voce examination of Mr./Ms. _______S1.,S2. ,S3….______

Has been held on ____/____/___________

(CSE Co-ordinator) (Supervisor) (External -Examiner)

Exhibit 4: Declaration Sample

DECLARATION

We, students of B. Tech hereby declare that the minor project titled “Credit Score
Prediction” which is submitted to Department of Computer Science and
Engineering, HMR Institute Of Technology And Management, Hamidpur Delhi,
affiliated to Guru Gobind Singh Indraprastha University, Dwarka(New Delhi)in
partial fulfillment of requirement for the award of the degree of Bachelor Of
Technology in Computer Science and Engineering, Has not been previously the
basis for award of any degree, diploma or other similar title or recognition. The list
of the members involved in the project is listed below:

S. No. Student Name Enrollment Number Student Signature

1. Krishna Balaji 01513307221

2. Aashima Gupta 00313302720

This is to certify that the above statement made by the candidate(s) is correct to be
best of my knowledge.

Signature Signature of Supervisor

Mr. Gyanender Kumar Mr. /Ms. ………
Dept. Co-ordinator Assistant Professor
Computer Science & Engineering
HMRITM, Hamidpur, New Delhi

New Delhi

Date:
Exhibit 5: Acknowledgment Sample

ACKNOWLEDGEMENT

The success and outcome of this project required a lot of guidance and assistance from many
people and we are extremely privileged to have got this all along the completion of our project.
It is with profound gratitude that we express our deep indebtedness to our mentor, Ms. Shristy
Goswami for their guidance and constant supervision as well as for providing necessary
information regarding the project in addition to offering their consistent support in completing
the project.
In addition to the aforementioned, we would also like to take this opportunity to acknowledge
the guidance from Mr. Gyanender Kumar (Dept. Co-ordinator, Computer Science and
Engineering) for their kind cooperation and encouragement which helped us in the successful
completion of this project.

Student Name
(Roll No)
 Exhibit 6: Abstract (Full Page)

Abstract

Abstract comprises of Brief introduction of the project followed by extract of methodology and
outcomes. The abstract should be brief, not less than 250 words and not more than 500 words.
Abstract should include a concise description of the research, problem definition, methodology,
results, and conclusions of the project. The abstract should be written using a single spacing.

Keywords: In-vehicle information system, situation awareness, augmented feedback

Exhibit 7: Chapter Organization

Chapter Organization

CHAPTER I: INTRODUCTION (14, TNR)

CHAPTER II: LITERATURE REVIEWL / THEORTICAL CONCEPT
CHAPTER III: PROBLEM FORMULATION & OBJECTIVES
Chapter IV: RESEARCH METHODOLOGY
Chapter V: RESULT ANALYSIS and DISCUSSION
Chapter VI: CONCLUTION & FUTURE SCOPE
Exhibit 8: Contents

CONTENTS (18, TNR)

Abstract (14,TNR) i
List of Tables ii
List of Figures iii

CHAPTER I: INTRODUCTION (14, TNR)

1.1 Introduction (12, TNR)

1.2 Aims and Objectives

1.3 Project Scope
1.4 Significance of Proposed Work
1.5 Report Structure
1.6 Chapter Summary
CHAPTER II: LITERATURE REVIEWL / THEORTICAL CONCEPT
2.1 Introduction
2.2 Background Problems
2.3 Problem Analysis on Existing System
2.4 Benefit Software Proposed
2.5 Technologies Used
2.6 Chapter Summary
CHAPTER III: RESEARCH METHODOLOGY / METHDOLOGY
3.1 Introduction
3.2 Methodology
3.3 Justification of Methodology
3.3.1 Methodology Prototype
3.3.1.2 Project Planning Phase
3.3.1.3 Analysis of Project Requirement Phase
3.3.1.4 Prototype Design Phase
3.3.1.4 Coding and Prototype Development Phase
3.3.1.5 Testing Phase
3.3.1.6 Maintenance Phase
3.4 Chapter Summary
Chapter IV: SYSTEM ANALYSIS AND DESIGN/ RESULT ANALYSIS
and DISCUSSION
4.1 Introduction
4.2 Software Requirements
4.2.1 Functional Requirements
4.2.2 Non-Functional Requirements
4.2.3 Interface Requirement
4.3 Use Case Diagram
4.3.1 Actor Description
4.3.2 Use Case Description
4.4 Analysis Phase
4.4.1 Sequence Diagram
4.4.2 Activity Diagram
4.5 Architecture Design Phase
4.5.1 System Architecture and Design
4.5.2 Database Design
4.6 Chapter Summary

Chapter V: SYSTEM IMPLEMENTATION

5.1 Introduction
5.2 System Implementation
5.3 Development Environment
5.4 Overall System Development
5.4.1 User Interface Development
5.4.2 Database Connection
5.5 Results
5.6 Snapshots
5.6 Chapter Summary
Chapter VI: CONCLUTION & FUTURE SCOPE
7.1 Introduction
7.2 Weakness of Developed System
7.3 Scope of Future Enhancement
7.4 Chapter Summary
REFERENCES
APPENDICES
Appendix 1: A
Appendix 2: B

Note:-

The contents of a major project report may vary from project to project.
 Exhibit 9: Arrangement of Chapter-
I
Chapter I is the Introduction. Arrange the first page as follows.

CHAPTER-I (16 bold)

INTRODUCTION (16 bold, caps)

Leave 1½” space from the top edge and 2 or 3 blank lines after the chapter title. Number
this page as page 1. The chapter may be organized as below.
1. Introduction
The size of the heading is 14-point boldface, initially capitalized, flush left, with one blank
line before, and one after. The remaining text (as in this paragraph) is 12-point, single- spaced.
Do not use double-spacing.
All paragraphs should be indented as is this one. Be sure your text is fully justified—that is,
flush left and flush right. Please do not place any additional blank lines between paragraphs.
This is an introductory section and should include a brief about the scope of work.
1.2Aims and Objectives
Define the aims and objectives of the project.
1.3 Methodology
Technical approach to the problem.
1.3.1 Sub-methodology. This is a third order heading (discouraged), size 12-point, boldface,
initially capitalized, flush left, preceded by one blank line, followed by a period and your text
on the same line.
1.4 Significance of Proposed Work
Importance and application areas.
1.5 Report Structure
Chapter wise.
1.6 Chapter Summary
A brief about chapter 1.
Exhibit 10: Arrangement of Chapters II through the last one

Chapter-II
LITERATURE REVIEW

Review literature related to the topic of work (if possible, mention all the work done earlier at
HMRITM besides other references). Present the problem, methodology used, and general
outline of the solution.

Chapter-III
PROBLEM FORMULATION & OBJECTIVES

Problem formulation and setting objectives are crucial steps in any project or initiative.

Chapter IV
RESEARCH METHODOLOGY
The students’ contribution. Work done covering analytical modeling, employment of software
package[s] and other computational algorithms, hardware/equipment design, simulation,
experimental verification, hardware/equipment fabrication and any other aspect of the work
you decide to mention should be given in this and subsequent chapters.
• Give detailed algorithms and flow charts, programs, code, detailed comments, etc.

Chapter V
RESULT ANALYSIS and DISCUSSION
The students’ contribution,

Chapter VI
CONCLUTION & FUTURE SCOPE
The Discuss results, applications future scope and conclusions/concluding remarks.
continued.
 Exhibit 11: References

References (16 bold, caps)

Citations are numbered consecutively inside brackets. In writing the references, follow American
Psychological Association (APA) style. The references below show examples of how to include a
book with 3 authors [1], a project report [2], a book with one author and cited 3 times [3-5], a book
with 2 authors [6], an online book [7], an article in a journal [8], an article from an online
newspaper [9], work with no author [10], an article in Wikipedia [11], a personal interview [12],
a website [13], and a video found online [14].
[1] Alred, G.J., Brusaw, C.T. & Oliu, W.E. Handbook of Technical Writing.
Bedford/St. Martin's, 2006.
[2] Al-Naim M. & Al-Mudara N. Electronic Court. King Faisal University College
of Computer Sciences and Information Technology, 2012.
[3-5] Bond, J. K. (2012). Advanced Programming in Java. (2nd ed.). New York:
ABC Publishing Company.
[6] Bond, J. K. & Lang, A. (2012). Action Script 3. (2nd ed.). New York: ABC
Publishing Company.
[7] Al-Arfaj, H. (2009). The Neural Networks in Motion. Retrieved from
http://books.google.com
[8] Al-Eid, A. (2012). The Changes in GUI. Journal of Computer Explosion,
27(10), 1327-33.
[9] Regal, R. (2012, April 7). Globalizing Variables. KFU News. Retrieved from
http://www.kfu.news.sa
[10] Snippets in C#. (2010). San Diego: ABC Press.
[11] Plagiarism. (n.d.). In Wikipedia. Retrieved January 10, 2013, from
http://en.wikipedia.org/wiki/Plagiarism
[12] Rosario, R. (2008, April 7). Personal interview.
[13] Sebastian, B. (2010, July 25). Programming Style. PCPrograms.com.
Retrieved July 25, 2010, from http://www.pcprograms.com.
 [14] Al-Mulhem, K. (2009). Delphi Guide [Online Video]. Delphi Videos.
Retrieved from http://www.youtube.com/watch?v=asd5thw.

Exhibit 12: Arrangement of an Appendix

Appendix A (16 bold)

IN-VEHICLE INFORMATION SYSTEM TO SUPPORT
DRIVERS’ SITUATION AWARENESS (16 bold, caps)

Leave 1½” space from the top edge and 2 or 3 blank lines after the appendix title. Page
numbering is a continuation of preceding material. The appendix is organized exactly like
chapter.
A.1 Important theorems (If there is any….)

The size of the heading is 14-point boldface, initially capitalized, flush left, with one blank
line before, and one after. The remaining text (as in this paragraph) is 12-point, single- spaced.
Do not use double-spacing.
All paragraphs should be indented as is this one. Be sure your text is fully justified—that is,
flush left and flush right. Please do not place any additional blank lines between paragraphs.