COMPUTER ENGINEERING DEPARTMENT

Project Guidelines and Progress Record

Topic: POP-N-DINE

Group Members:

1. Bhavya Gada (B014)

2. Shivesh Hegde (B017)

3. Manthan Kawa (B021)

Name of Guide: Mr. Pratik Shah

Academic year: 2024-2025

1
 Project Guidelines and Progress Record
This handbook outlines the contents relevant to the “Diploma Final Year Project”, which
is intended to be used by students and faculty members of the Department of Information
Technology in S.B.M. Polytechnic, Mumbai. This handbook is the result of an effort initiated
to define the policy and improve the quality of the Final Year Project. It presents an efficient
and object-oriented procedure for outcome-based assessment of CSE diploma engineering
final year projects. The intention of this handbook is to develop a standardised framework for
diploma engineers of Computer Engineering to show their project progress.

What is the Final Year Project?

Final Year Projects represent the culmination of my studies for the Diploma in
Engineering. Projects offer the opportunity to apply and extend material learned throughout
the program. Assessment is by means of a presentation, submission of a report, and a
demonstration of work undertaken. In contrast to the majority of courses studied elsewhere
in the program, projects are undertaken in small groups. This necessarily introduces the
dimension of workload management into the program to enable the completion of a large,
relatively unstructured assignment over the course of the semester. The projects undertaken
span a diverse range of topics and vary from year to year. The emphasis is necessarily on
facilitating student learning in technical, project management and presentation spheres.

2
 Contents

Sr. No. Topic Page

1. Course Details 04
2. Teaching and examination scheme 04
3. Objective 04
4. Skill competency 04
5. Course Outcomes 04-06
6. Identification of projects and allocation methodology 06

7. Process of monitoring and evaluation 06-07

8. Project Details 08
9. Student Details 09
10. Schedule of Presentations and Demonstrations 10
11. Weekly Progress 01-04 11-12
12. Assessment for project - Phase I 13
13. Weekly Progress 05-08 14-15
14. Assessment for project - Phase II 16
15. Weekly Progress 09-16 17-20
16. Assessment for project - Phase III 21
17. Appendix - A Project Report Formatting Guidelines 22-23
18. Appendix B - Contents of Synopsis Report 24-25
19. Appendix C - Contents of Project Report 26-27
20. Appendix D - Feedback survey by Co-Guide 28-31
21. Appendix E - Details of publications by the project members 32
22. POs and PSOs 33
23. VISION, MISSION and PEOs 34

3
 1. COURSE DETAILS

2. TEACHING AND EXAMINATION SCHEME

3. COURSE OBJECTIVE
To develop a project to give in depth understanding of all the concepts learnt at
the lower semesters. To expose students to the various stages of making a project and
the capability to work in a team.

4. SKILL COMPETENCY
The aim of this course is to help the student to attain the following industry-
identified competency through various teaching-learning experiences.

• Design and develop Hardware and/or Software system.

5. COURSE OUTCOMES

4
6. CO-PO, CO- PSO MAPPING TABLE

7. Each student/group of students will submit a project synopsis and detailed

project report with the following details
A) Project synopsis
Abstract
Chapter 1. Problem statement
Chapter 2. System requirement
specification Chapter 3. Proposed
system/solution Chapter 4. Estimation and
planning
Chapter 5. Future scope
Chapter 6. Conclusion
Bibliography and References
B) Project Report
The report shall be presented in the following sequence:
Title sheet
Project Certificate
Project approval sheet
Acknowledgement
Abstract
Table of contents
List of tables (if desired)
List of Figures (if desired)
Chapter 1: Introduction (domain)
Chapter 2: Problem statement and proposed system (input /output
statement, description, feasibility)
Chapter 3: Literature Review

5
 Chapter 4: Design and Implementation(System Architecture,
Requirement: hardware software any other, flow diagrams, activity diagrams,
DFD, ER diagram if desired, User Interface)
Chapter 5: Result & Conclusions (Reports, future scope and
limitation) Bibliography and References

8. Identification of projects and allocation methodology to faculty members and

relevance of the projects and their contribution towards attainments of POs.

9. Process for monitoring and evaluation, process to assess individual and team
performance.

10. Methodology to assess individual/collective contribution/understanding:

