Project Management

Sanjay Prasad Kushwaha

5/2/17 1
 Contents

Introduction
Project
Input
Output
Processing
Research Paper Oriented
Latex Report Writing Skills
Documentation Details
Poster Presentation
On Same topic or related area
Presentation
On the project

5/2/17 2
 Objective
The project may be done using any programming
language.

Type of application e.g. scientific application,

Information System, Games, Simulations, etc.

Student are required to do analysis, design,

coding, testing of the system that they develop.

Students must come up with a final output of

project.

5/2/17 3
 Project Work Timing /
Schedules
Activities Dates for the Fall 2013

Project Proposal Defense

Mid term Project Demo

Final Project Presentation

5/2/17 4
 Project Work Documents
There are three types of project work
documents to be submitted in different
occasions are:

Project Proposal

Mid-term Progress Report

Final Project Report (with output)

5/2/17 5
 Project Work Proposal
Students are required to come up
with a conceptual framework for their
project work.

Following sections are needed in

document(8-10 pages)

5/2/17 6
 Proposal includes
Title page
Abstract (with keywords)-250 words
Introduction
Problem Statement
Research Objectives
Significance of study
Methodology (Proposed)
Literature Study / Review (present if any)
Deliverables / Output (Proposed)
Bibliography / References
5/2/17 7
 Mid-term Progress Report
Design documents which shall comprise of
architectural design of proposed system.

Mid-term report should be built on the

proposal document with adding sections of
your work

An Appendix section at end of document

(like source codes of program, installation
and operation procedure of experiment).
5/2/17 8
 The Final Project Report
The final project report is prepared
by completing the section of your
work details.

Adding sections like conclusion and

further works but removing section
Deliverables.

5/2/17 9
 Contains of Final Report
Cover pages
Title Page
Abstract ( with keywords) 1 page
Problem Statement
Objectives
Significance of the study
Methodology

5/2/17 10
 Literature study/ Review
Sections of your work details
Conclusion
Further Works/ Recommendations
Bibliography / References
Appendix (if any)

5/2/17 11
 Format of the Project
Report:
Paper Size: A4 Plain white
Print at: Single side
Page Layout:
Orientation: Portrait
Margin: 1 inch each side
Binding Offset: 0.5 inch at the left (gutter
margin)
Spaces between lines: 1.5 inches
Paragraph Spacing 6 pt. before and after
Page Numbers: At the bottom center showing
total no. of pages e.g. [15/58]
Headers: Title of the thesis

5/2/17 12
Document contents:
Normal Text: Font name: Times New Roman
Font Size: 12 pt.
Font Style: Regular
Heading: Stepwise increment from the
normal text
Font style may be Italic and/or
Bold Faces
Document Organization:
Section Should start with on a
new page
Section headings should be
numbered in Legal style

5/2/17 13
 Thesis Contents:
Acknowledgements
Abstract
List of figures
Chapter 1: Introduction
1.1 : Introduction of superset
1.2 : Statement of Problems
1.3 : Objectives
1.4 Scope and Limitations
1.5 Thesis Organization
5/2/17 14
 Chapter 2: Literature Review
2.1 : Background
2.2 Related Works
2.3 Related Algorithms
2.4 Limitation of previous works

5/2/17 15
 Chapter 3: Methodology
3.1 Research Framework
3.2 Explanation of Each parts of
Framework
3.3 Choice of Algorithm and Statistical
Methods
3.4 Tools
3.5 Performance Parameters

5/2/17 16
 Chapter 4: Results and Discussions
4.1 Result
4.2 Analysis of Results
4.3 Comparisons
4.4 Descriptions of result

5/2/17 17
 Chapter 5: Conclusion and Future
works
5.1 Conclusion
5.2 Future works

References
Appendices

5/2/17 18
 Class
SRS
Literature Review
Design Documents
Research Framework
Results
Conclusions

5/2/17 19
 Next Class
Topic
Abstract

5/2/17 20
 How to prepare project synopsis

Synopsis provides an outline of

project work to be undertaken

Select a suitable topic, define the

problems and outline the manner in
which project study is to be
conducted,

Next step is to prepare synopsis

