Unit 4

Project Planning, Management And

Estimation
 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.
 Project Initiation
• Project initiation is the first step in starting a new project.
During the project initiation phase, you establish why you’re
doing the project and what business value it will deliver—then
use that information to secure buy-in from key stakeholders.
Steps

• . Create a project charter or business case

• Identify key stakeholders and pitch your project
• Run a feasibility study
• Assemble your team and tools
 COCOMO-II
• COCOMO is an abbreviation for "Constructive Cost Model“
• The COCOMO model was designed and developed by Barry W. Boehm in
the 1980s.
• Its primary goal is to offer methodologies, quantitative analytic structure, and tools. It
computes the total development time and effort that is based on the estimates of all individual
subsystems.
• There are mainly 4 types of COCOMO 2 estimation models.
1. Application Composition Model
It is intended for usage with reusable components to create prototype development
estimates and operates on the basis of object points. It is more suited to prototype
system development.
3. Reuse Model
 COCOMO-II
2. Early Design Model
After gathering requirements, the model is utilized during the system
design phase. It generates estimates based on function points, which
are subsequently converted into numerous lines of source code.

Effort = A x Size B x M

• A is a constant whose value should be 94.

• B represents the increase in effort ranges

from 1 to 1.24 depending on scaling factors such as development
flexibility, precedentedness, team cohesion, and many others.

• The M is determined by the cost drivers or the project parameters.

 COCOMO-II

• This model computes the effort that is required to join reusable

components and/or program code generated by design or program
conversion tools.
• There are mainly two kinds of reused codes: white-box and black-box
code. When there is no knowledge of the code, and no alteration is
conducted in it, black box code is employed. In contrast, the whitebox is
utilized when the new code is added.

• E = (ALOC x AT/100)/ATPROD

• ALOC represents the number of LOC that must be modified in a

component.
• AT represents the automatically produced adapted code percentage.
• ATPROD represents the productivity in code combining. It may be worth
up to 2400 LOC every month.
 COCOMO-II
• 4. Post Architecture Model
A more accurate software estimate may be
generated after designing the system architecture,
and it is regarded as the most detailed of all
models capable of producing an accurate estimate.
The post-architecture model effort may be
calculated using the following formula:

Effort = A x Size B x M
 Project Scheduling
• A comprehensive process that outlines
the project phases, tasks under each
stage, and dependencies is known
as project scheduling.