CS577a Software Engineering ARB #2 Workshop

1. CS577a Software Engineering ARB #2 Workshop A Winsor Brown 11/20/09 (c) 2000-2009 1

2. Topics 577B Participation options Regular student (ideally 3; 2 in unusual circumstances) DR (>2 units; or 1 unit + Unpaid Intern 5+hrs/week)) DR only DR with Class work (to qualify for Specialization in SE) Unpaid Intern (10+hours/week) Project's going forward: 4 to 5, ideally with 577a experience or strong technical skill match Participation Survey (c) 2000-2009

3. Instructional Incremental Commitment Model – Sw (c) 2000-2009

4. Packages: Instructional ICM-Sw Start of Fall Semester Semester Break Team formed, project assigned End of Spring Semester Client Evaluation Team reformed, project assigned FCP-Level OCD, SSRD, SSAD, LCP, FED, SID, QMP* Prototype DCP-Level OCD, SSRD, SSAD, LCP, FED, SID, QMP**, ATPC^, IP†, TP‡, Exec. Prototype DCP-Level OCD, SSRD, SSAD, LCP, FED, SID, QMP, ATPC, IP, TP, Exec. Prototype Client Evaluation, Close Out Report OCD, LCP, FED Project Release ECR VCR FCR DCR RDCR CCD TRR 1 TRR 2 OCR Exploration Valuation Foundations Development Operation Construction Transition High, but addressable High, but addressable Acceptable Acceptable Negligible Negligible Risk? Risk? Risk? Too High, unaddressable Too High, unaddressable Adjust Scope, priorities, or discontinue CCD-Core Capability Drivethrough; DCR- Development Commitment Review; ECR-Evaluation Commitment Review; FCR-Foundations Commitment Review; OCR- Operational Commitment Review; RDCR-Rebaselined Development Commitment Review; TRR-Transition Readiness Review; VCR-Valuation Commitment Review * Peer Review Strategy for Foundations; ** Peer Review and Test Strategy For Development; ^ at least one test case; † Skeletal for up through CCD; ‡ Team/Client tasks and dates identified Risk? Risk? Risk? Risk? Risk? (c) 2000-2009

5. DCR ARB DCR ARB Session Outline (x,y): (presentation time, total time) (5, 5) Acceptance Test Plan and Cases; Things done right; open issues to address (Remote Team member) (5, 5) 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) (5, 10) SSRD. 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 (no history) or ? as appropriate; Include plans for CTS initial cycle “Plans” during 2nd Foundations Iteration Team members’ roles & responsibilities in 577b. (5, 10) Feasibility Rationale. Refined business case; major risks; general discussion (0, 5) Feedback from Instructors • Plan on 2 minutes per briefing chart, except title • Focus on changes (particularly new things) since FCR • You may vary from the above: please notify ARB board members IN ADVANCE • QFP & QMP not presented/discussed due to time constraints. (c) 2000-2009 5

6. Instructional ICM-Sw: One semester projects (NDI/NCES) End of Fall Semester Start of Fall Semester Typical Project Milestones Draft DC Package ARB ARB FCP-Level OCD, SSRD?, SSAD*, LCP, FED*, SID*, QMP*, Prototype DCP-Level OCD, SSRD?, SSAD*, LCP, FED*, SID*, QMP, ATPC, IP, Prototypes Team formed, project assigned Client Evaluation, Close Out Report All developed artifacts OCD, LCP, FED Project Release TP, SP, ATPR, UM 08/22 09/22 10/06 10/20 11/14 11/21 12/01 T OR or CR R PTRR CCD ECR VCR FCR DCR Exploration Valuation Foundations Development Operation Construction Transition ATPC: Acceptance Test Plan & Cases; ATPR: Acceptance Test Procedure & Results; IP: Iteration Plan; TP: Transition Plan; SP: Support Plan; UM: User Manual * Document / Scope adjusted; All documents are based on minimal system capabilities; ? SSRD only if significant glue code (c) 2000-2009

7. TRR/OCR for One Semester Development Projects 10 min. Introduction • Operational concept overview, TRR specific outline, transition objective & strategy 15 min. Demo of IOC (Product status demonstration) 5 min. Support Plan 10 min. Data Reporting & Archiving 25 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.) 15 min. Feedback *** Times are approximate *** (c) 2000-2009

8. NDI/NCIS-intensive ARB Session Outline (x,y): (presentation time, total time) (5 , 5) Remote Team Member(s) (jointly) Team’s strong points & weak points (operational view and technical view) concerns & possible solutions (5, 5) OCD. System objectives; result/ benefit-chain diagram; system boundary diagram; project constraints; current processes; system capabilities; level of services; deployment diagram (10,10) Prototype/ demo/ sample screenshots Most significant capabilities [buying information](especially those with high risk if gotten wrong) (5, 10) SSAD. System Architecture; Info&Arctifacts (if RDB); Deployment; (5, 10) LCP. Overall strategy; milestones and schedule; deliverables; Risks (5, 10) FCP. Assessment approach, assessment results, evaluation criteria, business case, conclusion (5, 10) SID. Traceability Matrix (5, 10) Test Results. Test cases and results (5, 5) Transition Plan and Support Plan. HW/SW/Site preparation, support environment, release strategy • Things done right; issues to address (Instructional staff) • Plan on 2 minutes per briefing chart, except title • Each chart MUST have information SPECIFIC to your project (c) 2000-2009