5/2/17 21
 Format of Synopsis
Title of the project
Abstract
Introduction:
Types
Previous method
Cycle ( Model of System)
Statement about the problem
Clearly define problem in terms of nature,
size and scope of project
5/2/17 22
 Objective:
Reasons for selecting topic have to be explained along with
applicability or usefulness.
Scope:
What contribution the project can make in the selected
organization
Methodology:
Explain criteria for selection of sample size of data.
Statistical method used.
Results:
Conclusion and Discussion
Future works:
References:

5/2/17 23
 Tips for writing Abstract
Abstract is a brief paragraph (or two)
limited 250 words highlighting,
summarizing the major point of project.

A Clear and Simple Summary.

Emphasize: Purpose ( Hypothesis),

methods ( procedures used), data
summary or analysis, Conclusions.
5/2/17 24
 Focus only on current years research.
Omit details and discussions
Use past tense when describing what was
done.
Where appropriate use active verbs rather
than passive verbs.
Use short sentences.
Use complete sentences. Dont abbreviate
by omitting articles or small words

5/2/17 25
 Do NOT include:
Acknowledgements,
Self promotion,
Name of teacher, school,
Research institution,
Avoid mentioning awards or honors in
the body of abstract.

5/2/17 26
 Introduction
Project Management is similar to final
year project

Software product which is able to

take input, produce output after
processing the input.

5/2/17 27
 Requirement Analysis
Interview with client and End users.

Discussion with the groups of

Programmers

user requirements are

systematically organized into SRS
(System Requirement Specification)
document.
5/2/17 28
 Research field category
Image Processing

Data Mining

Soft-Computing

Semantic Web

Software Engineering

Network Security

5/2/17 29
 Uses of SRS
Requirement Analysis:
Functional, non-functional Requirement, and Goal
of Implementation

Design Phase:
Goal of Design phase is to transform requirements
specified in SRS into a structure suitable for
implementation in some programming language.

i.e. software architecture is developed from SRS

document.

5/2/17 30
 Context diagram and different levels of
DFDs are produces according to the SRS
document.

Testing:
The goal of system testing is to ensure
that developed system conforms to its
requirements laid out in the SRS
document.

5/2/17 31
 Parts of SRS
Functional Requirements of the system
Functionalities of the system which can be viewed as high level
function performed by the system.
It takes some input and produces some output.

Non-functional Requirements of the system

Maintainability, portability, usability, reliability issues, accuracy of
results, human-computer interface issues, etc.

Goal of Implementations
It documents issues such as revisions to the system functionalities,
New devices supported in future
Reusability issues

5/2/17 32
 Identifying Functional
Requirement
Functional requirements can be identified
from either informal problem definition
document or the conceptual understanding
of system.

It is useful to identify different types of users

who might use the system

Then try to identify the requirements from

each users perspective
5/2/17 33
 Input Data Output Data

fi

5/2/17 34
 Example
Consider Library Mgmt system
where-
F1: Search Book Function
Input: an authors name
Output: details of authors books and
location of these books in library.
Authors Book details
name
f1

5/2/17 35
 SRS - Example
Withdraw Cash from ATM
It is a high level requirement. It has several sub-
requirements corresponding to different user
interactions.
R1: withdraw cash
Description: The withdraw cash function first
determines the type of account that the user has and
the account number from which the user wishes to
withdraw cash. It checks the balance to determine
whether the requested amount is available in the
account. If enough balance is available, it outputs the
required cash, otherwise it generates an error
message.

5/2/17 36
 R1.1 select withdraw amount option
Input: withdraw amount option
Output: user prompted to enter the account type
R1.2: select account type
Input: Enter account type option
Output: prompt to enter amount
R1.3: get required amount
Input: amount to be withdrawn in integer values greater
than 100 and less than 10,000 in multiples of 100.
Output: The requested cash and printed transaction statement.
Processing: the amount is debited from the users account if
sufficient balance is available, otherwise an error message
displayed.

5/2/17 37
 LITERATURE REVIEW
Surveys all relevant literature to determine
what is known and not known about a
particular topic.

It may provide the background for larger

work, or it may stand on its own.

Presents the research and ideas of the field

