1. University of Southern California Center for Systems and Software Engineering RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong

2. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering 2

3. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering 3 4 ARB Review Success Criteria FCRDCR For at least one architecture, a system built to arch. will: Support the Ops Concept Satisfy the Requirements Be faithful to the Prototype Be buildable within the budgets and schedules in the Plan Show viable business case Key stakeholders committed to support Foundations Phase (to DCR) For the selected architecture, a system built to the arch. will: Support the Ops Concept Satisfy the Requirements Be faithful to the Prototype Be buildable within the budgets and schedules in the Plan All major risks resolved or covered by risk management plan Key stakeholders committed to support full life cycle

4. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering 4 4 ARB Session Outline RDCR similar format to DCR, different focus: More time on changes and updates More time for Architecture, Plans General rule on focus: emphasize your projects high risk areas –At FCR (in most cases) this will involve establishing the operational concept (including system analysis) –At DCR (in most cases) this will involve the system design and development plan (especially schedule) –At RDCR this will involve the system design and development plan and test plan

5. University of Southern California Center for Systems and Software Engineering 5 RDCR ARB Presentation Guidelines Dates: Location: SAL 322 Arrange with client; sign up ASAP! 80 minutes 60 points Every team member has to present

6. University of Southern California Center for Systems and Software Engineering RDCR ARB topics Topics to cover in your presentation & recommended time allocations –Summary of Change Sources & Resulting Changes –Progress of Prototype –Construction Plans; Transition Plan Draft –General Discussions –Risk analysis to determine course of actions 6

7. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering 7 RDCR ARB – Architected Agile Teams (x,y): (presentation time, total time) (8, 10) Acceptance Test Plan and Cases; Team's strong and weak points + Shaping & Overall Project Evaluation; Full test plan and cases (2, 3)OCD. System purpose; changes in current system and deficiencies, proposed new system, system boundary, and desired capabilities and goals; top-level scenarios (10,15) Prototype Update. Changes in significant capabilities (especially those with high risk if gotten wrong) (8, 10)Architecture. Overall and detailed architecture; design if critical; COTS/reuse selections (NOT JUST CHOICES) (6, 8)Life Cycle Plan. At lease until CCD or as appropriate; Include plans for CTS Team members’ roles & responsibilities in 577b, Full Iteration Plan (5, 10) Feasibility Evidence. Focus on Risk Analysis. Traceability Matrix. Definition of Done Plan on 2 minutes per briefing chart, except title Focus on changes (particularly new things) since DCR You may vary from the above: please notify ARB board members IN ADVANCE QFP & QMP not presented/discussed due to time constraints.

8. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering 8 8 RDCR ARB – NDI-intensive Teams (x,y): (presentation time, total time) (8, 10) Acceptance Test Plan and Cases; Team's strong and weak points + Shaping & Overall Project Evaluation; Full test plan and cases (2, 3)OCD. System purpose; changes in current system and deficiencies, proposed new system, system boundary, and desired capabilities and goals; top-level scenarios (10,15) Prototype Update. Changes in significant capabilities (especially those with high risk if gotten wrong) (5,7)Architecture. Overall and detailed architecture; design if critical; COTS/reuse selections (NOT JUST CHOICES) (6, 8)Life Cycle Plan. At lease until CCD or as appropriate; Include plans for CTS Team members’ roles & responsibilities in 577b, Full Iteration Plan (5, 10) Feasibility Evidence. Focus on Risk Analysis, Traceability Matrix. Definition of Done (0, 5) Feedback from Instructors Plan on 2 minutes per briefing chart, except title Focus on changes (particularly new things) since DCR You may vary from the above: please notify ARB board members IN ADVANCE QFP & QMP not presented/discussed due to time constraints.

9. University of Southern California Center for Systems and Software Engineering ARB Preparation Prepare and Dry run Printings –2 copies of presentation (4 slides per page) –1 copy of documents (all documents in RDC Package) 9