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 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. Development will be done by 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). 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. Two templates are provided in this assignment. You can use either (or create your own) in submitting your homework. Traffic Light COCOMO II Factors Effort Multipliers EM Description Category Value RELY required software reliability DATA database size CPLX product complexity RUSE develop for reuse DOCU documentation match to LC needs TIME time constraint STOR storage constraint PVOL platform volatility ACAP | analyst capability PCAP programmer capability PCON | personnel continuity APEX PLEX LTEX TOOL use of software tools SITE SCED applications experience platform experience language and tool experience multi-site development required development schedule Scaling Factors SF Description Category Value PREC FLEX RESL precedentedness development flexibility architecture and risk resolution TEAM team cohesion PMAT process maturity Rationale for non-nominal values: Grading Rubric Getting a "correct" value for PM and TDEV is worth 10 points each, given the values decided for the scale factors and effort multipliers. This is basically did you do the arithmetic for the effort and schedule formulas correctly. Identifying scale factors and effort multipliers correctly, 80 points total. You can leave out nominal effort multipliers (value = 1) Adding non-nominal effort multipliers not in the key . if you included a reasonable rationale, no penalty if the rationale was inadequate (a judgement call for the Grader) but not totally unrealistic, -1 point if no rationale (or a bad rationale) was provided, -5 points each Leaving out a non-nominal effort multiplier in the key, -5 points not including an effort multiplier implies a value of 1 (nominal), which would be incorrect if it should not have been nominal Providing the "wrong" value for a non-nominal effort multiplier, -1 point each some judgement is involved in deciding the ordinal value, but the guidance in the handout as mapped to the assignment should be sufficient rubric includes variants that the instructor considers a reasonable alternative judgment Include all five scale factors, even Extra High (value = 0) Providing the "wrong" value for a non-nominal scale factor reasonable rationale in the judgment of the Grader, no penalty inadequate rationale, -1 point missing or bad rationale, -5 points Remember that the nominal value for a scale factor is not 0 (or 1) the Extra High values for scale factors are 0