Guru Gobind Singh College of Engineering

and Research Center, Nashik.

Department of Computer Engineering

Final Year Project Work

(Guidelines & Log)
Academic Year: 2023-24

Project Title Voice Based Email For Blind People Using Face
Recognization.

1. Mr.Pranav S. Dharrao

2. Mr.Abhijeet B. Chavan

Team Members
3. Mr.Roshan K. Jadhav

4. Mr. Omkar D. Ghorpade

Internal Guide Mr.U.D.Butkar

 INDEX
1. Schedule of Project Work

2. Undertaking by Students

3. Project Activity Plan (Semester I)

4. Group Details

5. Synopsis/Abstract

6. Monthly Project Plan (Semester I)

7. Project Work Attendance (Semester I)

8. Project Log Book (Semester I)

9. Project Review – I Check List with Performance Evaluation Sheet

10. Project Review – II Check List with Performance Evaluation Sheet

11. Examination Evaluation Sheet (Semester-I)

12. Project Activity Plan (Semester II)

13. Monthly Project Plan (Semester I)

14. Project Work Attendance (Semester II)

15. Project Log Book

16. Project Review – III Check List with Performance Evaluation Sheet

17. Project Review – IV Check List with Performance Evaluation Sheet

18. Document required for final examination

19. Examination Evaluation Sheet (Semester-II)

20. Details about Participation in Project Competition/Event

21. Examination Evaluation Guidelines

22. Annexures
 Schedule of Project Work
Semester I
Sr. Date
Activity Scheduled
No. (Tentative)
Third Year Semester II/
1. Registration of Project Teams
Mid of July
2. Submission of Project Proposal Last Week of July
3. Project presentations First week of Aug
4. Finalization of projects & allotment of guide Second week of Aug
5. Submission of final Proposal Third week of Aug
Review meeting/ presentation for progress of
6. Last week of Aug
project work- I.I
Review meeting/ presentation for progress of
7. Second week of Sept
project work- I.II
Review meeting/ presentation for progress of
8. First week of Oct
project work- II.I
Review meeting/ presentation for progress of
9. Last week of Oct
project work- II.II
10. Submission of partial project report Last week of Oct
As per SPPU
11. Project work (Stage I) Examination
Notification

Semester II
Sr.
Activity Scheduled Date(Tentative)
No.
Review meeting/ presentation for progress of
1. Last week of Jan
project work –III.I
Review meeting/ presentation for progress of
2. Fourth week of Feb
project work –III.II
Review meeting/ presentation for progress of
3. Third week of March
project work- VI.I
Review meeting/ presentation for progress of
4. Last week of April
project work- VI.I
Submission of final project report and Project
5. First week of May
Work book to the project Coordinator
As per SPPU
6. Project Examination
Notification
SEMESTER-I
 UNDERTAKING BY STUDENTS

We, the students of B.E. Computer are hereby assured that we will follow all the rules and regulations of
SPPU related to the project work for the academic year 2023-24. The Project entitled

will be
fully designed and developed by us and no part of the project/full project will be designed and developed
by any external entity or copied from some external resources. We are fully aware that copying or taking
help of any external agency in the development of our project is totally unethical and illegal. The examiners
have /University has full rights to initiate an action against us as per university norms if involved in
unfair/illegal/unethical work.

Sr. No. Roll No. Name of Student Signature

4
 Rules & Regulations

1. All students must enter the correct information in the work book.

2. All the entries in the project work book must be verified by the concerned project guide.

3. Students must report to their respective guide on project day as per the time table.

4. Activities of the project work should be completed as per the project plan only.

5. Project group must submit soft copies of Project Abstract, Project Report and Publications in PDF

format only.

6. Project group member submit two hard copies of Project Report in the format provided by

department.

7. Project work book must be brought at the time of Project Reviews & Project Examination.

8. Any changes, if any, must be countersigned by the concerned project guide.

9. For project reviews and project examination, all students must report 15 minutes before the scheduled

time.

10. For any query, concerned guide should be consulted.

 Project Activity Plan
Semester I

July August September October November

3rd 4th 5th 3rd 4th 1st 2nd 4th 5th 1st 3rd 4th
1st 2nd 1st 2nd
Wee Wee Wee We We 5th Week We We 3rd Week We We We 2nd Week We We 5th Week
Week Week Week Week
k k k ek ek ek ek ek ek ek ek ek

First Second Third Fourth

Presentati Presenta Presentati Presenta Submission of
Project
on tion o n tion Partial Project
Presentation
(Review- (Review- (Review- (Review- Report
I) II) III) IV)
Fin
Regi aliz
strati Regi atio
on strati Sub n of Sub Syst
Proj mis Fea Sco
of on miss PPT Content em
ect sion PPT sibil pe Require UML PPT
Proj of ion 1.Problem Arc
and of Content: ity of ment Diagram Content:
ect Proj of 3 Definition hite
Stu Proj Analysi s
Gro ect topic 2. Area/Domain All Syn 1. Problem ctur PPT Content: Diagrams
otm opsi Statement dy ect PPT s 1. DFD
Participate in
up Gro s 3. Abstract Content e 1. Project
4.Literature ent s 2. 2. Class
Lead ups 1. Requirement Competition/
Survey of Motivation 3. Object Paper
ers Feasibilit Analysis
5. Scope of Gui 3. y 2. System 4.Use Publication/
Project Objective 2. Scope Architecture Case Presentation
de 4. 5.
6. Software-
Hardware Literature Sequence
Review 6. Activity
requirement

Project Discuss Verification of

Guidelines with Discuss with Project Guide Project Report
Awareness peers & Work Book

Presentation
Submit
Verify Certificate
Project
Synopsi Approve PPT & Report Content s
Coordinator
s
(If any) &
Project Report
 Project Details
Group Members

Group No.: Guide Name:

Project Title:

Roll No

Group Member Name

1 Mobile Number

E-Mail ID

Roll No

Group Member Name

2 Mobile Number

E-Mail ID

Roll No

Group Member Name

3 Mobile Number

E-Mail ID

Roll No

Group Member Name

4 Mobile Number

E-Mail ID

Name and Signature of Mr. S.G. Shukla

Internal Guide Head of the Department
 Abstract

 Abstract Contents

This study presents a voice-controlled email system for the visually impaired, complemented by face recognition
technology. This system offers an inclusive means for the blind to compose, send, and manage emails through
voice commands. The integration of face recognition adds a layer of security for user authentication, ensuring
both accessibility and privacy. This research highlights the potential of emerging tech for inclusivity in digital
communication.

a) Aim or Purpose of Project :

The goal of this project is to provide an easy-to-use mail system for individuals with disabilities while
enhancing login security. Our aim is to make email management more accessible.
Developing a voice-based interface that allows visually impaired users to perform essential email tasks,
including reading, composing, replying, and organizing emails, using spoken commands.

b) Method Used :
To create an Voice Based Email System for Blind People with security concepts, you can follow these simple
steps:
- Data Collection
- Data Preprocessing
- Machine Learning Model
- Security Features
- Data Encryption
- Text to Speech
- Speech to Text
- Face Recognition

c) Results :
The combination of voice-operated email systems for the visually impaired with face recognition has made it
easier for users to log in and interact with the system. Using unique traits like faces and voices for security, this
system is more protective. It's harder for people who shouldn't be using it to get in, making it safer and more
user-friendly for blind individuals.

d) Conclusion :
In our project, we propose an innovative approach to empower blind individuals with convenient and
interactive voice recognition methods for email management. Our system aims to simplify email access
for the visually impaired, addressing the challenges they face. By efficiently facilitating E-Mail services, our
project seeks to enhance the overall email experience for those with visual impairments.
 Synopsis
Topic of the Project: Voice Based Email For Blind People Using Face Recognization.

Objective :
- To perform tasks and make human life easy.
- Create technology that allows machine and computer to Work intelligently.
- A virtual Voice based system interacting with Users.

Scope:
- Accessibility is a central focus, ensuring that individuals with visual impairments can independently manage their
email accounts.
- The user only requires listening to the voice commands given by the system and respond accordingly in order to
get the desired operations performed.

Process Description:

In System We Used This This Mathematical Model .We are Designing registeration page, login Page, Also
implementing face Based login for security purpuse.Users initiate the process by enrolling in the system, providing
personal information and a reference image for face recognition.The system captures the user's voice and facial data,
creating a unique biometric profile.Users use voice commands to compose, send, and manage emails.

Fig.2. System Architecture

 Resources: The requirement of the resources for designing and developing the proposed system must be given.
The resources might be in form of the hardware / software or real time data.

Gesture Recognition
Voice Assistant
Programming Language
Hardware

References and bibliography:

[1] 1. Voice Email Based On SMTP For Physically Blind,– Sunny Kumar , Ms. Yogitha. R, Ms. R. Aishwarya [2021]
2. A Voice Communication-Augmented Simulation Framework For Aircraft
Trajectory Simulation- Yuhao Wang, Michael Thomas [2021]
3. Design and implementation of voice mail in IP telephony based on
Mediastreamer2- Xu Yue and Xu Bing[2021]
4. Transfer Learning From Speech Synthesis to Voice Conversion with Non- Parallel Training Data- Mingyang Zhang,
Yi Zhou and Li Zhao [2021]
5. Email classification via intention based Segmentation Sanjay Kumar
Sonbhadra, Sonali Agarwal and Krishna Adiyarta [2020]
 Project Work Attendance

Semester-I

Group Member Sign

Sr. Guide Dated
Date Topic Discussed
No. Sign
1 2 3 4

10

11

12

13

14

15

16

17
 PROJECT REVIEW–I
(FINALIZATION OF SCOPE)

REVIEW-I CHECKLIST

PROJECT STATEMENT

1. Is the statement short and concise (10-20 words maximum)?

2. Does the statement give clear indication about what your project will accomplish?

3. Can a person who is not familiar with the project understand scope of the project by reading the
Project Problem Statement?

REQUIREMENT: SCOPE AND OBJECTIVES

1. Does the Scope and Objectives establish the "context" for the proposed project by referencing to
the following elements:

2. Area all aspects of the requirements document (i.e., Functional Spec.) addressed in the design?

3. Is the architecture/ block diagram well defined and understood?

4. The project's objective of study (what product, process, resource, etc.) is being addressed

5. The project's purpose: is the purpose of project addressed properly (why it's being pursued: to
evaluate, reduce, increase, etc.)?

