Scribd
Upload
10 views

Lecture 78

Uploaded by

ash.qureshi993
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
10 views

Lecture 78

Uploaded by

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

Chapter 23

Estimation

Software Engineering: A Practitioner’s Approach


6th Edition
Roger S. Pressman
Software Project Estimation (1)
• S/W is the most expensive element of virtually
all computer based systems
• S/W cost and effort estimation will never be
an exact science
– Too many variables
• Human
• Technical
• Environmental
• Political

2
3
An Example of FP-Based Estimation (1)

Information Domain Count Weighting factor


Value
Simple Average Complex

External Inputs (EIS) 3 X 3 4 6 = 9

External Outputs (EOs) 2 X 4 5 7 = 8

External Inquiries (EQs) 2 X 3 4 6 = 6

Internal Logical Files 1 X 7 10 15 = 7


(ILFs)
External Interface Files 4 X 5 7 10 = 20
(EIFs)
Count Total 50

Figure 15.4: Computing function points 8


An Example of FP-Based Estimation (2)

9
An Example of FP-Based Estimation (3)

Value Adjustment Factors 1.17


11
An Example of FP-Based Estimation (4)

• Now,
– FPestimated = count-total  [0.65 + 0.01   (Fi)]
• Fi (i = 1 to 14 are value adjustment factors)
• So,
– FPestimated = W = 320  [0.65 + 0.01  52] = 375 (approx.)
• Let,
– Average Productivity = X = 6.5 FP/pm
– Labor rate = Y = $8,000 per month
• So,
– Cost per FP = Z = Y/X = $1,230 (approx.)
– Total estimated project cost = W*Z = $461,000 (approx.)
– Estimated effort = W/X = 58 person-months (approx)
12
Software Project Estimation (2)
• Options for estimation
– Delay estimation until late in the project
• Attractive, but not practical
– Base estimates on similar projects that have already
been completed
• Unfortunately, past experience has not always been a good
indicator of future results
– Use relatively simple decomposition techniques to
generate project cost and effort estimates
• “Divide and conquer” approach
– Use one or more empirical models for software cost
and effort estimation
• Can be used as a cross-check for the previous option and vice
versa
24
Decomposition Techniques
• Two different points of view for the
decomposition approach
– Decomposition of the problem
– Decomposition of the process
• But first, the project planner must
– Understand the scope of the s/w to be built
– Generate an estimate of its “size”

25
Software Sizing
• Sizing represents the project planner’s first major
challenge
• Size refers to a quantifiable outcome of the s/w
project (e.g. LOC and/or FP)
• Four different approaches to the sizing problem
[PUT92]
– “Fuzzy Logic” sizing
– Function point sizing
– Standard component sizing
– Change sizing
26
The COCOMO II Model (1)
• COnstructive COst Model
• A hierarchy of estimation models
• Addresses the following areas
– Application composition model
– Early design stage model
– Post-architecture stage model
• Three different sizing options are available
– Object points
– Function points
– Lines of source code

27
Chapter 23
• 23.5, 23.6, 23.6.1, 23.6.3, 23.6.4
• 23.7
• 23.10
• Exercises-
23.4, 23.5, 23.7

https://www.youtube.com/watch?v=CeKP0rUIotc

28

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy