1. COCOMO II 資管研一 張永昌

2. Agenda Overall Model Definition COCOMO II Models for the Software Marketplace Sectors COCOMO II Model Rationale and Elaboration Development Effort Estimates Software Economies and Diseconomies of Scale Previous Approaches Scaling Drivers Precedentedness (PREC) and Development Flexibility (FLEX) Architecture / Risk Resolution (RESL) Team Cohesion (TEAM) Process Maturity (PMAT) Adjusting Nominal Effort Development Schedule Estimation Using COCOMO II Lines of Code Function Points Converting Function Points to Lines of Code Breakage

3. Overall Model Definition COCOMO II strategy: Preserve the openness of the original COCOMO; Key the structure of COCOMO II to the future software marketplace sectors described earlier; Key the inputs and outputs of the COCOMO II submodels to the level of information available; Enable the COCOMO II submodels to be tailored to a project's particular process strategy.

4. COCOMO II Models for the Software Marketplace Sectors COCOMO II capability for estimation ： Application Generator System Integration Infrastructure Two life cycle ： Early Design Post-Architecture

5. COCOMO II Model Rationale and Elaboration

6. Three-stage The earliest phases or spiral cycles will generally involve prototyping, using the Application Composition model capabilities. The next phases or spiral cycles will generally involve exploration of architectural alternatives or incremental development strategies. Once the project is ready to develop and sustain a fielded system, it should have a life- cycle architecture, which provides more accurate information on cost driver inputs, and enables more accurate cost estimates.

7. Development Effort Estimates PM ： Person Months （人月） A ： constant Size ： Size of software development units ＝ KSLOC （ units of thousands of source lines of code ） B ： scale factor

8. Software Economies and Diseconomies of Scale B ＜ 1.0 ： the project exhibits economies of scale. B ＝ 1.0 ： the economies and diseconomies of scale are in balance. B ＞ 1.0 ： the project exhibits diseconomies of scale.

9. Previous Approaches Original COCOMO ： Organic B=1.05 Semidetached B=1.12 Embedded B=1.20 Ada COCOMO ： Embedded （ COCOMO ） B ： 1.04~1.24 COCOMO II ： combin ： COCOMO and Ada COCOMO Arcgitecture 、 Risk （ Ada COCOMO ） =>RESL add ： Precedentedness (PREC) 、 Development Flexibility (FLEX) 、 Team Cohesion (TEAM)

10. Scaling Drivers

12. Precedentedness (PREC) and Development Flexibility (FLEX) FeatureVery LowNominal / High Extra High Precedentedness Organizational understanding of product objectives GeneralConsiderableThorough Experience in working with related software Systems ModerateConsiderableExtensive Concurrent development of associated new hardware and operational procedures ExtensiveModerateSome Need for innovative data processing architectures, algorithms ConsiderableSomeMinimal Development Flexibility Need for software conformance with preestablished requirements FullConsiderableBasic Need for software conformance with external interface specifications FullConsiderableBasic Premium on early completionHighMediumLow

13. Architecture / Risk Resolution (RESL)

14. Team Cohesion (TEAM)

15. Process Maturity (PMAT) organized around ： Software Engineering Institute’s Capability Maturity Model (CMM) two ways of rating Process Maturity ： CMM Maturity level Overall Maturity Level p CMM Level 1 (lower half) p CMM Level 1 (upper half) p CMM Level 2 p CMM Level 3 p CMM Level 4 p CMM Level 5 Key Process Areas （ KPAs ）

17. KPAs:

18. Adjusting Nominal Effort Early Design Model Post-Architecture Model

19. Development Schedule Estimation

20. Using COCOMO II Determining Size Lines of Code

22. Function Points

23. Counting Procedure for Unadjusted Function Points 1.Determine function counts by type. 2. Determine complexity-level function counts.

24. Apply complexity weights. Compute Unadjusted Function Points.

25. Converting Function Points to Lines of Code

26. Breakage