6. The project's viewpoint: is the project's viewpoint is understood? (who is the project's end user)?

7. Is the project goal statement is in alignment with the sponsoring organization's business goals and
mission?

ANALYSIS

1. Is information domain analysis complete, consistent, and accurate?

2. Is problem statement categorized in identified area and targeted towards specific area therein?

3. Are external and internal interfaces properly defined?

4. Does the Use Case Model properly reflect the actors and their roles and responsibilities?
 5. Are all requirements traceable to system level?

6. Is similar type of methodology / model is used for existing work?

7. Are requirements consistent with schedule, resources, and budget?

Review – I & II : Deliverables

• Problem Statement / Title
• Purpose, Scope, Objectives
• Abstract (System Overview)
• Literature Survey
• H/W,S/W & other requirement, Test Environment/Tools
• System Overview- (Proposed system & Proposed outcome)
• Architecture & DFD
• References
• Project Plan 1.0
 Students Performance Evaluation (Review-I.I)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Need Scope
Evaluation Role in idea & Objective Problem
Presentation Q&A Total
Criteria Generation (Relevance) Statement

CO Attended:

Name of Student 5 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Students Performance Evaluation (Review-I.II)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Evaluation Literature Conclusion

Teamwork Presentation Q&A Total
Criteria review from LR

CO Attended:

Name of Student 10 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 PROJECT REVIEW–II
(Design)

REVIEW-II CHECKLIST

DESIGN

1. Are requirements reflected in the system architecture?

2. Does the design support both project (product) and project goals?

3. Does the design address all the issues from the requirements?

4. Is effective modularity achieved and modules are functionally independent?

5. Are structural diagrams (Class, Object, etc.) well defined and understood?

6. Are all class associations clearly defined and understood? (Is it clear which classes provide
which services)?

7. Are the classes in the class diagram clear? (What they represent in the architecture design
document?)

8. Is inheritance appropriately used?

9. Are the multiplicities in the use case diagram depicted in the class diagram?

10. Area behavioral diagrams (use case, sequence, activity, etc.) will defined and
11. understood?

12. Is aggregation/ contaminant (if used) clearly defined and understood?

13. Does each case have clearly defined actors and input/ output?

14. Is all concurrent processing (if used) clearly understood and reflected in the
15. sequence diagrams?

16. Are all objects used in sequence diagram?

17. Does the sequence diagram match class diagram?

18. Are the symbols used in all diagrams correspond to UML standards?
 19. Does code completely & correctly implement the design?

20. Does code comply with coding standards?

21. Is code well structured, consistent in style & consistently formatted?

22. Are basic functions in the design coded?

23. Is code clearly & adequately documented?

24. Are test results highlighted?

Review-II: Deliverables
• Methodology and Design / algorithms / techniques used
• Modules Split-up /Proposed System
• Software Tools/Technologies to be used
• Working module
• Partial Report (Semester – I)
 Students Performance Evaluation (Review-II.I)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

UML Present
Evaluation Requirement System ation & Total
Feasibility
Criteria Analysis Architecture Diagrams Q&A

CO Attended:

Name of Student 10 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Students Performance Evaluation (Review-II.II)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Evaluation Design and Report

Teamwork Presentation Q&A Total
Criteria Development Preparation

CO Attended:

Name of Student 5 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Semester -I Summary

Review Attendance Total

Guide (RT + Att.
Grading +
Name of Students I.I I.II II.I II.II Total % Out of
Grading)

5 5 5 5 20 100 10 20 50

Guide Project Co-coordinator HOD

 Evaluation Sheet for Oral Examination

Problem
Statement
/
Name(s) of Motivatio Requirem Planning Presentation Partial
the student n ent & n& Project Total
Sr. in / Literature Analysis Modeling Prototyping Report
& Question -
No. the project Objectives Survey Answer
group / Scope/ Designing
Feasibility
Requirement
Marks -> 5 5 5 10 5 10 10 50

Examiners Feedback and Suggestions:

Internal Examiner External Examiner

Name and Signature Name and Signature
SEMESTER -II
 Project Activity Plan
Semester II
Jan Feb March April May
1st 2n 3r 4t 5th Week 1st 2nd 4th Week 1st 2n 3rd 1st 2n 3r 4th Week 1st Week
d d h d d d
W W & We Week W
ee W W W ee 3rd ek W ee W W
k ee ee ee k We ee k ee ee
k k k ek k k k

Modelling Review Coding/ Review Validati Revie Report Review Mock

(Model III.I Implem III.II on & w IV.I Writing IV.II Project
Refinement Presentat entation Testing Prese Present Examinati
and Algorithm Presentat
ion ntatio ation on
development) ion
n

PPT PP PPT PPT PPT

Content T Conte Content Content
Do you clearly identify data objects, their attributes & relationships?

Co nt
Alpha testing & beta testing? & Code using standard datasets
1.Proces 1. 1.Abstra
Does any functional dependencies are identified and described?

nte
Does the mathematical model clearly states goal of project?

s Model 1.Ma Report ct

Report properly organized ,spelled, grammatically correct

nt
Which Software Development Process Model is Used?

Which architectural model does your system supports?

nual Prepar
2.Mathe Pr 2.Introdu
Test ation

Submission of Draft of Report for Checking

oje
Are all comments consistent with the code?

matical ction

Complete results & Comparative graphs

Cases
Are all Function in the design coded?

model ct 2.
3.Literatu
Code in real time environment?

De 2. Results
3. re Survey
mo Auto &
Architec
matic Conclu 4.Algorith
tural
Test sion m/Metho
model
Cases dology
4.compo used
nent
5.Implene
diagram
tation
5.deploy
6.Testing
ment
diagram 7.Results
6.NP- 8.Conclus
Complet ion
eness
9.Referen
ces

Check Contents & Presentation Review of Prescribed format? Plagiarism free?

Participation
Are all figures & tables properly
Activity
cited?
Weather references are properly
cited?
 Semester-II

Group Member Sign

Sr. Guide Dated
Date Topic Discussed
No. Sign
1 2 3 4

10

11

12

13

14

15

16

17
 PROJECT REVIEW–III

REVIEW-III CHECKLIST

Structure

1. Does the code completely and correctly implement the design?

2. Does the code comply with the Coding Standards?

3. Is the code well-structured, consistent in style, and consistently formatted?

4. Does the implementation match the design?

5. Are all functions in the design coded?

6. Does Mathematical model developed correctly?

Documentation

1. Is the code clearly and adequately documented?

2. Are all comments consistent with the code?

Review-III: Deliverables
 Detailed Design (if any deviation)
 80% of code implementation
 Some Experimental Results
 Project Plan 3.0
 Students Performance Evaluation (Review-III.I)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Models
Evaluation (Process, UML Diag. NP-
Presentation Q&A Total
Criteria Architectural, (Component, Completeness
Mathematical) Deployment)

CO Attended:

Name of Student 5 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Students Performance Evaluation (Review-III.II)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Evaluation
Project Demonstration Presentation Q&A Total
Criteria

CO Attended:

Name of Student 15 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 PROJECT REVIEW–IV

REVIEW-IV CHECKLIST

1. Is every feature tested?

2. Are all functions, user screens and navigation tested? (e.g. module, object,
integration, usability, system)

3. Are test cases designed? (manual and automated)

4. Is testing tool used?

5. Is result analysis done properly and appropriate conclusion drawn?

6. Implementation status ( code completion in percentage)

7. Final thesis status( in percentage)

Review-IV: Deliverables
 Detailed Design
 100% of code implementation
 Experimental Results
 Performance Evaluation
 Test Cases
 Result Analysis and Conclusion
 Final Thesis
 Project Plan 4.0
 Students Performance Evaluation (Review-IV.I)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Evaluation Manual Automatic Teamwork- Presentation Q&A Total

Criteria Testing Testing Contribution

CO Attended:

Name of Student 5 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Students Performance Evaluation (Review-IV.II)

Group ID Guide Name

Project Title:

Roll
Sr.No. Name of Student
No.

Project Covers
Aspects of
Evaluation Report Envi., Safety, Results &
Criteria Preparation Research & Conclusion Presentation Q&A Total
Innov., Prod.
Devel. & Ethics

CO Attended:

Name of Student 5 5 5 5 5 25

1.

2.

3.

4.

Remark

Evaluator 1: Evaluator 2: Internal Guide

Name and Signature Name and Signature Name and Signature
 Semester -II Summary

Review Attendance Total

Guide (RT + Att.
Grading +
Name of Students III.I III.II IV.I IV.II Total % Out of
Grading)

5 5 5 5 20 100 10 20 50

Guide Project Co-coordinator HOD

 Participation in Project Competition/Event
(Academic Year: 2023-24)
Participation in Project Competition/Event
Name & Place of Project Competition / Certificate / Prizes
Sr. No. Date
Exhibition won

Paper Publication / Presentation

Sr. No. Name of the organizing society Date Certificate / Prizes Win

Patents Details
Sr. No. Patent Name Date Certificate (if any)

Product Development/Technology
Sr. No. Company name Date of Submission Remark

* Photocopy of the certificate must be attached to this booklet.

Project Coordinator Internal Guide

 Examination Evaluation Guidelines

Along with Internal Examiner, the External Examiner should see their Partial or Final project
reports, project log book and the presentation of each group along with live project demonstration
(applicable in second semester).
There is a possibility that the marks obtained in B.E. Projects by various groups across the university
may not be uniform because of the involvement of many examiners. It is expected that the examiners
should evaluate the students rigorously. Both the examiners are supposed to evaluate each student /
group based on some or all of the following points. Also the evaluation of the examiners must be fair
enough so that the student gets appropriate credit/ marks for his/her efforts. Marks breakup is enclosed
in the attached excel sheet.

The following are the guidelines for the presentation and should be shared with the students.
a. Purpose or Significance or Motivation of Study / topic identified
b. Objectives of Problem Statement
c. Technical relevance and originality of problem
d. Literature reviewed followed by sufficient requirements analysis
e. Design and coding effort along with best practices followed
f. Analysis, interpretation, implementation and validity of results
g. Extent of technical knowledge and coding skill gained
h. Use of project management techniques and maintaining project log Book.
i. Use of modern CASE tools and techniques in development (if required for the problem)
j. Team-work and collaboration
k. Use of professional ethics and social relevance
l. Presentation Skills
m. Answers to questions - analysis, depth of understanding of problem/ conclusions/ inference
n. Project Report / Thesis Contents Quality
NOTE:
1. The project groups obtaining more than 90% of marks in the project exam may be moderated by the committee
appointed by the University of Pune.

2. The evaluation sheet enclosed should be duly filled according to project group and sent along with the chairman
copy of the mark list

3. The project guide should initiate the presentation in the project examination (SEM-I to create a context and to
understand the motivation of the project topic.
 Department of Computer Engineering

Documents required for final examination

 Log Book
 Base Paper along with reference papers (if applicable)
 Sponsorship letter (if applicable)
 Abstract (if project based on application oriented/fulfill society need)
 Certificate of participant in project competition (if any)
 Certificate of Publish paper or publish paper (if any)

 Plagiarism report of Abstract, introduction, system implementation and Conclusion

 Appreciation Letter where project is actual working

Note:

These document should be maintained by students in separate file.

 Evaluation Sheet for Oral Examination

Answers to
Implementation questions -
Originality of analysis, depth
& Coding
Problem of
Standards Content
Statement understanding Quality of Total
Technology /
Sr. Attainment of the problem / Project
Software / Tools
Name of Students Objectives Analysis & Presentation conclusions / Report out
Design Used
No. Skills inference of
100)
Marks -> 10 20 20 10 20 20 100

Examiners Feedback and Suggestions:

Internal Examiner External Examiner

Name and Signature Name and Signature
 Annexure I: Final Synopsis (after approval of the project work)

Title Page
 Project Group ID/ group Details
 Title of the project
 Domain such as databases, image processing, network based, web technology based etc.
 Team Members (List with Signatures)
 Sponsorship details if any (Name, External Guide name and Designation with
 Signature, e- Mail ID)
 Internal Guide (with signature of approval)

Inner Pages:
 Keywords (ACM Keywords)
 Problem Definition
 List of modules/ functionalities
 Current market survey: This should include list of similar products available, if any and also, their
pros and cons.
 Scope of the project
 Literature survey (List of references only): This should include the list of books, magazines,
research papers, web links etc referred by the students.
 Software and hardware requirements of the project
 Probable date of completion
 Outcomes
 Annexure II: Partial Project Report (Semester I)

A preliminary report of project work (Partial Project Report) is to be prepared as per the guideline given
below using Latex and is to be submitted at the end of semester I.
Title Page
First page containing Name, Topic Name, Guide Name, Year, Branch, and College Name etc. (see format
displayed herewith)
Certificate
 Certificate (provided by college)
 Project approval sheet (see format displayed herewith)
 Certificate certifying the project work done approved by the sponsoring authority, if any.
Acknowledgements (if any)
Thanking any person / staff member / friend if to be done so.
Abstract
A minimum of 100 words briefing the topic in consideration.
Keywords
A minimum of 5 and maximum of 10
Introduction
Introduction should be minimum of 200 words, briefing of the details to follow. It should cover details of
project work, objectives, scope of the project and organization of report.

Literature Survey
The purpose of the literature survey is to identify information relevant to project work and the potential
and known impacts of it within the project area. This section should include a comprehensive report of
current market survey done with respect to problem. Include study of similar systems available, if any
along with their pros and cons. Identify, those areas where there is an absence or scarcity.

Design Details (Phase I to IV)

Phase I: Requirements Analysis

The Group is to submit a detailed write – up indication the requirements that the project demands, viz.

Detailed problem definition.

 The definition is to include all that is to be done and is to be put up in the final software and / or hardware
(product) that is to be generated from the years’ work (User’s point of view).
 Requirement may not be final and provision should be available to add features dynamically without
affecting the actual flow and design of the document.
 Modified Requirements (After doing feasibility study) are to be prepared under all the 3 categories
listed above from the developer’s point of view. The requirement listed herein should be feasible
technically from the software / Hardware point of view.
 The new should be categorized in the 3 categories listed above. Follow the standard format of SRS.

Phase II: Analysis Phase

The group (based on Phase I) is to suggest the paradigm followed by them in the project. The
paradigm should be justifiable from Phase I. The various stages and work to be completed under them
is to be indicted in detail.

Phase III: Design Phase

ERDs (Optional, decide in consultation with guide)
● The group is to draw the ERD (Entity Relationship Diagram) for the project. (This
● should be justifiable with regard to Phase I & II)
● The ERD after getting evaluated (by dry running) is to be analyzed for
● incompleteness from any point of view.
● The ERD thus validated should be made fair in a presentable fashion.
● This ERD is to be included in the Report.
IF
The project group is to follow an “Object Oriented” Approach for their Project.
THEN
● The group will draw all (all the nine) UML (Unified Modeling Language) diagrams for the project.
● These diagrams are to be refined in every aspect for this report(as per requirements finalized in phase
I)
● Proper notations are to be used in all the figures drawn.
● Proper Color-coding if required is to be used.
● Extensions to diagrams / customizations may be done and represented ( if the project demands it)
ELSE (groups following Structured Approach)
● The group will draw the DFD-s (Data Flow Diagrams) for the Project. (These should be justifiable
with respect to Phase I, II and the ERD)
● DFD Level 0, Level 1, Level 2 should be drawn in an evolutionary fashion ( No
● entries to appear in Level 2 unless they are in Level 1, which in turn are in Level 0)
● The DFD’s are to be validated and made final in a presentable fashion.
● Proper Color- coding is expected
● Extensions to DFD-s may be represented (if the project demands it)
 Phase – IV: Planning Phase
● The group is to finalize the Front End/ Back End required for the project as per the demands of the
project( Software and / or hardware)
● The Front End/ Back End should be justifiable depending on the complexity of the project.
● The structure of the database to be finalized depending on the complexity of the project.
● Any Normalization required on the database is done so as to ensure correctness for the future phase.
● Coding Language / Methodology should be finalized/
● Time requirement to be finalized and indicated
● Actual project plan including major milestones should be decide and finalized
● Rough estimates of lines of code / functions / routines to be made.
● Rough estimates of lines of code / Objects / Classes to be made ( for Groups
● following OO Paradigm)
● Software Reuse /Re – Engineering possibilities are to be expected and indicated
● Software and Hardware requirement.
● Probable date of completion.
● Scope of the project.
Phase – V: Prototyping
● A prototype is expected which basically includes all the MAJOR features in the project.
● The GUI/ Front end is to be prepared.
● The structure of the database / back end (if any) to be indicated.
● The prototype is built basically to give a feel of the actual software and / or hardware (Product) that is
expected Major routines / Functions are expected.
Conclusions
Include conclusions from the work done with a minimum of 50 words
References
List out Books, Magazines, Thesis, Journals, Web links etc referred in IEEE format
Plagiarism Check Report
 Annexure III: Project Report (Semester II)

A report of project work is to be prepared as per the guidelines given below using Latex and is to be
submitted at the end of semester II along with CD containing (copy of Partial Project Report, Final
Project Report along with .tex files, Power point presentation, copy of base paper and reference papers,
executable Project Code, supportive software platform for the project execution).

First page as per standard college reports

First page containing Name, Topic Name, Guide Name, Year, Branch, and College Name etc. (see
format displayed herewith)
Certificate (will be provided by college)
Dissertation approval sheet (see format displayed herewith) Also attach certificate certifying the project
work done approved by the sponsoring authority, if any.
Abstract
A minimum of 100 words briefing the topic in consideration.
Keywords
A minimum of 5 and maximum of 10
Index
Details of various Topics, Sub-Topics, with Page No. Figure Index, giving details of page number, figure
number and figure caption Table Index, giving details of page number, table number and table caption
(If any) Index of Pseudo-code / Sample code (If any)

I) Introduction
Minimum of 200 words, giving some briefing of the details to follow.
· Detailed problem definition
· Justification of problem
· Need for the new system
· Advances/additions/updating the previous system
· Presently available systems for the same
· Purpose of your system
· Organization of the report
This section should be relevant to the Literature Survey done and reported in the partial project report.
The purpose of the literature survey is to identify information relevant to project work and the potential
and known impacts of it within the project area. This section should include a comprehensive report of
current market survey done with respect to problem. Include study of similar systems available, if any
along with their pros and cons. identify those areas where there is an absence or scarcity.