a. Internal evaluation (50 marks) by project
guide. Phase-I: 30% evaluation
At the end of first month, all the groups are asked to give presentation on progress
made till date in front of committee consisting of HOD and project guides. The
projects are evaluated based on project idea, knowledge, amount of work done,
adherence to plan at every stage, motivation, interest shown, demonstration of skills
(hardware, software, presentation), self-motivation, sincerity, punctuality, ethics etc.
by the project guide and project evaluation committee.
Phase-II: 30% evaluation
The above activity is carried out at the end of second month. The students are
guided for preparation of project reports.

6
 Phase III: 40% evaluation
The above activity is carried out at the end of the semester along with demo and
submission of project report.
The internal evaluation will be done on the basis of following criteria and
weightage:

The student/ group will maintain the weekly report to monitor the progress of the
project.
b. External evaluation (50 marks) by expert from industry/institute (external
examiner)
The students demonstrate the prototype/ working projects and give powerpoint
presentation in front of
External examiner. Internal and external examiners evaluate the student on the
following aspects:
a. Understanding and completeness of the Project
b. Approach to the solution of problem
c. Planning and implementation
d. Design and testing procedure
e. Project Report
f. Students’ involvement in the Project

7
PROJECT DETAILS

Title:

Domain:

Name of Guide:

Name of Co-Guide (only for sponsored projects):

Problem Definition:

8
 STUDENT DETAILS

Name: Roll No.:

Contact: E-Mail:
Permanent Address:

Name: Roll No.:

Contact: E-Mail:
Permanent Address:

Name: Roll No.:

Contact: E-Mail:
Permanent Address:

9
 Schedule of Presentations and Demonstrations

Semester-VI
Date
Phase-I - Presentation and Submission of Synopsis

Phase-II- Presentation and partial implementation

Phase-III- Final demonstration/presentation and submission of Project Report

Project Guide

1
0
Week-01
Expected Task to be completed:
Details of discussion with the Guide

Signature: O9Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-02
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide:

Team Member 3: Date:

1
1
Week-03
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide:

Team Member 3: Date:

Week-04
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

1
2
 Partial Assessment Phase-I conducted on

Title and Problem Topic relevance and Synopsis approval

Definition objective Literature Categorization, Planning and
(05) Survey Cost Estimation
(05) (05)

M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4

Excellent: >=04 Excellent: >=04 Excellent: >=04

Good: 03 Good: 03 Good: 03
Acceptable: 02 Acceptable: 02 Acceptable: 02

Marks obtained by Member1:

Marks obtained by Member2:

Marks obtained by Member3:

Project guide

1
3
Week-05
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-06
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guid

Team Member 3: Date:

1
4
Week-07
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-08
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

1
5
Phase-II assessment conducted on

Topic outcome Methodology Partial Implementation (Mid review)

(05) (05) (05)

M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4

Excellent: >=04 Excellent: >=04 Excellent: >=04

Good: 03 Good: 03 Good: 03
Acceptable: 02 Acceptable: 02 Acceptable: 02

Marks obtained by Member1:

Marks obtained by Member2:

Marks obtained by Member3:

Project guide

1
6
Week-09
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-10
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

1
7
Week-11
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-12
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

1
8
Week-13
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-14
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide:

Team Member 3: Date:

1
9
Week-15
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

Week-16
Expected Task to be completed:
Details of discussion with the Guide

Signature: Team Member 1:

Team Member 2: Project Guide

Team Member 3: Date:

2
0
 Final Assessment Phase-III conducted on

Final project submission Demonstration/Presentation Final report

(05) (05) (10)

M1 M2 M3 M4 M1 M2 M3 M4 M1 M2 M3 M4

Excellent: >=04 Excellent: >=04 Excellent: >=08

Good: 03 Good: 03 Good: 06
Acceptable: 02 Acceptable: 02 Acceptable: 04

Marks obtained by Member1:

Marks obtained by Member2:

Marks obtained by Member3:

Final Assessment conducted by project guide

2
1
 Appendix-A Project Report Formatting Guidelines

