Professional Documents
Culture Documents
Oose Unit-5
Oose Unit-5
Oose Unit-5
Hardware attributes ‘* Run-time performance constraints ‘+ Memory constraints Cost driver ‘Volatility of virtual machine attributes ‘© Computer turnabout time | Personnel attributes Analyst capability # Software engineer capability « Applications experience Virtual machine experience ‘* Programing language experience L____» project attributes + Use of software tools « Applications of software engineering methods « Required development schedule | a these 15 attributes get : Very Low — Nominal High Very Extra point scale ranging from "very low" low high high ‘o "extra high", These ratings can be pra following table. Th , il is iven in following table. The ‘The eff ipli Jh cost driver, attribute is 26 given i ffort multipliers for eacl venent Factot” (EAB): Product of all effort multipliers result in “Effort Adjust a High Very high Extra” Pas es 7 very low Low Nominal high Cost drivers | See <<** pplication database5-94 Object Oriented Software Engineering aay of software 0.70 0.85 1.00 1.15 | Hardware attributes “Run-time performance 1.00 11 ‘constraints | Memory constraints 1.00 1.06 | Volatility of virtual machine 0.87 1.00 115 - Computer turmabout time 0.87 1.00 1.07 115 Personnel attributes Analyst capability” 1.46 1.19 1.00 0.86 at _ Software engineer capability 4 49 1.17 1.00 0.86 0.70 Applications experience 129 113 1.00 0.91 0.82 | Virtual machine experience 121 1.10 1.00 0.90 Programming language 4 44 1.07 1.00 0.95 experience Project attributes sss of acftwareinos 1.24 1.10 1.00 0.91 0.82 papplications (of /sGhWaM <7 jo4 1.10 1.00 091 0.83 - engineering methods BBenired Seve 193 1.08 1.00 1.04 1.10 Lischedule s z Table 5.10.2 The formula for effort calculation can be - E = a, (KLOC)®~ EAF person-months The values for a, and b, for various class of software projects are - Table 5.10.3 The duration and person estimate is same as in basic COCOMO model. ice. = a : D = c4(B)* months Le. use values of c, and d, coefficients that are in Tabl P = E/D persons eeeSe AE soot | ot Oriented Software Engineering ers of intermediate mode} fect Management . This model can be applie ummm re Pplied to almost entire softw; estimation during early stage, ate product for easy and rough cost 2, It can also be applied at the software accurate cost estimation, Product component level for obtaining more Limitations of intermediate mode! timation 1a atta 1. The est ‘ation is within 20 % of actual 68 % of the time. 7 ffort ipli 2. The effort aout are not dependent on phases, 3. A product with many components is difficult to estimate. Example Consider a project having 30,000 lines of code which is an embedded software with atitical aréa hence reliability is high. The estimation can be E = a,(KLOO)-EAF As reliability is high, EAF = 1.15 (product attribute) a, =2.8 b a} for embedded software E = 2.8(30)!#1.15 = 191 person-month D = c,(E)* = 2.5(191)” = 13 months approximately P = ED = 191/13 P = 15 persons approximately 3) Detailed COCOMO model The detailed model uses the same equi But detailed model can estimate the effort (E), development phases, subsystems, modules. The experimentation with different develo] Four phases used in detailed COCOMO model are = 1. Requirements Planning and Product Design (RPD) 2. Detailed Design (DD) 3. Code and Unit Test (CUT) 4. Integrate and Test (IT) a ee ee ee TECHNICAL PUBLICATIO' ations for estimation as the Intermediate Model. duration (D) and persons (P) of each of pment strategies is allowed in this model.Object Oriented Software Engineering 5-36 Project Leen The effort multipliers for detailed COCOMO are Very low Low Nominal _ High Very we 1.80 0.85 1.00 0.75 ie 1.35 0.85 1.00 Fes cur 1.35 0.85 1.00 ie IT i 1.50 H20 1.00 070 Using these detailed cost drivers, an estimate is determined for each phase of the lifecycle. 1. Describe in detail COCOMO model for software cost estimation. Illustrate considering a suitable example. AU : May-17, Marks 13 2. Discuss about the COCOMO models (Basic, intermediate and detailed) for cost estimation. AU : May-14, 15, Marks 16 3. Explain how effort and cost estimation are determined using COCOMO model ? AU : Dec.-20, Marks 13 4. Discuss about the basic COCOMO model with advantages and limitations. 5. Explain.COCOMO model for software estimation. NORCO ERE cocomo 1 Model 17,18, Marks 16 COCOMO I] is applied for modern software development practices addressed for the projects in 1990's and 2000's. : The sub-models of COCOMO II model are - 1. Application composition model * For estimating the efforts required for the prototyping projects and the projects ® which the existing software compo, ct ition model ® ieioatiea: iponents are used application-composition ™ * The estimation in this model is based on the number of application point ™ application points are similar to the object points rrCC ee oriented ‘Software Engineering 5-37 This estimation is based on the leve Boehm has suggested the object point produc Project Management : of difficulty of object points. tivity in the following manner. ( med erlence a d z vevelopee enility in Very low Low Nominal High Very high CASE maturity Very low Low Nominal High Very high productivity (NOP/Month) 4 7 B 5 50 « Effort computation in application-composition model can be done as follows - | PM=(NAP®%sset00) / PROD | where PM means effort required in terms of person-months. NAP means number of application points required. % reuse indicates the amount of reused components in the project. These | reusable components can be screens, reports or the modules used in previous projects. PROD is the object point productivity. These values are given in the above table. 2.Anearly design model * This model is used in the early stage of the project development. That is after gathering the user requirements and before the project development actually starts, this model is used. Hence approximate cost estimation can be made in this model. © The estimation can be made based on the functional points. * In early stage of development different ways of implementing user requirements can be estimated. * The effort estimation (in terms of person month) in this model can be made using the following formula : Effort = Ax size” x M where Boehm has proposed the value of coefficient A = 2.94. Size should be in terms of Kilo source lines of code i.e. KSLOC. The lines of code can be computed with the help of function point. The value of B is varying from 1.1 to 1.24 and depends upon the project. eee5-38 Project Man, Object Oriented Software Engineering Mis based on the characteristics such as Product reliability and complexity (RCPX) . Reuse required (RUSE) . Platform difficulty (PDIF) Personnel capability (PERS) Personnel experience (PREX) . Schedule (SCED) . support facilities (FCIL) These characteristics values can be computed on the following scale - 1 6 Ce Very Very low high © Hence the effort estimation can be given as PM = 2.94xsize*xM M = RUSEx PDIF x PERS x PREX x SCED x FCIL NO PF wD o 3. Areuse model * This model considers the systems that have significant amount of code which i reused from the earlier software systems. The estimation made in reuse model is nothing but the efforts required to integrated the reused models into the new systems. There are two types of reusable codes : Black box code and white box code. The an box code is a kind of code which is simply integrated with the new system ; thou modifying it The white box code is a kind of code that has to be modified 'o some extent before integrating it with the new system, and then only it can work . 2 Q a i 8 q a 3 a é = E 5 = 5 o a 5 3 2 8 3 3 a a Z e = z 3 > é = 5 Senerators, the system model is given @ inp’ tion about the system is taken and the code * The efforts required for automatica lly th A PM = (ASLOC AT/OOVATPROS aie