1. University of Southern California Center for Systems and Software Engineering CS 577b: Software Engineering II Class Introduction

2. University of Southern California Center for Systems and Software Engineering Outline Overview Schedule –In-Class Team Discussion –Guest Lecturers –Individual Research Presentation Marks Allocation Possible 577b risks Team Re-Formation (C) 2012 USC-CSSE2

3. University of Southern California Center for Systems and Software Engineering CS 577b Course Objective Learn how to go –From a successful RDC package –To a successfully "delivered" software system Main elements –Coping with “devils in the details” –Doing cost-effective quality management –Understanding how stakeholders will operate & maintain system –Using IICSM-Sw Architected-Agile project guidelines (C) 2012 USC-CSSE3

4. University of Southern California Center for Systems and Software Engineering CS 577b Course Goals Teaching & Learning Research Product delivering Stakeholders Satisficing (C) 2012 USC-CSSE4

5. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE5 ICSM –Class Milestones 02/08 03/23 04/0904/27

6. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE6

7. University of Southern California Center for Systems and Software Engineering Software Engineering Project Course (CS 577) Fall: Develop Life Cycle Architecture Packages –Ops. Concept, Requirements, Prototype, Architecture, Plan –Feasibility Rationale, including business case –Results chain linking project results to desired outcomes Spring: Develop Initial Operational Capability –Software, personnel, and facilities preparation –2-week transition period –then the student teams disappear Tools and techniques: WikiWinWin; Benefit Chain; Rational Software Modeler; Subversion; USC COCOMO II; MS Project; USC Incremental Commitment Spiral model method (C) 2012 USC-CSSE7

8. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE8 Stakeholder Win-Win Approach Stakeholders Students, Employers Project clients Faculty, Profession Win Conditions Full range of SW Engr. skills Real-client project experience Non-outsourceable skills Advanced SW tech. experience Useful applications Advanced SW tech. understanding Moderate time requirements Educate future SW Engr. leaders Better SW Engr. technology Applied on real-client projects

9. University of Southern California Center for Systems and Software Engineering University of Southern California Center for Systems and Software Engineering Project Schedule –Spring 2012 Jan. 10 to 27- Re-form teams Feb. 6- Draft RDCR Feb. 8-10- RDCR ARB Mar. 28-30- Core Capability Drivethru Apr. 9 - Draft Transition Package on Web Apr. 11-13- Transition Readiness Reviews Apr. 18-20- Installation and Transition May 4- Operational Commitment Review for IOC May 7- Client Evaluations 9

10. University of Southern California Center for Systems and Software Engineering 10 Dec. 12, 2011..Jan. 9 to Feb. 11: Work with [parts of] teams: –Rebaseline prototype, prioritize requirements –Plan for CS 577b specifics, including transition strategy, key risk items –Participate in ARB review Feb 15 to April 30: Scheduled Weekly Meetings with Teams to: –Discuss status and plans –Provide access to key transition people for strategy and readiness discussions Mar 28 to 30: Core Capability Drivethrough (Clients exercise systems) Apr 11- Apr 13: Project Transition Readiness Reviews Apr 21: Installation and Transition –Install Product –Execute Transition Plan May 3-4: Operational Commitment Review for Initial Operational Capability May 7: Client Evaluations Timelines: Spring 2012

11. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE11 Main Challenge for Clients Products are delivered on or before April 19 th –Design Code Review: April 18 th Finals: May 7-14 Students disappeared by May 14, or earlier

12. University of Southern California Center for Systems and Software Engineering Course Etiquette Observe normal rules of classroom etiquette –Be on time! If you are late, don’t slam the door –ONE conversation at a time –ONE topic at a time –Direct all comments to the instructor –Encourage (rather than criticize) other students –E-mail & browsing at breaks or after class only –Turn off/silent cell phones (C) 2012 USC-CSSE12

13. University of Southern California Center for Systems and Software Engineering Outline Overview Schedule –In-Class Team Discussion –Guest Lecturers –Individual Research Presentation Marks Allocation Possible 577b risks Team Re-Formation (C) 2012 USC-CSSE13

14. University of Southern California Center for Systems and Software Engineering Course Schedule See –http://greenbay.usc.edu/csci577/spring2012/schedule.phphttp://greenbay.usc.edu/csci577/spring2012/schedule.php In-Class Team discussion –January 27, March 11 –Iteration planning and assessment –Retrospective analysis –Q&A (C) 2012 USC-CSSE14

