Department of Computer Science

University Institute of Engineering

DEPARTMENT OF COMPUTER SCIENCE
& ENGINEERING
Bachelor of Engineering (Computer Science & Engineering)
Subject Name: Software Engineering
Subject Code: 22CST-313
Prepared by:
Er. Puneet Kaur(E6913)

Software Project Management DISCOVER . LEARN . EMPOWER

1
 Department of computer Science

• Software project planning

• Project Estimation Techniques

2
 Department of computer Science

Software Project Planning

• A Software Project is the complete methodology of programming

advancement from requirement gathering to testing and support,
completed by the execution procedures, in a specified period to
achieve intended software product.
• A project is well-defined task, which is a collection of several
operations done in order to achieve a goal (for example, software
development and delivery).

3
 Software Project Planning

• A Project can be characterized as:

• Every project may has a unique and distinct goal.
• Project is not routine activity or day-to-day operations.
• Project comes with a start time and end time.
• Project ends when its goal is achieved hence it is a temporary phase
in the lifetime of an organization.
• Project needs adequate resources in terms of time, manpower,
finance, material and knowledge-bank.

4
 Need of Software Project
Management
• Software development is a sort of all new streams in world business,
and there's next to no involvement in structure programming items.
• Most programming items are customized to accommodate customer's
necessities.
• The most significant is that the underlying technology changes and
advances so generally and rapidly that experience of one element
may not be connected to the other one.
• All such business and ecological imperatives bring risk in software
development; hence, it is fundamental to manage software projects
efficiently.
5
 Software Project Manager

• Software manager is responsible for planning and scheduling project

development.
• They manage the work to ensure that it is completed to the required
standard.
• They monitor the progress to check that the event is on time and
within budget.
• The project planning must incorporate the major issues like size &
cost estimation scheduling, project monitoring, personnel selection
evaluation & risk management.

6
 Software Project Manager
To plan a successful software project, we must understand:
• Scope of work to be completed
• Risk analysis
• The resources mandatory
• The project to be accomplished
• Record of being followed

7
 Software Project Manager

• A software project manager is a person who undertakes the

responsibility of executing the software project.
• Software project manager is thoroughly aware of all the phases of
SDLC that the software would go through.
• Project manager may never directly involve in producing the end
product but he controls and manages the activities involved in
production.

8
 Software Project Manager

• A project manager closely monitors the development process,

prepares and executes various plans, arranges necessary and
adequate resources, maintains communication among all team
members in order to address issues of cost, budget, resources, time,
quality and customer satisfaction.

9
Responsibility of Software Project
Manager
Managing People :
• Act as project leader
• Liaison with stakeholders
• Managing human resources
• Setting up reporting hierarchy etc.

10
Responsibility of Software Project
Manager
Managing Project
• Defining and setting up project scope
• Managing project management activities
• Monitoring progress and performance
• Risk analysis at every phase
• Take necessary step to avoid or come out of problems
• Act as project spokesperson

11
 Software Management Activities

• Software project management comprises of a number of activities,

which contains planning of project, deciding scope of software
product, estimation of cost in various terms, scheduling of tasks and
events, and resource management. Project management activities
may include:
• Project Planning
• Scope Management
• Project Estimation

12
 Project Planning

• Software project planning is task, which is performed before the

production of software actually starts.
• It is there for the software production but involves no concrete
activity that has any direction connection with software production;
rather it is a set of multiple processes, which facilitates software
production.

13
• Software Project planning starts before technical work start. The
various steps of planning activities are:

14
 Scope Management

• It defines the scope of project; this includes all the activities, process
need to be done in order to make a deliverable software product.
• Scope management is essential because it creates boundaries of the
project by clearly defining what would be done in the project and
what would not be done.
• This makes project to contain limited and quantifiable tasks, which
can easily be documented and in turn avoids cost and time overrun.

15
 Scope Management

During Project Scope management, it is necessary to -

• Define the scope
• Decide its verification and control
• Divide the project into various smaller parts for ease of management.
• Verify the scope
• Control the scope by incorporating changes to the scope

16
 Project Estimation

• For an effective management accurate estimation of various

measures is a must.
• With correct estimation managers can manage and control the
project more efficiently and effectively.
• Project estimation may involve the following:
• Software size estimation Software size may be estimated either in
terms of KLOC (Kilo Line of Code) or by calculating number of function
points in the software. Lines of code depend upon coding practices
and Function points vary according to the user or software
requirement.
17
 Project Estimation

• Effort estimation : The managers estimate efforts in terms of

personnel requirement and man-hour required to produce the
software.
• For effort estimation software size should be known.
• This can either be derived by managers’ experience, organization’s
historical data or software size can be converted into efforts by using
some standard formulae.

18
 Project Estimation

• Time estimation Once size and efforts are estimated, the time
required to produce the software can be estimated.
• Efforts required is segregated into sub categories as per the
requirement specifications and interdependency of various
components of software.
• Software tasks are divided into smaller tasks, activities or events by
Work Breakthrough Structure (WBS).
• The tasks are scheduled on day-to-day basis or in calendar months.
• The sum of time required to complete all tasks in hours or days is the
total time invested to complete the project.
19
 Project Estimation