rather than each individual work or author
by itself.
5/2/17 38
 WHY Literature Review
To discover what has been written
about a topic already
To determine what each source
contributes to the topic
To understand the relationship
between the various contributions,
identify and (if possible) resolve
contradictions, and determine gaps
or unanswered questions
5/2/17 39
 Steps
Gathering sources
Focus your topic: A literature review aims to
cover all of the research on a given topic. If
the topic is too large, there will be too much
material to cover it adequately.

Read with a purpose: Although you will need

to briefly summarize sources, a good literature
review requires that you isolate key themes or
issues related to your own research interests.

5/2/17 40
 Evaluating sources
For each book or article consider:
Credentials: Is the author an expert?

Argument/Evidence: Does the evidence support the conclusion?

Is the argument or evidence complete?

When comparing sources, consider:

Conclusions: Does all research arrive at the same conclusion or
are there differing opinions? What evidence or reasoning are
the differences based on?

Gaps or omissions: What questions are raised by the literature?

5/2/17 41
 Writing a Literature Review
Introduction
The introduction should identify your topic,
some discussion of the significance of that
topic and a thesis statement that outlines
what conclusion you will draw from your
analysis and synthesis of the literature.

If your literature review is part of a larger

work, explain the importance of the review
to your research question.
5/2/17 42
 Body
In the body, discuss and assess the research
according to specific organizational principles
(see examples below), rather than addressing
each source separately.
Most, if not all, paragraphs should discuss
more than one source.
Avoid addressing your sources alphabetically
as this does not assist in developing the
themes or key issues central to your review.

5/2/17 43
 Example

5/2/17 44
 Conclusion
The conclusion should provide a summary of
YOUR findings from the literature review.
Explain what your analysis of the material
leads you to conclude about the overall state
of the literature, what it provides and where it
is lacking.
You can also provide suggestions for future
research or explain how your future research
will fill the gaps in the existing body of work
on that topic.
5/2/17 45
 Finding research topics
http://web.mit.edu/research/topic/co
mputer.html#labs

5/2/17 46
 Introduction
Chapter 1: Introduction
1.1 : Introduction of superset of Topic
1.2 : Statement of Problems
1.3 : Objectives
1.4 Scope and Limitations
1.5 Thesis Organization

5/2/17 47
Web Project Costimation
-The first and most important phase of
project planning is Estimation.

-managers allocate resources, control

costs, and schedule and improve
current practices, which allow
projects to be finished on time and
within budget.
Costimation

-Web costimation is the process of predicting the

most realistic use of cost required to develop
or maintain a software.

-Effort estimates are used to calculate effort in

person-months (PM).
Cost=PM*Salary per month.
 Types Of Web Project
-Web hypermedia application: Static
applications characterized by nodes,
anchors , access structure.
-Web software application: uses the
Webs infrastructure for execution.
-Web application: An application
delivered over the Web that combines
characteristics of both Web hypermedia
and Web software applications
Types of Estimation Methods

- Expert Judgment
Judgment Based
- Delphi Method

- COCOMO
Algorithm Based
- Function Point

- ANN
Analogy Based
- CBR
Demerits in the Expert and
AM
-Expert may be some biased and hard to
document the factors used by the experts
-Unable to deal with exceptional conditions,
such as exceptional teamwork, and an
exceptional match between skill-levels
and tasks.
-Poor sizing inputs and inaccurate cost
driver rating will result in inaccurate
estimation.
Motivation

-Users are more willing to accept results it is a

similar form of reasoning as human
problem solving
-able to deal with poorly understood domains
that are difficult to model
-very early phase of a software project when
detailed information about the project is not
yet available
-The estimation are based on actual project
characteristic data.
 Objective

- Design of CBR Systems using JCOLIBRI

Framework and Angel tool

- Application on public web dataset

- Comparison of CBR systems

 Structured Analysis
aim of the structured analysis activity is to
transform a textual problem description into a
graphic model.

Structured analysis is used to carry out the

top-down decomposition of the set of high-
level functions depicted in the problem
description

During SA, functional decomposition of the

system is achieved.
5/2/17 55
 Necessity DFD
