plain [CE]CollegeN ame, Departmentof ComputerEngineering2015−16[RE]1

SAVITRIBAI PHULE PUNE UNIVERSITY

A PROJECT REPORT ON

PROJECT TITLE

SUBMITTED TOWARDS THE

PARTIAL 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. Guide Name

collegelogo.png

DEPARTMENT OF COMPUTER ENGINEERING

College Name
College Address

1
 collegelogo.png

College Name
DEPARTMENT OF COMPUTER ENGINEERING

CERTIFICATE

This is to certify that the Project Entitled

PROJECT TITLE
Submitted by
Student Name Exam No:
Student Name Exam No:
Student Name Exam No:
Student Name Exam No:
is a bonafide work carried out by Students under the supervision of Prof.
Guide Name and it is submitted towards the partial fulfillment of the re-
quirement of Bachelor of Engineering (Computer Engineering).

Prof. Guide Name Prof. HOD Name

Internal Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.

Dr. A. V. Deshpande
Principal
Smt.Kashibai Navale College of Engineering

Signature of Internal Examiner Signature of External Ex-

aminer

2
 PROJECT APPROVAL SHEET

A Project Title

(Project Title)

Is successfully completed by

Student Name Exam No:

Student Name Exam No:
Student Name Exam No:
Student Name Exam No:

at

DEPARTMENT OF COMPUTER ENGINEERING

(COLLEGE NAME)

SAVITRIBAI PHULE PUNE UNIVERSITY,PUNE

ACADEMIC YEAR 2015-2016

Prof. Guide Name Prof. HOD Name

Internal Guide H.O.D
Dept. of Computer Engg. Dept. of Computer Engg.

3
College Short Form Name, Department of Computer Engineering 2015-16 0

I
 Abstract

Please Write here One Page Abstract. It should mainly include introduction,
motivation,outcome and innovation if any.

II
 Acknowledgments

Please Write here Acknowledgment.Example given as

It gives us great pleasure in presenting the preliminary project report on ‘BE
PROJECT TITLE’.

I would like to take this opportunity to thank my internal guide Prof. Guide
Name for giving me all the help and guidance I needed. I am really grateful
to them for their kind support. Their valuable suggestions were very helpful.

I am also grateful to Prof. HOD Name, Head of Computer Engineering

Department, CollegeName for his indispensable support, suggestions.

In the end our special thanks to Other Person Name for providing various
resources such as laboratory with all needed software platforms, continuous
Internet connection, for Our Project.

Student Name1
Student Name2
Student Name3
Student Name4
(B.E. Computer Engg.)

III
Contents

IV
List of Figures

V
List of Tables

VI
[display] 0 1pc

[
]

VIII
Chapter 1

Synopsis

1.1 Project Title

Project Title

1.2 Project Option

Please mention type either industry sponsored, entrepreneur or internal project

1.3 Internal Guide

Prof. Internal Guide Name

1.4 Sponsorship and External Guide

Please write if any sponsorship

1.5 Technical Keywords (As per ACM Key-

words)
Please note ACM Keywords can be found : http://www.acm.org/about/class/ccs98-
html
Example is given as
1. C. Computer Systems Organization
(a) C.2 COMPUTER-COMMUNICATION NETWORKS

IX
 i. C.2.4 Distributed Systems
A. Client/server
B. Distributed applications
C. Distributed databases
D. Network operating systems
E. Distributed file systems
F. Security and reliability issues in distributed applications

1.6 Problem Statement

Define Problem Statement

1.7 Abstract
• Abstract (10 to 15 lines)

1.8 Goals and Objectives

• Objectives

1.9 Relevant mathematics associated with the

Project
System Description:
• Input:
• Output:
• Identify data structures, classes, divide and conquer strategies to ex-
ploit distributed/parallel/concurrent processing, constraints.
• Functions : Identify Objects, Morphisms, Overloading in functions,
Functional relations
• Mathematical formulation if possible
• Success Conditions:
• Failure Conditions:

X
1.10 Names of Conferences / Journals where
papers can be published
• IEEE/ACM Conference/Journal 1

• Conferences/workshops in IITs

• Central Universities or SPPU Conferences

• IEEE/ACM Conference/Journal 2

1.11 Review of Conference/Journal Papers sup-

