Scribd
Upload
10 views7 pages

Unit 2-1

unit 2 part 1

Uploaded by

Chetan
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 views7 pages

Unit 2-1

unit 2 part 1

Uploaded by

Chetan
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/ 7

Cost Estimation

The necessity of cost estimation stems from the requirements


of scheduling and cost planning. For lack of more precise
methods, cost estimation for software development is almost
always based on a comparison of the current project with
previous ones.
1. Delay estimation until late in the project. The longer
we wait, the less likely we are to make errors in our
estimates. However, this is not practical.
2. Base estimates on similar projects that have already
been completed. This works well if the current project
is quite similar to past efforts. Unfortunately, past
experience has not always been a good indicator of
future results.
3. Use “decomposition techniques” to generate project
cost and effort estimates. These techniques use a
“divide and conquer” approach to estimation. By
decomposing a project into major functions and
related software engineering activities, cost and effort
estimation can be performed in a step-wise fashion.
SOFTWARE COST FACTORS
• Experience and qualifications of the estimator
• Type of software (e.g., function-, data- or object-oriented, time-
critical software with high efficiency requirements)
• Anticipated complexity (e.g., number of components (modules,
classes), number of component couplings, number of methods
per class, complexity of methods)
• Expected size of program (number of statements)
• Experience and qualifications of personnel (e.g., project
experience, programming experience, knowledge of methods,
experience in use of tools,…)
• Techniques and tools to be used (planning, design and
documentation techniques, test strategies and tools,
programming languages)
LOC (Lines of Code)
Based Estimation
• To illustrate the LOC based estimation
technique, let us consider the
development of software for
Computer-Aided Design (CAD)
application.
Optimistic: 4600
Most likely: 6900
Pessimistic: 8600
Applying the equation to compute EV (Earned Value), the expected
value for the 3D geometric analysis function is 6800 LOC .
Process-Based Estimation

The process is decomposed into a relatively small set of


activities or tasks and the effort required to accomplish
each task is estimated. A process-based estimation
involves the following steps:
I. Delineate the software functions obtained from the
project scope.
II. A series of software process activities must be
performed for each function.
III. Functions and related software process activities
may be represented as part of a table.
IV. The planner estimates the effort (eg. person-months) that will be
required to accomplish each software process activity for each
software function.
V. Average labor rates (eg. cost/unit effort) are applied to the effort
estimated for each process activity.
VI. Costs and Effort for each function and software process activity are
computed.
Major factors that influence
software cost
• Programmer ability
• Product complexity
• Product size
• Available time
• Required reliability
• Level of technology

You might also like