CS 577b Software Engineering II -- Introduction 18 February 2019 RDCR ARB CS 577b Software Engineering II Supannika Koolmanojwong © 2002-6 USC Center for Software Engineering

ARB Review Success Criteria FCR DCR 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: All major risks resolved or covered by risk management plan Key stakeholders committed to support full life cycle 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 4

RDCR ARB Presentation Guidelines CSCI 577b Software Engineering II, CTS & R-LCA Guidelines 2/18/2019 RDCR ARB Presentation Guidelines Dates: February 6(M), 8(W) Location: SAL 322 Arrange with client; sign up ASAP! 80 minutes 30 points Every team member has to present ©2002-2006 USC-CSE

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

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 (5,10) Prototype Update. Changes in significant capabilities (especially those with high risk if gotten wrong) (2, 3) SSRD. ALL high priority or changes in requirements; rating for all others (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 (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.

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 (8,10) Prototype Update. Changes in significant capabilities (especially those with high risk if gotten wrong) (2, 3) SSRD. ALL high priority or changes in requirements; rating for all others (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 (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. 8

ARB Preparation Prepare and Dry run Printings Client’s parking request 4 copies of presentation (2 slides per page) 2 copies of documents (all documents in RDC Package) Email to csci577 24 hours in advance Client’s parking request Email to Julie – jasanche@usc.edu