II) Analysis
· Project plan
· Requirement analysis
· Team structure
The Group is to submit a detailed write-up indicating the requirements that the project demands

Actual detailed problem definition

The definition is to include all that is to be done and is to be developed in the final software and / or
Hardware (product) that is to be generated from the years’ work (User's point of view).
The entries under this section are to be categorized under the categories,
1. Necessary functions,
2. Desirable functions,
3. Others
Requirement may not be final and provision should be available to add features dynamically without
affecting the actual flow and design of the document. Modified Requirements (after doing feasibility study)
are to be prepared under all the 3 categories listed above from the developer's point of view. The
requirements listed herein should be feasible technically from the Software / Hardware point of view. The
new list is also be categorized in the 3 categories listed above. (Follow the IEEE format of SRS). The group
is to suggest the Paradigm followed by them in the Project. The Paradigm should be justifiable from Phase
I. The various stages and work to be completed under them is to be indicted in detail.

III) Design
· Software Requirement Specification (SRS) format is as given below.
· Risk assessment
·Brief discussion on Project plan submitted in semester I including major milestones and the work done
as per it.

IV) Modelling
· UML diagrams (all 9)
· ERD & Normalization (NF) for database (if any)

ERDs (Optional, decide in consultation with guide)

·The group is to draw the ERD (Entity Relationship Diagram) for the Project. (This should be justifiable
with regard to Phase I & II)
·The ERD after getting evaluated (by dry running) is to be analyzed for incompleteness from any point of
view
· The ERD thus validated should be made fair in a presentable fashion
· This ERD is to be included in the Report

