[PDF] desjardins assurance invalidité salaire
[PDF] assurance invalidité refuse de payer
[PDF] assurance pret immobilier invalidité permanente
[PDF] delai reponse apres expertise medicale assurance
[PDF] expertise médicale accident du travail fonction pu
[PDF] fiche de procédure type
[PDF] modèle courrier comité médical supérieur
[PDF] comment se passe une expertise médicale
[PDF] modèle lettre commission de réforme
[PDF] exemple de procédure administrative
[PDF] rôle des délégués du personnel en commission de ré
[PDF] déclaration de valeur déménagement pdf
[PDF] déclaration de valeur déménagement demeco
[PDF] modèle déclaration de valeur
[PDF] déclaration de valeur transport
[PDF] assurance invalidité refuse de payer
[PDF] assurance pret immobilier invalidité permanente
[PDF] delai reponse apres expertise medicale assurance
[PDF] expertise médicale accident du travail fonction pu
[PDF] fiche de procédure type
[PDF] modèle courrier comité médical supérieur
[PDF] comment se passe une expertise médicale
[PDF] modèle lettre commission de réforme
[PDF] exemple de procédure administrative
[PDF] rôle des délégués du personnel en commission de ré
[PDF] déclaration de valeur déménagement pdf
[PDF] déclaration de valeur déménagement demeco
[PDF] modèle déclaration de valeur
[PDF] déclaration de valeur transport
TypeAECF
Autonome2,401,052,500,38
Couplé3,001,122,500,35
Embarqué3,601,202,500,32
Départementd'informatique,Facultédessciences,UniversitédeSherbrooke,Québec¢SituationinitialeDéveloppement100%Échéanciernoncontraint(NS:nominalschedule)¢A=2,94B=0,91¢C=3,67D=0,28¢EM(effortmultiplier)pourmodulerl'effort¢SF(scalefactor)pourmodulerladurée2020-02-1013GP031:Estimationdel'effort(v102c)-LucLavoieCOCOMOII-SITUATION"INITIALE»Réf.: [a], extraits des pages 9-15
Version 2.1 1
© 1995 - 2000 Center for Software Engineering, USC1. Introduction
1.1 Overview
This manual presents two models, the Post-Architecture and Early Design models. These two models are used in the development of Application Generator, System Integration, or Infrastructure developments [Boehm et al. 2000]. The Post-Architecture is a detailed model that is used once the project is ready to develop and sustain a fielded system. The system should have a life-cycle architecture package, which provides detailed information on cost driver inputs, and enables more accurate cost estimates. The Early Design model is a high-level model that is used to explore of architectural alternatives or incremental development strategies. This level of detail is consistent with the general level of information available and the general level of estimation accuracy needed. The Post-Architecture and Early Design models use the same approach for product sizing (including reuse) and for scale factors. These will be presented first. Then, the Post-Architecture model will be explained followed by the Early Design model.1.2 Nominal-Schedule Estimation Equations
Both the Post-Architecture and Early Design models use the same functional form to estimate the amount of effort and calendar time it will take to develop a software project. These nominal-schedule (NS) formulas exclude the cost driver for Required Development Schedule, SCED. The full formula is given in Section 3. The amount of effort in person-months, PM NS , is estimated by the formula: 5 1j j n 1i i E NSSF0.01BE where
EMSizeAPM
Eq . 1
The amount of calendar time, TDEV
NS , it will take to develop the product is estimated by the formula:B)(E0.2D
SF01.00.2DF where
PMCTDEV
5 1j j F NSNSEq . 2
The value of n, the number of effort multipliers, EM i , is 16 for the Post-Architecture model effort multipliers, EM i , and 6 for the Early Design model. SF j stands for the exponential scale factors. The values of A, B, EM 1 , ..., EM 16 , SF 1 , ..., and SF 5 for the COCOMO II.2000 Post-Architecture model are obtained by calibration to the actual parameters and effort values for the 161 projects currently in the COCOMO II database. The values of C and D for theVersion 2.1 1
© 1995 - 2000 Center for Software Engineering, USC1. Introduction
1.1 Overview
This manual presents two models, the Post-Architecture and Early Design models. These two models are used in the development of Application Generator, System Integration, or Infrastructure developments [Boehm et al. 2000]. The Post-Architecture is a detailed model that is used once the project is ready to develop and sustain a fielded system. The system should have a life-cycle architecture package, which provides detailed information on cost driver inputs, and enables more accurate cost estimates. The Early Design model is a high-level model that is used to explore of architectural alternatives or incremental development strategies. This level of detail is consistent with the general level of information available and the general level of estimation accuracy needed. The Post-Architecture and Early Design models use the same approach for product sizing (including reuse) and for scale factors. These will be presented first. Then, the Post-Architecture model will be explained followed by the Early Design model.1.2 Nominal-Schedule Estimation Equations
Both the Post-Architecture and Early Design models use the same functional form to estimate the amount of effort and calendar time it will take to develop a software project. These nominal-schedule (NS) formulas exclude the cost driver for Required Development Schedule, SCED. The full formula is given in Section 3. The amount of effort in person-months, PM NS , is estimated by the formula: 5 1j j n 1i i E NSSF0.01BE where
EMSizeAPM
Eq . 1
The amount of calendar time, TDEV
NS , it will take to develop the product is estimated by the formula:B)(E0.2D
SF01.00.2DF where
PMCTDEV
5 1j j F NSNSEq . 2
The value of n, the number of effort multipliers, EM i , is 16 for the Post-Architecture model effort multipliers, EM i , and 6 for the Early Design model. SF j stands for the exponential scale factors. The values of A, B, EM 1 , ..., EM 16 , SF 1 , ..., and SF 5 for the COCOMO II.2000 Post-Architecture model are obtained by calibration to the actual parameters and effort values for the 161 projects currently in the COCOMO II database. The values of C and D for theDépartementd'informatique,Facultédessciences,UniversitédeSherbrooke,Québec2020-02-10GP031:Estimationdel'effort(v102c)-LucLavoie16COCOMOII-SF(LAMATRICE)Réf.: [a], extraits des pages 18
Version 2.1 18
© 1995 - 2000 Center for Software Engineering, USCTable 10. Scale Factor Values, SF
j , for COCOMO II Models ScaleFactors
Very Low
LowNominal
HighVery High
Extra High
PREC thoroughly unpreceden ted largely unpreceden ted somewhat unpreceden ted generally familiar largely familiar thoroughly familiar SF j6.20 4.96 3.72 2.48 1.24 0.00
FLEX rigorous occasional relaxation some relaxation general conformity some conformity general goals SF j5.07 4.05 3.04 2.03 1.01 0.00
RESL little (20%) some (40%) often (60%) generally (75%) mostly (90%) full (100%) SF j7.07 5.65 4.24 2.83 1.41 0.00
TEAM very difficult interactions some difficult interactions basically cooperative interactions largely cooperative highly cooperative seamless interactions SF j5.48 4.38 3.29 2.19 1.10 0.00
The estimated Equivalent Process Maturity Level (EPML) or PMATSW-CMM
Level 1
LowerSW-CMM
Level 1
UpperSW-CMM
Level 2
SW-CMM
Level 3
SW-CMM
Level 4
SW-CMM
Level 5
SF j : 7.80 6.24 4.68 3.12 1.56 0.00 The two scale factors, Precedentedness and Flexibility largely capture the differences between the Organic, Semidetached, and Embedded modes of the original COCOMO model [Boehm 1981]. Table 11 and Table 12 reorganize [Boehm 1981; Table 6.3] to map its project features onto the Precedentedness and Development Flexibility scales. These tables can be used as a more in depth explanation for the PREC and FLEX rating scales given in Table 10.3.1.1 Precedentedness (PREC )
If a product is similar to several previously developed projects, then the precedentedness is high.Table 11. Precedentedness Rating Levels
Feature Very Low Nominal / High E xtra High
Organizational understanding of product
objectivesGeneral Considerable T horough
Experience in working with related software
systemsModerate Considerable Extensive
Concurrent development of associated new
hardware and operational proceduresExtensive Moder ate Some
Départementd'informatique,Facultédessciences,UniversitédeSherbrooke,Québec2020-02-1022GP031:Estimationdel'effort(v102c)-LucLavoieCOCOMOII-EM:SYNTHÈSE(1/3)*** voir tableau complémentaire ***