A-1 Paper:
The report shall be printed on white bond paper, whiteness 95% or above, weight
70 gram or more per square meter. The size of the paper shall be standard A4; height 297
mm, width 210 mm.
A-2 Type Setting, Text Processing and Printing:
The text shall be printed on single side of a page employing laser jet or Inkjet printer, the
text having been processed using a standard text processor. The standard font shall be
“Times New Roman of 12 pts with 1.5 line spacing”.
Page Format: The Printed Sheets shall have the following written area and margins:
Top Margin : 15 mm
Left Margin : 30 mm
Right Margin : 20 mm
Bottom Margin : 22 mm
Head Height : 3 mm
Head Separation : 12 mm
Footer : 3 mm
Foot Separation : 10 mm
Text Height : 245 mm
Text Width : 160 mm
When header is not used the top margin shall be 30 mm.
Pagination:
Page numbering in the text of the report shall be Hindu numerals at the center of the
footer. Page number “1” for the first page of the chapter shall not appear in print; only
the second page will bear the number “2”. The subsequent chapters shall begin on a fresh
page. Pagination for pages before the Introduction chapter shall be in lower case
Roman numerals, e.g., “iv”.
Header:
When the header style is chosen, the header can have the Chapter number and Section
number (e.g., Chapter 2, Section 3) on even numbered page headers and Chapter title or
Section title on the odd numbered page header.
Paragraph format:
Vertical space between paragraphs shall be about 2.5 line spacing. The first line of each
paragraph should normally be indented by five characters or 12mm. A candidate may,
however, choose not to indent if she/he has provided sufficient paragraph
separation. A paragraph should normally comprise more than one line. A single line of a
paragraph shall not be left at the top or bottom of a page. The word at the right end of the
first line of a page or paragraph should, as far as possible, not be hyphenated.

2
2
A-3 Chapter and Section Format:
Chapter:
Each chapter shall begin on a fresh page with an additional top margin of about 75mm.
Chapter number and title shall be printed at the center of the line in 6mm font size 18pt
in bold face using both upper and lower case all capitals or small capitals shall not be
used. A vertical gap of about 12 mm spacing after font size 36 with single line spacing
shall be left between the Chapter number and Chapter title lines and between chapter title
line and the first paragraph.
Sections and Subsections:
A chapter can be divided into Sections, Subsections and Sub-sub Sections so as to
present different concepts separately. Sections and subsections can be numbered
using decimal points, e.g. 2.2 for the second section in Chapter 2 and 2.3.4 for the fourth
Subsection in third Section of Chapter 2. Chapters, Sections and Subsections shall be
included in the contents with page numbers flushed to the right. Further
subsections need not be numbered or included in the contents. The Section and section
titles along with their numbers in 5 and 4mm (16 and 14 pt) fonts, respectively, in bold
face shall be flushed to the left (not centered) with 15 mm space above and below these
lines. In further subdivisions character size of 3 and 3.5 with bold face, small caps, all
caps and italics may be used for the titles flushed left or centered. These shall not
feature in the contents.
Table / Figure Format:
Tables and figures should be presented in portrait style as far as possible. Small size
table and figures (less than half of writing area of a page) should be incorporated within
the text, while larger ones may be presented on separate pages. Table and
figures shall be numbered chapter wise. For example, the fourth figure in chapter 5 will
bear the number Figure 5.4 or Fig 5.4. Table number and title will be placed above the
table while the figure number and caption will be located below the figure. Reference for
Table and Figures reproduced from elsewhere shall be cited in the last and separate line
in the table and figure caption.

2
3
Appendix-B Contents of Synopsis Report

Title Sheet (Specimen

A) Abstract
The 500-word abstract shall highlight the important features of the
project report. The Abstract in the report, however, shall have two more parts, namely,
the layout of the thesis giving a brief chapter wise description of the work and the key
words.
Contents, List of Figures and Tables:
The contents shall follow the Abstract and shall enlist the titles of the chapters, section
and sub section using decimal notation, as in the text, with corresponding page
number against them, flushed to the right. Two separate lists of Figure captions and
Table titles along with their numbers and corresponding page numbers against them shall
follow the Contents.
Abbreviation Notation and Nomenclature:
A complete and comprehensive list of all abbreviations, notations and nomenclature
including Greek alphabets with subscripts and superscripts shall be provided after the list
of tables and figures. (As far as possible, generally accepted symbols and notation
should be used). Auxiliary page from dedication (if any) to abbreviations shall be
numbered using Roman numerals in lower case, while the text starting from the
Introduction shall be in Hindu Arabic. (The first pages in the both the cases shall not bear
a page number).
Chapter 1: Introduction
It shall justify and highlight the problem posed, define the topic and explain the aim and
scope of the work presented in the report. It may also highlight the significant
contributions from the investigation.
Chapter 2: Review of Literature
It shall present a critical appraisal of the previous work published in the literature
pertaining of the topic of the investigation.
Chapter 3: Report on Present Investigation
The reporting on the investigation shall be presented in one or more chapters with
appropriate chapter titles. Due importance shall be given to experimental setups,
procedures adopted, techniques developed, methodologies developed and adopted. While
important derivations/formulae should normally be presented in the text of these
chapters, extensive and long treatments, copious details and tedious information, detailed
results in tabular and graphical forms may be presented in Appendices. Representative
data in table and figures may, however, be included in appropriate chapters. Figures and
tables should be presented immediately following their first mention in the text. Short
tables and figures (say, less than half the writing area of the page) should be presented
within the text, while large table and figures may be presented on separate pages.
Equations should form separate
2
4
lines with appropriate paragraph separation above and below the equation line, with
equation numbers flushed to the right.
Chapter 4: Conclusion
This will be the final chapter of the report. A brief report of the work carried out shall
form the first part of the Chapter. Conclusions derived from the logical analysis
presented in the Results and Discussions Chapter shall be presented and clearly
enumerated, each point stated separately. Scope for future work should be stated lucidly
in the last part of the chapter.

