1. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20101 CSCI577B 2010 Light Weight Sw Engg for Off-the-Books Projects A Winsor Brown (AWBrown@USC.edu) Mar. 3, 2010

2. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20102 Goals of this Presentaiton Set the stage for non-577ab students to run/assist "Off-the-Books" projects –Project Life Cycle(s) –Tools to be used: Project G&O WinWin Wiki IICM-Sw EPG –What needs to be communicated

3. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20103 Context Instructional Incremental Commitment Model – Software Eng'g } Off-the-Books

4. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20104 "Real Projects for Real Clients" Name from Dr. David Klappholz, SIT –USC has one of the few graduate level courses doing it –If you go on to become a CS/SE educator, we are happy to help you and your institution WIIFM (actually WIIFY): –Dr. Klappholz says his students "blow [HR] interviewers away" because they can talk about the not just CS side of Sw Development: Pre & Post Design, Code and [maybe] Test Requirements Elicitation Sys. Sw. Engineereing; Transition: Hw/Sw/Pw Integration

5. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20105 Projects' Info. http://greenbay.usc.edu/ csci577/fall2009/site/ projects/index.html

6. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20106 Project 13 as Example

7. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20107 Current Off-the-Books Projects Continuing[Have]/Need Tm #: Proj Name [Client] OffCOnC /Reg OffC /DR OnC /DR Reg DR Tm 3: Theater Stage Manager Program [Julie Sanchez] Tm 8: Freehelplist.org [Steven Wolfson] Tm 10: BHCC Website Devel. [Cesar Armendariz] Tm 13: Healthcare The Rightway website [Roderick Foreman] Tm 14: AROHE Web Development [Janet Brown]

8. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20108 The Incremental Commitment Model Life Cycle Process: Overview Stage I: DefinitionStage II: Development and Operations Anchor Point Milestones Synchronize, stabilize concurrency via FEDs Risk patterns determine life cycle process

9. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-20109 ICM HSI Levels of Activity for Complex Systems Start of Fall Semester

10. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201010 RUP & ICM Anchor Points Enable Concurrent Engineering

11. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201011 What's different about IICM-Sw [from other SDLCs] Risk Driven Full Product Life Cycle Based on models and principles Architecture Review Boards Documents –Operational Concept Description (OCD; only about one in 50 software developers have seen) –Feasibility Evidence Description (FED) Documentation extent: Risk Driven

12. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201012 ICM P 3 S Model Integration Framework Process models Life cycle anchor points Risk management Key practices Success models Business case IKIWISI Stakeholder win-win Property models Cost Schedule Performance Reliability Product models Domain model Requirements Architecture Code Documentation Planning and control Milestone content Evaluation and analysis Process entry/exit criteria Product evaluation criteria

13. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201013 ICM-Sw & P 3 S Model Integration Process

14. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201014 Anchor Point Feasibility Evidence Description (FED) Evidence provided by developer and validated by independent experts that: If the system is built to the specified architecture, it will –Satisfy the requirements: capability, interfaces, level of service, and evolution –Support the operational concept –Be buildable within the budgets and schedules in the plan –Generate a viable return on investment –Generate satisfactory outcomes for all of the success-critical stakeholders All major risks resolved or covered by risk management plans Serves as basis for stakeholders’ commitment to proceed

15. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201015 Operational Concept Description (OCD) Shared Vision – Success-Critical Stakeholders – System Capability Description – Expected Benefits – Benefits Chain – System Boundary and Environment System Transformation –Information on Current System –System Objectives, Constraints and Priorities – Proposed New Operational Concept –Organizational & Operational Implications

16. University of Southern California Center for Systems and Software Engineering 3/3/2010© USC-CSSE 2005-201016 First Steps Get into Collaborative System to record time worked Get explanation of why "Off-the-Books" READ OCD, scan the other documents (using links pages) Find additional resources, if needed Contact Mentor (ex 577ab student as advisor) Contact Client: negotiate Goals/Objectives for the semester (G&O WinWin Wiki; http://seacliff.usc.edu/gowiki2/ ) Set up Project Wiki Pages (577 Projects Wiki; http://seacliff.usc.edu/projectwiki/ )