Scribd
Upload
8 views26 pages

spm ppt unit 1

The document discusses Software Project Management (SPM), highlighting its characteristics, activities, and differences from traditional management. It emphasizes the importance of planning, monitoring, and controlling in project execution, as well as the challenges faced in software projects, such as invisibility and complexity. Additionally, it outlines cost estimation models and the evolution of software development practices over the decades.

Uploaded by

meghanaalluri2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
8 views26 pages

spm ppt unit 1

The document discusses Software Project Management (SPM), highlighting its characteristics, activities, and differences from traditional management. It emphasizes the importance of planning, monitoring, and controlling in project execution, as well as the challenges faced in software projects, such as invisibility and complexity. Additionally, it outlines cost estimation models and the evolution of software development practices over the decades.

Uploaded by

meghanaalluri2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

Software Project Management

M.V.R JYOTHISREE
CSE, MVSREC
Introduction
• What is Software Project Management?
• How it is different from management?
• To know it we have to observe
– Planning
– Monitoring
– Controlling
• What is a project?
It is a planned activity
Few characteristics of project are

• Non routine tasks are involved


• Planning is required
• Specific objectives to be met or a specific
product is to be created
• The project has predetermined time span
• Work is carried out for some one else
• Work involves several specialisms
• Work carried out in several phases
• Project may be large or complex etc.,
Examples
• Producing an edition of news paper
• Construction of a building
• Writing an Operating System for a
computer
• Getting a Degree etc.,
Difference in Software Projects
• Invisibility
• Complexity
• Conformity (inconsistency)
• Flexibility
Activities covered by SPM

Feasibility study

Plan

Project Execution

Project execution includes design and implementation sub


phases
• Design
– Thinking and making Decisions about the
product
• Plan
– This is to show the activities that have to be
carried out while creating product
Water fall model
In theory
• According to Winston Royce 1970
• There are two essential steps common to
the development of computer programs:
analysis and coding
Disadvantages
• Sequential
• Moving back is not possible
• Testing at the end
• No iterations
• Product can be seen at the end
• No customer involvement
Five suggestions
• Program design comes first
• Document the design
• Do it twice
• Plan control and monitor testing
• Involve the customer
In practice
Projects destined for trouble frequently
exhibit the following symptoms:
– Protracted integration and late design
breakage
– Late risk resolution
– Requirements-driven functional
decomposition
– Adversarial (conflict or opposition)
stakeholder relationships
– Focus on documents and review meetings
Protracted integration and late
design breakage
Late risk resolution
Requirements-driven functional
decomposition
Focus on documents and review
meetings
Conventional Software
Management Performance
• Finding and fixing a software problem after delivery
costs 100 times more than finding and fixing the
problem in early design phases
• You can compress software development schedules
25% of nominal, but no more.
• For every $1 you spend on development, you will
spend $2 on maintenance
• Software development and maintenance costs are
primarily a function of the number of source lines of
code
• Variations among people account for the biggest
differences in software productivity
• The overall ratio of software to hardware costs
is still growing. In 1955 it was 15:85; in 1985,
85:15.
• Only about 15% of software development effort
is devoted to programming.
• Software systems and products typically cost 3
times as much per SLOC as individual
software programs. Software-system products
(i.e., system of sys­tems) cost 9 times as much.
• Walkthroughs catch 60% of the errors
• 80% of the contribution comes from 20% of the
contributors
Evolution of software Economics
Software Economics
• Five basic parameters of software Cost
model
– Size
– Process
– Personnel
– Environment
– Quality
The relationships among these parameters
and the estimated cost can be written as
follows:

Effort = (Personnel) (Environment)


( Quality)( Sizeprocess)
Three generations of software
development
• Conventional: 1960s and 1970s, craftsmanship.
Organizations used custom tools, custom processes,
and virtually all custom components built in primitive
languages.

• Transition: 1980s and 1990s, software engineering.


Organizations used more-repeatable processes and
off-the-shelf tools, and mostly (>70%) cus­tom
components and the components (<30%) were
available as commercial products.

• Modern practices: 2000 and later, software


production. the use of managed and measured
processes, integrated automation environments, and
mostly (70%) off-the-shelf components. Perhaps as
few as 30% of the components need to be custom built
Pragmatic software cost estimation
• Which cost estimation model to use

• Whether to measure software size in


SLOC or function points

• What constitutes a good estimate


• Popular Cost estimation models
– COCOMO
– CHECKPOINT
– ESTIMACS
– KnowledgePlan
– Price-S
– ProQMS
– SEER
– SLIM
– SOFTCOST, and
– SPQR/20

• The primary advantage of using FP is that


this method is independent of technology.
• Good estimation has the following attributes
– It is conceived and supported by the project
manager, architecture team, development team,
and test team accountable for performing the
work.
– It is accepted by all stakeholders as ambitious
but realizable.
– It is based on a well-defined software cost model
with a credible basis.
– It is based on a database of relevant project
experience that includes similar processes,
similar technologies, similar environments,
similar quality requirements, and similar people.
– It is defined in enough detail so that its key risk
areas are understood and the probability of
success is objectively assessed.

You might also like