1. University of Southern California Center for Systems and Software Engineering Course Overview and ICSM Incremental Commitment Spiral Model CSCI 577a Software Engineering I Supannika Koolmanojwong, Barry Boehm August 24, 2015

2. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE2 Outline Software Engineering Definition and Learning Objectives –Importance of trust, honoring commitments –Comparison of CS 510 and CS 577a Class Overview –Nature of Projects –Incremental Commitment Spiral Model –Project Structure, Schedule, and Risks Course Reponsibilities 2

3. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE3 CS 577 Learning Objectives 3 “Software Engineering:” The disciplines which distinguish the coding of a computer program from the development of a software product. Prepare you for software leadership careers through the 2050’s -Agility with discipline; COTS/OSS, cloud services, model-based and network centric systems, apps, widgets, social networking Integrate all these considerations -Via value-based, Incremental Commitment Spiral Model (ICSM) and project experience Stages Issues

4. University of Southern California Center for Systems and Software Engineering I-shaped vs T-shaped person A T-shaped person is one who has technical depth in at least one aspect of the system’s content, and a workable level of understanding of a fair number of the other system aspects An I-shape computer science graduate is one who has a great deal of depth in software technology, but little understanding of the other disciplines involved 4

5. University of Southern California Center for Systems and Software Engineering Factors contributing to I-shaped software engineer problems Hardware-first system engineering practices discourage software engineers to participate in overall system requirements and architecture decisions Narrow-focused Software-CMM (Capability Maturity Model) process areas stimulate more I-shaped thinking 5

6. University of Southern California Center for Systems and Software Engineering Problems created by I-shaped software engineers The Golden Rule: Do unto others as you would have others do unto you –Platinum Rule: Do unto others as they would be done unto. Computer scientists prize abstraction –User name: U1, U2 vs Jim, Tina –Inventing personas effectively help students represent classes of stakeholders Making programmer-convenient, but user- inconvenient decisions –10-day data buckets vs weekly, monthly reporting 6

7. University of Southern California Center for Systems and Software Engineering T-Shaped Course Practices (1/2) Visit clients’ workplace and jointly develop a desired concept of operation Jointly negotiate prioritized stakeholder win-win requirements Jointly develop evaluation criteria for choices of non-developmental items Jointly determine and prioritize project risks, develop risk mitigation plans Develop clients’ business case linking investments to quantitative and qualitative benefits 7

8. University of Southern California Center for Systems and Software Engineering T-Shaped Course Practices (2/2) Identify complementary client activities Participate in 4 major milestone reviews with clients and instructors Develop initial increment and hold a client Core Capability Drivethrough Jointly negotiate prioritized end-game revisions Transition software and support materials 8

9. University of Southern California Center for Systems and Software Engineering Software Systems Engineering Course at USC Project Roles –Operational Concept Engineer, Requirements Engineer, Prototyper, UML Modeler, Software Architect, Life Cycle Planner, Feasibility Analyst, Quality Focal Point, Independent Integrated V&V, Coder, Tester, Trainer, Project Manager WinWin Negotiation Roles –Personal Knowledge Contributor, Shaper 9

10. University of Southern California Center for Systems and Software Engineering What is the ICSM? Risk-driven framework for determining and evolving best-fit system life-cycle process Integrates the strengths of phased and risk- driven spiral process models Synthesizes together principles critical to successful system development –Stakeholder value-based guidance –Incremental commitment and accountability –Concurrent multidiscipline engineering –Evidence and risk-driven decisions Principles trump diagrams… Provided via course textbook and Electronic Process Guide 10(c) 2007-2015 USC CSSE

11. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE11 Most Important Learning Objective: Honoring Commitments Leadership is built on a bedrock of trust Trust is built on a bedrock of commitments Two major commitments in CS577a –Commitment to USC copyright and academic integrity standards Checked via copying-identification tools –Commitment to your team and clients to collaborate, produce high quality artifacts on schedule Checked via FCR, DCR peer assessments 5% of grade based on honoring commitments –Can be up to 2 grade-level loss –Or F in course for plagiarism 11

12. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE12

13. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE13

14. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE14 Reuse of Others’ Work Personal Use (read, experiment with) –OK, within your access rights Offered for credit or sale (class, journal, product) –OK within your access and usage rights –Also need to acknowledge source Team projects for course –Reuse among team members usually OK, but check Powerful tools used to detect unauthorized reuse –Serious penalties at USC and elsewhere –Best to check access and usage rights –When in doubt, acknowledge the source –Mark copy-and-paste placeholders for replacement 14

15. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE15 Comparison of CS 510 and CS 577a COCOMO II Extensions Microeconomics – Decision Theory Agile and Rapid Development People Management 2 Midterms, Final ICSM Principles and Practices WinWin – Risk Management Planning & Control – COCOMO II Business Case Analysis S/W - System Architecting Operational Concept & Rqts. Definition – Winbook System – Prototyping OO Analysis & Design – Visual Paradigm Team Project (DEN: IV&V) CS 510 CS 577a VBSE Theory, Practice

16. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE16 Outline Software Engineering Definition and Learning Objectives –Importance of trust, honoring commitments –Comparison of CS 510 and CS577a Class Overview –Nature of Projects –Incremental Commitment Spiral Model –Project Structure, Schedule, and Risks Course Reponsibilities 16

17. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE17 e-Services Projects Overview Clients identify prospective projects –Operational capabilities or feasibility explorations –Fall: 12 weeks to prototype, analyze, design, plan, validate –Spring: 12 weeks to develop, test, transition –Fall: 12 weeks to do it ALL (some projects) –MS-level, 5-6 person, CS 577 project course Clients, CSSE, USC Professors: negotiate workable projects –Useful results within time constraints –Operationally supportable as appropriate Clients work with teams to define, steer, evaluate projects –Exercise prototypes, negotiate requirements, review progress –Mutual learning most critical success factor 17

18. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE18 Stakeholder Win-Win Approach Builds trust through observed actions 18 StakeholdersWin Conditions Students, Employers Full range of Sw Engineering Skills Real-client project experience Non-outsourceable skills Advanced Sw technology experience Project clientsUseful applications Advanced Sw technology understanding Moderate time requirements Faculty, ProfessionEducate future Sw Engineering leaders Better Sw Engineering technology Applied on real-client projects

19. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE19 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 –20 projects; 120 students; about 20 clients –Or deliver complete Initial Operational Capability Spring: Develop Initial Operational Capability –5-8 projects; 30-50 students; 5-8 clients –Software, personnel, and facilities preparation –2-week transition period –then the student teams disappear Tools and techniques: WinBook; Benefits Chain; Rational Software Modeler, Subversion; USC COCOMO II; MS Project; USC Incremental Commitment Spiral Model method –Reworked annually based on student & client feedback 19

20. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE20 Instructional Incremental Commitment Spiral Model – Software Engineering 10/12 11/30

21. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE21 Outline Software Engineering Definition and Learning Objectives –Importance of trust, honoring commitments –Comparison of CS 510 and CS577a Class Overview –Nature of Projects –Incremental Commitment Spiral Model –Project Structure, Schedule, and Risks Course Reponsibilities 21

22. University of Southern California Center for Systems and Software Engineering The Incremental Commitment Spiral Model 22(c) 2007-2015 USC CSSE

23. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE 23 Incremental Commitment in Gambling Total Commitment: Roulette –Put your chips on a number E.g., a value of a key performance parameter –Wait and see if you win or lose Incremental Commitment: Poker, Blackjack –Put some chips in –See your cards, some of others’ cards –Decide whether, how much to commit to proceed 23(c) 2007-2015 USC CSSE

24. University of Southern California Center for Systems and Software Engineering The Incremental Commitment Spiral Process: Phased View Anchor Point Milestones Synchronize, stabilize concurrency via FEDs Risk patterns determine life cycle process 24(c) 2007-2015 USC CSSE

25. University of Southern California Center for Systems and Software Engineering ICSM Activity Levels for Complex Systems 25(c) 2007-2015 USC CSSE

26. University of Southern California Center for Systems and Software Engineering Anchor Point Feasibility Evidence Descriptions 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 Synchronizes and stabilizes concurrent activities Can be used to strengthen current schedule- or event-based reviews 26(c) 2007-2015 USC CSSE