15. University of Southern California Center for Systems and Software Engineering Potential Guest Lecturers Boeing Aerospace Corporation Disney TestMax Cornerstones (C) 2012 USC-CSSE15

16. University of Southern California Center for Systems and Software Engineering Individual Research Presentation 8% of your final grade Topics, but not limited to Software Process Improvement Process Quality Assurance Emerging Software Engineering topics Note: must be related to CSCI577ab Students must select topic and get approval Due date: March 07 Each student most cover a different aspect of a topic 10 minutes presentation April 20-25 (C) 2012 USC-CSSE16

17. University of Southern California Center for Systems and Software Engineering Outline Overview Schedule –In-Class Team Discussion –Guest Lecturers –Individual Research Presentation Marks Allocation Possible 577b risks Team Re-Formation (C) 2012 USC-CSSE17

18. University of Southern California Center for Systems and Software Engineering Marks Allocation (C) 2012 USC-CSSE18 Category% Individual Score (HW/In-Class)22% Individual Critique10% Individual Research Presentation8% Individual Contribution5% Team Score50% Client Evaluation5% 100%

19. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE19 Primary CS577b Risk Items Personnel –Commitment –Compatibility –Ease of communication –Skills (management, web/java, Perl, CGI, data compression, …) Schedule –Project scope –IOC content –Critical-path items (COTS, platforms, reviews, …) COTS –See next chart –Multiple COTS

20. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE20 Primary CS577b Risk Items (cont.) Requirements & UI –Not matching client user needs Performance –Memory, Disk Space usage (#Bits) –Bus, Network, CPU utilization & bandwidth (#Bits/sec) –Overhead sources –Reliability of deliver –Safe –Secure External tasks –Client/operator preparation –Commitment for transition

21. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE21 COTS & External Component Risks COTS risks –Immaturity –Inexperience –Incompatibility with Application Platform Other COTS –Controllability

22. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE22 COTS & External Component Risks (cont.) Non-commercial off-the shelf components –Sources Reuse libraries Government (GOTS) Universities (ROTS) –Issues Qualification testing Benchmarking Inspections Reference checking Compatibility analysis Both –Safety –Dependability –Security

23. University of Southern California Center for Systems and Software Engineering Top 11 - Risk distribution in CSCI577 08/26/11©USC-CSSE23

24. University of Southern California Center for Systems and Software Engineering Comparing between risks in Fall and Spring 08/26/11©USC-CSSE24

25. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE25 Heads-Up: CS 577b Planning Common LCP Problems @ RDCR RDCR operational prototype, business-case iterations: What have you done since last semester? Too many internal-increment deliverables Lack of core-capability specifics –End-to-end demonstrable capability Lack of specific team member responsibilities –By artifact & increment; but flexible Transition preparation –Transition-leader’s success plan (teammates, clients)

26. University of Southern California Center for Systems and Software Engineering Outline Overview Schedule –In-Class Team Discussion –Guest Lecturers –Individual Research Presentation Marks Allocation Possible 577b risks Team Re-Formation (C) 2012 USC-CSSE26

27. University of Southern California Center for Systems and Software Engineering (C) 2012 USC-CSSE27 CS577 Academic Integrity Guidelines Individual Assignments –OK to discuss –Not OK to copy each others’ solution elements –Not OK to copy external sources without attribution Within “Fair Use Guidelines” Team Assignments –OK to use other teams’ patterns e.g. MS Project tasks Must give credit!!! –Not OK to copy other teams’ complete/partial solutions e.g. MS course & project schedules

28. University of Southern California Center for Systems and Software Engineering Outline Overview Schedule –In-Class Team Discussion –Guest Lecturers –Individual Research Presentation Marks Allocation Possible 577b risks Team Re-Formation (C) 2012 USC-CSSE28

29. University of Southern California Center for Systems and Software Engineering 577b project roles Project Manager Implementer Tester Trainer IIV&Ver Quality Focal Point (C) 2012 USC-CSSE29

30. University of Southern California Center for Systems and Software Engineering 30(C) 2012 USC-CSSE

31. University of Southern California Center for Systems and Software Engineering 577b Project Activities Rebaselined Foundations Phase (C) 2012 USC-CSSE31

32. University of Southern California Center for Systems and Software Engineering 577b Project Activities Development Phase – Construction Increment (C) 2012 USC-CSSE32

33. University of Southern California Center for Systems and Software Engineering 577b Project Activities Development Phase – Transition Increment (C) 2012 USC-CSSE33

34. University of Southern California Center for Systems and Software Engineering 577b Project Artifacts Exploration, Valuation, and Foundations set –OCD, SSRD, PRO, SSAD, LCP, FED –QMP, SID, WW report Initial Operational Capability set –Test Plan & Cases, Test Procedures & Results –Iteration Plan & Iteration Assessment Report –CCD Report Transition and Support set –Transition Plan, Training Materials –Regression Test Package –User Manual (C) 2012 USC-CSSE34

35. University of Southern California Center for Systems and Software Engineering Team Reformation #Project On- Campus Off- Campus Plan 1Improving Thai CDC 2Using Social Media 3ISTARTONMONDAY 11 4LEMA - Integrated Family Accountability System 5LACGC Employment Opportunities Online App 51Continue 6Mission Science Information and Data Mgnt Sys 1 7Leamos 1 8LADOT SCANNING 9Amer i Can Re-Up 1 10LACGC Employment Opportunities Online App 11Central Avenue Business District Operating System 3Continue 12LEMA Pilot School Integrated Scheduling Sys 11 13Los Angeles Community Garden Inventory and Locator 31Continue 14Transportation Grant Fund Database 41Continue (C) 2012 USC-CSSE35

36. University of Southern California Center for Systems and Software Engineering Team Reformation #Project On- Campus Off- Campus Plan 1 Improving Thai CDC 2 Using Social Media 3 ISTARTONMONDAY 11 To team 12 4 LEMA - Integrated Family Accountability System 5 LACGC Employment Opportunities Online App 51 6 Mission Science Information and Data Mgnt Sys 1 To team 12 7 Leamos 1 To team 11 8 LADOT SCANNING 9 Amer i Can Re-Up 1 To team 11 10 LACGC Employment Opportunities Online App 11 Central Avenue Business District Operating System 3 + Jeff T. + David W. 12 LEMA Pilot School Integrated Scheduling Sys 11 + Thammanoon K. + Mark V. + Kathleen B 13 Los Angeles Community Garden Inventory and Locator 31 14 Transportation Grant Fund Database 41 (C) 2012 USC-CSSE36

37. University of Southern California Center for Systems and Software Engineering Feedback on lectures - Favorite lectures CountFavorite Topics 16Software Architecture (Booch) 10B-Chain & B-Realization 8ICSM 8VBSE 5Architecture in general 5Risk Management 4OOA&D 4Requirements Prioritization 4WinWin negotiation 3Agile Concepts 3Ethics 3Life Cycle Management 2Cost Estimation 2Prototype (C) 2012 USC-CSSE37

38. University of Southern California Center for Systems and Software Engineering Feedback on lectures – Beneficial lectures CountFavorite Topics 11Software Architecture (Booch) 9B-Realization & WW negotiation 6ICSM 5Architecture 5VBSE 4COCOMO 4Risk Management 3Architecture Workshop &Modeling 3Client Interaction 3Prototype & UI 3Software Process Models (C) 2012 USC-CSSE38

39. University of Southern California Center for Systems and Software Engineering Feedback on lectures – should be added CountFavorite Topics 5Design Pattern 4Software processes used in the industry 4Team Dynamics 3Client Communication & Negotiation 3COCOMO Formula & Calculation 3Guest Lecturer for various industries 3Testing 2Cloud Computing 2Configuration Management 2Domain specific topics (e.g. Healthcare) 2how to select NDI/NCS 2More interactive classes 2Real Agile Experience 2Technical Writing (C) 2012 USC-CSSE39

40. University of Southern California Center for Systems and Software Engineering Feedback on lectures – should be removed CountFavorite Topics 15NONE 5Agile concepts 5Client interaction 5COCOMO II 5OOA&D 3Duplicate of ICSM 3Software Ethics 3Testing 3VBSE 2History of SE 2Project Management 2Schedule estimation and improvement 2Software process models - join with others (C) 2012 USC-CSSE40