Project Report Formatting Guidelines

1) Report Size: Limit your Project report to preferably 80-100 pages for the final project report.

2) Footer: The footer “Department of Computer Engineering, JSPM NTC Pune.” and page nos. on the right should be

included. It should be TIMES NEW ROMAN 10 pt. and centrally justified. Start numbering from the introduction.

3) Header: Project Title centred should be included.

4) Paper Size: A4 Size, bond paper.

5) Margins: Mirrored.

1. Top: 1 inch

2. Bottom: 1 inch

3. Inside:1.25 inch

4. Outside :1 inch

6) Line Spacing: 1. 5 lines

7) Title of Chapter:

1. Font: Arial (Boldface, Capital, )

2. Size:16 pt. Alignment: centred
8) All Topics heading:

i. First order Heading: (for example -1. Introduction)

1. Font: Times New Roman(Bold Face)

2. Size: 14 pt.
ii. Second order Heading: (for example -1.1 Evolution)

1. Font: Times New Roman(Bold Face)

2. Size: 12 pt.
iii. Third order Heading: for example -1.1.1 Image Processing

1. Font: Times New Roman(Normal Face)

2. Size: 12 pt.
9) Text:

1. Font: Times New Roman(Bold Face)

2. Size: 12 pt
10) Figures and Tables:

1.Caption:(for figures below the figure and for tables above the

table)

2. Font: Garamond(Bold)
3. Size:11 pt.

4. Alignment: Center

11) References:

Book

Author name(s), Book Title, Publisher, Copyright Year, page nos. if any.

Journal/ Magazine/ Periodical

Author name(s), paper name, Journal/ Magazine/ Periodical name, issue no., page nos
 SAVITRIBAI PHULE PUNE UNIVERSITY

A PROJECT REPORT ON

PROJECT TITLE

SUBMITTED TOWARDS THE

FINAL FULFILLMENT OF THE REQUIREMENTS OF

BACHELOR OF ENGINEERING (Computer Engineering)

BY

Student Name Exam No

Student Name Exam No

Student Name Exam No

Student Name Exam No

Under The Guidance of

Prof. Shruti Naik

JSPM NARHE TECHNICAL CAMPUS

DEPARTMENT OF COMPUTER ENGINEERING

Narhe, Pune-411041

2022-2023
 JSPM NARHE TECHNICAL CAMPUS
DEPARTMENT OF COMPUTER ENGINEERING

CERTFICATE

This is to certify that the Project Entitled

PROJECT TITLE

is a bonafide work carried out by Students under the supervision of Prof. Shruti
Naik and it is submitted towards the partial fulfilment of the requirement of a
Bachelor of Engineering (Computer Engineering).

Submitted by

Student Name Exam No

Student Name Exam No
Student Name Exam No

Student Name Exam No

Prof. Shruti Naik Prof. M. S. Sawalkar Dr. Nisha Auti

Internal Guide Project Coordinator H.O.D
Dept. of Comp. Engg. Dept. of Comp. Engg. Dept. of Comp. Engg.

Dr. S. A. Choudhari
Signature of External Examiner Director,
Date: JSPM Narhe Technical Campus
 Acknowledgments

It gives us great pleasure in presenting the final project report on

‘PROJECT TITLE’.

I would like to take this opportunity to thank my internal guide Prof. Name

Surname for giving me all the help and guidance I needed. I am really grateful to

her for her kind support. Their valuable suggestions were very helpful.

I am also grateful to Dr. Nisha Auti, Head of the Computer Engineering

Department, JSPM Narhe Technical Campus for her indispensable support and

suggestions.

I would like to express my sincere gratitude to Dr. S. A. Choudhari, Director of

our college for his invaluable support and guidance throughout our project. His
unwavering commitment and encouragement have been instrumental in our

success, and we are truly grateful for his contributions.

Student Name
Student Name
Student Name
Student Name
(B.E. Computer Engg.)
 Abstract