27. University of Southern California Center for Systems and Software Engineering 27(c) 2007-2015 USC CSSE

28. University of Southern California Center for Systems and Software Engineering 28(c) 2007-2015 USC CSSE

29. University of Southern California Center for Systems and Software Engineering Principles Trump Diagrams 1. Stakeholder value-based guidance 2. Incremental commitment and accountability 3. Concurrent system engineering 4. Evidence and risk-driven decisions 29(c) 2007-2015 USC CSSE Counterexample: Bank of America Master Net Good example: Symbiq Medical Infusion Pump

30. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE 30 ICSM Principles Counterexample: Bank of America Master Net

31. University of Southern California Center for Systems and Software Engineering Principles Trump Diagrams: Master Net 1.Stakeholder value-based guidance –Overconcern with Voice of Customer: 3.5 MSLOC of rqts. –No concern with maintainers, interoperators: Prime vs. IBM 2.Incremental commitment and accountability –Total commitment to infeasible budget and schedule –No contract award fees or penalties for under/overruns 3.Concurrent multidiscipline engineering –No prioritization of features for incremental development –No prototyping of operational scenarios and usage 4.Evidence and risk-driven decisions –No evaluation of Premier Systems scalability, performance –No evidence of ability to satisfy budgets and schedules 31(c) 2007-2015 USC CSSE

32. University of Southern California Center for Systems and Software Engineering Example ICSM Commercial Application: Symbiq Medical Infusion Pump Winner of 2006 HFES Best New Design Award Described in NRC HSI Report, Chapter 5 32(c) 2007-2015 USC CSSE

33. University of Southern California Center for Systems and Software Engineering Symbiq IV Pump ICSM Process - I Exploration Phase –Stakeholder needs interviews, field observations –Initial user interface prototypes –Competitive analysis, system scoping –Commitment to proceed Valuation Phase –Feature analysis and prioritization –Display vendor option prototyping and analysis –Top-level life cycle plan, business case analysis –Safety and business risk assessment –Commitment to proceed while addressing risks 33(c) 2007-2015 USC CSSE

34. University of Southern California Center for Systems and Software Engineering Symbiq IV Pump ICSM Process - II Foundations Phase –Modularity of pumping channels –Safety feature and alarms prototyping and iteration –Programmable therapy types, touchscreen analysis –Failure modes and effects analyses (FMEAs) –Prototype usage in teaching hospital –Commitment to proceed into development Development Phase –Extensive usability criteria and testing –Iterated FMEAs and safety analyses –Patient-simulator testing; adaptation to concerns –Commitment to production and business plans 34(c) 2007-2015 USC CSSE

35. University of Southern California Center for Systems and Software Engineering Principles Satisfaction: Symbiq IV Pump 1.Stakeholder value-based guidance –Extensive involvement of users, buyers, funders, regulators –Extensive use of prototyping, safety analysis methods 2.Incremental commitment and accountability –Expanding system definition and evidence elaboration –Decision to start with composable 1- and 2-channel pumps 3.Concurrent multidiscipline engineering –Concurrent evaluation of display, alarm, pump suppliers –Concurrent definition, evaluation of safety and business cases 4.Evidence and risk-driven decisions –Evidence-based reviews of technical and business feasibility –Outstanding risks covered by next-phase risk mitigation plans 35(c) 2007-2015 USC CSSE

36. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE36 Outline Software Engineering Definition and Learning Objectives –Importance of trust, honoring commitments –Comparison of CS 510 and CS577a Class Overview –Nature of Projects –Incremental Commitment Spiral Model –Project Structure, Schedule, and Risks Course Reponsibilities 36

37. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE37 ICSM Model Integration: Valuation Phase 37 Domain Model WinWin Taxonomy Basic Concept of Operation Frequent Risks Stakeholders, Primary win conditions WinWin Negotiation Model IKIWISI Model, Prototypes, Properties Models Environment Models WinWin Agreements, Shared Vision Viable Architecture Options Updated Concept of Operation Life Cycle Plan elements Outstanding FCR risks Requirements Description FCR Rationale FCR Package Anchor Point Model determines identifies determines situatesexercise focus use of focus use of determines guides determination of validate inputs for provides initializeadoptidentify update achieveiterate to feasibility, consistency determines exit criteria for validates readiness of initializesinitializes

38. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE38 Team Structure Six-person, on-campus teams (augmented by DEN students) –Each artifact should have a lead producer and a co-producer –DEN students do IIV&V, Issue/Bug tracking, etc. Project Manager generally the lead for Feasibility Rationale 1. Ensures consistency among the team members’ artifacts (and documents this in the Rationale). 2. Leads the team’s development of plans for achieving the project results, and ensures that project performance tracks the plans. Teams formed and project selected by Wednesday, Sept. 9, 4:00pm –Web questionnaires should help in team formation (EF-3) Start forming teams now! –What are your skills? What roles would you prefer? –What skills does your team need? Who does them? –What projects does your team prefer? Note: Team Mixer Activity : Friday Sept. 4, After Class, E-Quad 38

39. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE39 Timelines: Fall 2015 Wed. Sept. 9: Teams formed; projects selected; Fri. Sept 11: 1:00 - 2:00 pm Win-Win negotiation Training for Clients (SAL322) 2:00 - 3:20 pm CS 577a class Session with clients (OHE122) Sept 14-16: Site visit During the semester: Sept. 16 – Dec. 11 Intermediate consultation, prototype reviews, WinWin negotiation, scheduled weekly meetings with team, prototype evaluations, on-campus win-win negotiation participation & off campus follow up, Identify other success-critical stakeholders Oct. 16 – 18: FCR ARB meetings Nov. 30, Dec 1,4: DCR ARB meetings Dec. 11: Submit Client evaluation form DCR: Development Commitment Review; FCR: Foundations Commitment Review; VCR: Valuation Commitment Review

40. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE40 Dec. 11, 2015…Jan. 11 to Feb.5: 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 6 to April 22: Scheduled Weekly Meetings with Teams to: –Discuss status and plans –Provide access to key transition people for strategy and readiness discussions Mar 14 to 18: Core Capability Drivethrough (Clients exercise systems) Apr 11 - Apr 15: Project Transition Readiness Reviews Apr 18: Installation and Transition –Install Product –Execute Transition Plan Apr 29: Operational Commitment Review for Initial Operational Capability May 3: Client Evaluations Timelines: Spring 2016

41. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE41 Top 10 Risk Items: ICSM Book, Chapter 15 41 1. Inflated expectations 2.Success-critical stakeholder lack of involvement or value conflicts 3.Underdefined plans and requirements 4.Architecture/reuse/non-developmental item (NDI) conflicts 5.Personnel shortfalls 6.Immature or obsolete processes; unbridled requirements volatility 7.Human–system integration shortfalls 8.Legacy asset incompatibilities 9.Unbalanced nonfunctional requirements or -ilities 10.Immature technology

42. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE42 Primary CS577 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; multi-COTS Rqts, UI: mismatch to end-user needs Performance: #bits; #bits/sec; overhead sources External tasks: Client/Operator preparation, commitment for transition 42

43. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE43 NDI and External Component Risks Non-Developmental Items: Commercial-Off-the-Shelf, Cloud Services, Non-commercial Commercial NDI risks: immaturity; inexperience; NDI incompatibility with application, platform, other NDI; controllability Non-commercial off-the shelf components: Open source, reuse libraries, government, universities, etc. –Qualification testing; benchmarking; inspections; reference checking; compatibility analysis 43

44. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE44 Outline Software Engineering Definition and Learning Objectives –Importance of trust, honoring commitments –Comparison of CS 510 and CS577a Class Overview –Nature of Projects –Incremental Commitment Spiral Model –Project Structure, Schedule, and Risks Course Responsibilities 44

45. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE45 Academic Integrity Acknowledgement Single most-serious offense: Plagiarism –Using other people’s work, directly or indirectly, without crediting them –Homework, exams, class exercises, individual assignments Minor first offense: You lose one grade level –E.g., B+ instead of A- Major first offense or second offense: F for the course 45

46. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE46 We are Serious About Plagiarism –And experienced in finding it 46

47. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE47 Early Assignments 1st Class (Done in class; DEN students – email or fax to DEN office [if you miss 1 st class(es), get from Class Website]: –EF-1: Basic Questionnaire : Commitment Form (5 points) submit signed version ASAP to TAs –EF-2: Academic Integrity and Copyright Agreement (5 points) submit signed version ASAP to TAs Next Wednesday 09/02 –HW-1 : Incremental Commitment Spiral Model Submit thru D2L; http://courses.uscden.nethttp://courses.uscden.net http://greenbay.usc.edu/csci577/fall2015/assignments Next Friday 09/04 –EF-3: Online "Questionnaire for CSCI 577a: Software Engineering I--Fall 2013" [on line ONLY] (5 points) Submit thru class website http://greenbay.usc.edu/csci577/fall2015/assignments Next Monday 09/07: Labor Day – No Class 47

48. University of Southern California Center for Systems and Software Engineering (c) 2007-2015 USC CSSE48 Individual Responsibilities Homework assignments Selected pre-class and in-class exercises –Drop lowest 1 in-class quiz Acquire Book: USC bookstore, Amazon, B&N,... –Boehm et al., The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software, Addison Wesley, 2014 Contribute to team project –Lead on one artifact; on other, co-lead –Part of Honoring commitment grade (50 points) Individual Critique –90 points, due after Development Commitment packages submitted Effort reports; Review other peoples artifacts Presentation at two project reviews (ARB’s) Academic integrity! 48

49. University of Southern California Center for Systems and Software Engineering To be done before class Elaboration of pre-class exercise; Details and due dates on course schedule Pre-Class Exercise (some classes; relates readings to lecture and to ICSM) Lecture & Discussion (beginning with short review of where we are) In-Class Exercise Homework Lecture Format for In-class Exercises, etc.

50. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE References - I Beck, K., Extreme Programming Explained, Addison Wesley, 1999. Boehm, B., "Some Future Software Engineering Opportunities and Challenges," In Sebastian Nanz (Ed.): The Future of Software Engineering, Springer Berlin Heidelberg, 2011, pp. 1-32.The Future of Software Engineering Boehm, B., Brown, W., Basili, V., and Turner, R., “Spiral Acquisition of Software- Intensive Systems of Systems, CrossTalk, Vol. 17, No. 5, pp. 4-9, 2004. Boehm, B. and Lane J., "21st Century Processes for Acquiring 21st Century Software- Intensive Systems of Systems." CrossTalk: Vol. 19, No. 5, pp.4-9, 2006. Boehm, B., and Lane, J., “Using the ICSM to Integrate System Acquisition, Systems Engineering, and Software Engineering,” CrossTalk, October 2007, pp. 4-9. Boehm, B., and Lane, J., “A Process Decision Table for Integrated Systems and Software Engineering,” Proceedings, CSER 2008, April 2008. Boehm, B. et al., Software Cost Estimation with COCOMO II, Prentice Hall, 2000. Boehm, B. and Lane, J., "Evidence-Based Software Processes," New Modeling Concepts for Today's Software Processes, Springer Lecture Notes in Computer Science, 2010, Volume 6195/2010, pp. 62-73.New Modeling Concepts for Today's Software Processes Boehm, B., Lane, J., Koolmanojwong, S., and Turner, R., “An Evidence-Based SE Data Item Description,” Proceedings, CSER 2013, Elsevier, www.sciencedirect.comwww.sciencedirect.com Boehm, B., Lane, J., Koolmanojwong, S., and Turner, R., The Incremental Commitment Spiral Model: Principles and Practices for Successful Systems and Software, Addison Wesley, 2014. Checkland, P., Systems Thinking, Systems Practice, Wiley, 1980 (2nd ed., 1999). Electronic Industries Alliance (1999); EIA Standard 632: Processes for Engineering a System Highsmith, J., Adaptive Software Development, Dorset House, 2000 Huang, L., Boehm, B., Hu, H., Lv,J., and Qian, C., “Applying Value-Based Software Process: an ERP Example,” Intl. J. Software and informatics, July 2008, pp. 1-15. 50(c) 2007-2015 USC CSSE

51. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE References -II International Standards Organization, Information Technology Software Life Cycle Processes, ISO/IEC 12207, 1995 ISO, Systems Engineering – System Life Cycle Processes, ISO/IEC 15288, 2008. Krygiel, A., Behind the Wizard’s Curtain; CCRP Publication Series, July, 1999, p. 33 Lane, J. and Boehm, B., "System of Systems Cost Estimation: Analysis of Lead System Integrator Engineering Activities", Information Resources Management Journal, Vol. 20, No. 2, pp. 23-32, 2007. Lane, J. and Valerdi, R., “Synthesizing SoS Concepts for Use in Cost Estimation”, Proceedings of IEEE Systems, Man, and Cybernetics Conference, 2005. Madachy, R., Boehm, B., Lane, J., "Assessing Hybrid Incremental Processes for SISOS Development", USC CSSE Technical Report USC-CSSE-2006-623, 2006. Maier, M., “Architecting Principles for Systems-of-Systems”; Systems Engineering, Vol. 1, No. 4 (pp 267-284). Maier, M., “System and Software Architecture Reconciliation,” Systems Engineering 9 (2), 2006, pp. 146-159. Northrop, L., et al., Ultra-Large-Scale Systems: The Software Challenge of the Future, Software Engineering Institute, 2006. Pew, R. W., and Mavor, A. S., Human-System Integration in the System Development Process: A New Look, National Academy Press, 2007. Rechtin, E. Systems Architecting, Prentice Hall, 1991. Schroeder, T., “Integrating Systems and Software Engineering: Observations in Practice,” OSD/USC Integrating Systems and Software Engineering Workshop, http://csse.usc.edu/events/2007/CIIForum/pages/program.html, October 2007. http://csse.usc.edu/events/2007/CIIForum/pages/program.html USC CSSE, ICSM Electronic Process Guide, http://greenbay.usc.edu/IICMSw/index.htm#publish.icm.base- usc/customcategories/icm_welcome_page_D99DA7B2.html http://greenbay.usc.edu/IICMSw/index.htm#publish.icm.base- usc/customcategories/icm_welcome_page_D99DA7B2.html 51(c) 2007-2015 USC CSSE

52. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE List of Acronyms B/LBaselined C4ISRCommand, Control, Computing, Communications, Intelligence, Surveillance, Reconnaissance CDConcept Development CDRCritical Design Review COTSCommercial Off-the-Shelf DCRDevelopment Commitment Review DIDevelopment Increment DoDDepartment of Defense ECRExploration Commitment Review EVMSEarned Value Management System FCRFoundations Commitment Review FEDFeasibility Evidence Description FMEAFailure Modes and Effects Analysis FRPFull-Rate Production GAOGovernment Accountability Office GUIGraphical User Interface 52(c) 2007-2015 USC CSSE

53. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE List of Acronyms (continued) HMIHuman-Machine Interface HSIHuman-System Interface HWHardware ICSMIncremental Commitment Model IOCInitial Operational Capability IRRInception Readiness Review IS&SEIntegrating Systems and Software Engineering LCOLife Cycle Objectives LRIPLow-Rate Initial Production MBASEModel-Based Architecting and Software Engineering NDINon-Developmental Item NRCNational Research Council OCOperational Capability OCROperations Commitment Review OO&DObserve, Orient and Decide OODAObserve, Orient, Decide, Act O&MOperations and Maintenance 53(c) 2007-2015 USC CSSE

54. University of Southern California Center for Systems and Software Engineering Copyright © USC-CSSE List of Acronyms (continued) PDRPreliminary Design Review PMProgram Manager PRPublic Relations PRRProduct Release Review RUPRational Unified Process SoSSystem of Systems SoSESystem of Systems Engineering SSESystems and Software Engineering SWSoftware SwESoftware Engineering SysESystems Engineering Sys EngrSystems Engineer S&SESystems and Software Engineering USD (AT&L)Under Secretary of Defense for Acquisition, Technology, and Logistics VCRValidation Commitment Review V&VVerification and Validation WBSWork Breakdown Structure WMIWarfighter-Machine Interface 54(c) 2007-2015 USC CSSE