Starting with a set of high-level functions
that a system performs, a DFD model
hierarchically represents various sub-
functions

To represent the results of structured

analysis of a software problem

To shows the flow of documents or items

in an organization.
5/2/17 56
 Context diagram
The context diagram is the most abstract data
flow representation of a system.

It represents the entire system as a single bubble.

Bubble is labeled according to the main function

of the system
various external entities with which the system
interacts and
the data flow occurring between the system and
the external entities are also represented

5/2/17 57
 DFD contd..
The data input to the system and the data
output from the system are represented
as incoming and outgoing arrows.

These data flow arrows should be

annotated with the corresponding data
names

The context diagram is also called as the

level 0 DFD.
5/2/17 58
 Example:-
A supermarket needs to develop the following software to encourage
regular customers.
For this, the customer needs to supply his/her residence address,
telephone number, and the driving license number.
Each customer who registers for this scheme is assigned a unique customer
number (CN) by the computer.
A customer can present his CN to the check out staff when he makes any
purchase. In this case, the value of his purchase is credited against his CN.
At the end of each year, the supermarket intends to award surprise gifts to
10 customers who make the highest total purchase over the year.
Also, it intends to award a 22 caret gold coin to every customer whose
purchase exceeded Rs.10,000. The entries against the CN are the reset on
the day of every year after the prize winners lists are generated.

5/2/17 59
 Example DFD 0

5/2/17 60
 DFD Model of a system
A DFD model of a system graphically
depicts the transformation of the data
input to the system to the final result
through a hierarchy of levels.

To develop a higher-level DFD model,

processes are decomposed into their sub-
processes and the data flow among these
sub-processes is identified.
5/2/17 61
 1-DFD
If there are between 3 to 7 high-level
functional requirements, then these can
be directly represented as bubbles in the
level 1 DFD

Examine input data to these functions

and the data output by these functions
and represent them appropriately in the
diagram

5/2/17 62
 Decomposition
Decomposition of a bubble is also known as
factoring or exploding a bubble.
Each bubble at any level of DFD is usually
decomposed to anything between 3 to 7 bubbles
Too few bubbles at any level make that level
superfluous. For example, if a bubble is
decomposed to just one bubble or two bubbles,
then this decomposition becomes redundant.
Too many bubbles, i.e. more than 7 bubbles at
any level of a DFD makes the DFD model hard to
understand.

5/2/17 63
 Numbering of Bubbles
Numbers help in uniquely identifying any bubble
in the DFD by its bubble number.

The bubble at the context level is usually assigned

the number 0 to indicate that it is the 0 level DFD.

Bubbles at level 1 are numbered, 0.1, 0.2, 0.3, etc.

By looking at the number of a bubble we can

unambiguously determine its level, its ancestors,
and its successors

5/2/17 64
 Level 1 DFD

5/2/17 65
 Level-2 DFD

5/2/17 66
5/2/17 67
Use Case Model
Consists of set of use cases
An important analysis and design
artifact
The central model:
Other models must confirm to this
model
Not really an object-oriented model
Represents a functional or process
model
Use Cases
Different ways in which a system can
be used by the users
Corresponds to the high-level
requirements
Represents transaction between the
user and the system
Defines external behavior without
revealing internal structure of system
Set of related scenarios tied together
by a common goal.
Use Cases
Cont
Normally, use cases are independent
of each other
Implicit dependencies may exist
Example: In Library Automation
System, renew-book & reserve-book
are independent use cases.
But in actual implementation of renew-
book: a check is made to see if any book
has been reserved using reserve-book.
Example Use Cases
For library information
system
issue-book
query-book
return-book
create-member
add-book, etc.
Representation of
Use Cases
Represented by use case diagram
A use case is represented by an ellipse
System boundary is represented by a
rectangle
Users are represented by stick person
icons (actor)
Communication relationship between
actor and use case by a line
External system by a stereotype
An Example Use Case
Diagram

Play Move

Tic-tac-toe game
Player

Use case model

