Home

USC COCOMOII

1. Life Cycle Phase Programming Life Cycle Effort 404 754 Person Months Life Cycle Schedule 14 070 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 4 000 16 190 14 070 i hea kina Product Design 8 000 32 380 14 070 2 301 Programming 56 500 228 686 14 070 16 253 Test Planning 030 20 360 14 070 1 447 Verification and Validation 8 030 32 502 14 070 2 310 Project Office 6 470 26 187 14 070 bats Loh CM QA 6 500 26 309 14 070 1 870 Manuals 5 470 22 139 14 070 1 574 60 COCOMO Reference Manual 6 1 4 Product Design Phase The product design phase distribution allows the user to view the components of this particular phase When the Product Design distribution is chosen from the Project Phase distribution menu the window shown in FIGURE 6 3 is displayed This window displays the following information project name the total project SLOC the total estimated project effort and the total estimated project schedule In addition the window displays the estimated effort for the activities of requirements analysis product design programming test planning verification amp validation project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 5 To exit from this window click the OK button FIGURE 6 5 Product Design window for the overall project Life Cycle Phase Prod
2. Module Maintenance Module 1 Ea Effort Ajustment Factor 0 70 T Product Platform F RELY DATA DOCU CPLX RUSE TIME STOR PVOL Low Nominal High Nominal Nominal Nominal V High High 0 amp 0 25 0 0 0 50 0 Personnel t ACAP AEXP PCAP PEXP LTEX PCON High High High V High High Nominal 25 754 0 04 504 0 Project User gt TOOL SITE USRI USRZ High Nominal Nominal Nominal 50 0 0 0 Page No 2 Previous The third page of the maintenance window contains the effort and cost estimation for the next N number of years as defined by the user With each year is a listed the KSLOC SLOC 10 the nominal effort for development PM nom the estimated effort for maintenance PM maint the number of full time software personnel necessary to maintain the module for the year FSWP the number of instructions that are to be maintained be per personnel KSLOC FSWP and the total cost for maintenance for the year see Figure 7 15 FIGURE 7 15 Module Maintenance window page 3 Module Maintenance Module 1 x WORK LOAD PROJECTION FOR THE NEXT 3 YEARS Year ESLOC Effort Nom Effort Maint Staff ESLOC Staff Cost T 13 57 24 36 13183 1 43 9 51 80516 07 z 16 97 31 14 21 90 1 82 9 30 102909 27 3 cub 39 80 SEE 2 33 9 09 131530 49 Page No 3 Previous 79 The fourth window of the maintenance window contains the cumulative figures for effort and cost for maintenance for the total number of years see Figure 7
3. COCOMO Reference Manual 51 Chapter 5 Calibrate Menu COCOMOI now has the ability to archive your own software project data Using this data COCOMOII will compute various coefficients and exponents involved in the effort and schedule equations This will make your COCOMOII estimates even more reliable Each software project to be archived is described as a complete COCOMOII project It may include multiple modules each with their own SLOC estimate and EAF factors In addition a software project consists of a name date time actual effort and actual schedule The actual effort and actual schedule must be supplied by the COCOMOII user Entering revised values for effort and schedule are always possible Effort is given in units of person months Schedule is given in units of months Both assume the COCOMO hours per month value of 152 FIGURE 5 1 Calibrate Menu C COCOMOII sample est USC COCOMO 11 1999 0 File Edit View Parameters ZCE Phase Maintenance Help DIE E File Load File Save File Save As aa Schedule Project N rojec ame sample Project Development Model Post Architecture Compute Module 1 13574 5670 00 4 27 57 3 244 7 55 5 1387226 21 102 2 8 6 7 414 5 1 File Load The Calibrate File Load option is used to retrieve a calibration project file as well as loading all project data on the working project window Figure5 2 52 COCOMO Reference Manua
4. Save s Save in Y Cocomoi Al e a sample est Save as type Project Files est Cancel Z 3 Look at the Files scroll window If the file saving is to update overwrite a existing project file the desired filename should be found in the Files scroll list If the filename can not be found from current list change the directory from the Directories scroll list until the desired filename is being shown When the desired filename is on the list click it 4 If the file saving is to store a new project file choose the desired directory then type in a new filename in the SELECTION box 5 After the desired filename is selected or input click the OK button to initiate project saving After a project file is saved the project file name will be displayed on the PROJECT FILE field at the upper left corner of the working window Load Model The Load Model command is used when a specific model in which the values of multiplying factors and scale factors are different from the COCOMO default model is to be applied to the current project The Load Model option is used to retrieve a model file as well as loading it for the current project To Retrieve or Load a Model File 1 Choose Load Model from the File menu 2 If a previous model has been modified in the current project the following dialog box will appear COCOMO Reference Manual FIGURE 2 7 Warning Dialog Box USC COCOMO Il x Current Project Has B
5. 47 4 1 4 auc cp M 47 AVS User Defined EAE eden eie eer en tr ete et e sus t p Hp n Ee e need 48 4 2 SAA reete etit iere obo PER et tie o te eR 49 43 Seale Factors oue ee ree e PG ne e pne eret NN 49 O NN 50 4 5 I CSS M 51 Chapter 5 Calbrate Menu 5e etes ierat et e oec itp er rer ee tet E dai dtr Us 52 5 1 InigE C 52 32 FIGS A E cnin DR E Oe ot reis 53 5 3 Elle Save AS id idos oie 54 S T NN 54 5 5 Comp lte snssoheoneee opa eu Oase D pene DUE Den 56 Chapter 6 Phase Distribution ennt eene REESE eere perg testet 57 6 1 Project Phase DistribUtiOD coil pum Dan RP EEEE E EaD ETE ESSES Ries 58 6 1 1 Overall Project Phase Distribution ennemi tee Drei tiet ER EH din Dep e dete ce 58 6 1 2 Plans and Requirements Project Phase Distribution sess 59 6 1 3 Programming Project Phase usen e eet ette He oet e e ee tere 60 COCOMO Reference Manual 1 6 1 4 Product Design Phase ctore tedio ee Re ERR RR EEr ERR ERE bets ira 61 6 1 5 Integration and Test Project Phase eoe teer recettes tp beer o P cb p ERR as ness 61 6 2 Module Phase Distributions AAA tede epe i ERR rir PERSE ERREUR ath pepe 62 6 2 1 Overall Module Phase Distribution eene energie o ter eec TETE EE sess 64 6 2 2 Plans and Requirements Module Phase Distribut
6. SLOC 10 the nominal effort for development PM nom the actual effort for maintenance PM maint the number of full time software personnel necessary to maintain the project for the year FSWP the number of instructions that are to be maintained be per personnel KSLOC FSWP and the total cost for maintenance for the year see Figure 7 7 FIGURE 7 7 Project Maintenance window page 3 Project Maintenance x WORK LOAD PROJECTION FOR THE NEXT 3 YEARS Year KSLOC Effort_Nom Effort_Maint Staff ESLOC Staff Cost T 37 79 66 00 71 36 5 95 6 36 392474 64 2 47 24 84 35 ae 7 60 6 22 501630 04 3 59 05 107 81 116 57 ciet 6 08 641143 85 Page No 3 Previous The fourth window of the maintenance window contains the cumulative figures for effort and cost for maintenance for the total number of years see figure 7 8 This first displays the total amount of effort estimated for maintenance then sums the effort of development and maintenance together It also displays the total cost of maintenance of the project and then displays the summed total cost of development and maintenance for the entire project 74 COCOMO Reference Manual FIGURE 7 8 Project Maintenance window page 4 Project Maintenance x SUMMARY OF PROJECTION Cumulative Maintenance Person month 279 14 Overall Development and Maintenance Person month E o Cumulative Maintenance Cost 1535248 53 Overall Development and Maintenance Cost 5676351 82 Page No
7. click it 4 If the file saving is to store a new report file choose the desired directory then type in the filename 5 Choose desired directory for file saving Look at the filter input box The path found in this box represents the directory where the report file is going to be saved This path will be changed after each directory change To change the directory click the appropriate directory choice from the Directories scroll list then click the Filter button 6 After the desired filename is selected or inputted click the OK button to initiate report file saving 7 To print a COCOMO project report execute the local commands for your system in order to send the file for printing Export The Export option lets you select a directory to write files that can be imported into Excel COCOMO Import amp Analyze Tool is an Excel template which automates the process of importing the Comma Separated Values CSV files produced by the COCOMO File Export command This command produces two sheets Main which contains Project and Module information and Phases which contains the phase distribution information DO NOT rename those worksheets COCOMO Reference Manual The template automates the process of generating charts which are useful for software project management Though the template produces many useful charts it is still possible to perform your own analysis of the COCOMO data However to do that you must have a detailed kn
8. most likely estimate there is also an optimistic estimate no less than this 90 of the time and a pessimistic estimate no greater than this 9096 of the time 10 Status bar This window displays a short definition of the column headings clicked upon and also displays a short description of the result of the last function initiated by the user 11 Schedule Button This button displays the Schedule Dialog Box as shown in Figure 1 9 Schedule applies to the entire project 12 Scale Factor Button This button displays the Scale Factor Dialog Box as shown in Figure 1 10 Scale factors apply to the project size as a whole 13 Model Selection button This button displays COCOMOII Post Architecture and Early Design Model One of the Models can be selected and applied to the project COCOMO Reference Manual 17 14 Risk Column This column contains the Total risk level for each specific module By clicking on this field a dialog box appears see Figure 1 11 This box displays all of the COCOMOIL related risk levels for the chosen module The total risk of a module 1s computed as total_risk schedule_risk product_risk personnel_risk process_risk platform_risk re use_risk total risk of a module total risk 373 100 For the definitions of schedule risk product risk platform risk personnel risk process risk and reuse risk see Madachy 1997 15 Full time SoftWare Personnel FSWP Column This column houses the calculated
9. ratings for all factors will have SF 5 B 1 16 and a relative effort E 209 PM This represents a large variation but the increase involved in a one level step change in one of the factors is only about 4 7 Scale Factors Very Low Low Nominal High Very High Extra High SE PREC thoroughly largely Somewhat generally largely thoroughly unprecedented unprecedented unprecedented familiar familiar familiar FLEX rigorous occasional some general some general goals relaxation relaxation conformity conformity RESL little 20 some 40 often 60 Generally mostly 90 full 100 15 TEAM very difficult some difficult Basically largely highly seamless interactions interactions cooperative cooperative cooperative interactions interactions PMAT Weighted average of Yes answers to CMM Maturity Questionnaire Table 1 1 Scale Factors for COCOMO II Early Design and Post Architecture Models 1 1 4 Sizing Methods SLOC Lines of Code Counting Rules In COCOMOII the logical source statement has been chosen as the standard line of code Defining a line of code is difficult due to conceptual differences involved in accounting for executable statements and data declarations in different languages The goal is to measure the amount of intellectual work put into program development but difficulties arise when trying to define consistent measures across different languages Breakage due
10. 16 This first displays the total amount of effort estimated for maintenance then sums the effort of development and maintenance together It also displays the total cost of maintenance of the module and then displays the summed total cost of development and maintenance for the entire module FIGURE 7 16 i Module Maintenance Module 1 Note Each individual page can be seen by cycling through the pages pressing either the Previous or Next buttons as needed 80 COCOMO Reference Manual References Amadeus 1994 Amadeus Measurement System User s Guide Version 2 3a Amadeus Software Research Inc Irvine California July 1994 Behrens C 1983 Measuring the Productivity of Computer Systems Development Activities with Function Points JEEE Transactions on Software Engineering November 1983 Boehm B 1981 Software Engineering Economics Prentice Hall Boehm B and W Royce 1989 Ada COCOMO and the Ada Process Model Proceedings Fifth COCOMO Users Group Meeting Software Engineering Institute Pittsburgh PA November 1989 Boehm et al 1995 Cost Models for future Software Life Cycle Process COCOMO 2 0 Annals of Software Engineering Special Volume on Software Process and Product Measurement J D Arther and S M Henry Eds J C Baltzer AG Science Publishers Amsterdam The Netherlands Vol 1 pp 45 60 Chidamber S and C Kemerer 1994 A Metrics Suite for Object Oriented Design IEEE Transactio
11. 16 Print Preview Dialog Box COCOMOII sample est USC COCOMO 11 1999 0 Nest Page PievPaae ImoPage Zoomin 20s Close reet UCI Cerelogemor Adel tossimioci c DENN 3 Select the Print button to print 4 The Next Page button to advance to the next Page 5 The Zoom In button zooms in and the Zoom Out button becomes enabled so that the user can zoom out 6 The Close button closes the Print Preview dialog 2 12 Print Setup The Print Setup option allows the user to set up printing To set up Printing 1 Choose Print Setup from the File menu 2 The Print Setup dialog box will appear as seen in Figure 2 17 COCOMO Reference Manual 39 Figure 2 17 Print Setup Dialog Box 40 2 13 Print Setup HEI Printer Name HP LaserJet 5M Properties Status Default printer Ready Type HP LaserJet 5M Where SATINAXHPLaser Comment Paper Drientation Size Letter y Portrait Source AutoSelect Tray y C Landscape Cancel The Name of the printer can be selected from the dropdown list Properties of the printer can be set by clicking on the Properties button The Network button can be selected to connect to a printer on a network 3 4 5 The Size and Source of the paper can be selected from the dropdown lists 6 7 Select OK when finished to print or select Cancel to not print Exit The Exit option leaves the COCOMO system To Exit C
12. 3 7 To Cut a Module and Remove It From the CLEF 1 Check the module which is to be cut The Check boxes for modules are located in the leftmost column of the CLEF area Place the mouse in the box just to the left of the module name and click 2 Choose Cut from the Edit menu with the mouse 3 The cut module disappears Copy The Copy option copies a module The copied module can be used for Paste To Copy a Module 1 Check the module which is to be copied The Check boxes for modules are located in the leftmost column of the CLEF area 2 Choose Copy from the Edit menu with the mouse 3 The cross sign in the check box disappears Paste The Paste option pastes a previously copied or cut module in the CLEF To Paste a Previously Copied or Cut Module 1 Check the module above which the previously copied or cut module is to be pasted The Check boxes for modules are located in the leftmost column of CLEF area 2 Choose Paste from the Edit menu with the mouse 3 The pasted module appears at the checked position and the modules lower than it were pushed one row down 4 If there is no module checked the Paste will attach the previously copied or cut module at the end COCOMO Reference Manual Chapter 4 Parameters Menu The Parameters menu option will enable you to look at or change the values of effort adjustment factors scale factors and effort schedule estimating equations factors for the current proje
13. 4 Done Help Previous Note Each individual page can be seen by cycling through the pages pressing either the Previous or Next buttons as needed 7 2 Module Maintenance In order to view the maintenance estimation calculations for a module the user can click on Module under the Maintenance menu see Figure 7 1 Upon clicking upon this selection a window will appear displaying the current module names Choose only one of the modules by highlighting the appropriate module name and then clicking upon OK see Figure 7 9 FIGURE 7 9 Module Selection window Modules List Module 1 Module 3 Cancel ad Module Selected Module 1 Help COCOMO Reference Manual 75 Upon exiting the module selection window another window will be appear that displays the selected module name an EAF button an editable labor rate field editable number of years of maintenance field an editable percent of added source instructions field per year of maintenance and an editable percent of modified source instructions field per year of maintenance see Figure 7 10 FIGURE 7 10 Module Maintenance Dialog Box Maintenance Module 1 x EAF HW Labor Rate 4700 Life Span 3 Year Code Modified per Year zo Code Added per Year 25 E Software Understanding SU 0 50 30 Unfamiliarity with Software UNFN 0 0 1 0 0 4 Cancel Help The EAF rate can be changed by clicking upon
14. COCOMO Reference Manual FIGURE 6 2 Phase Distribution window displaying a sample project s overall phase distribution Phase Distribution Project Overall Overall Phase Distribution PROJECT sample SLOC 37791 TOTAL EFFORT 700 036 Person Months PCNT EFFORT PM PCNT SCHEDULE FSWP Plans And Requirements 7 000 43 002 DELE 5 928 8 267 Product Design 17 000 119 006 26 060 7 678 T5 5g Programming 57 819 404 754 47 759 14 070 28 767 Detailed Design 24 940 174 587 ssas ges Code and Unit Test 32 879 230 167 cm c mmm Integration and Test EBCTBI 176 276 eoelow Perak 22 854 In addition each phase of the project s development cycle is represented by the estimated effort the estimated schedule and the estimated number of personnel needed for phase completion Again looking at FIGURE 6 2 the information has been separated into columns The first column displays the phase name The second column displays the percentage that the corresponding phase takes in the estimated effort The third column displays the estimated effort for each phase The fourth column displays the percentage of the estimated schedule that is dedicated to the corresponding phase s completion The fifth column displays the estimated schedule for phase completion And the last column displays the estimated number of personnel needed for phase completion FSWP Note The programming phase has been broken down into two additional phases Detailed Design and Code and
15. COst MOdel version II COCOMOII This is the newly revised version of the original COnstructive COst MOdel COCOMO first published by Dr Barry Boehm in his book Software Engineering Economics Prentice Hall 1981 and Ada COCOMO 1989 predecessors The current model is described in Boehm et al 1995 The primary objectives of the COCOMOIT 1999 effort are To develop a software cost and schedule estimation model tuned to the life cycle practices of the 1990 s and 2000 s To develop software cost database and tool support capabilities for continuous model improvement To provide a quantitative analytic framework and set of tools and techniques for evaluating the effects of software technology improvements on software life cycle costs and schedules The full COCOMOII model includes three stages Stage 1 supports estimation of prototyping or applications composition efforts Stage 2 supports estimation in the Early Design stage of a project when less is known about the project s cost drivers Stage 3 supports estimation in the Post Architecture stage of a project This version of USC COCOMOII implements stage 3 formulas to estimate the effort schedule and cost required to develop a software product It also provides the breakdown of effort and schedule into software life cycle phases and activities from the original COCOMO manual These are still reasonably valid for waterfall model software projects but need to be interpreted for
16. EAF Project x base Incr rating Product RELY DATA DOCU CPLX RUSE base vHI mri m nom mox m Te Tar as Platform TIME STO base _non uz Incr amp os _25s Personnel AEXP PCAP PEXP LTEX PCON base ur uz ac wom won Incr amp 0 75 0 0 0 Project TOOL SITE base nox LO Incr 0 0 User USR1 USRZ base NOM NOM Incr amp 05 05 EAF 1 08 m a DK Cancel Help Figure 7 3 shows the EAF dialog box that is used in the Post Architecture Model It contains sixteen EAF factors plus two user defined factors Figure 7 4 shows the EAF dialog box that is used in the Early Design model Here there are only six EAF factors and two user defined factors FIGURE 7 4 Early Design EAF Maintenance Factors Dialog Box EAF lt sample gt x base incr rating RCPX RUSE PDIF PERS PREX FCIL USRI USRZ base NOM NOM NOM NOM NOM NOM NOM NOM 0 0 0 0 0 0 0 0 Incrz EAF is also affected by Schedule EAF 72 COCOMO Reference Manual When the OK button is clicked in the Project Maintenance Dialog Box a window displaying the first of four pages appears It contains the project name the current development mode the total number of source instructions for development of the project EDSI that is loaded in the CLEF the nominal effort of the project the actual effort of the project t
17. P Print Preview Print Setup Exit ll 2 1 New The New option creates a new project file in the COCOMO working window replacing any previous project file in the working window To Create a New Working File 1 Choose New from the File menu with mouse The working window will now be clear the previous project file in the working window has been removed Note New can be selected anytime however if the previous project file or model file has been modified a warning dialog box will appear and requests confirmation as seen in Figure 2 2 24 COCOMO Reference Manual FIGURE 2 2 Warning Dialog Box USC COCOMO Il x Current Project Has Been Modified Do You Want To Save The Changes 2 If the modifications on the previous file are not to be saved choose Yes otherwise choose No If the No is selected a Save File dialog will appear See Save Project and Save Model respectively 2 2 Load Project The Load Project option is used to retrieve a project file as well as loading it on the working window To Retrieve or Load a Project File 1 Choose Load Project from the File menu with the mouse 2 If a previous project file has been modified in the working window the dialog box as in Figure 2 3 will appear FIGURE 2 3 Warning Dialog Box USC COCOMO Il x Current Project Has Been Modified Do You Want To Save The Changes j No Cancel 3 If the previous project file is to be saved choose
18. Yes then a Save File dialog box will appear See Save Project If the modified file is not to be saved choose No 4 The Load Project dialog box will appear as seen in Figure 2 4 COCOMO Reference Manual 25 FIGURE 2 4 Load Project Dialog Box 26 2 3 Look in C3 Cocomoi Al e ex E a sample est File name Files of type Project Files est y Cancel Z The file name of a COCOMO project has a default format with est as an extension With this window the desired project file can be selected from the Files scroll list for loading If the desired project file does not exist in the scroll list it is necessary to navigate to an appropriate directory 5 Choose desired directory for file loading 6 When the desired file is shown on the Files list click it and click the OK button to initiate project loading 7 After a project file is loaded its file name will be displayed on the PROJECT FILE field at upper left corner on the working window and all modules and related items will be displayed in the CLEF area If the number of modules is beyond the window scope the scroll bar can be used to look at all items Save Project The Save Project option is used to store the results of the current COCOMO project as a file with est extension To Store the Results of Current Project 1 Choose Save Project from the File menu with the mouse If the current project is loaded from a previo
19. column contains the calculated result of the module s individual SLOC divided by the modules most likely effort estimate 19 Estimated Person Month EST PM Column This column holds the module s most likely effort estimate obtained from multiplying Effort Adjustment Factor EAF by Nominal Person Month NOM PM 20 Nominal Person Month NOM PM Column This column holds the module s most likely effort estimate without incorporating the Effort Adjustment Factors EAF but including the proportional effect of the scale factors FIGURE 1 10 Scale Factor Dialog Box 20 Scale Factors x Precedentedness NOM 3 72 Development Flexibility mox 3 04 Architecture risk resolution NOM 4 24 T smcohew ton EE ox soe Process maturity 21 52 NOM 4 68 COCOMO Reference Manual FIGURE 1 11 Risk Level Dialog Box Risk Level lt sample gt x Schedule Risk 0 00 Product Risk 0 00 Platform Risk 0 00 Personnel Risk 0 00 Process Risk 0 00 Reuse Risk 0 00 1 3 Begin Using COCOMO To begin entering a new module either click on the Add Module button on the Tool bar or on the pulldown menu item EditlAdd Module At this point a new module will appear in the CLEF with all values set to their respective defaults Double click upon the module name field in order to give the new module a name U
20. non waterfall projects 1 1 1 Effort Estimation Equation Estimate effort with EQ 1 1 5 0 91 0 01 SP se BRAK NE eod ic DE ET ies i224 A Iu x Size ree i where a kastoc qu ATA AA SU 04 DM 03 CM 03 2 100 100 3 B 091 001 gt SF J 1 Symbol Description A Constant currently calibrated as 2 45 AA Assessment and assimilation ADAPT Percentage of components adapted represents the effort required in understanding software AT Percentage of components that are automatically translated ATPROD Automatic translation productivity BRAK Breakage Percentage of code thrown away due to requirements volatility CM Percentage of code modified DM Percentage of design modified EM Effort Multipliers RELY DATA CPLX RUSE DOCU TIME STOR PVOL ACAP PCAP PCON AEXP PEXP LTEX TOOL SITE IM Percentage of integration and test modified KASLOC Size of the adapted component expressed in thousands of adapted source lines of code KNSLOC Size of component expressed in thousands of new source lines of code PM Person Months of estimated effort SF Scale Factors PREC FLEX RESL TEAM PMAT SIZE In thousands of lines of code of new or adapted source lines of code SU Software understanding zero if DM 0 and CM 0 COCOMO Reference Manual 1 1 2 Schedule Estimation Equation Determine time to develop TDEV with an estimated effort PM that ex
21. the section labeled COCOMOII Downloads Software and Documentation or ftp ftp usc edu pub soft engineering COCOMOII where you will see 6 files c99sunos tar gz c99windows zip usersman ps usersman pdf modelman ps modelman pdf 22 COCOMO Reference Manual Chapter 2 File Menu The COCOMO file types include project file model file report file calibration file and csv file The first three are discussed here The others are discussed in later chapters The project file in COCOMO stores a project s data which include project name project scale factors project schedule constraint module name SLOC labor rate effort adjustment factors EAF and COCOMO related calculation results The COCOMO system gives all project files an est extension Regarding the model file as we mentioned in chapter one COCOMO incorporates 17 predictor factors or cost driver attributes which are grouped into four categories software product attributes platform attributes personnel attributes and project attributes Each of these cost drivers attributes determines a multiplicative factor which estimates the effect of the attribute in software development effort There are also two user defined EAF factors plus the project level required development schedule EAF factor Besides these cost drivers COCOMO also has scale factors These multiplying factors and effort estimating equations constitute the model of a project COCOMO has assign
22. to change of requirements also complicates sizing To minimize these problems the Software Engineering Institute SET definition checklist for a logical source statement is used in defining the line of code measure The Software Engineering Institute SEI has developed this checklist as part of a system of definition checklists report forms and supplemental forms to support measurement significant module interfaces specified 46 significant risks eliminated COCOMO Reference Manual COCOMO Reference Manual definitions Park 1992 Goethert et al 1992 Figure 1 1 shows a portion of the definition checklist as it is being applied to support the development of the COCOMOII model Each checkmark in the Includes column identifies a particular statement type or attribute included in the definition and vice versa for the excludes Other sections in the definition clarify statement attributes for usage delivery functionality replications and development status There are also clarifications for language specific statements for ADA C C CMS 2 COBOL FORTRAN JOVIAL and Pascal Some changes were made to the line of code definition that departs from the default definition provided in Park 1992 These changes eliminate categories of software which are generally small sources of project effort Not included in the definition are commercial off the shelf software COTS government furnished software GFS other products langua
23. 0 Plans and Requirements Phase window for the overall Module Phase Distribution Module Plans Requirements Module 1 Life Cycle Phase Plans nd Requirements Life Cycle Effort 24 408 Person Months Life Cycle Schedule 5 928 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 45 940 DIIS 5 928 1 892 Product Design 17 030 4 157 5 928 0 701 Programming 4 560 TITS 5 928 0 188 Test Planning 3 530 0 862 5 928 0 145 Verification and Validation 7 030 IUIS 5 928 0 289 Project Office 13 440 3 280 5 928 0 553 CM QA 3 000 0 732 5 928 0 124 Manuals 5 470 1 335 5 928 0 225 6 2 3 Programming Module Phase Distribution The programming phase distribution allows the user to view the components of this particular phase When the Programming distribution is chosen from the Module Phase distribution menu the window shown in FIGURE 6 11 is displayed This window displays the following information Module name the total Module SLOC the total estimated Module effort and the total estimated Module schedule In addition the window displays the activity s requirements analysis product design programming test planning verification amp validation Project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 11 To exit from this window click the OK button COCOMO Reference
24. 0 modules the predefined graphs may not display correctly However by disabling the labeling of the data points resizing the graphs you may be able to achieve an acceptable display To Export 1 Choose Export from the File menu 2 The Export dialog box will appear as seen in Figure 2 12 Figure 2 12 File Export Dialog Box File Export Ea Select a directory for COCOMOI to save csv files Use these files in Excel with COCOMO xls CACOCOMOII Browse Cancel Help 3 When you click on OK a dialog box appears if Main csv and Phases csv already exist as shown in Figure 2 13 Figure 2 13 Subsequent File Export Dialog Box USC COCOMO II 9 Main csv and Phases csv already exist Do you want to replace them 36 COCOMO Reference Manual 4 If Yes is selected COCOMO saves two files main csv and phase csv in the chosen directory If No is selected these files will not be replaced 2 10 Save Screens The Save Screens option allows the user to save the image of any Cocomo window To Save Screens 1 Choose Save Screens from the File menu 2 The Save Screens dialog box will appear as seen in Figure 2 14 3 Follow the directions on the dialog box Figure 2 14 Save Screens Dialog Box USC COCOMO Il To Save the image of any COCOMO window 1 Click on the window 2 Press Alt Print Screen 3 Place your cursor in any program e g Word PowerPoint Paint etc 4 Press C
25. 43 1 14 1 00 1 00 1 00 SITE 1 22 1 09 o LEE modification click the OK button 4 1 5 User Defined EAF The User Defined EAF option displays two cost driver USR1 and USR2 and their corresponding ratings and multipliers Select User EAF from the Parameters menu with the mouse The User EAF Dialog Box will appear as Figure 4 6 FIGURE 4 6 User Defined EAF Dialog Box USER DEFINED PARAMETERS Eg VLO LO NOM D HI VHI XHI USRl 1 00 1 0 1 00 1 00 1 00 1 00 USRZ 1 00 1 00 1 00 1 00 1 00 1 00 Cancel Help To modify these values go straight to those edit boxes and type new values When finished with the modification click the OK button 48 COCOMO Reference Manual 4 2 Early Design Model FIGURE 4 7 Early Design Model EAF Dialog Box XLO VLO LO NOM HI VHI XHI RCPX fo 73 fo ez fo 98 p oo 1 30 f 74 E 38 RUSE ox poo 0 95 1 00 1 07 1 15 1 24 PDIF ox poo 0 87 1 00 1 29 1 81 2 61 PERS 2 12 1 62 1 26 1 00 0 83 0 63 0 50 PREX 1 59 1 33 1 12 1 00 0 87 0 71 0 62 FCIL 1 4 f 20 1 10 1 00 fo 87 fo 73 Jo sz SCED po 1 43 1 14 1 00 1 00 1 00 poa USRl fox 1 1 00 1 00 1 00 poor USRZ fox 1 1 00 1 00 1 00 poa Cancel i 4 3 Scale Factors The Scale Factors option displays five development attributes PREC FLEX RESL TEAM and PMAT and their corresponding ratings and values Select Scale Factors from the Parameters menu with the mouse The Scale Fact
26. CLEF data a warning message appears as shown in Figure 5 7 To insert a new archived project from the CLEF click on Insert COCOMO Reference Manual FIGURE 5 5 Projects Dialog Box Projects x Date Effort Schedule 725738114716 520 21 a 7 25 988 11 47 30 168 13 7 25 98 11 47 40 75 12 5 7 25 88 11 47 53 418 18 Insert Delete Display Cancel Help FIGURE 5 6 Delete Warning Dialog USC COCOMO II e Do you want to delete the selected project COCOMO Reference Manual 55 FIGURE 5 7 Display Warning Dialo USC COCOMO Il Do you want continue w e This operation will delete all data on the CLEF 5 5 Compute This command takes all of the data that has been archived and uses it to compute new constant and or exponent values for the effort equation and for the schedule equation There are two options to calibrate equation parameters One is the Constant Term and the other one is Development Mode Those two options are explained below in detail They are displayed in this window and compared to the values currently used by COCOMOII To get COCOMOII to use these values click on Accept as shown Figure 5 8 FIGURE 5 8 Compute Dialog Box Calibrated Parameters x Calibration Method For less than 8 projects select md the cofficients only calibration Coefficients and Exponents method Current Effort Coefficient 2 94 Effort Expone
27. COCOMO Import and Analyze Tool provides you with maximum flexibility by Copying the relevant parts of Main and Phases sheets into the sheet for the purpose of the generation of graphs Using references to the values entered in Main and Phases sheets so that if you update the values in those sheets the changes will be reflected in all the other calculated sheets as well as the charts Note however that if you introduce changes in any calculated sheet the changes wont be carried over to Main or Phases Allowing you to change some values In particular the sheets Project Cumulative Cost and Project Cost per Phase allow you to enter the Cost per Person Month per Phase The provided value is just an average computed from the COCOMO values However you can use the value which reflects more accurately your organizational process If you click on the button marked Delete All Generated Sheets and you select OK all the calculated sheets will be deleted If you introduce changes to one of the calculated sheets and to prevent the sheet from being deleted it is recommended that you rename the sheet The Menu sheet is protected to avoid accidental displacement of the various buttons It also disables resizing rows and columns as well as selecting a range of cells If you need to make changes to the Menu sheet toggle the Protect Sheet Unprotect Sheet from the Protection command under the Tools menu Chart Explanations Project Sch
28. COCOMO Reference Manual FIGURE 6 12 Product Design window for the overall Module Phase Distribution Module Product Design Module 1 x Life Cycle Phase Product Design Life Cycle Effort 59 276 Person Months Life Cycle Schedule 7 678 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 12 500 7 409 7 678 0 965 Product Design 41 000 24 303 7 678 3 165 Programming 13 030 7 724 7 678 1 006 Test Planning 5 530 3 278 7 678 0 427 Verification and Validation 7 030 4 167 7 678 0 543 Project Office 10 940 6 485 7 678 0 845 CH QA 2 500 1 482 7 678 0 193 Manuals 7 470 4 428 7 678 0 577 6 2 5 Integration and Test Module Phase Distribution The integration amp test phase distribution allows the user to view the components of this particular phase When the Integration and Test distribution is chosen from the Module Phase distribution menu the window shown in FIGURE 6 13 is displayed This window displays the following information Module name the total Module SLOC the total estimated Module effort and the total estimated Module schedule In addition the window displays the activities requirements analysis product design programming test planning verification amp validation Project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 13 To exit from this window click t
29. COMO is not calibrated for Total SLOC 2000 and a warning is issued FIGURE 1 4 SLOC Dialog Box Source Lines of Code SLOC SLOC Imput Dialog lt sample gt 9 e 14 COCOMO Reference Manual FIGURE 1 5 SLOC Dialog Box Function Points FP SLOC Imput Dialog lt sample gt A COCOMO Reference Manual FIGURE 1 6 SLOC Dialog Box Adaptation Adjustment Factor AAF SLOC Input Dialog lt sample gt e El 16 COCOMO Reference Manual 7 Labor Rate Column This column contains the amount of money at which a developer working on a particular module would be paid per month The labor rate can be edited by clicking on the corresponding Labor Rate box and entering the new value via the edit area The range on labor rate is between 0 and 99 999 8 Effort Adjustment Factor EAF Column This column displays the product of the effort multiplier cost drivers for each specific module By clicking on this field a dialog box appears see Figure 1 7 This box displays all of the cost drivers inter cost drivers and their current ratings The cost drivers are divided into the groupings Product Platform Personnel and Project The increments on the cost drivers are rated as 0 25 5096 and 75 i e the amount of change to the next rating level The ratings for each multiplier can be changed by cycling through the available ratings until the desired rating is displayed As the cost dr
30. Dialog Box will appear as Figure 4 3 FIGURE 4 3 Platform Dialog Box Platform Parameters x VLO LO NOM HI VHI XHI To modify these values go straight to those edit boxes and type new values When finished with the modification click the OK button 46 COCOMO Reference Manual 4 1 3 Persomnel The Personnel option displays six cost drivers ACAP AEXP PCAP PEXP LEXP and PCON and their corresponding ratings and multiplier values Select Personnel from the Parameters menu with the mouse The Personnel Dialog Box will appear as Figure 4 4 FIGURE 4 4 Personnel Dialog Box Personnel Parameters x VLO LO NOM HI VHI ACAP az 1 19 1 00 0 85 0 71 AEXP zz 1 10 1 00 0 88 0 81 PCAP 34 1 15 PEXP 19 1 09 1 00 0 91 0 85 LTEX 20 1 09 1 00 0 91 0 84 TT i mm PCON 29 1 12 1 00 0 90 fo To modify these values go straight to those edit boxes and type new values When finished with the modification click the OK button 4 1 4 Project The Project option displays three cost drivers TOOL SCED and SITE and their corresponding ratings and multiplier values Select Project from the Parameters menu with the mouse The Project Dialog Box will appear as Figure 4 5 COCOMO Reference Manual 47 FIGURE 4 5 Project Dialog Box To modify these values go straight to those edit boxes and type new values When finished with the Project Paramters x VLO LO NOM TOOL 1 17 1 09 0 i SCED 1
31. M QA 58 59 60 61 62 64 66 67 COCOMO 1 9 11 13 21 22 24 25 27 28 29 30 36 38 43 49 57 59 COCOMOSI 57 COCOMOII 1 3 5 51 56 87 coefficient 51 complexity level 8 Computer 43 Copy 41 Cost 18 cost drivers 16 COTS 5 CPLX 10 43 Cut 41 D DATA 9 43 Design 57 development mode 16 DI 8 DM9 DOCU 9 43 E EAF 10 18 21 51 Edit 11 37 38 40 41 EDSI 57 Effort Adjustment Factor 16 effort multipliers 10 EM 10 Equations 43 EST PM 16 18 Exit 36 exponent 51 F File 11 Files 25 FLEX 48 FSWP 16 17 58 60 61 62 64 66 57 Function point 8 functionality 5 8 G GFS 5 84 COCOMO Reference Manual H Help 11 I IM 9 Instruction Cost 17 integration amp test 57 integration amp test phase 62 68 J Java 87 Java COCOMO 87 K KSLOC 4 9 L Labor Rate 16 labor rate 21 LEXP 10 45 M Main Menu bar 11 Maintenance 11 71 Microhelp 16 Module 12 77 module 1 16 41 43 57 71 model file 21 22 27 28 30 Module Phase Distribution 64 N New 22 NOM PM 18 57 O overall phase 65 P Parameters menu 43 45 46 48 49 Paste 41 PCAP 10 45 PCON 10 45 Percent of Code Modification CM 9 Percent of Design Modification DM 9 Percent of Integration Required for Modified Software IM 9 Personnel 43 45 Personnel attributes 10 personnel attributes 9 21 PEXP 10 45 Phase Distribution 11 57 phase distribution 57 Plan amp Requirement
32. Manual 65 FIGURE 6 11 Phase Distribution Module Programming Module 1 Programming Phase window for the overall Module Life Cycle Phase Programming Life Cycle Effort 201 604 Person Months Life Cycle Schedule 14 070 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 4 000 8 064 14 070 0 573 Product Design 8 000 16 128 14 070 1 146 Programming 56 500 113 907 14 070 8 096 Test Planning 5 030 10 141 14 070 0 721 Verification and Validation 8 030 16 189 14 070 PREGI Project Office 6 470 13 043 14 070 0 927 CH QA 6 500 13 104 14 070 0 931 Manuals 5 470 115027 14 070 0 784 6 2 4 Product Design Phase Distribution The product design phase distribution allows the user to view the components of this particular phase When the Product Design distribution is chosen from the Module Phase distribution menu the window shown in FIGURE 6 12 is displayed This window displays the following information Module name the total Module SLOC the total estimated Module effort and the total estimated Module schedule In addition the window displays the activities requirements analysis product design programming test planning verification amp validation Project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 12 To exit from this window click the OK button 66
33. OCOMO 1 Choose Exit from the File menu with the mouse 2 This causes your system to terminate the cocomo program COCOMO Reference Manual Chapter 3 Edit Menu The Edit Menu option supplies several useful commands which will enable you to establish a project more conveniently To select the Edit menu and its options click on Edit with the mouse then the Edit menu will appear as Figure 3 1 FIGURE 3 1 Edit Menu File View Parameters Calibrate Phase Maintenance Help Ol Add Module Etre Clear All Modules Str eZ Scale Factor Schedule Development Model Post Architecture Ij nda Sat Str 98 ony te Paste Bike Snap Shot Module 1 13574 5670 00 4 27 57 3 244 7 55 s 1387226 21 10z 2 8 5 7 4 3 1 Add Module The Add Module option adds a new module to the project that is currently being worked upon by the user This Add Module function can be done by pressing the Add Module button in the Tool bar area 3 2 Clear All Module The Clear All option erases all modules of the current project on the working window To Erase All Modules of Current Project 1 Choose Clear from the Edit menu During the execution of the Clear command if some changes have occurred on the currently viewed project and have not been saved the warning dialog box will appear as Figure 3 2 2 If you really want to clear click Yes If not click No 3 Aft
34. Save As Model Make Report Exit mA lt O gt Ar Z View Alt V Edit Meta E Alt E Add Module Ctrl A Clear All Modules Snapshot aaz w zx o o Undo Ctrl Z Ctrl Z Cut Ctrl X Ctrl X Copy Ctrl C Ctrl C Paste Ctrl V Walaa ry gt Ctrl V Parameters Meta P Alt R Product Platform Personnel Project User EAF Scale Factor Equation Reset AN EZ Calibrate Meta C Alt C File Load File Save File Save As Project Compute C 5ur Phase On Ad An mato Meta P Alt P Project Overall Phase Plans amp Requirement Programming Product Design Integration amp Test CU VEO CU VAEO COCOMO Reference Manual Module Overall Phase Plans amp Requirement Programming Product Design Integration amp Test 9 um oz Help Meta H Alt H On Application O On Version O COCOMOII User s Manual Z lt PTI TO V ODO a zz Using Help About USC COCOMOII 2G COCOMO Reference Manual 83 A AA9 AAF 9 ACAP 10 45 ACT PM 18 57 Adaptation 9 Adaptation Adjustment Factor 13 Add Module 19 ADSI 9 AEXP 10 45 ASLOC 9 B Boehm 1 Breakage 2 C Calibrate 11 43 calibration 11 Clear 37 CLEF 11 41 CM9 C
35. Sched PROD COST INST Staff RISK meta Hines FE optinietic Sea eed paa mea ie woot nel erra 250 apro a zi ses mea ses O ES 22s 10 Project File C COCOMOII sample est Is Loaded A 20 Pessimistic 4 X This column is reserved for identifying a module Pressing upon this field for a given module will mark the desired module Marking is denoted by an x that appears in this column Only one module can be marked at a time Modules are marked in order to perform module deletion cutting copying or pasting 5 Module Name Column This column is used to house the name of each module located in the Module Area The module name can be changed by clicking twice on the desired module name box and entering the changes into the module name field Upon completion of editing press Return 6 Module Size SLOC Column This column shows the SLOC of each module located in the Module Area The value for SLOC can be computed in one of three ways One the value can be entered directly in the SLOC field as shown in Figure 1 4 Two by using the function point model as shown in Figure 1 5 Three by using Adaptation Adjustment Factor as shown in Figure 1 6 Each of the three dialog boxes allows the setting of BRAK Upon completion click on OK in the associated dialog box There is a limit to the range of input The input or computed value for SLOC must be within the range 0 9 999 999 COCOMO Reference Manual 13 Note CO
36. The requirements as defined in the first phase are used to determine the fitness of the delivered product The phase distribution menu has two selections project phase distribution and module phase distribution The project phase distribution allows the user to view the development phases for the entire project all together or individually The module phase distribution allows the user to view the development phases for a particular module either all together or individually These two variations of phase distribution are discussed further in this chapter under sections 6 1 and 6 2 in this chapter NOTE These phase distribution estimates are retained from the COCOMO81 model which assumed a waterfall sequentially phased process model If your project s process model is not a waterfall these phase distributions are either inapplicable or need to be reinterpreted FIGURE 6 1 Phase Distribution Sub menu If C COCOMOII sample est USC COCOMO 11 1999 0 File Edit View Parameters Calibrate MESA Maintenance Help Overall Phase Plans amp Requirements Programming Project Name Product Design Integration amp Test Schedule 1 Post Architecture Module 1 13574 5670 00 4 27 57 3 244 7 55 s 1387226 21 102 2 8 6 7 414 COCOMO Reference Manual 57 6 1 Project Phase Distribution In order to view the phase distribution of an entire project the user can click o
37. USC COCOMOII Reference Manual University of Southern California COCOMO Reference Manual This manual is compatible with USC COCOMOIT 1999 version 0 Copyright Notice This document is copyrighted and all rights are reserved by University of Southern California Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and full citation on the first page Abstracting with credit is permitted To copy otherwise to republish to post on servers or to redistribute to lists requires prior specific permission and or fee Copyright O 1995 1999 USC All rights reserved Warranty This manual is provided as is without warranty of any kind either express or implied including but not limited to the implied warranties of merchantability and fitness for a particular purpose Moreover USC reserves the right to revise this manual and to make changes periodically without obligation to notify any person or organization of such revision or changes Trademark Acknowledgment USC has made every effort to supply trademark information about company names products and services mentioned in this document Trademarks indicated below were derived from various sources UNIX is a registered trademark of AT amp T Bell Laboratories Motif is a tradem
38. Unit Test The detailed design is a follow up to the product design phase In this sub phase those points developed in the product design are elaborated to a point necessary to breakdown agreed functions into units necessary for coding The code and unit test sub phases house the actual coding effort of the individual units of code The testing of these units upon completion is also encompassed within this sub phase 6 1 2 Plans and Requirements Project Phase Distribution The plans and requirements phase distribution allows the user to view the components of this particular phase When the Plans and Requirements distribution is chosen from the Project Phase distribution menu the window shown in FIGURE 6 3 is displayed This window displays the following information project name the total project SLOC the total estimated project effort and the total estimated project schedule In addition the window displays the estimated effort for the activities of requirements analysis product design programming test planning verification amp validation project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 3 To exit from this window click the OK button COCOMO Reference Manual 59 FIGURE 6 3 Plans and Requirements Phase window for the overall project Phase Distribution Proje
39. ang Hyun and Eunsook Bang COCOMO II 1998 0 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Jongmoon Baik COCOMO II 1999 0 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Jongmoon Baik Cyrus Fakharzadeh Marwan Abi Antoun Note This manual is sufficient for the X Windows and MS Windows 95 98 NT versions of USC COCOMO II 1999 programs Though there are some user interface differences between these systems the core component of all versions is identical Some of the material used in this manual has been taken from Software Engineering Economics by Barry Boehm Prentice Hall with permission of the author COCOMO Reference Manual Chapter LE Introduction atico eee eR 3 1 I What is COCOMO Posse ep Der RE Pei ORBE tenderet 3 1 1 1 Effort Estimation Equation irri Mer EPOR EHE EE ETE EE sb Pet eR UY 4 1 1 2 Schedule Estimation Equation terit ipee dtp tee P HER eL leer tenet ipt 5 1 1 3 Scale Factors ses once PED RUPEE EHE OE UO DO v IRR 5 1 1 4 Sizing Methods neo eere iter Up HD arp epi PE OU OPERE Uer ERE 6 1 1 5 FP Counting with Unadjusted Function Points essere ener nennen trennen trennen 9 1 1 6 A AF Adaptation Adjustment Factors tereti dnb tpe petet ir deer eee USE HR ep obsesededs 10 1 1 7 Etfort Multipliers 3 ene tei ene ERR DERE e 10 152 Navigating COCOMO inre EROR URS OE IER Wes te
40. ark of Open Software Foundation Inc Sun Microsystem and Sun Workstation are registered trademarks and OpenWindows Sun 3 Sun 4 and SPARCstation are trademarks of Sun Microsystems Inc X Window System is a trademark of the Massachusetts Institute of Technology MS Windows95 is a trademark of Microsoft Corporation Acknowledgments COCOMO81 Version 1 0 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Alfredo Arcilla Joyce Balimbin Gina Gaborno Larry Klein Robert Kosai Deseree Moon Jason Pan Thomas Quayle Isaiah Simmons Scott Zechiel COCOMO 81 Version 1 1 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Ing Jer Huang COCOMO 81 Version 10 0 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers M Susan Lane Ping Luo Lorna Zorman COCOMO 2 0 Version 2 0 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Wiryadi Adidharma Sen Ho Chang Shu fen Cheng Yu Chuan Lin Steve K Luk Shawne Robinson Tuan Ton COCOMO 2 0 Version 2 0 5 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Thomas Majchrowski Suppachai Sangtongkhamsuk Lloyd Manglapus COCOMO 1I 1997 2 Principal Investigator Dr Ellis Horowitz Student Designers Testers and Programmers Jongmoon Baik Jungwon Park James Chou Dana Flora Adams S
41. ave a maximum of 5 contribution to estimated effort This is inconsistent with COCOMO experience thus COCOMO II uses Unadjusted Function Points for sizing and applies its reuse factors cost driver effort multipliers and exponent scale factors to this sizing quantity COCOMO Reference Manual 9 1 1 6 AAF Adaptation Adjustment Factors Adaptation of Existing Code COCOMO is not only capable of estimating the cost and schedule for a development started from scratch but it is also able to estimate the cost and schedule for products that are built upon already existing code 1 e reused code Adaptation considerations have also been incorporated into COCOMO where an estimate for KSLOC will be calculated This value will be substituted in place of the SLOC found in the equations already discussed This adaptation of code utilizes an additional set of equations that are used to calculate the final count on source instructions and related cost and schedule These equations use the following values as components Adapted Source Lines of Code ASLOC The number of source lines of code adapted from existing software used in developing the new product Percent of Design Modification DM The percentage of the adapted software s design that received modification to fulfill the objectives and environment of the new product Percent of Code Modification CM The percentage of the adapted software s code that receives modification to fulfill the o
42. bjectives and environment of the new product Percent of Integration Required for Modified Software IM The percentage of effort needed for integrating and testing of the adapted software in order to combine it into the new product Percentage of reuse effort due to Software Understanding SU Percentage of reuse effort due to Assessment and Assimilation AA Programmer Unfamiliarity with Software UNFM These components are brought together in Figure 1 6 The AAF is the adaptation adjustment factor The AAF is the calculated degree to which the adapted software will affect overall development 1 1 7 Effort Multipliers There are a number of contributing factors to a project s delivery time and effort Development productivity was found to be affected by additional factors that were found to fall under the headings product attributes platform attributes personnel attributes and project attributes Product attributes refer to the constraints and requirements placed upon the project to be developed These included Required software reliability RELY Database size DATA Documentation match to life cycle needs DOCU Product complexity CPLX Required Reusability RUSE Platform attributes refer to the limitations placed upon development effort by the hardware and operating system being used to run the project These limitations are COCOMO Reference Manual COCOMO Reference Manual listed below Execution time constra
43. button 42 COCOMO Reference Manual 2 Upon completing the modification of the project values a comparison can be made between the previously snapped project and the modified project by clicking again upon the Snapshot option in the Edit menu 2 Now the values in the upper part of the window will likely be different from the current values in the lower part To restore the upper values click on Revert The two sets of values are interchanged FIGURE 3 4 Snapshot Dialog Box 2 SnapShot x Snapped Project EST PM Sched PROD COST INST FSWP RISK Total EDSI 37791 Optimistic 494 2 26 4 76 5 2961917 82 78 4 Most Likely 617 7 28 3 61 2 3702397 27 98 0 772 11 30 4 48 9 4627996 59 122 5 Current Project EST PM Sched PROD COST INST FSWP RISK Total EDSI 37791 Optimistic seo o 27 4 67 5 3312882 63 87 7 Most Likely 700 0 4141103 29 109 6 RE REI KE EDO 875 0 31 6 43 2 5176379 12 137 0 27 7 Pessimistic Pessimistic 4 When finished click the Done button 3 4 Undo The Undo option retracts the previous cut or paste done on a module To Retract Previous Cut Paste for a Module 1 Choose Undo from the Edit menu with the mouse 2 The changed module will go back to its previous status 3 5 Cut The Cut option copies a module into the cut buffer and removes it from the current project The cut module can be used for Paste COCOMO Reference Manual 43 3 6
44. cludes the effect of the SCED effort multiplier 028 02x B 1 01 TDEV 3 67 lt ced y loss where 5 B 0 91 001 b SF Peal Symbol Description PM Person Months of estimated effort from Early Design or Post Architecture models excluding the effect of the SCED effort multiplier SF Scale Factors PREC FLEX RESL TEAM PMAT TDEV Time to develop SCED Schedule SCED The compression expansion percentage corresponding to the SCED effort multiplier 1 1 3 Scale Factors Table 1 1 provides the rating levels for the COCOMOII scale drivers The selection of scale drivers is based on the rationale that they are a significant source of exponential variation on a project s effort or productivity variation Each scale driver has a range of rating levels from Very Low to Extra High Each rating level has a weight W and the specific value of the weight is called a scale factor A project s scale factors W are summed across all of the factors and used to determine a scale exponent B via the following formula 5 B 09140501 x SF j 1 COCOMO Reference Manual For example if scale factors with an Extra High rating are each assigned a weight of 0 then a 100 KSLOC project with Extra High ratings for all factors will have SF 0 B 91 and a relative effort E 100 66 PM If scale factors with Very Low rating are each assigned a weight of 5 then a project with Very Low 5
45. ct To choose the Parameters menu and its options click on Parameters with the mouse The Parameters menu will appear as Figure 4 1 FIGURE 4 1 Parameters Menu ACOCOMO llAsample est USC COCOMO 11 1999 0 Product B Platform Early Design P PODES Scale Factor Schedule Project Name Scale Factors Project User Defined Development Model Post Architecture Equation Reset Module m 13574 5670 00 4 27 57 3 244 7 55 51387226 21 102 2 8 5 7 4 4 1 Post Architecture Model 4 1 1 Product The Product option displays five cost drivers RELY DATA DOCU CPLX and RUSE and their corresponding ratings and multiplier values Select Product from the Parameters menu with the mouse The Product Dialog Box will appear as Figure 4 2 COCOMO Reference Manual 45 FIGURE 4 2 Product Dialog Box Product Paramters x VLO LO RELY fo ez fo sz DATA ox 59 DOCU DC fo 91 o i CPLX 0 73 fo e7 1 00 1 17 1 34 1 74 RUSE fox 5s o 1 07 1 15 To modify these values go straight to those edit boxes and type new values When finished with the modification click the OK button 4 1 2 Platform The Platform option displays three cost drivers TIME STOR and PVOL and their corresponding ratings and multiplier values Select Platform from the Parameters menu with the mouse The Platform
46. ct Plans Requirements Life Cycle Phase Plans And Requirements Life Cycle Effort 49 002 Person Months Life Cycle Schedule 5 928 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 45 940 AE 5 928 3 798 Product Design 17 030 8 345 5 928 1 408 Programming 4 560 2 235 5 928 0 3727 Test Planning 3 530 1 730 5 928 0292 Verification and Validation 7 030 3 445 5 928 0 581 Project Office 13 440 6 586 5 928 TIT CM QA 3 000 1 470 5 928 0 248 Manuals 5 470 2 680 5 928 0 452 6 1 3 Programming Project Phase The programming phase distribution allows the user to view the components of this particular phase When the Programming distribution is chosen from the Project Phase distribution menu the window shown in FIGURE 6 4 is displayed This window displays the following information project name the total project SLOC the total estimated project effort and the total estimated project schedule In addition the window displays the estimated effort for the activities of requirements analysis product design programming test planning verification amp validation project office CM QA and manuals These activities are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 4 To exit from this window click the OK button FIGURE 6 4 Programming Phase window for the overall project Phase Distribution Project Programming
47. d Test Life Cycle Effort 176 276 Person Months Life Cycle Schedule 7 713 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 2 500 4 407 7 713 0 571 Product Design 5 000 8 814 7 713 1 143 Programming pra al 65 435 7 713 8 484 Test Planning 3 000 5 288 7 713 0 686 Verification and Validation 29 440 51 895 Conte oe 6 728 Project Office 7 470 13 168 TON le T0 CH QA 8 000 14 102 mud 1 828 Manuals 7 470 13 168 l3 T2707 FIGURE 6 7 Phase Distribution Module Sub menu 129 C COCOMOII sample est USC COCOMO 11 1999 0 File Edit View Parameters Calibrate Ma Maintenance Help NATA 3 25 Project OSW Ea Oj el i E 3 px ne Overall Phase Plans amp Requirements Project Name Programming Product Design Integration amp Test Schedule el Post Architecture Module 1 13574 5670 00 4 27 57 3 244 7 55 s 1387226 21 102 2 8 6 7 4 4 6 2 Module Phase Distribution Four formats for viewing will appear in another menu overall phase plan amp requirements programming and integration amp test see FIGURE 6 7 Each of these menu selections will be discussed in sections 6 2 1 6 2 4 respectively The phase distribution of plan amp requirements programming and integration amp test are broken down into activities These activities include requirements analysis product design programming test planning verification amp validation Project o
48. de Da ees 12 1 3 Begin Using COCOMO nite ee ea eee e eter Reo At Hd dette Roto 21 1 4 Running COCOMO Windows NT and UNIKX sese enenene tene tren trennen rene enne ens 22 Chapter 2 File Menu zuo neben n er rH ing aan EO TORO ege asa eere d o e eerte ae 23 2 1 NeWastuenedu neuem aio ataca 24 2 2 Load Project a in 25 2 3 Save Project ne ias 26 2 4 Save AS Project zu ioi erae paro eee ee Ee EU eden 27 2 5 Load Model ens ete eed io elite eddie tte De 28 2 6 Save Model eeu is 30 2 7 Save As Model c tte eoe eee eie ien eiie ie He Rede aes 30 2 8 Make pc 31 2 9 Export EE ee aede ad 32 210 Save Screens eie ah veces ote e ERE spe tt tei Pet erint ro n gee mite E bete e e ee 37 2 11 PrmntsScreenc ecoute atada 37 21 Print Previews i deeem et bebe a 38 2 12 ES gd ete gie E etd tee e ttes d bores 39 ZAG E gt tub UD petet is 40 Chapter 3 Edit Menu iiir dete tte pia 41 3 1 Add Mod le te MM 41 3 2 Clear All Module iii degens 41 3 3 Snapshot RN 42 ron E Y n 43 MG ee 43 3 6 NN 44 3 7 Past aras 44 Chapter 4 Parameters Men ribera die penes 45 4 1 Post Architecture Model ete ee eed iia 45 4 1 1 zou gc 45 4 1 2 A H 46 4 1 3 Personnel e
49. ect name an EAF button an editable labor rate field editable 70 COCOMO Reference Manual number of years of maintenance field an editable percent of added source instructions field per year of maintenance and an editable percent of modified source instructions field per year of maintenance see Figure7 2 The EAF rate can be changed by clicking upon the corresponding button This action FIGURE 7 2 Project Maintenance Dialog Box EAF 1 00 Labor Rate 5500 Life Span 3 Year Code Modified per Year 15 Code Added per Year Software Understanding S0 0 50 30 Unfamiliarity with Software UNFM 0 0 1 0 0 4 Cancel Help will result in the appearance of an EAF dialog box where the cost driver ratings can be changed as described in the introduction see Figure 7 3 Upon completing the adjustment of the cost drivers click the OK button or click the Cancel button to return to the CLEF without viewing maintenance estimations After exiting the EAF dialog box with the OK button you will be returned to the Project Maintenance Dialog box to continue inputting the editable values Click upon the OK button upon completion of editing the displayed fields or click upon the Cancel button if no changes are desired to the default values if more assistance the Help button is available to receive on line assistance COCOMO Reference Manual 71 FIGURE 7 3 Project Maintenance EAF Dialog Box Maintenance
50. ed default values and equations for the annually calibrated default model Each time a COCOMO project is created its effort estimate is based on the default model COCOMO provides flexibility in changing the values of multiplicative factors effort estimating equation or schedule estimating equation An adjusted model can no longer be considered default values and therefore it will be lost if COCOMO is exited without saving it in a model file Upon saving this model file these altered values can be applied to another project by loading the saved model file The COCOMO system gives all model files a mod extension The report file is a summary report of the COCOMO project This report contains all entered and calculated values of a project in a formatted text file These files are given a rpt extension The File menu option will enable you to create retrieve save or print COCOMO files To select the File menu and its options click on File with the mouse The File menu will appear as Figure 2 1 COCOMO Reference Manual 23 FIGURE 2 1 File Menu If C COCOMOII sample est USC COCOMO 11 1999 0 Edit View Parameters Calibrate Phase Maintenance Help New Ctl N E Load Project Ctrl L SaveProject Ctrl S Du Eius Save As Project Development Model Post Architecture Load Model Save Model Save As Model Make Report Ctl R uos UE E Save Screens Print Screen Ctrl
51. edule per Phase This chart is useful for determining the total calendar time required for the completion of the project COCOMO computes the schedule as the calendar time in months from the determination of a product s requirements baseline to the completion of an acceptance activity certifying that the product satisfies its requirements Time spent in requirements is computed as an additional 2096 COCOMO Reference Manual 33 34 Cost per Phase This chart is useful for determining the cumulative cost as the project moves from one phase to another It also displays the milestones between the phases using the assumption of the Waterfall Model To obtain the Cost per Phase given that the COCOMO computes only the Effort per Phase it is necessary to compute the average Cost per Person Month as Total Cost for entire project excluding requirements Total Effort in Person Months Effort for requrements is assumed at an additional 796 of the Total Effort and with the same Cost per Person Month as the overall project If your organization uses other Costs per Person Month you can use those values instead Cumulative Cost This chart is useful for determining the cumulative cost of a project over time It also displays the milestones between the phases using the assumption of the Waterfall Model To obtain the Cost per Phase given that the COCOMO computes only the Effort per Phase it is necessary to compute the average Cost per Person Mont
52. een Modified Do You Want To Save The Changes E No Cancel 3 If the previous model file is to be saved choose Yes then a Save Model dialog box will appear See Save Model If the modified model is not to be saved choose No 4 The Load Model dialog box will appear as seen in Figure 2 8 FIGURE 2 8 Load Model Dialog Box Open Look in a Cocomoii al c z a sample mod File name EEE Files of type Project Files mod Cancel Z The file name of a COCOMO model has a default format with mod as an extension With this window the desired model file can be selected from the Files scroll list for loading If the desired model file does not exist in the scroll list look for it in the other directories 5 Choose desired directory for file loading 6 When the desired file is shown on the Files list click it and click the OK button to initiate model loading 7 After a model file is loaded its file name will be displayed on the MODEL FILE field at upper left corner on the working window and the related costs of current project will be recalculated and shown on the working window COCOMO Reference Manual 29 2 6 FIGURE 2 9 30 2 7 Save Model The Save Model option is used to store the results of the current COCOMO model as a file with mod extension To Store the Results of Current Model 1 Choose Save Model from the File menu If the current model is loaded from a
53. en completed COCOMO treats the effort and the schedule spent on plans and requirements as separate from the effort and the schedule spent on the other phases Product Design Programming Integration and Test The Effort percentages computed by COCOMO exclude the effort spent on requirements COCOMO computes the schedule as the calendar time in months from the determination of a product s requirements baseline to the completion of an acceptance activity certifying that the product satisfies its requirements Time spent in requirements is computed as an additional 2096 COCOMO uses a single labor rate for a given module within the project and therefore does not use Cost per Person Month for a phase To compute the cumulative cost per phase or over time the Average Cost per Person Month is computed as Total Cost for entire project excluding requirements Total Effort in Person Months excluding requirements Total Effort 2 Effort Product Design Effort Programming Effort Integration and Test Effort for requirements is assumed at an additional 796 of the Total Effort and with the same Cost per Person Month as the overall project COCOMO Reference Manual 35 Known Problems If the project does not have any cost information I e cost related data has not been entered and defaults to zero some charts may be incorrectly displayed and some cells may have a Division by Zero error For unusually large COCOMO data sets e g 5
54. er Clear all modules of current project will disappear COCOMO Reference Manual 41 FIGURE 3 2 Warning Dialog Box USC COCOMO Il Warning This Operation Is Irreversible Do You Want To Proceed 3 3 Snapshot The Snapshot option enables users to compare the effort estimation change for a project so that he she can decide to apply the change or not This function makes COCOMO more convenient and powerful for software project decision analyses The Snapshot command stores the current set of modules effort adjustment factors and all other data associated with a project At a later time this data can be restored To Compare the Overall Change of a Project 1 Choose Snapshot from the Edit menu The Snapshot dialog box will initially appear as Figure 3 3 FIGURE 3 3 Snapshot Dialog Box 1 SnapShot x Snapped Project Current Project EST PM Sched PROD COST INST FSWP RISK sea mosr erre optimistic wad cep cep aaa ve ie wei 0 erf mr sec zs ze Eme REZO ec E E Revert Pessimistic Snap In the dialog box the lower section represents the current results for the project The upper section is previously snapped results The current project can be snapped by clicking upon the Snap button After completing this action the upper and lower section of the Snapshot window will contain identical information At this point changes can be made to the current project values after clicking upon the Done
55. f the shelf software COTS other than libraries Government furnished software GFS other than reuse libraries Another product Avendor supplied language support library unmodified Avendor supplied operating system or utility unmodified Alocal or modified language suppon library or operating system Other commercial library A reuse library software designed for reuse Other software component or library 8 COCOMO Reference Manual 1 1 5 FP Counting with Unadjusted Function Points The function point cost estimation approach is based on the amount of functionality in a software project and a set of individual project factors Behrens 1983 Kunkler 1985 IFPUG 1994 Function points are useful estimators since they are based on information that is available early in the project life cycle A brief summary of function points and their calculation in COCOMOII is as follows Function points measure a software project by quantifying the information processing functionality associated with major external data input output or file types Five user function types should be identified as defined in the Table 1 2 External Input Inputs Count each unique user data or user control input type that 1 enters the external boundary of the software system being measured and ii adds or changes data in a logical internal file External Output Count each unique user data or control output type that leaves the Outputs external boundary
56. ffice CM QA and manuals For each of these activities the percentage of the phase the estimated effort the estimated schedule and the estimated FSWP is displayed A description of each of these activities follows 62 COCOMO Reference Manual Requirements analysis Determination specification review and update of software functional performance interface and verification requirements Product Design Determination specification review and update of hardware software architecture program design and database design Programming Detailed design code unit test and integration of individual computer program components Includes programming personnel planning tool acquisitions database development component level documentation and intermediate level programming management Test Planning Specification review and update of product test and acceptance test plans Acquisition of associated test drivers test tools and test data Verification amp Validation V amp V Performance of independent requirements validation design V amp V product test and acceptance test Acquisition of requirements and design V amp V tools Are we building the product right and are we building the right product Project Office Functions Project level management functions Includes Project level planning and control contract and subcontract management and customer interface Configuration Management and Quality Assurance CM QA Configura
57. ge support libraries and operating systems or other commercial libraries Code generated with source code generators is not included though measurements will be taken with and without generated code to support analysis The COCOMOT line of code definition can be calculated in several ways One way is to use the suite of software programs known as Code Count which are available from the Center for Software Engineering website under category Tools Figure 1 1 Definition Checklist for Source Statements Counts Definition Checklist for Source Statements Counts Definition name Logical Source Statements Date basic definition Originator COCOMO II Measurementunit Physical source lines Logical source statements NUS Statement type Definition 8 Data Array D RH When a line or statement contains more than one type classify it as the type with the highest precedence 1 Executable Order of precedence 2 Nonexecutable Declarations Compiler directives Comments On their owen lines On lines with source code Banners and non blank spacers Blank empty comments Blank lines How produced Definition Data array 1 Programmed 2 Generated with source code generators 3 Converted with automated translators 4 Copied or reused without change 5 Modified 5 Removed 7 8 Origin Definition Data array 1 New work no prior existence 2 Prior work taken or adapted from A previous version build or release Commercial of
58. h as Total Cost for entire project excluding requirements Total Effort in Person Months Effort for requirements is assumed at an additional 796 of the Total Effort and with the same Cost per Person Month as the overall project If your organization uses other Costs per Person Month you can use those values instead Cost per Module This chart is useful for determining the cost of every module and comparing which modules are accounting for the highest part of the cost The cost of the entire project is the sum of the costs of the individual modules Since these are only estimates error bars are used to display the range within which the actual cost will fall with a very high probability COCOMO generates only the Optimistic as 0 8xMost Likely and the Pessimistic bound as 1 25xMost Likely for the cost of the entire project The Optimistic Pessimistic bounds on the cost estimates of the individual modules are similarly computed This assumes that the error on the cost estimate for the entire project is the sum of the errors on the cost of the component modules You can modify the Optimistic Pessimistic bounds on the individual modules to match your organizational experience The error bars will be adjusted accordingly Effort Project Effort per Phase This chart displays how the total effort for the overall project is distributed across phases The Effort percentages computed by COCOMO that are displayed under Percentage exclude the effor
59. he OK button COCOMO Reference Manual 67 FIGURE 6 13 T Integration amp Test window for the overall Module Phase Distribution Module Integration amp Test Module 1 68 COCOMO Reference Manual Chapter 7 Maintenance Maintenance is one of the menu selections in the menu bar that can be accessed by either clicking upon Maintenance in the menu bar or pressing Meta M Its function is to calculate and display an estimate of the effort and cost necessary to maintain a post development software product for a user defined number of years maximum five years Maintenance encompasses the process of modifying existing operational software while leaving its primary functions intact This process excludes the following types of activities Major re design and re development more than 5096 new code of a new software product performing substantially the same functions Design and development of a sizeable more than 20 of the source instructions comprising the existing product interfacing software package which requires relatively little redesigning of the existing product Data processing system operations data entry and modification of values in the database Maintenance does include the following types of activities Re design and re development of small portions of an existing software product Design and development of small interfacing software packages which require some redesign of the existing software product Modification
60. he development cost the provided maintenance labor rate the provided percent of code added during maintenance per year the provided percent of code modified during maintenance per year see Figure 7 5 and the calculated annual change traffic FIGURE 7 5 Project Maintenance window page 1 Project Maintenance x PROJECT sample Development SLOC 37791 Development Nominal Person Month 159 59 Development Adjusted Person Month 700 04 Development Cost 4141103 29 Maintenance Labor Rate 5500 00 Percentage Added 25 00 Percentage Modified 15 00 Maintenance Software Understanding 30 00 Unfamiliarity with the Software 0 40 Annual Change Traffic 40 00 Previous Next The second page of the maintenance window can be seen by clicking upon the Next button It contains the settings for the 18 cost drivers see Figure 7 6 FIGURE 7 6 Project Maintenance window page 2 Effort Ajustment Factor 1 08 y Product T Platform t RELY DATA DOCU CPLX RUSE TIME STOR PVOL V High High High Nominal Nominal Nominal V High High 0 amp 0 50 0 0 0 25 0 m Personnel t ACAP AEXP PCAP PEXP LTEX PCON High High V High High Nominal Nominal 0 amp 75 0 0 0 0 Project User ar TOOL SITE USRl USRZ Nominal Low Nominal Nominal 0 0 0 0 Page No 2 Previous 73 The third page of the maintenance window contains the effort and cost estimation for the next N number of years as defined by the user With each year is listed the KSLOC
61. imation formulas by multiplying them together see Figure 1 8 for the COCOMO dialog box The numerical value of the i adjustment factor there are 16 of them is called EM and their product is called the adjustment factor or EAF The actual effort PM is the product of the nominal effort times the EAF total In addition to the 16 EAF factors there are two user defined factors named USRI and USR2 Their initial values are all set to 1 They may be redefined by using the Parameters User Defined EAF menu item A final effort multiplier Required Development Schedule SCED is treated separately as it operates at the overall project level rather than potentially varying from module to module FIGURE 1 2 Estimate Development Effort 18 PMtotal SCED x PMnominal x I EMi i 1 2 Navigating COCOMO 12 This software is a stand alone software system intended for a single user The software is user interactive in that it attempts to interface well with a user s needs using extensive mouse interaction wherever possible On the screen in Figure 1 3 is the CLEF Component Level Estimation Form This is where all of the entered information will be displayed The top of the screen shows all of the subfunctions which the user may call The choices appear in pop down menus according to the major headings of Project Model and Phase In order to efficiently use COCOMO you must become familiar with the Component Level Estimat
62. ing Form CLEF The different areas that are to be discussed have been given a corresponding number These sections are given a descriptive label as a point of reference as well as a summary of their contents and functions The sections found in Figure 1 3 and their descriptions are as follows 1 Main Menu bar This area contains the menu selection of the main functions of COCOMO These selections are File Edit View Parameters Calibrate Phase Distribution Maintenance and Help File Edit View Parameters Calibrate Maintenance and Phase Distribution are discussed in chapters 2 3 4 5 6 and 7 respectively Help is the selection used to receive on line assistance with the available functions 2 Tool bar This area contains image buttons like other windows applications for New Project Open Project Save Project Delete Module Copy amp Paste Insert clipboard content Insert a module and About functions 3 Project Name This editable field displays the name of the currently displayed project To edit the name click twice upon this field and proceed to edit name Upon completion of editing press the Return key The Default name of a new project is lt sample gt COCOMO Reference Manual FIGURE 1 3 COCOMO CLEF ES USC COCOMO 11 1999 0 1 gt Ele Edit View Parameters Calibrate Phase Maintenance Help Scale Factor chedule E Development Model post Architecture Estimated Effort
63. int TIME Main storage constraint STOR Platform volatility PVOL Personnel attributes refer to the level of skills that are possessed by the personnel The skills in question are general professional ability programming ability experience with the development environment and familiarity with the project s domain These skills are characterized below Analyst capabilities ACAP Applications experience AEXP Programmer capabilities PCAP Platform experience PEXP Programming language experience LEXP Personnel Continuity PCON Project attributes refer to the constraints and conditions under which project development takes place The issues that affect development are Use of software tools TOOL Multisite Development SITE These 16 factors are incorporated into calculating an estimated effort and schedule Each of the factors has associated with it up to six ratings These ratings are very low low nominal high very high and extra high Each rating has a corresponding real number based upon the factor and the degree to which the factor can influence productivity A rating less than denotes a factor that can decrease the schedule and effort A rating greater than 1 denotes a factor that extends the schedule or effort Lastly a rating equal to 1 does not extend nor decrease the schedule and effort this rating is called nominal These 16 factors or effort multipliers are incorporated into the schedule and effort est
64. ion sese nene eene 64 6 2 3 Programming Module Phase DistributiON oooonncnnncnnnnnonononnnononanonnconoconoconocn nooo nc nn nono nenne trennen 65 6 2 4 Product Design Phase Distribution ene tetti e rer e re RE SEERE Siena 66 6 2 5 Integration and Test Module Phase DistributiON ooonnononcnocnconoconccononancnnnonnnnanonnonnnonnn cono co nono rennen nenne enne ene 67 Chapter 7 Maintenance rente a 69 7 1 Project Maintenance xiv nean prie ditte perte 70 7 2 Module Maintenance iet e eee WR Oe HER et ede aer Med 75 References ore e ete te edu e e pre sei m cde redi d ede e A eed 81 Appendix A Accelerator Keys eere ee idad 82 2 COCOMO Reference Manual Chapter 1 Introduction 1 1 What is COCOMO COCOMO Reference Manual COCOMO COnstructive COst MOdel refers to a parametric model used to estimate effort and schedule for software development projects The COCOMO software system is a screen oriented interactive program that assists in budgetary planning and schedule estimation of a software development project Through the flexibility of COCOMO a software project manager or team leader can develop a model or multiple models of projects in order to identify potential problems in resources personnel budgets and schedules both before and while the potential software package is being developed The COCOMO software package is based upon the software cost and schedule estimation model COnstructive
65. iver ratings are changed the total product of the cost drivers is displayed in the upper right hand corner of the dialog box along with the module name The final rating of a cost driver is calculated using this formula for the interpolation Final rating Next cost driver rating Current cost driver rating Current inter cost driver 100 COCOMO supports two different models called Early Design and Post Architecture The Early Design model is supposed to be used at the earliest phase of a software project The Post Architecture Model applies once a software architecture has been formulated In terms of the COCOMO program the Early Design Model differs from the Post Architecture Model in its use of Effort Adjustment Factors The Early Desing Model considers only seven pre defined effort adjustment factors including schedule SCHED Only six are shown in Figure 1 7 The Post Architecture Model makes use of seventeen pre defined effort adjustment factors and sixteen of these are shown in Figure 1 8 Each of the models can be specified by selecting it using the button in the upper right portion of the COCOMO main scrren 9 Totals Area This area houses the calculated results of all of the modules combined Within this area is the total SLOC count for the project the total estimated effort EST PM schedule Sched productivity PROD cost COST cost per instruction INST full time software programmers FSWP and risk In addition to a
66. l FIGURE 5 2 Load Calibration Dialog Box Look in Y Cocomoi y Kal ex cr eH a test cal File name Files of type Calibration Files cal Cancel Z 5 2 File Save The Calibrate File Save command saves the current calibration data in the file whose name was previously identified using File Save As FIGURE 5 3 Save Calibration Dialog Box Save As Save in C3 Cocomoi El Al e Eig a test cal File name Save as type Calibration Files cal y Cancel A COCOMO Reference Manual 53 5 3 FIGURE 5 4 54 5 4 File Save As The Calibrate File Save As command stores the current calibration data as a cal file which has a different file name from the current file This command works precisely the same as the File Save As for est and mod files see Figure 5 4 Save As Calibration Dialog Box Save s Save in a Cocomoii al c E3 E a test cal File name Save as type Calibration Files cal Cancel Project A windows appears shown in Figure 5 5 which displays the archived project data To remove the window click on Cancel To delete an existing entry first place an x at the leftmost end of the row and click on Delete A warning box appears as shown in Figure 5 6 To display the entire set of values for an archived project click on Display Since the display of an archived project eliminates the display of any existing
67. most likely estimate for the number of full time developers that would be needed to complete a module in the estimated development time 16 SLOC Cost Column This column contains the calculated most likely cost per SLOC This number is calculated from Cost SLOC in each module FIGURE 1 7 EAF Dialog Box Early Design EAF sample x base incr rating RCPX RUSE PDIF PERS PREX FCIL USRl USPRZ base wom mom mom wom mom mom wom mom mer ov sol or os mai os raaf sae EAF is also affected by Schedule EAF 1 00 Cancel Help 18 COCOMO Reference Manual FIGURE 1 8 EAF Dialog Box Post Architecture EAF sample x base Incr rating Product RELY DATA DOCU CPLX RUSE base nox nox NOM nox nox Incr amp 0 0 0 amp 0 0 Platform TIME STOR PVOL base NOM NOM NOM Incr amp 0s 0 04 Personnel ACAP AEXP PCAP PEXP LTEX PCON base NOM NOM NOM NOM NOM NOM Incr 04 0 04 0 0 amp 0 Project TOOL SITE base NOM NOM Incr amp 0 amp 0 User USRl USRZ base NOM NOM Incr os o EAF is also affected by Schedule EAF 1 00 2 Cancel Help FIGURE 1 9 Schedule Dialog Box Schedule x ingo eiT rss NOM 1 00 COCOMO Reference Manual 19 17 Cost Column This column contains the calculated most likely estimate of the development cost for a particular module 18 Productivity PROD Column This
68. n FSWP Note The programming phase has been broken down into two additional phases Detailed Design and Code and Unit Test The detailed design is a follow up to the product design phase In this sub phase those points developed in the product design are elaborated to a point necessary to breakdown agreed functions into units necessary for coding The code and unit test sub phase houses the actually coding effort of the individual units of code The testing of these units upon completion is also encompassed within this sub phase 6 2 2 Plans and Requirements Module Phase Distribution The plans and requirements phase distribution allows the user to view the components of this particular phase When the Plans and Requirements distribution is chosen from the Module Phase distribution menu the window shown in FIGURE 6 10 is displayed This window displays the following COCOMO Reference Manual information Module name the total Module SLOC the total estimated Module effort and the total estimated Module schedule In addition the window displays the activities requirements analysis product design programming test planning verification amp validation Project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 10 To exit from this window click the OK button FIGURE 6 1
69. n the Project Phase Distribution button under the Phase Distribution menu see FIGURE 6 1 Four formats for viewing will appear in another menu overall phase plan amp requirements programming and integration amp test Each of these menu selections will be discussed in sections 6 1 1 6 1 4 respectively The phase distribution of plan requirements programming and integration amp test are broken down into sub phases These phases include requirements analysis product design programming test planning verification amp validation project office CM QA and manuals For each of these sub phases the percentage of the phase the estimated effort the estimated schedule and the estimated FSWP is displayed A description of each of these sub phases follows Requirements analysis Determination specification review and update of software functional performance interface and verification requirements Product Design Determination specification review and update of hardware software architecture program design and database design Programming Detailed design code unit test and integration of individual computer program components Includes programming personnel planning tool acquisitions database development component level documentation and intermediate level programming management Test Planning Specification review and update of product test and acceptance test plans Acquisition of associated test drivers test to
70. ns on Software Engineering to appear 1994 Goethert W E Bailey M Busby 1992 Software Effort and Schedule Measurement A Framework for Counting Staff Hours and Reporting Schedule Information CMU SEI 92 TR 21 Software Engineering Institute Pittsburgh PA IEPUG 1994 IFPUG Function Point Counting Practices Manual Release 4 0 International Function Point Users Group Westerville OH Kunkler J 1985 A Cooperative Industry Study on Software Development Maintenance Productivity Xerox Corporation Xerox Square XRX2 52A Rochester NY 14644 Third Report March 1985 Madachy J Raymond 1997 Heuristic Risk Assessment Using Cost Factors JEEE Software May June 1997 pp 51 59 Park R 1992 Software Size Measurement A Framework for Counting Source Statements CMU SEI 92 TR 20 Software Engineering Institute Pittsburgh PA Selby R A Porter D Schimidt and J Berney 1991 Metric Driven Analysis and Feedback systems for Enabling Empirically Guided Software Development Proceedings of the Thirteenth International Conference on Software Engineering ICSE 13 Austin TX May 13 16 1991 pp 288 298 COCOMO Reference Manual 81 Appendix A Accelerator Keys 82 File Sparc Meta F Windows Alt F New Ctrl N Ctrl N Load Project Ctrl L Ctrl L Save Project Ctrl S Ctrl S Save As Project uuu Ctrl A Ctrl A Load Model Save Model
71. nt 0 91 Schedule Coefficient 3 67 Schedule Exponent 0 28 New Effort Coefficient 6 85 Effort Exponent 0 91 Schedule Coefficient 3 83 Schedule Exponent 0 28 Accept Ignore Help Accent 56 COCOMO Reference Manual Chapter 6 Phase Distribution The Phase Distribution is one of the menu selections in the menu bar that can be accessed by clicking upon Phase Distribution in the main menu Its function is to display a breakdown of the software effort and schedule into the phases of the waterfall development cycle These phases are plans amp requirements design programming and integration amp test These phases are described as follows Plans amp Requirements In this phase a statement for the required functions interfaces and performance is created These expectations are used to define the capabilities of the software product as expressed by representatives of all interested parties Product Design In this phase a hardware software architecture control structure and data structure for the product are defined A draft of the user s manual and test plans are also created during this phase Programming In this phase the design of the previous phase is implemented in the creation of complete sets of software components Integration amp Test In this phase the various software components are brought together in order to achieve a properly functioning software product composed of loosely coupled modules
72. of the software product s code documentation or database structure Maintenance effort and costs are determined by essentially the same cost driver attributes used to determine the software development costs and effort exceptions are the RELY MODP and SCED factors which will be discussed in greater detail later in this chapter The maintenance calculations are heavily based upon the Maintenance change Factor MCF and the Maintenance Adjustment Factor MAP The MCF is similar to the Annual change Traffic in COCOMOSI except that maintenance periods other than a year can be used see EQ 7 1 Maintenance Change Factor EQ 7 1 SizeAdded Size Modified m BaseCodeSize The initial maintenance size is obtained in one to two ways The first equation in EQ 7 2 is used when the base code size is known and percentage of change to the base code is known The second equation in EQ 7 2 is used when the fraction of code added or modified to the existing base code during the maintenance period is known Size BaseCodeSize x MCF MAF Size g SizeAdded SizeModified x MAF Initial Maintenance Size EQ 7 2 COCOMO Reference Manual 69 As shown in EQ 7 2 the initial maintenance size estimate is adjusted with a Maintenance Adjustment Factor see EQ 7 3 Maintenance Adjustment Factor EQ 7 3 SU MAF 1 x UNPM The resulting maintenance effort estimation formula is the same as the COCOMOII Post Architecture development model
73. of the software system being measured Internal Logical File Count each major logical group of user data or control information Files in the software system as a logical internal file type Include each logical file e g each logical group of data that is generated used or maintained by the software system External Interface Files passed or shared between software systems should be counted Files Interfaces as external interface file types within each system External Inquiry Count each unique input output combination where an input Queries causes and generates an immediate output as an external inquiry type Table 1 2 User Function Types Each instance of these function types is then classified by complexity level The complexity levels determine a set of weights which are applied to their corresponding function counts to determine the Unadjusted Function Points quantity This is the Function Point sizing metric used by COCOMII The usual Function Point procedure involves assessing the degree of influence DI of fourteen application characteristics on the software project determined according to a rating scale of 0 0 to 0 05 for each characteristic The 14 ratings are added together and added to a base level of 0 65 to produce a general characteristics adjustment factor that ranges from 0 65 to 1 35 Each of these fourteen characteristics such as distributed functions performance and reusability thus h
74. ols and test data Verification amp Validation V amp V Performance of independent requirements validation design V amp V product test and acceptance test Acquisition of requirements and design V amp V tools Are we building the product right and are we building the right product Project Office Functions Project level management functions Includes project level planning and control contract and subcontract management and customer interface Configuration Management and Quality Assurance CM QA Configuration management includes product identification change control status accounting operation of program support library development and monitoring of end item acceptance plan Quality assurance includes development and monitoring of project standards and technical audits of software products and processes Manuals Development and update of users manuals operators manuals and maintenance manuals 6 1 1 Overall Project Phase Distribution 58 The overall phase distribution allows the user to view an entire project s estimated effort schedule and number of personnel needed for phase completion Upon clicking on Overall Phase a window will be displayed showing the phase breakdown of the current project in COCOMO see FIGURE 6 2 This window displays the project name project SLOC and the total estimated effort for the project Looking at FIGURE 6 1 this information can be seen in the upper left corner of the window
75. or Dialog Box will appear as Figure 4 8 COCOMO Reference Manual 49 FIGURE 4 8 Scale Factors Dialog Box 50 Scalefactor Paramters x VLO LO NOM HI VHI XHI PREC e 2 4 6 2 72 2 42 1 24 o o To modify these values go straight to those edit boxes and type new values When finished with the modification click OK button 44 Equation The Equation option displays effort and schedule equations Select Equation from the Parameters menu with the mouse The Equation Dialog Box will appear as Figure 4 9 COCOMO Reference Manual FIGURE 4 9 Equation Dialog Box Equation Parameters x Exponent Equation B o 21 a oo a E Effort Equation PRES CEMI A e SCC EMT 2 54 Size Bt iASLOC AT 100 ATPROD Schedule Equation TE 3 67 puro lo zs 0 2 B 0 91 CED 100 Cancel Help To modify these values go straight to those edit boxes and type new values When finished with the modification click the OK button 4 5 Reset The Reset option resets the values of multiplying factors and effort schedule estimating equations of the current project back to the COCOMO default values Select Reset from the Parameters menu with mouse The command will be executed directly and there is no warning message for users After the RESET the values of all multiplying factors and effort estimating equations of current project will be changed to the COCOMO default values
76. owledge of Excel and become familiar with the format of the csv files produced by COCOMO Note that Excel does not permit you to open two workbooks with the same name even if the workbooks are in different folders To open the second workbook you can either close the curren workbook or rename it However it is recommended that you do not rename cocomo xls Step 1 Start Excel and import the files generated by COCOMO Click on Import COCOMO Files The Browse For Folder dialog box will appear Select the folder containing the Comma Separated Values Files CSV generated by USC COCOMO If COCOMO Import amp Analyze can find the files it is looking for Main csv and Phases csv it will open each file read its contents and place it in the appropriate worksheet Step 2 Generate Charts Once the sheets Main and Phases have been correctly initialized you can generate meaningful analyses of the data with the click of a button Specific help on each chart is given below If the sheet corresponding to the chart you are trying to create has been already created then the existing sheet will be activated and get the input focus If you want to overwrite the existing sheet you will have to delete it by selecting the Delete Sheet command from the Edit menu Performing your own analyses The charts that the COCOMO Import and Analyze tool can generate for you are just a subset of what you can do with the data imported into the Main and Phases sheets
77. pon typing the module name press Return A value for SLOC and Labor rate may also be given by clicking on the respective field and editing appropriately see Figure 1 12 FIGURE 1 12 Create Sample Module and give values to SLOC and Labor Rate 129 C XCOCOMOlINsample est USC COCOMO 11 1999 0 File Edit View Parameters Calibrate Phase Maintenance Help Cy E e Scale Factor Schedule Development Model Post Architecture Y frames eue 5670 00 4 27 67 0 200 5 ieipeneen 102 2 ce 42 COCOMO Reference Manual 21 NOTE In order to change any of the editable fields just click on the desired field twice and begin editing the field Upon completing editing either hit the Return key or click on OK All of the final results can be found at the bottom of the CLEF in the Totals area see Figure 1 13 FIGURE 1 13 Totals area after calculations have been completed Estimated Effort Sched PROD COST INST Staff RISK meta pine aia optimistic ea cep ra cep ies woot taxeay erc 200 ea seo aa ses L RES EZ Pessimistic Project Is Saved To File CCOCOMOIINsample est 7 1 4 Running COCOMO Windows NT and UNIX Currently there are two implementations of COCOMOII a Windows 95 98 NT version and a Sun Microsystems Sparcstation under Solaris version To download any these versions you should enter this in a web browser http sunset usc edu COCOMOT cocomo html and scroll down to
78. previously stored model file the Save Model will overwrite the same model file with the current model 2 If the current model is a new one the Save Model dialog box will appear as seen in Figure 2 9 Save Model Dialog Box Save s Save in CX Cocomoi a Al e a sample est Save as type Project Files est Cancel Z 3 Look at the Files scroll window If the file saving is to update overwrite an existing model file the desired filename should be found in the Files scroll list If the filename can not be found on the list change the directory from the Directories scroll list until the desired filename is being shown When the desired filename is on the list click it 4 If the file saving is to store a new model file choose the desired directory then type in the filename 5 After the desired filename is selected or input click the OK button to initiate model saving Save As Model The Save As Model option is to store the current model as a COCOMO model file which has a file name different from current model To Store Current Model With different File Name COCOMO Reference Manual FIGURE 2 10 1 Choose Save As Model from the File menu 2 The Save Model dialog box will appear as seen in Figure 2 10 Save As Model Dialog Box 2 8 a sample est Save as type Project Files est Cancel Z 3 Look at the Files scroll window If the file saving is to update over
79. rall phase plan amp requirements programming and integration amp test see FIGURE 6 9 To exit from this window click the OK button Phase Distribution window displaying a sample Module s overall phase distribution Phase Distribution Module Overall Module 1 Ea Overall Phase Distribution MODULE Module 1 SLoc 13574 TOTAL EFFORT 348 682 Person Months PCNT EFFORT PM PCNT SCHEDULE FSWP Plans nd Requirements 7 000 24 408 Ole 928 4 118 Product Design 17 000 59 275 26 060 7 678 rel Programming pl 201 604 47 759 14 070 14 329 Detailed Design 24 940 86 960 Code and Unit Test 32 879 114 644 Soo gt Integration and Test 25 181 87 801 26 181 7 713 11 383 64 In addition each phase of the Module s development cycle is represented by the estimated effort the estimated schedule and the estimated number of personnel needed for phase completion Again looking at FIGURE 6 9 the information has been separated into columns The first column displays the phase name The second column displays the percentage that the corresponding phase takes in the estimated effort The third column displays the estimated effort for each phase The fourth column displays the percentage of the estimated schedule that is dedicated to the corresponding phase s completion The fifth column displays the estimated schedule for phase completion And the last column displays the estimated number of personnel needed for phase completio
80. s 57 plans amp requirements 57 plans and requirements phase 66 Platform 16 44 platform attribute 9 21 Platform attributes 10 PM 10 57 PMAT 48 PREC 48 predictor factors 21 PROD 18 Product 16 43 Product attributes 10 product attributes 9 21 product design phase 61 67 Productivity 18 COCOMO Reference Manual 85 Programming 57 programming 57 programming phase 61 67 Project 43 46 73 project 1 25 39 43 51 54 57 71 project attribute 10 21 Project attributes 10 Project File 23 project file 21 22 24 26 28 Protocol 87 PVOL 10 44 R RELY 9 43 report 21 report file 21 31 Reset 43 49 RESL 48 Risk 16 risk level 16 RUSE 10 43 S Scale Factors 48 scale factors 4 SCED 10 Schedule 16 SEI 5 SITE 10 46 SLOC 9 13 16 17 21 61 62 66 Snapshot 38 39 software architecture 57 STOR 10 44 SU 9 T TCP IP 87 TEAM 48 TIME 10 44 TOOL 10 46 U Unadjusted Function Points 8 Undo 40 UNFM 9 User Defined EAF 10 47 V V amp V 59 64 Virtual COCOMOII 87 Ww waterfall model 1 X x 12 86 COCOMO Reference Manual
81. see EQ 7 4 Maintenance Effort EQ 7 4 17 PMy AX Size x 22 i l As stated previously some cost drivers for maintenance differ from development Those cost drivers are software reliability RELY and schedule SCED The reason for the change in RELY is that increased investment in software reliability has a strong positive effect upon the maintenance stage The SCED driver is no longer editable in the EAF window but is calculated from the user input value for number of years when the maintenance function is engaged For more information on these cost drivers please refer to the introduction of this manual The Maintenance menu option offers sub menu for either a maintenance effort estimation based upon either an entire project or an individual module see Figure 7 1 These separate options are discussed in sections 7 1 and 7 2 FIGURE 7 1 Maintenance sub menu If C COCOMOII sample est USC COCOMO 11 1999 0 File Edit View Parameters Calibrate Phase MEMCEa Help ls Project BI 2 Module Scale Factor Schedule Development Model Post Architecture Y Module 1 13574 5670 00 4 27 57 3 244 7 58 5 1987226 21 102 2 eej 7 4 4 7 1 Project Maintenance In order to view the maintenance estimation calculations for an entire project the user can click on Project under the Maintenance menu see Figure 7 1 Upon clicking this selection a window will appear displaying the current proj
82. t spent on requirements However the percentages displayed on the chart include the effort spent on Requirements hence the slight difference Effort per Phase and Module This chart displays the effort spent on every module during the phases of the project It can be used to quickly identify the modules which are the most effort intensive Effort for requirements is assumed at an additional 7 of the Total Effort Staffing Project Personnel per Schedule This chart displays the staffing levels of the project over its duration The cutoff points between the various phases are also clearly displayed Staffing levels are assumed to remain constant during a given phase and to experience a sharp increase decrease at the beginning end of a phase COCOMO Reference Manual Project Personnel per Phase This chart displays the staffing levels of the project during the various phases Staffing levels are assumed to remain constant during a given phase and to experience a sharp increase decrease at the beginning end of a phase Personnel per Module This chart displays the staffing requirements for every module It is useful for identifying the most labor intensive modules and to appropriately plan for the staffing of teams which are typically responsible for modules within the project Activity Project Activity per Phase This chart displays the effort spent by activity during the project lifetime The activities correspond to the ones associated wi
83. tal number of source lines of code for development of the module SLOC that is loaded in the CLEF the nominal effort of the module the actual effort of the module the development cost the inputted maintenance labor rate the inputted percent of code added during maintenance per year the inputted percent of code modified during maintenance per year see figure 7 13 and the calculated annual change traffic COCOMO Reference Manual 77 FIGURE 7 12 Module Maintenance Dialog Box Early Design EAF lt sample gt Ea base incr rating RCPX RUSE PDIF PERS PREX FCIL USRl USR2 base non nom nom nom non non nom NOM Incr os os os os os os os os EAF is also affected by Schedule EAF 1 00 Cancel Help FIGURE 7 13 Module Maintenance window page 1 Module Maintenance Module 1 x MODULE Module 1 Development SLOC 13574 Development Nominal Person Month 57 32 Development Adjusted Person Month 348 68 Development Cost 1977026 07 Maintenance Labor Rate 4700 00 Percentage Added 25 00 Percentage Modified 20 00 Maintenance Software Understanding 30 00 Unfamiliarity with the Software 0 40 Annual Change Traffic 45 00 Previous The second page of the maintenance window can be seen by clicking upon the Next button It contains the settings for the 16 cost drivers SCED is not applicable see Figure 7 14 78 COCOMO Reference Manual FIGURE 7 14 Module Maintenance window page 2
84. th a waterfall model The effort spent per activity is computed as a percentage from the total effort spent during a phase Refer to the EFFORT 406 section of the Phases sheet to view the percentages used The same percentages are used for the overall project and for the individual modules If you think from your organizational experience that some modules may require different activity distribution than others you can recompute the effort spent by activity for those modules Project Personnel per Activity and Phase This chart displays the personnel required for every activity during each phase of the project The activities correspond to the ones associated with a waterfall model The personnel required for every activity is computed from the effort spent per activity The effort spent per activity is computed as a percentage from the total effort spent during a phase Refer to the EFFORT section of the Phases sheet to view the percentages used The same percentages are used for the overall project and for the individual modules If you think from your organizational experiencen that some modules may require different activity distribution than others you can recompute the effort spent by activity for those modules General Assumptions The general assumptions behind COCOMO are briefly listed below For all the analyses it is assumed that the waterfall model is used in particular a phase does not start until the previous one has be
85. the corresponding button This action will result in the appearance of an EAF dialog box where the cost driver ratings can be changed as described in the introduction The EAF factors for the Post Architecture Model are shown in Figure 7 11 and for the Early Design Model in Figure 7 12 76 COCOMO Reference Manual FIGURE 7 11 Maintenance EAF Module 1 Ea Product base Incr Plat form base Incr amp Personnel base Incr amp Project base Incr amp User base Incr amp Module Maintenance EAF Dialog Box base Incr rating RELY DATA DOCU CPLX RUSE to won mr won won ls E ls be a bo ha te bi x id d a bo a d ti A B LTEX PCON d i om sonj gus vd Upon completing the adjustment of the cost drivers click the OK button or click the Cancel button to return to the CLEF without viewing maintenance estimations After exiting the EAF dialog box you will be returned to the Module Maintenance Dialog box to continue inputting the editable values Click upon the OK button upon completion of editing the displayed fields or click upon the Cancel button if no changes are desired to the default values if more assistance the Help button is available to receive on line assistance When the OK button is clicked in the Module Maintenance Dialog Box a window displaying the first of four pages that contains the module name the current development mode the to
86. tion management includes product identification change control status accounting operation of program support library development and monitoring of end item acceptance plan Quality assurance includes development and monitoring of Module standards and technical audits of software products and processes Manuals Development and update of users manuals operators manuals and maintenance manuals In order to view the phase distribution of an entire Module the user can click on the Module Phase Distribution button under the Phase Distribution menu When choosing any of the views of phase distribution you will be confronted with a module selection window see FIGURE 6 8 At this point you may choose which module is to be viewed by clicking on the desired module name which will be highlighted after the click Click the OK button in order to initiate phase distribution of the chosen module FIGURE 6 8 Module selection window Component List Ea Modules List Module 1 Module 2 Module 3 Cancel ik Module Selected d Module 1 Help COCOMO Reference Manual 63 FIGURE 6 9 6 2 1 Overall Module Phase Distribution The overall phase distribution allows the user to view an entire Module s estimated effort schedule and number of personnel needed for phase completion Upon clicking on Overall Phase a window will be displayed showing the phase breakdown four formats for viewing will appear in another menu ove
87. trl V and the window image appears 2 11 Print Screen The Print Screen option prints the screen of the main Cocomo window To Print Screen 1 Choose Print Screen from the File menu 2 The Print Screen dialog box will appear as seen in Figure 2 15 COCOMO Reference Manual 37 Figure 2 15 Print Screen Dialog Box Print ka ES Printer Name MTINSAHP LaserJet 5 5M PostScript Properties Status Ready Type HP LaserJet 5 5M PostScript Where LPT1 Comment Print to file Print range Copies i 6 All Number of copies C Pages from fi ta E m C Selection iu of o solate ox Cancel 3 The Name of the printer can be selected from the dropdown list Alternatively you can print to a file by clicking on the Print to file checkbox 4 Properties of the printer can be set by clicking on the Properties button 5 The Print range can be All or Pages e g from 1 to 3 6 The Number of copies can be selected by clicking the up and down arrows or by typing a number directly 7 Select OK when finished to print or select Cancel to not print 2 11 Print Preview The Print Preview option displays what will be printed if Print Screen is selected from the File menu To Preview what is to be printed 1 Choose Print Preview from the File menu 2 The Print Preview dialog box will appear as seen in Figure 2 16 38 COCOMO Reference Manual Figure 2
88. uct Design Life Cycle Effort 119 006 Person Months Life Cycle Schedule 7 678 Months PCNT EFFORT PM SCHEDULE FSWP Requirements Analysis 12 500 14 876 7 678 1 938 Product Design 41 000 48 792 7 678 6 355 Programming 13 030 15 507 7 678 2 020 Test Planning 5 530 6 581 7 678 0 857 Verification and Validation 7 030 8 366 7 678 1 090 Project Office 10 940 13 2019 7 678 1 696 CM QA 2 500 2 975 7 678 0 388 Manuals 7 470 8 890 7 678 1 158 6 1 5 Integration and Test Project Phase The integration amp test phase distribution allows the user to view the components of this particular phase When the Integration and Test distribution is chosen from the Project Phase distribution menu the window shown in FIGURE 6 6 is displayed This window displays the following information project name the total project SLOC the total estimated project effort and the total estimated project schedule In addition the window displays the estimated effort for the activities of requirements analysis product design programming test planning verification amp validation project office CM QA and manuals These activity estimates are accompanied with a percentage of the phase effort that they encompass the estimated effort schedule and FSWP for the activity s completion as shown in FIGURE 6 6 To exit from this window click the OK button COCOMO Reference Manual 61 FIGURE 6 6 Integration and Test window for the overall project Life Cycle Phase Integration an
89. usly stored project file the Save Project will overwrite the same project file with the current project COCOMO Reference Manual 2 If the current project is a new one 1 e being created by the New command the Project Save dialog box will appear as seen in Figure 2 5 FIGURE 2 5 Save Project Dialog Box Save As MES Save in E Cocomoii Al e E Eg a sample est Save as type Project Files est y Cancel Zi 3 Look at the Files scroll window If the file saving is to update overwrite a existing project file the desired filename should be found in the Files scroll list If the filename can not be found from current list change the directory from the Directories scroll list until the desired filename is being shown When the desired filename is on the list click it 4 If the file saving is to store a new project file choose the desired directory then type in a new filename 5 After the desired filename is selected or input click the OK button to initiate project saving 2 4 Save As Project The Save As Project option is to store the current project as a COCOMO project file which has a file name different from current file To Store Current Project With different File Name 1 Choose Save As Project from the File menu with the mouse 2 The Save Project dialog box will appear as seen in Figure 2 6 COCOMO Reference Manual 27 FIGURE 2 6 Save Project Dialog Box 28 2 5
90. write an existing model file the desired filename should be found in the Files scroll list If the filename can not be found on the current list change the directory from the Directories scroll list until the desired filename is being shown When the desired filename is on the list click it 4 If the file saving is to store a new model file choose the desired directory then type in the filename in the SELECTION box 5 After the desired filename is selected or input click the OK button to initiate model saving After a model file is saved the project file name will be displayed on the MODEL FILE field at the upper left corner of the working window Make Report The Make Report option creates a COCOMO report in the form of a text file for printing To Create Project Report 1 Choose Make Report from the File menu 2 The Make Report dialog box will appear as seen in Figure 2 11 COCOMO Reference Manual 31 FIGURE 2 11 32 2 9 Make Report Dialog Box Make Report Save in CX Cocomoi al c sample rpt Save as type Report Files rpt y Cancel Z 3 Look at the Files scroll window If the file saving is to update overwrite an existing report file the desired filename should be found in the Files scroll list If the filename can not be found on the current list change the directory from the Directories scroll list until the desired filename is shown When the desired filename is on the list

USC COCOMOII

Contents

Download Pdf Manuals

Related Search

Related Contents