Stutzke-p219 - SoftwareCostandScheduleEstimation...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Cost and Schedule Estimation  [and Tracking] By: Richard D. Stutzke Presenter: Stephen Lopez-Couto
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Discussion Topics Introduction Creating an Estimate Identification Size Productivity Parametric Models Risks Scheduling Costing Putting the Estimate Together “Good Ideas” for Improving Estimates Tracking Execution Managing Estimate Changes Conclusion
Background image of page 2
Introduction The main purpose of the paper is to  present approaches for deriving an  estimate of the cost and schedule of a  software project Discusses methods to track and alter  the estimates as development  progresses Discusses ways to get a project back  on track after changes have been  made to a schedule
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Creating an Estimate… Estimates Generally focus on labor hours, quantity  of materials and amount of services, not  the cost This is computed later Requires determining the work required  to meet requirements and the effort  required to perform that work
Background image of page 4
Creating an Estimate… Step 1: Identify the tasks They fall under four main categories: 1. Engineering 2. Program Management 3. Configuration Management 4. Quality Assurance Tasks are recorded in a Work Breakdown  Structure (WBS) Hierarchically identifies all tasks in a project Each successive layer should be more descriptive  than its parent For a software project, the lowest level should be  detailed enough to show class names This is not always possible, or even necessary
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Creating an Estimate… Step 2: Estimate the resources  required per task There are many types of resources  (that are often billed differently) Materials  Subcontracted Items Travel Labor (the biggest one) The focus of the paper is mainly  applied to estimating  labor  based on  the engineering (development) efforts
Background image of page 6
Creating an Estimate… Step 3a: Estimating the Software  Development Effort Basic Method E = S/P (Estimate = Size/Productivity) The hard part is determining the size and  productivity variables Estimating Size – three main factors 1. Units of measure 2. Software included in the measurement 3. Amount of reused code Reused code is generally counted differently than  newly written code Must track code Added, Changed and Deleted from  the reused code 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Creating an Estimate… Step 3a Continued…  Estimating Productivity – An aggregate  of the capabilities of the development  team
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 08/25/2011 for the course EEL 6883 taught by Professor Staff during the Spring '08 term at University of Central Florida.

Page1 / 23

Stutzke-p219 - SoftwareCostandScheduleEstimation...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online