Why Develop A
Use Case Diagram?
Serves as requirements
specification
How are actor identification useful
in software development:
User identification helps in
implementing appropriate interfaces
for different categories of users
Another use in preparing appropriate
documents (e.g. users manual).
Factoring Use Cases
Two main reasons for factoring:
Complex use cases need to be factored
into simpler use cases
To represent common behavior across
different use cases
Three ways of factoring:
Generalization
Includes
Extends
Factoring Use Cases Using
Generalization

Pay membership fee

Pay through credit card Pay through library pay card

Factoring Use Cases
Using
Includes Common <<include>>
Base use case
use case

Base use case Base use case

<<include>>
<<include>>
<<include>> <<include>>

Base use case Base use case Base use case

Factoring Use Cases Using
Extends

Base <<extends>> Common

use case use case
 When an use case is compulsory to
be included in another use case then
<<include>> use case relationship
is used. <<include>> Pin identification
Cash withdrawal

5/2/17 79
 <<extends>>
Mends ATM Fill Money

<<extends>>
Fix ATM

5/2/17 80
5/2/17 81
 `

5/2/17 82
5/2/17 83
5/2/17 84
 Class diagrams
A class diagram describes the static structure of a
system.

It shows how a system is structured rather than

how it behaves.

The main constituents of a class diagram are

classes and their relationships.

generalization, aggregation, association, and

various kinds of dependencies.
5/2/17 85
 Classes
The classes represent entities with common
features, i.e. attributes and operations.

Classes are represented as solid outline

rectangles with compartments

Classes have a mandatory name compartment

where the name is written centered in boldface.

5/2/17 86
 Attributes
An attribute is a named property of a class. It
represents the kind of data that an object
might contain.

Attributes are listed with their names, and

may optionally contain specification of their
type, an initial value, and constraints

Example bookName : String

5/2/17 87
 Operation
Operation is the implementation of a service that can
be requested from any object of the class to affect
behaviour.

An objects data or state can be changed by invoking

an operation.

A class may have any number of operations or no

operation at all of the object.

An example for an operation is given.

issueBook(in bookName):Boolean

5/2/17 88
 Associations are needed to enable objects to
communicate with each other.

An association describes a connection between

classes. The association relation between two objects
is called object connection or link.

A link is a physical orconceptual connection between

object instances.

For example, suppose Amit has borrowed the book

Graph Theory.

5/2/17 89
 An arrowhead may be placed on the association line to
indicate
the reading direction of the association.
Many books may be borrowed by a Library Member

5/2/17 90
 Aggregation
Aggregation is a special type of association where the
involved classes represent a whole-part relationship.

Aggregation is represented by the diamond symbol at

the composite end of a relationship.

When an instance of one object contains instances of

some other objects

Aggregation (or composition) relationship exists

between the composite object and the component
object.

5/2/17 91
5/2/17 92
 Composition

Composition is a stricter form of aggregation, in which

the parts are existence-dependent on the whole.

This means that the life of the parts closely

ties to the life of the whole.

When the whole is created, the parts are created and

when the whole is destroyed, the parts are destroyed.

5/2/17 93
5/2/17 94
 Interaction Diagrams
Interaction diagrams are models that
describe how group of objects collaborate
to realize some behavior.

each interaction diagram realizes the

behavior of a single use case.

Types of interaction diagrams:

sequence diagrams
collaboration diagrams.

5/2/17 95
 Sequence Diagram
A sequence diagram shows interaction among objects as a
two dimensional chart.

The chart is read from top to bottom.

The objects participating in the interaction are shown at

the top of the chart as boxes attached to a vertical dashed
line.

Inside the box the name of the object is written with a colon
separating it from the name of the class

both the name of the object and the class are underlined.

5/2/17 96
 The vertical dashed line is called the objects
lifeline.

The lifeline indicates the existence of the object at

any particular point of time.

The rectangle drawn on the lifetime is called the

activation symbol and indicates that the object is
active as long as the rectangle exists.
5/2/17 97
5/2/17 98
 collaboration diagram
A collaboration diagram shows both structural and
behavioral aspects explicitly.

The structural aspect of a collaboration diagram

consists of objects and the links existing between
them.

an object is also called a collaborator.

The behavioral aspect is described by the set of

messages exchanged among the different
collaborators.

5/2/17 99
5/2/17 100