St.

John College of Engineering and Management

Project Title

Presented by: Guided by:

First_Name Surname (PID No.) Mr./Ms./Mrs./Dr. First_Name Surname
First_Name Surname (PID No.)
First_Name Surname (PID No.)

Department of Computer Engineering 1

Contents:
• Abstract • System Architecture
• Introduction to Domain • System Design
• Problem Definition • Observations
• Proposed System • Results
• Objectives • Conclusion
• Scope • Future Scope
• Literature Survey • References
• Requirement Analysis

Department of Computer Engineering 2

Abstract:
The 500-word abstract shall highlight the important features of the
mini-project and shall correspond to the electronic version to be
submitted to the Library for inclusion in the website. Abstract is simply
a short, stand-alone summary of the work that others can use as an
overview. An abstract describes what you do in your mini-project. It
should help the reader to understand the mini-project. To write an
abstract, finish your Literature review first, then type a summary that
identifies the purpose, problem, methods, results, and conclusion of
your work. After you get the details down, all that's left is to format it
correctly.

Department of Computer Engineering 3

Introduction to Domain:
• This part should consist of only one slides.
• The introduction to domain should consist of general description of
the domain in brief.
• Introduction should also describe relevance of domain with respect to
mini-project.

Department of Computer Engineering 4

Introduction to Domain:
Example:
• Image processing is a method to convert an image into digital form
and perform some operations on it, in order to get an enhanced
image or to extract some useful information from it.
• It is a type of signal dispensation in which input is image, like video
frame or photograph and output may be image or characteristics
associated with that image.

Department of Computer Engineering 5

Problem Statement:
• A problem statement is a clear description of the issue(s) of the
existing systems.
• A problem statement expresses the words that will be used to keep
the effort focused and it should represent a solvable problem.
• Solution for the problem should not be mentioned in this slide.
• Problem statement should be drafted in bulleted points(maximum 2
to 3)

Department of Computer Engineering 6

Proposed System:
• The proposed system should clearly define the core idea/solution to
the problem statement(s).
• Title of the project should be stated along with proper justification.

Department of Computer Engineering 7

Objectives:
• Objectives, should be specific statements that define measurable
outcomes.
• E.g. what steps will be taken to achieve the desired outcome.

Department of Computer Engineering 8

Scope:
• The scope of a project is the clear identification of the work that is
required to successfully complete or deliver a project.
• The scope of the project will explain the boundaries of the project.
• The scope clearly states what the project is supposed to achieve and
what it cannot accomplish.

Department of Computer Engineering 9

Literature Survey I:
• Summarize the research paper 1 using few points.
• Note: Proper citation number must be used according to
“references” slide.

Department of Computer Engineering 10

Literature Survey I:
• System Architecture:

Department of Computer Engineering 11

Literature Survey I:
Advantages:
• Advantage 1
• Advantage 2
• Advantage 3

Disadvantages:
• Disadvantage 1
• Disadvantage 2
• Disadvantage 3

Department of Computer Engineering 12

Literature Survey II:
• Summarize the research paper 1 using few points.
• Note: Proper citation number must be used according to
“references” slide.

Department of Computer Engineering 13

Literature Survey II:
System Architecture:

Department of Computer Engineering 14

Literature Survey II:
Advantages:
• Advantage 1
• Advantage 2
• Advantage 3

Disadvantages:
• Disadvantage 1
• Disadvantage 2
• Disadvantage 3

Department of Computer Engineering 15

Literature Survey III:
• Summarize the research paper 1 using few points.
• Note: Proper citation number must be used according to
“references” slide.

Department of Computer Engineering 16

Literature Survey III:
System Architecture:

Department of Computer Engineering 17

Literature Survey III:
Advantages:
• Advantage 1
• Advantage 2
• Advantage 3

Disadvantages:
• Disadvantage 1
• Disadvantage 2
• Disadvantage 3

Department of Computer Engineering 18

Requirement Analysis:
Functional Requirements:
• Functional requirement should describe all the requirement
functionality or system services.
• Functional requirement are heavily dependent on the type of
software, expected user and type of system where the software is
used.

Department of Computer Engineering 19

Requirement Analysis:
Functional Requirements:
Example:
• In developing the web application for the auto car shop, some of the
functional requirements could include:
• The web application shall accept customer orders
• The web application shall be able to cash a sale
• The web application shall produce a receipt detailing a customers’
purchase information and include name of customer, items purchased, cost
of each item and total cost
• The web application shall be able to produce weekly, monthly and yearly
reports about sales
Department of Computer Engineering 20
Requirement Analysis:
Non-Functional Requirements:
Non-functional requirements are not concerned with the functions of the
system.
Non-functional requirements can include things like response time and
reliability.
 It can also be closely tied to user satisfaction.
Example:
• The web application shall be easy to use by all employees including sales
representatives and managers
• The web application shall be available in several languages
• The web application shall allow several sales to be made at the same time
without downgrading performance
Department of Computer Engineering 21
Requirement Analysis:
Hardware Requirements:
Note: Requirements should be specific in nature.
For example,
• Intel Core i7 8086K Coffee Lake Processor 4.0GHz
• Raspberry Pi 3 Model B+ (1.4GHz 64-bit quad-core processor)

Department of Computer Engineering 22

Requirement Analysis:
Software Requirements:
Note: Requirements should be specific in nature.
For example,
• Java SE Development Kit 11.0.1
• Eclipse IDE 4.10 (2018-12 R)

Department of Computer Engineering 23

System Architecture:
Refer Folder named “system-arch” for System Architecture diagrams.

Department of Computer Engineering 24

System Design:
• Refer the following link for drawing DFD level 0, 1 & 2:
https://www.tutorialspoint.com/software_engineering/software_anal
ysis_design_tools.html
• ER Diagram (If Database is used)
• Class Diagram
• Use Case Diagram
• Activity Diagram
• Sequence Diagram

Department of Computer Engineering 25

Observations:
• Observations may contain snapshots of the working project.
• Small description should accompany the snapshots.

Department of Computer Engineering 26

Results:
• Present your results in a logical sequence, highlighting what is
important and how the data you obtained have been analyzed to
provide the results you discuss.
• You should discuss what you infer from the data.

Department of Computer Engineering 27

Conclusion:
Your conclusions needs to do three main things:
• Recap what you did. In about one paragraph recap what your
research question was and how you tackled it.
• Highlight the big accomplishments, explaining the highlights of the
results.
• Finally, finish off with a sentence or two that wraps up your project.

Department of Computer Engineering 28

Future Scope:
• It should let people know what you’re thinking of doing next.
• It should just provide enough information as to a possible research
path and why the path may be important.

Department of Computer Engineering 29

References:
Refer the following link for writing the references:
https://libguides.murdoch.edu.au/IEEE/sample

[1] A. Rezi and M. Allam, "Techniques in array processing by means of

transformations, " in Control and Dynamic Systems, Vol. 69, Multidemsional
Systems, C. T. Leondes, Ed. San Diego: Academic Press, 1995, pp. 133-180.
[2] G. O. Young, "Synthetic structure of industrial plastics," in Plastics, 2nd
ed., vol. 3, J. Peters, Ed. New York: McGraw-Hill, 1964, pp. 15-64.
[3] S. M. Hemmington, Soft Science. Saskatoon: Univ. of Saskatchewan Press,
1997.

Department of Computer Engineering 30