An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach [email protected] 15Chapter OverviewChapter Overview (contd)PlanningPlanning and the Information System Life CycleSlide 7Slide 8Slide 9Slide 10Slide 11Estimating Duration and CostEstimating Duration and Cost (contd)Slide 14Slide 15Slide 16Slide 17Slide 18Metrics for the Size of an Information SystemSlide 20Slide 21Slide 22Slide 23Slide 24Slide 25Techniques of Cost EstimationSlide 27Techniques of Cost Estimation (contd)COCOMOSlide 30COCOMO (contd)Slide 32Slide 33Slide 34Slide 35COCOMO IICOCOMO II (contd)Tracking Duration and Cost EstimatesTracking Duration and Cost Estimates (contd)Components of a Project Management PlanSlide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Project Management Plan Framework (contd)Slide 49Slide 50Slide 51Planning of TestingPlanning of Testing (contd)Slide 54Training RequirementsDocumentation StandardsDocumentation Standards (contd)CASE Tools for Planning and EstimatingCASE Tools for Planning and Estimating (contd)Testing the Project Management PlanTesting the Project Management Plan (contd)Slide 15.1Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction toObject-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004Stephen R. [email protected] 15.2Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CHAPTER 15PLANNING AND ESTIMATINGSlide 15.3Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter OverviewPlanning and the Information System Life CycleEstimating Duration and CostComponents of a Project Management PlanProject Management Plan FrameworkIEEE Project Management Plan FrameworkProject Management Plan: Osbert Oglesby Case StudyPlanning of TestingSlide 15.4Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter Overview (contd)Training RequirementsDocumentation StandardsCASE Tools for Planning and EstimatingTesting the Project Management PlanSlide 15.5Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. PlanningThere are two types of planning–Planning, like testing, must continue throughout the development and maintenance life cycle –After the specification document has been drawn up, duration and cost estimates are computed and a detailed plan is producedSlide 15.6Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life CycleIdeally, the plan for the entire information system project would be drawn up at the very beginning of the life cycleThis is impossible–There is insufficient information that earlySlide 15.7Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life CycleThere is not enough information available at the end of the requirements workflow to plan the system–At that stage, the developers at best have an informal understanding of what the client needsPlanning has to wait until the end of the analysis workflow–At that stage, the developers have a detailed appreciation of most aspects of the target information system –This is the earliest point in the life cycle at which accurate duration and cost estimates can be determinedSlide 15.8Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life CycleEarly estimates can be wildly inaccurateSlide 15.9Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life CycleSuppose that the delivered cost of an information system is found to be $1 millionThe figure shows that if a cost estimate had been made –Midway through the requirements workflow, the relative range for the cost estimate was 4»The cost estimate was probably in the range ($1 million / 4, $1 million  4), or ($0.25 million, $4 million) –Midway through the analysis workflow the relative range for the cost estimate was 2»The range of likely estimates would have shrunk to ($1 million / 2, $1 million  2), or ($0.5 million, $2 million)Slide 15.10Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life Cycle–At the end of the analysis workflow, the relative range at this point was 1.5»The estimate was probably in the still relatively wide range of ($1 million / 1.5, $1 million  1.5) or ($0.67 million, $1.5 million)Cost estimation is not an exact science–And a premature estimate is likely to be even less accurate than one made at the correct timeSlide 15.11Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Planning and the Information System Life CycleThe assumption throughout the remainder of this chapter is that–The analysis workflow has been completed,so meaningful estimating and planning now can be carried outSlide 15.12Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Estimating Duration and CostBefore development commences, the client wants to know how much the information system will cost–If the development team underestimates, the development organization will lose money on the project–If the development team overestimates, then the client may decide against proceeding, or–The client may give the job to another development organization whose estimate is more reasonableAccurate cost estimation is criticalSlide 15.13Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Estimating Duration and Cost (contd)Internal cost–The cost to the developers, including»Salaries of the development teams, managers, and support personnel»The cost of the hardware and software»The cost of overhead such as rent, utilities, and salaries of senior managementExternal cost–The cost to the clientSlide 15.14Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Estimating Duration and Cost (contd)Sometimes–External cost = internal cost + profit marginHowever, economic and psychological factors can affect this–If the developers desperately need work they may charge the client the internal cost or less–When a contract is awarded on the basis of bids, a team may try to come up with a bid that will be slightly lower than what