IF
The project group is to follow an “Object Oriented “Approach for their Project.
THEN
· The group is to draw all (all the nine) UML (Unified Modeling Language) diagrams for the project
· These diagrams are to be refined in every aspect for this report (as per requirements finalized in phase I)
· Proper notations are to be used in all the figures drawn
· Proper Color-coding if required is to be used
· Extensions to diagrams / customizations may be done and represented (if the project demands it)

ELSE (groups following Structured Approach)

·The group is to draw the DFD-s (Data Flow Diagrams) for the Project. (These should be justifiable with
respect to Phase I, II and the ERD)
·DFD Level 0, Level 1, Level 2 should be drawn in an evolutionary fashion (No entries to appear in
Level 2 unless they are in Level 1, which in turn are in Level 0)
· The DFD-s are to be validated and made final in a presentable fashion.
· Proper notations are to be used in all the figures drawn
· Proper Color-coding is expected
· Extensions to DFD-s may be represented (if the project demands it)

V) Coding
. Algorithms/ Flowcharts
· Software used
· Hardware specification
· Programming language
· Platform
· Components
· Tools
. Coding Style Format

V) Result Sets

VI) Testing
· Format technical reviews
· Test plan
· Test cases
· Test results
(Unit, integration, regression, system,α,β)

VII) Configuration Management Plan

VIII) Software Quality Assurance Plan

* Costing (Time, Money and Resources)
(Do not include costing in the project report; submit to the guide)

Conclusion
Your conclusions from the topic dealt with a minimum of 50 words.

References
List out Books, Magazines, Thesis, Journals, Web links etc referred in IEEE format

Glossary
In Keyword Alphabetical Order Ascending along with Page numbers

Plagiarism Check Report

 Format of SRS
Software requirement Specification is a detailed write-up indicating the requirements that the project
demands. It contains actual detailed problem definition. The definition is to include all that is to be done
and is to be developed in the final software and / or Hardware (product) that is to be generated form the
years’ work (User’s point of view).
The entries under this section are to be categorized under the categories like

1. Necessary functions,
2. Desirable functions, and others
Requirement may not be final and provision should be available to add features dynamically without
affecting the actual flow and design of the document. Modified requirements (after doing feasibility
study) are to be prepared under all the 3 categories listed above form the developer’s point of view.
The requirements listed herein should be feasible technically form the software/ Hardware point of view.

It should include following important requirements.

1. Detailed Problem Definition

2. External Interface Requirements
● User interfaces
● Hardware Interfaces
● Software Interfaces
● Communication Interfaces
3. System Features
● Feature 1
● Feature 2 etc.
4. Other Non- functional requirements.
● Performance requirements
● Safety requirements
● Software Quality attributes
 Annexure IV: Project Report Formatting Guidelines

1)Report Size: Limit your Project report to preferably 25- 40 pages for partial project report. Limit your
Project report to preferably 80-100 pages for final project report.
2)Footer: The footer “Department of Computer Engineering, MCERC Nashik” should be included. It
should be TIMES NEW ROMAN 10 pt and centrally justified.
3)Header: Project Title centered and page nos. on right should be included. Start numbering from
introduction.
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 (Bold face, Capital, )
2. Size :16 pt, Alignment: centered
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:
1. Book
Author name(s), Book Title, Publisher, Copyright Year, page nos. if any.
2. Journal/ Magazine/ Periodical
Author name(s), paper name, Journal/ Magazine/ Periodical name, issue no.,page nos.
3. Web Resources
Complete URL including File name.
 Annexure V: Project Report Cover page/ Title page

(Partial) Project Report On

Title of Project

By

Name of Student 1 (Exam NO:)

Name of Student 2 (Exam NO:)

Under the guidance of

Name of the Guide

College Logo

Department of Computer Engineering

Guru Gobind Singh College of Engineering & Research Centre

SAVITRIBAI PHULE PUNE UNIVERSITY 2023-2024