Part 3-Requirements Development and Maintenance Project R used a spiral developm

Question

Part 3-Requirements Development and Maintenance Project R used a spiral development model to incrementally develop requirements with Requirements Development scheduled at months 1, 4, 7, and 10. For the remainder of the project, requirements were added, changed, or deleted per the following table. Month Added Changed Deleted Total 1 20 20 20 2 22 4 15 2 35 5 4 E3 2 37 39 7 10 49 8 52 52 100 10 62 11 I 62 12 1 63 Requirements churn is a measure of changes, including additions and deletions, to the requirements after they are initially agreed to (i e., baselined). One metric for requirements churn is the ratio of the number of baselined requirements minus the total number of changes to the number of baselined requirements RB- (RA+ RD +Rc) Churn RB where RB is the number of baselined requirements, RA is the number of additions to the requirements after they were baselined, RD is the number of deletions to the requirements after they were baselined, and Rc is the number of changed requirements after they were baselined. Requirements creep is defined as the addition to the requirements after they are agreed to (i.e., baselined). One metric for requirements creep is the ratio of the number of baselined requirements minus the additions after the requirements were baselined to the number of baselined requirements. creep RB-RA

Explanation / Answer

Spiral RB RA RD RC Churn Creep 1 20 2 5 0 (20-(2+5+0))/20 = 0.65 (20-2)/20 = 0.9 2 35 6 3 2 24/35 = 0.686 29/35=0.83 3 49 5 3 2 39/49=0.79 44/49=0.9 4 62 1 3 0 58/62=0.936 61/62=0.984

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

---