Appendix
Detailed information, lengthy derivations, raw experimental observations etc. are to be
presented in the separate appendices, which shall be numbered in Roman Capitals (e.g.
“Appendix I”). Since reference can be drawn to published/unpublished literature in the
appendices these should precede the “Literature Cited” section.

Literature Cited/ references

This should follow the Appendices, if any, otherwise the Conclusions chapter. The
candidates shall follow the style of citation and style of listing in one of the standard
journals in the subject area consistently throughout his/her report, for example,
IEEE in the Department of Electrical Engineering, ASME in Department of Mechanical
Engineering. However, the names of all the authors along with their initials and the full
title of the article/monogram/book etc. have to be given in addition to the
journals/publishers, volume, number, pages(s) and year of publication. Citation from
websites should include the names(s) of author(s) (including the initials), full
title of the article, website reference and when last accessed. Reference to
personal communications, similarly, shall include the author, title of the communication
(if any) and date of receipt. Articles, technical notes etc. on the topic of the report
published by the candidate may be separately listed after the literature cited. This may
also be included in the contents. The candidates may also include reprints of his/her
publications after the literature citation.

Acknowledgements
The acknowledgments by the candidate shall follow the citation of literature, signed by
him /her, with date.

2
5
 Appendix-C Contents of Project Report

Contents of the Project Report will be the same as that of the Synopsis Report with few
additions as follows and few chapters added before the Conclusion chapter.

Title Sheet (Specimen A)

Certificate (Specimen B)

Approval sheet (Specimen C)

Letter of Sponsorship (If sponsored project)

Vision and Mission of Institute and Department

PSOs and PEOs of Programme

Abstract

Contents, List of Figures and Tables:

Abbreviation Notation and Nomenclature:

Chapter 1: Introduction

Chapter 2: Review of Literature

Chapter 3: Report on Present Investigation

Chapter 4: Conclusion
This will be the final chapter of the report. A brief report of the work carried out shall
form the first part of the Chapter. Conclusions derived from the logical analysis
presented in the Results and Discussions Chapter shall be presented and clearly
enumerated, each point stated separately. Scope for future work should be stated lucidly
in the last part of the chapter.

Appendix
Detailed information, lengthy derivations, raw experimental observations etc. are to be
presented in the separate appendices, which shall be numbered in Roman Capitals (e.g.

2
6
“Appendix I”). Since reference can be drawn to published/unpublished literature in the
appendices these should precede the “Literature Cited” section.

Literature Cited/ references

This should follow the Appendices, if any, otherwise the Conclusions chapter. The
candidates shall follow the style of citation and style of listing in one of the standard
journals in the subject area consistently throughout his/her report, for example,
IEEE in the Department of Electrical Engineering, ASME in Department of Mechanical
Engineering. However, the names of all the authors along with their initials and the full
title of the article/monogram/book etc. have to be given in addition to the
journals/publishers, volume, number, pages(s) and year of publication. Citation from
websites should include the names(s) of author(s) (including the initials), full
title of the article, website reference and when last accessed. Reference to
personal communications, similarly, shall include the author, title of the communication
(if any) and date of receipt. Articles, technical notes etc. on the topic of the report
published by the candidate may be separately listed after the literature cited. This may
also be included in the contents. The candidates may also include reprints of his/her
publications after the literature citation.

Acknowledgements
The acknowledgments by the candidate shall follow the citation of literature, signed by
him /her, with date.
Chapter 4: Implementation and Result
Details of algorithm or technique used in the system can be added here. The program
module having major contribution to the system can be also included along with
explanation. Some important snapshots or generated diagrams/tables can be included as
part of Result.