• Cost estimation This might be considered as the most difficult of all

because it depends on more elements than any of the previous ones.
For estimating project cost, it is required to consider -
• Size of software
• Software quality
• Hardware
• Additional software or tools, licenses etc.
• Skilled personnel with task-specific skills
• Travel involved
• Communication
• Training and support
20
 Project Estimation Techniques

• Project manager can estimate the listed factors using two broadly
recognized techniques –
• Decomposition Technique
• This technique assumes the software as a product of various
compositions.
• There are two main models -
• Line of Code Estimation is done on behalf of number of line of codes in
the software product.
• Function Points Estimation is done on behalf of number of function
points in the software product.
21
 Project Estimation Techniques

• Estimation is the process of finding an estimate, or approximation,

which is a value that can be used for some purpose even if input data
may be incomplete, uncertain, or unstable.
• Estimation determines how much money, effort, resources, and time it
will take to build a specific system or product. Estimation is based on −
• Past Data/Past Experience
• Available Documents/Knowledge
• Assumptions
• Identified Risks

22
 Project Estimation Techniques

• The four basic steps in Software Project Estimation are −

• Estimate the size of the development product.
• Estimate the effort in person-months or person-hours.
• Estimate the schedule in calendar months.
• Estimate the project cost in agreed currency.

23
 Project Estimation Techniques

• Empirical Estimation Technique

• This technique uses empirically derived formulae to make estimation.
These formulae are based on LOC or FPs.
• Putnam Model This model is made by Lawrence H. Putnam, which is
based on Norden’s frequency distribution (Rayleigh curve). Putnam
model maps time and efforts required with software size.
• COCOMO COCOMO stands for COnstructive COst MOdel, developed
by Barry W. Boehm. It divides the software product into three
categories of software: organic, semi-detached and embedded.

24
 Estimation Accuracy

• Important factors that affect the accuracy of estimates are −

• The accuracy of all the estimate’s input data.
• The accuracy of any estimate calculation.
• How closely the historical data or industry data used to calibrate the model
matches the project you are estimating.
• The predictability of your organization’s software development process.
• The stability of both the product requirements and the environment that
supports the software engineering effort.
• Whether or not the actual project was carefully planned, monitored and
controlled, and no major surprises occurred that caused unexpected delays.
25
PROJECT ESTIMATION TECHNIQUES
• Estimation of various project parameters is a basic project planning activity.

• The important project parameters that are estimated include: project size, effort
required to develop the software, project duration, and cost.

• There are three broad categories of estimation techniques:

• Empirical estimation techniques
• Heuristic techniques
• Analytical estimation techniques
26
EMPIRICAL ESTIMATION TECHNIQUE
Empirical estimation techniques are based on making an educated guess of the
project parameters.

• While using this technique, prior experience with development of similar

products is helpful.

• Empirical estimation techniques are based on common sense, different activities

involved in estimation have been formalized over the years.

• Two popular empirical estimation techniques are: Expert judgment technique

and Delphi cost estimation.
27
Expert judgment technique Expert judgment technique

• Experts divide a software product into component units:

• e.g. GUI, database module, data communication module, billing module, etc.

• Add up the gauesses for each of the components.

28
 Delphi cost estimation
• Delphi estimation is carried out by a team comprising of a group of experts and a coordinator.
• In this approach, the coordinator provides each estimator with a copy of the software
requirements specification (SRS) document and a form for recording his cost estimate.
• Estimators complete their individual estimates anonymously and submit to the coordinator. In
their estimates, the estimators mention any unusual characteristic of the product which has
influenced his estimation.
• The coordinator prepares and distributes the summary of the responses of all the estimators,
and includes any unusual rationale noted by any of the estimators.
• Based on this summary, the estimators re-estimate. This process is iterated for several rounds.
No discussion among the estimators is allowed during the entire estimation process.
• After the completion of several iterations of estimations, the coordinator takes the responsibility
of compiling the results and preparing the final estimate.

29
 Heuristic techniques
• Heuristic techniques assume that the relationships among the different project parameters can be modeled
using suitable mathematical expressions. Once the basic (independent) parameters are known, the other
(dependent) parameters can be easily determined by substituting the value of the basic parameters in the
mathematical expression.

• Different heuristic estimation models can be divided into the following two classes:
• Single variable estimation model: It provide a means to estimate the desired characteristics of a
problem, using some previously estimated basic (independent) characteristic of the software product
such as its size. A single variable estimation model takes the following form:
Estimated Parameter = c1 * ed1

• multivariable cost estimation model: takes the following form: Multivariable estimation models are
expected to give more accurate estimates compared to the single variable models, since a project
parameter is typically influenced by several independent parameters.
Estimated Resource = c1*e1d1 + c2*e2d2 + ...

30
 Department of computer Science

References

• https://www.tutorialspoint.com/software_engineering/software_proj
ect_management.htm
• https://www.javatpoint.com/software-project-planning
• https://www.tutorialspoint.com/estimation_techniques/estimation_t
echniques_overview.htm

31
THANK YOU

32