porting Project idea
Atleast 10 papers + White papers or web references
Brief literature survey [ Description containing important description of at
least 10 papers

1.12 Plan of Project Execution

Using planner or alike project management tool.

XI
Chapter 2

Technical Keywords

2.1 Area of Project

Project Area

2.2 Technical Keywords

Please note ACM Keywords can be found : http://www.acm.org/about/class/ccs98-
html
Example is given as

1. C. Computer Systems Organization

(a) C.2 COMPUTER-COMMUNICATION NETWORKS

i. C.2.4 Distributed Systems
A. Client/server
B. Distributed applications
C. Distributed databases
D. Network operating systems
E. Distributed file systems
F. Security and reliability issues in distributed applications

XII
Chapter 3

Introduction

3.1 Project Idea

• Project Idea

3.2 Motivation of the Project

• Motivation of the Project

3.3 Literature Survey

• Review of the papers, Description , Mathematical Terms

XIII
Chapter 4

Problem Definition and scope

4.1 Problem Statement

Description of Problem

4.1.1 Goals and objectives

Goal and Objectives:

• Overall goals and objectives of software, input and output description

with necessary syntax, format etc are described

4.1.2 Statement of scope

• A description of the software with Size of input, bounds on input,
input validation, input dependency, i/o state diagram, Major inputs,
and outputs are described without regard to implementation detail.

• The scope identifies what the product is and is not, what it will and
wont do, what it will and wont contain.

4.2 Major Constraints

• Any constraints that will impact the manner in which the software is
to be specified, designed, implemented or tested are noted here.

XIV
4.3 Methodologies of Problem solving and ef-
ficiency issues
• The single problem can be solved by different solutions. This considers
the performance parameters for each approach. Thus considers the
efficiency issues.

4.4 Outcome
• Outcome of the project

4.5 Applications
• Applications of Project

4.6 Hardware Resources Required

Sr. No. Parameter Minimum Requirement Justification

1 CPU Speed 2 GHz Remark Required
2 RAM 3 GB Remark Required

Table 4.1: Hardware Requirements

4.7 Software Resources Required

Platform :

1. Operating System:

2. IDE:

3. Programming Language

XV
Chapter 5

Project Plan

5.1 Project Estimates

Use Waterfall model and associated streams derived from assignments 1,2,
3, 4 and 5( Annex A and B) for estimation.

5.1.1 Reconciled Estimates

5.1.1.1 Cost Estimate
5.1.1.2 Time Estimates

5.1.2 Project Resources

Project resources [People, Hardware, Software, Tools and other resources]
based on Memory Sharing, IPC, and Concurrency derived using appendices
to be referred.

5.2 Risk Management w.r.t. NP Hard anal-

ysis
This section discusses Project risks and the approach to managing them.

5.2.1 Risk Identification

For risks identification, review of scope document, requirements specifications
and schedule is done. Answers to questionnaire revealed some risks. Each
risk is categorized as per the categories mentioned in [?]. Please refer table ??
for all the risks. You can refereed following risk identification questionnaire.

XVI
 1. Have top software and customer managers formally committed to sup-
port the project?

2. Are end-users enthusiastically committed to the project and the sys-

tem/product to be built?

3. Are requirements fully understood by the software engineering team

and its customers?

4. Have customers been involved fully in the definition of requirements?

5. Do end-users have realistic expectations?

6. Does the software engineering team have the right mix of skills?

7. Are project requirements stable?

8. Is the number of people on the project team adequate to do the job?

9. Do all customer/user constituencies agree on the importance of the

project and on the requirements for the system/product to be built?

5.2.2 Risk Analysis

The risks for the Project can be analyzed within the constraints of time and
quality

Impact
ID Risk Description Probability
Schedule Quality Overall
1 Description 1 Low Low High High
2 Description 2 Low Low High High

Table 5.1: Risk Table

5.2.3 Overview of Risk Mitigation, Monitoring, Man-

agement
Following are the details for each risk.

XVII
 Probability Value Description
High Probability of occurrence is > 75%
Medium Probability of occurrence is 26 − 75%
Low Probability of occurrence is < 25%

Table 5.2: Risk Probability definitions [?]

Impact Value Description

Very high > 10% Schedule impact or Unacceptable quality
High 5 − 10% Schedule impact or Some parts of the project have
low quality
Medium < 5% Schedule impact or Barely noticeable degradation
in quality Low Impact on schedule or Quality can
be incorporated

Table 5.3: Risk Impact definitions [?]

Risk ID 1
Risk Description Description 1
Category Development Environment.
Source Software requirement Specification document.
Probability Low
Impact High
Response Mitigate
Strategy Strategy
Risk Status Occurred

XVIII
Risk ID 2
Risk Description Description 2
Category Requirements
Source Software Design Specification documentation review.
Probability Low
Impact High
Response Mitigate
Strategy Better testing will resolve this issue.
Risk Status Identified

Risk ID 3
Risk Description Description 3
Category Technology
Source This was identified during early development and test-
ing.
Probability Low
Impact Very High
Response Accept
Strategy Example Running Service Registry behind proxy bal-
ancer
Risk Status Identified

XIX
5.3 Project Schedule
5.3.1 Project task set
Major Tasks in the Project stages are:

• Task 1:

• Task 2:

• Task 3:

• Task 4:

• Task 5:

5.3.2 Task network

Project tasks and their dependencies are noted in this diagrammatic form.

5.3.3 Timeline Chart

A project timeline chart is presented. This may include a time line for the
entire project. Above points should be covered in Project Planner as Annex
C and you can mention here Please refer Annex C for the planner

5.4 Team Organization

The manner in which staff is organized and the mechanisms for reporting are
noted.

5.4.1 Team structure

The team structure for the project is identified. Roles are defined.

5.4.2 Management reporting and communication

Mechanisms for progress reporting and inter/intra team communication are
identified as per assessment sheet and lab time table.

XX
Chapter 6

Software requirement
specification

6.1 Introduction
6.1.1 Purpose and Scope of Document
The purpose of SRS and what it covers is to be stated

6.1.2 Overview of responsibilities of Developer

What all activities carried out by developer?

6.2 Usage Scenario

This section provides various usage scenarios for the system to be developed.

6.2.1 User profiles

The profiles of all user categories are described here.(Actors and their De-
scription)

6.2.2 Use-cases
All use-cases for the software are presented. Description of all main Use cases
using use case template is to be provided.

XXI
 Sr No. Use Case Description Actors Assumptions
1 Use Case 1 Description Actors Assumption

Table 6.1: Use Cases

6.2.3 Use Case View

Use Case Diagram. Example is given below

use-case.jpg

Figure 6.1: Use case diagram

XXII
6.3 Data Model and Description
6.3.1 Data Description
Data objects that will be managed/manipulated by the software are described
in this section. The database entities or files or data structures required to
be described. For data objects details can be given as below

6.3.2 Data objects and Relationships

Data objects and their major attributes and relationships among data objects
are described using an ERD- like form.

6.4 Functional Model and Description

A description of each major software function, along with data flow (struc-
tured analysis) or class hierarchy (Analysis Class diagram with class descrip-
tion for object oriented system) is presented.

6.4.1 Data Flow Diagram

6.4.1.1 Level 0 Data Flow Diagram
6.4.1.2 Level 1 Data Flow Diagram

6.4.2 Activity Diagram:

• The Activity diagram represents the steps taken.

6.4.3 Non Functional Requirements:

• Interface Requirements

• Performance Requirements

• Software quality attributes such as availability [ related to Reliabil-

ity], modifiability [includes portability, reusability, scalability] , perfor-
mance, security, testability and usability[includes self adaptability and
user adaptability]

XXIII
6.4.4 State Diagram:
State Transition Diagram
Fig.?? example shows the state transition diagram of Cloud SDK. The states
are represented in ovals and state of system gets changed when certain events
occur. The transitions from one state to the other are represented by arrows.
The Figure shows important states and events that occur while creating new
project.

state-dig.jpg

Figure 6.2: State transition diagram

6.4.5 Design Constraints

Any design constraints that will impact the subsystem are noted.

6.4.6 Software Interface Description

The software interface(s)to the outside world is(are) described. The require-
ments for interfaces to other devices/systems/networks/human are stated.

XXIV
Chapter 7

Detailed Design Document

using Appendix A and B

7.1 Introduction
This document specifies the design that is used to solve the problem of Prod-
uct.

7.2 Architectural Design

A description of the program architecture is presented. Subsystem design or
Block diagram,Package Diagram,Deployment diagram with description is to
be presented.

7.3 Data design (using Appendices A and B)

A description of all data structures including internal, global, and temporary
data structures, database design (tables), file formats.

7.3.1 Internal software data structure

Data structures that are passed among components the software are de-
scribed.

XXV
arch2.jpg

Figure 7.1: Architecture diagram

XXVI
7.3.2 Global data structure
Data structured that are available to major portions of the architecture are
described.

7.3.3 Temporary data structure

Files created for interim use are described.

7.3.4 Database description

Database(s) / Files created/used as part of the application is(are) described.

7.4 Compoent Design

Class diagrams, Interaction Diagrams, Algorithms. Description of each com-
ponent description required.

7.4.1 Class Diagram

XXVII
class-dig.jpg

Figure 7.2: Class Diagram

XXVIII
Chapter 8

Project Implementation

8.1 Introduction
8.2 Tools and Technologies Used
8.3 Methodologies/Algorithm Details
8.3.1 Algorithm 1/Pseudo Code
8.3.2 Algorithm 2/Pseudo Code

8.4 Verification and Validation for Acceptance

XXIX
Chapter 9

Software Testing

9.1 Type of Testing Used

Unit,Integration,system etc.

9.2 Test Cases and Test Results

for each type of testing done.

XXX
Chapter 10

Results

10.1 Screen shots

Outputs / Snap shots of the results

10.2 Outputs
Outputs / Snap shots of the results

XXXI
Chapter 11

Deployment and Maintenance

11.1 Installation and un-installation

11.2 User help

XXXII
Chapter 12

Conclusion and Future Scope

Write summary , conclusion and future scope

XXXIII
References

(Strictly in ACM Format)

XXXIV
Annexure A

Laboratory assignments on
Project Analysis of Algorithmic
Design

• To develop the problem under consideration and justify feasibilty using

concepts of knowledge canvas and IDEA Matrix.
Refer [?] for IDEA Matrix and Knowledge canvas model. Case studies
are given in this book. IDEA Matrix is represented in the following
form. Knowledge canvas represents about identification of opportunity
for product. Feasibility is represented w.r.t. business perspective.

I D E A
Increase Drive Educate Accelerate
Improve Deliver Evaluate Associate
Ignore Decrease Eliminate Avoid

Table A.1: IDEA Matrix

• Project problem statement feasibility assessment using NP-Hard, NP-

Complete or satisfy ability issues using modern algebra and/or relevant
mathematical models.

• input x,output y, y=f(x)

XXXV
Annexure B

Laboratory assignments on
Project Quality and Reliability
Testing of Project Design

It should include assignments such as

• Use of divide and conquer strategies to exploit distributed/parallel/concurrent

processing of the above to identify object, morphisms, overloading in
functions (if any), and functional relations and any other dependencies
(as per requirements). It can include Venn diagram, state diagram,
function relations, i/o relations; use this to derive objects, morphism,
overloading

• Use of above to draw functional dependency graphs and relevant Soft-

ware modeling methods, techniques including UML diagrams or other
necessities using appropriate tools.

• Testing of project problem statement using generated test data (using

mathematical models, GUI, Function testing principles, if any) selec-
tion and appropriate use of testing tools, testing of UML diagram’s
reliability. Write also test cases [Black box testing] for each identified
functions. You can use Mathematica or equivalent open source tool for
generating test data.

• Additional assignments by the guide. If project type as Entreprenaur,

Refer [?],[?],[?], [?]

XXXVI
Annexure C

Project Planner

Using planner or alike project management tool.

XXXVII
Annexure D

Reviewers Comments of Paper

Submitted

(At-least one technical paper must be submitted in Term-I on the project de-
sign in the conferences/workshops in IITs, Central Universities or UoP Con-
ferences or equivalent International Conferences Sponsored by IEEE/ACM)

1. Paper Title:

2. Name of the Conference/Journal where paper submitted :

3. Paper accepted/rejected :

4. Review comments by reviewer :

5. Corrective actions if any :

XXXVIII
Annexure E

Plagiarism Report

Plagiarism report

XXXIX
Annexure F

Term-II Project Laboratory

Assignments

1. Review of design and necessary corrective actions taking into consid-

eration the feedback report of Term I assessment, and other competi-
tions/conferences participated like IIT, Central Universities, University
Conferences or equivalent centers of excellence etc.

2. Project workstation selection, installations along with setup and instal-

lation report preparations.

3. Programming of the project functions, interfaces and GUI (if any) as

per 1 st Term term-work submission using corrective actions recom-
mended in Term-I assessment of Term-work.

4. Test tool selection and testing of various test cases for the project per-
formed and generate various testing result charts, graphs etc. including
reliability testing.
Additional assignments for the Entrepreneurship Project:

5. Installations and Reliability Testing Reports at the client end.

XL
Annexure G

Information of Project Group

Members

one page for each student .

XLI
 prashant.jpg

1. Name :

2. Date of Birth :

3. Gender :

4. Permanent Address :

5. E-Mail :

6. Mobile/Contact No. :

7. Placement Details :

8. Paper Published :

XLII