Presentation is loading. Please wait.

Presentation is loading. Please wait.

Homework 3 Solution Lecture Packet 16 © John W. Brackett.

Similar presentations


Presentation on theme: "Homework 3 Solution Lecture Packet 16 © John W. Brackett."— Presentation transcript:

1 Homework 3 Solution Lecture Packet 16 © John W. Brackett

2 Homework 3 Questions You are responsible for preparing the fixed-price bid for developing the production version of the Disney software and the bid for maintaining the production software for 3 years after delivery. You are responsible for preparing the fixed-price bid for developing the production version of the Disney software and the bid for maintaining the production software for 3 years after delivery. a.What is the principal estimating technique that you would use determining for the cost of developing the production version of the software? b.What information is required by the selected estimating technique? c. What secondary estimating technique would you use to validate the reasonableness of the estimate made using your primary estimating technique? d. What estimating error ranges would you give your boss if he asks the likely error range after you have finished using your principal estimating technique? e. What is the principal estimating technique you would use for the cost of maintaining the software for 3 years after delivery? What information does your selected estimating technique require?

3 Contract Types Fixed PriceFixed Price –The price is established based upon project plan, requirements, customer support expected, and delivery conditions –Contract changes required if the customer makes changes to the requirements or delivery conditions – Profit can be higher if expenditures are low, but contract can lose money –Vendor absorbs most of the financial risks

4 Homework 3, Question 1 Production System Software Estimation Preferred estimating process: Bottom-up estimating process using the WBS with tasks estimated by the developers who will do themPreferred estimating process: Bottom-up estimating process using the WBS with tasks estimated by the developers who will do them –Changed requirements are known and impact on the design and code can be evaluated –Reuse of prototype code and need to write new code can be assessed –All tasks required to complete implement of the software can be identified and included into the WBS –Developers now have project experience and can estimated their tasks based on previous work

5 Two Phase Estimation Estimation for Market Test Prototype Estimation for Production System

6 Production System Estimation Key information which can be used to support estimating:Key information which can be used to support estimating: –Revised, approved requirements –Evaluation of the impact on design and code of the requirements changes –Analysis of existing design and code for reuse, maintainability, defects –Detailed WBS of all tasks remaining, with tasks assigned to developers –Developer and team productivity data from market test system development Bottom-up estimating is capable of meeting the required precision for a fixed-price bid (15-20%)Bottom-up estimating is capable of meeting the required precision for a fixed-price bid (15-20%)

7 Production System Estimation A secondary estimating alternative: Expert judgment, with experts having full access to previous work, to information now available and to existing development staffA secondary estimating alternative: Expert judgment, with experts having full access to previous work, to information now available and to existing development staff Unacceptable estimating alternatives are based upon using less relevant dataUnacceptable estimating alternatives are based upon using less relevant data –Cost estimating models –Estimation based on cost or schedule for market test system development (since we hope most code to be reusable, and not developed again) –Estimation based on other systems

8 Maintenance Estimation Maintenance = generating changes required to make the software operate consistent with the updated requirementsMaintenance = generating changes required to make the software operate consistent with the updated requirements Preferred estimating approach: Expert judgment, with experts having access to maintenance data on your companys previous software projectsPreferred estimating approach: Expert judgment, with experts having access to maintenance data on your companys previous software projects Other reasonable approaches:Other reasonable approaches: –Level of effort--estimate cost of N full-time staff devoted for 3 years to maintenance (customer would prioritize bugs) –Estimation based upon maintenance costs from previous software projects in your company Unacceptable: Bottom-up using a maintenance WBS defining what tasks will be done (unknowable )Unacceptable: Bottom-up using a maintenance WBS defining what tasks will be done (unknowable )


Download ppt "Homework 3 Solution Lecture Packet 16 © John W. Brackett."

Similar presentations


Ads by Google