2
7
 Appendix-D Feedback survey by Co-Guide (only for sponsored projects)

Through this survey, we are requesting our co-guides to express their experience with
students of S.B.M. POLYTECHNIC, Mumbai. All responses will be used as quality
assessment tool to improve our academic policies. Evaluation Scheme: Excellent (5)/ Good
(3) / Acceptable (1)
Please mark tick (√) wherever
Parameter to review our students and their work applicable
Excellent Good Acceptable
Regular reporting by the students

Innovativeness/ Uniqueness of the idea being

implemented
Knowledge depth of the topic

Knowledge of Implementation Technology

Presentation and communication skills

Date: Name and Signature of Co-guide:

2
8
 Title Sheet (Specimen A)

Project Report

On

“POP-N-DINE”

Submitted in partial fulfilment of the requirement for the award of the

DIPLOMA IN COMPUTER ENGINEERING

By

BHAVYA GADA : B014

SHIVESH HEGDE : B017
MANTHAN KAWA : B021

Under the guidance of

Mr. PRATIK SHAH

Lecturer, Computer Engineering Department,

Shri Vile Parle Kelavani Mandal’s

SHRI BHAGUBHAI MAFATLAL POLYTECHNIC

Academic Year: 2024 - 2025

2
9
 Certificate (Specimen B)

Shri Vile Parle Kelavani Mandal’s

SHRI BHAGUBHAI MAFATLAL POLYTECHNIC

CERTIFICATE

This is to certify that the project entitled “POP-N-DINE” is a bonafide work of

BHAVYA GADA : B014

SHIVESH HEGDE : B017
MANTHAN KAWA : B021

Submitted in partial fulfilment of the requirement for the award of Diploma in Computer
Engineering.

Project Guide Head Principal

3
0
 Approval sheet (Specimen C)

Shri Vile Parle Kelavani Mandal’s

SHRI BHAGUBHAI MAFATLAL POLYTECHNIC

Approval Sheet

This is to certify that the project entitled “POP-N-DINE” is presented by

BHAVYA GADA : B014

SHIVESH HEGDE : B017
MANTHAN KAWA : B021

in partial fulfilment of the requirement for the award of Diploma in Computer Engineering.

Signature:

Name :
Internal Examiner

Signature:

Name :
External Examiner

Date:
Place: Mumbai

3
1
 Appendix-E Details of publications by the project members

Name of Conference/Journal/College:

Date/Month/Year of Publication:

Publication ID:

Other Details (If Any):

3
2
PROGRAMME OUTCOMES (POs)

1. Basic and Discipline specific knowledge: Apply knowledge of basic

mathematics, science and engineering fundamentals and engineering
specialization to solve the engineering problems.
2. Problem analysis: Identify and analyse well-defined engineering problems using
codified standard methods.
3. Design/ development of solutions: Design solutions for well-defined technical
problems and assist with the design of systems components or processes to meet
specified needs.
4. Engineering Tools, Experimentation and Testing: Apply modern engineering
tools and appropriate technique to conduct standard tests and measurements.
5. Engineering practices for society, sustainability and environment: Apply
appropriate technology in context of society, sustainability, environment and
ethical practices.
6. Project Management: Use engineering management principles individually, as a
team member or a leader to manage projects and effectively communicate about
well-defined engineering activities.
7. Life-long learning: Ability to analyse individual needs and engage in updating in
the context of technological changes

PROGRAMME SPECIFIC OUTCOMES (PSOs)

PSO1: Demonstrate the fundamental knowledge in the areas of Operating system, Web
Technology, Microprocessor based system and IOT by applying programming skills and
developing applications.

PSO2: Administer and manage Open source, Networking, Security and Database domains to
enhance student growth.

3
3
 COMPUTER ENGINEERING DEPARTMENT

Vision
Create a sustainable academic environment to produce highly competent computer
professionals of the future

Mission

M1. To expose students to latest tools and technologies in computing.

M2. To foster the professional development of students by providing excellence in
education.
M3. To Adapt rapid advancements in computing by engaging students in the lifelong
learning.
M4. To inculcate sound ethical,moral and social values amongst students for benefit of
the society.

Program Educational Objectives

The program educational objectives (PEOs) are to produce Computer professionals.

PEO1. Identify, design and solve computing problems by applying knowledge in
Computer engineering.
PEO2. Promote lifelong learning by integrating academic knowledge and practical
applications.
PEO3. Depict effective team work and practical skills for holistic development.

3
4