1. ARB Schedule Locations
All will be at SAL 322, except 2:00 – 3:20 slots will be at OHE 122
Print out a copy of your presentation for your client
Put your slides on team website
Otherwise, -2 points
Monday 11/26/2018
Friday 11/30/2018
12:30 - 1:50
2:00 - 3:20
3:30 - 4:50
5:00 - 6:20
6:30 – 7:50
Monday Nov 30,
3:30 - Team 2
5pm - Team 1
Tues Dec 1
12:30 - Team 5
3:30 - Team 3
Fri Dec 4
12:30 - Team 7
2pm - Team 4
3:30pm - Team 6

2. DCR success criteria
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

3. DCR Expectation Less time for OCD Continue on Prototype
More time for Architecture, Plan 
Fine-tuning based on FCR ARB experience 
Focus on changes since FCR 
Emphasize material that is relevant to 577B (or to end of class) 
Risk management still fundamental

4. Presentation Outline (2 semesters)
(x,y): (presentation time, total time)
(5, 5) Acceptance Test Plan and Cases; Team's strong and weak points & Overall Project Evaluation (DEN Remote Team member)
(5, 5) OCD. System boundary, and desired capabilities and goals; top-level scenarios 
(10,10) Prototype Update. Changes in significant capabilities (especially those with high risk if gotten wrong)
(5, 5) Requirements. ALL high priority or changes in requirements; rating for all others
(10, 15) Architecture. Overall and detailed architecture; design if critical; COTS/reuse selections (NOT JUST CHOICES)
(10, 15) Life Cycle Plan. Focus on 577b Plan; Include plans for Construction-Transition-Support initial cycle “Plans” during 2nd Foundations Iteration; Team members’ roles & responsibilities in 577b, Iteration Plan
(5, 10) Feasibility Evidence. Refined business case; major risks; general discussion
(5,5) Quality Focal Point –Solved & Remaining Technical Debt, Traceability Matrix between OCD, Arch, Test cases, 2 selected metrics
(10) Feedback from Instructors
Focus on changes (particularly new things) since FCR

5. Transition Readiness Review
Product works as expected (or not with noted exceptions)
Product will help users do job
Show quality development
Show sustainability 
Show confidence that product is/will be ready to be used
e.g. Transition plan & status

6. TRR Presentation Outline
5 minutes Operational concept overview, TRR specific outline, transition objective & strategy
25 min. Demo of Initial Operational Capability (Product status demonstration)
10 min. Test Cases, Procedures and Results 
5 min Quality Focal Point - (Solved & Remaining)Technical Debt, Traceability Matrix, 2 selected Metrics
10 min. Summary of Transition Plan (as appropriate)
HW, SW, site, staff preparation
Operational testing, training, & evaluation
Stakeholder roles & responsibilities
Milestone plan
Required resources Software product elements (code, documentation, etc.)

7. Marks allocation (70 points)
Quality of the presentation: 10
Quality of the project: 40
Progress: 10
Consistency: 5
Time Management: 5