You are estimating the effort and schedule needed to implement a new traffic light control system. The estimated size of the system is 175 KSLOC.
This is a life-critical system since failures can lead to serious accidents. This means it should be very high reliability. A standard is being applied that requires less than 70% of execution cycles and memory space to be used in normal operation.
This is the third product in a traffic-light product line, with this release being built for an international customer.
The team is very highly knowledgeable and experienced in this application domain and with these tools and can be considered very highly qualified and collaborative.
The development will be done by a tightly co-located team, all on the same hallway of the same floor of their facility.
The organization has been assessed as a CMMI maturity level 2 organization.
Use the COCOMO II Post-Architecture Model to estimate the effort and schedule for this project (tables listed as “Boehm, 2000” under References). PROVIDED BELOW
The default value for each factor is Nominal.
Show your work; in particular, state (briefly) why you set each non-nominal factor to the value that you chose.
Explicitly list the category (Very Low to Extra High) and value (e.g., 0.88 or 4.39) for each scale factor (all five) and each non-nominal effort multiplier.

COCOMO II Post-Architecture Model to estimate the effort and schedule:

 
 
 

Traffic Light COCOMO II Factors Effort Multipliers EM RELY DATA CPLX RUSE DOCU TIME STOR PVOL ACAP PCAP PCON APEX PLEX LTEX OOL SITE SCED Description required software reliability database size product complexity develop for reuse documentation match to LC needs RESL TEAM PMAT time constraint storage constraint platform volatility analyst capability programmer capability personnel continuity applications experience platform experience language and tool experience use of software tools multi-site development required development schedule Scaling Factors SF PREC FLEX Description precedentedness development flexibility architecture and risk resolution team cohesion process maturity Rationale for non-nominal values: Category Value Category Value