Write it in 300 words
Add Keywords describing your Project at the end
LIST OF FIGURES

4.3 Proposed System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

5.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

5.2 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

5.3 UML Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

5.3.1 Use Case Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

5.3.2 Class Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00
5.3.3 Activity Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00
LIST OF TABLES

2.2 Brief literature survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

3.1.1 Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

3.1.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 00

 INDEX

CERTIFICATE I
ACKNOWLEDGEMENT II

ABSTRACT III

LIST OF FIGURES IV
LIST OF TABLE V

1. Introduction 01

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 02

1.2 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 03

1.3 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 04

1.4 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 05

2. Literature Survey 06
2.1 Review of Conference/Journal Papers supporting Project idea . . . . . . . . 07
2.2 Brief literature survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 08

3. Requirements Specifications 09
3.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.1 Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2 Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3 Non-Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

.
4. System Architecture
15
4.1 Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.2 Limitations of Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3 Proposed System Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5. System Design 19

5.1 Data flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.2 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.3 UML Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.3.1 Use Case Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.3.2 Class Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.3.3 Activity Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6. Implementation and Methodology 26

6.1 Overview of Project Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.2 Tools and Technologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6.3 Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
.
7. Results 30
7.1 Outcomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Screenshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

.
8. Conclusion
33
8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
8.2 Future Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
8.2 Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36

References 37

Annexure A Project Plan 38

Annexure B Published Paper and Paper Publication Certificates 39

Annexure C Poster and Certificate 40

Annexure D Skill Certifications 41

 CHAPTER 1
INTRODUCTION
1.1 OVERVIEW

1.2 MOTIVATION
1.3 PROBLEM STATEMENT

1.4 OBJECTIVES
 CHAPTER 2
LITERATURE SURVEY
2.1 REVIEW OF CONFERENCE/JOURNAL PAPERS SUPPORTING

PROJECT IDEA

Atleast 12 papers or White papers or web references

2.2 BRIEF LITERATURE SURVEY

Brief literature survey in Tabular form [ Description containing important

description of at least 10 papers
 CHAPTER 3
REQUIREMENTS SPECIFICATIONS
3.1 SYSTEM REQUIREMENTS

3.1.1 HARDWARE REQUIREMENTS

3.1.2 SOFTWARE REQUIREMENTS

3.2 FUNCTIONAL REQUIREMENTS

3.3 NON-FUNCTIONAL REQUIREMENTS

 CHAPTER 4
SYSTEM ARCHITECTURE
4.1 EXISTING SYSTEM

4.2 LIMITATIONS OF EXISTING SYSTEM

4.3 PROPOSED SYSTEM ARCHITECTURE

 CHAPTER 5
SYSTEM DESIGN
5.1 DATA FLOW

5.2 ER DIAGRAM

5.3 UML DIAGRAM

5.3.1 USE CASE DIAGRAM

5.3.2 CLASS DIAGRAM

5.3.3 ACTIVITY DIAGRAM

 CHAPTER 6
IMPLEMENTATION AND
METHODOLOGY
6.1 OVERVIEW OF PROJECT MODULE

6.2 TOOLS AND TECHNOLOGIES

6.3 ALGORITHMS
CHAPTER 7
RESULTS
7.1 OUTCOMES

7.2 SCREENSHOTS
CHAPTER 8
CONCLUSION
8.1 CONCLUSION

8.2 FUTURE SCOPE

8.2 APPLICATION
REFERENCE
Book

Author name(s), Book Title, Publisher, Copyright Year, page nos. if any. .

Journal/ Magazine/ Periodical

Author name(s), paper name, Journal/ Magazine/ Periodical name, issue no., page

nos.
ANNEXURE A
Using planner or alike project management tool.
ANNEXURE B
Published Paper and Paper publications certificate of every student
ANNEXURE C
Poster and Participation Certificate
ANNEXURE D
Skill Certificates of every students (MOOC Course)