“Title of Project Based Learning”
Submitted to the
Savitribai Phule Pune University
In partial fulfillment for the award of the Degree of
Bachelor of Engineering
in
Information Technology
by
FirstName Last Name
(Exam Seat No. / Roll No. & Division)
Under the guidance of
Prof. Name of the Guide
Department of (Branch Name)
PVGCOET & GKPIM, Pune
Pune, Maharashtra 411009
2022-23
CERTIFICATE
This is to certify that the project-based learning report entitled “Title of Project Based
Learning” being submitted by Name of Students (Exam Seat No. / Roll No. & Division) is a
record of bonafide work carried out by him/her under the supervision and guidance of Guide
Name in partial fulfillment of the requirement for SE (Branch Name) 2019 course of
Savitribai Phule Pune University, Pune in the academic year 2022-23.
Date:
Place: Pune
Guide Head of the Department
ACKNOWLEDGEMENT
Purpose of acknowledgements page is to show appreciation to those who contributed in
conducting this dissertation work / other tasks and duties related to the report writing. Therefore,
when writing acknowledgements page, you should carefully consider everyone who helped
during research process and show appreciation in the order of relevance. In this regard it is
suitable to show appreciation in brief manner instead of using strong emotional phrases.
In this part of your work, it is normal to use personal pronouns like “I, my, me” while in the rest
of the report this articulation is not recommended. Even when acknowledging family members
and friends make sure of using the wording of a relatively formal register. The list of the persons
you should acknowledged, includes guide (main and second), academic staff in your department,
technical staff, reviewers, companies, family and friends.
You should acknowledge all sources of funding. It’s usually specific naming the person and the
type of help you received. For example, an advisor who helped you conceptualize the project,
someone who helped with the actual building or procedures used to complete the project,
someone who helped with computer knowledge, someone who provided raw materials for the
project, etc.
(Students Name & Signature)
CONTENTS
Sr. No TITLE Page no
Abstract
1. INTRODUCTION 2
1. Introduction and Objectives
1. Motivation
2. Objective
2. Purpose of the project
3. Existing System and Disadvantages
4. Proposed System with Features
2. LITERATURE SURVEY 4
3. SYSTEM REQUIREMENTS 5
SPECIFICATIONS
5. Functional / Non-Functional
Requirement
6. Software Requirement
4. 7.Hardware
6
Requirement SYSTEM
DESIGN
8. Process Model
9. System Block Diagram
5. GRAPHICAL USER
/Architecture INTERFACE
Diagram 9
10. UML Diagrams / ER
6. FUTURE ENHANCEMENTS
Diagram 19
7. CONCLUSION 20
8. REFERENCES 21
ABSTRACT
Most difficult and important component of project report is to write abstract. Presented at the
beginning of the report, it is likely the first substantive description of your work read by an
external examiner/reader. You should view it as an opportunity to set accurate expectations.
The abstract is a summary of the whole project work.
It presents all the major elements of your work in a highly condensed form. An abstract often
functions, together with the project title, as a stand-alone text. An abstract is not merely an
introduction in the sense of a preface, preamble, or advance organizer that prepares the reader
for the report.
In addition to that function, it must be capable of substituting for the whole report when there
is insufficient time and space for the full text. The final version of the abstract will need to be
written after you have finished reading your report for the last time. However, if you think
about what it has to contain, you realize that the abstract is really a summary of your
project/seminar work.
Your abstract should answer specific questions: What was done? Why was it done? How was it
done? What was found? What is the significance of the findings?
1. INTRODUCATION
5|Page
1. Introduction to Project
Students are expected to write brief introduction of the project topic. This section may be
common for all the students of that group. However, students can have different approach in
explaining their project.
Since we are not going to get separate project report from the students, it is good to have one
or two pages common for all the students of that project. Once this project introduction and
aim objectives of explained, students can start with actual seminar content writing.
1. Motivation behind project topic
Students are expected to write “Why they thought about this project”. They could also explain
the “Explain need of the project”. Any statement which motivated to take up this project
2. Aim and Objective(s) of the work
Project aims are a statement of the overall “Why” of the project. A project aim is a statement
starting with the words: “The aim of this project is…”
That statement tells the reader what your overall goal is, what it is you want to achieve. It does
not go into details or describe specific tasks.
Project objectives tell the “How” of the project aim. You want to achieve your goal and the
objectives state how this will be done – what major tasks will be undertaken and what your
major targets are. Most projects will have between six and nine objectives. A project objective
is usually a statement starting with the words “To…”
Objectives are subsidiary to aims and are the steps you are going to take to answer your
problem statement or a specific list of tasks needed to accomplish the goals of the project. This
must be highly focused and feasible and should address the more immediate project outcomes
Guide must personnel check these aim and objectives and make students write these
statements properly.
6|Page
2. Purpose of the project
3. Existing System and Disadvantages
4. Proposed System with Features
2. LITERATURE SURVEY
Students are expected to write similar or related work already done by various researchers.
They could also explain existing tools/technologies in this section. There advantages and
disadvantages of each method or technique. They should also explain how their project is
different from those existing systems. You need to read lot of books/ papers/ magazines for
making this survey.
7|Page
3. SYSTEM REQUIREMENTS SPECIFICATIONS
In this chapter, you have to mentioned all system requirements specifications for
project-based learning including functional /non-functional requirement, software
requirement and hardware requirement.
8|Page
4. SYSTEM DESIGN
4.1 Process Model (Methodology)
There are various software development approaches defined and designed
which are employed during development process of software. These software
approaches are also referred as "Software Development Process Models". Each
process model follows a particular life cycle in orderto ensure success in process of
9|Page
software development. One such software approach used here is "The Waterfall
Model".
Waterfall software approach was first Process Model to be introduced and
followed widely in Software Engineering to ensure success of the project. In "The
Waterfall" software approach, the whole process of software development is divided
into separate process phases. The phases in Waterfall model are Requirement
Specifications phase, Software Design, Implementation and Testing and there are
various software development software approaches defined and designed which are
used during development process of software; these software approaches are also
referred as "Software Development Process Models".
Each process model follows a particular life cycle in order to ensuresuccess in
process of software development. One such software approach/process used in
Software Development is "The Waterfall Model". Waterfall software approach was
first Process Model to be introduced andfollowed widely in Software Engineering to
ensure success of the project. In"The Waterfall" software approach, the whole process
of software development is divided into Maintenance.
All these phases are cascaded to each other so that second phase isstarted as
and when defined set of goals are achieved for first phase and it issigned off, so the
name "Waterfall Model".
Fig: General Overview of Waterfall Process Model
4.2 System Block Diagram /Architecture Diagram
In this section, you have to specify the System Block Diagram /Architecture Diagram of your
project
10 | P a g e
4.3 UML Diagrams / ER Diagram
In this section, specify the UML diagrams / ER Diagram of your
project
11 | P a g e
Example: Sample Use Case Diagram
5. GRAPHICAL USER INTERFACE
This chapter, include screen shots/graphical user interface design of your
project
12 | P a g e
6. FUTURE ENHANCEMENTS
13 | P a g e
7. CONCLUSION
14 | P a g e
8. REFERENCES
List all the material used from various sources for making this project proposals
1Journal article – A. A. Author of article. "Title of article," Title of Journal, vol. #, no. #, pp.
page number/s, Month year.
2Books- Author's last name, first initial. (Publication date). Book title. Additional
information. City of publication: Publishing company.
3Magazine - Author's last name, first initial. (Publication date). Article title. Periodical
title, volume number (issue number if available), inclusive pages
4Website or Webpage Author's name. (Date of publication). Title of article. Title of
Periodical, volume number, Retrieved month day, year, from full URL
15 | P a g e
