University of Southern California Center for Systems and Software Engineering ICSM Stage II: Phases and Continuing Project Example Anandi Hira CS 510, Fall 2014

University of Southern California Center for Systems and Software Engineering Outline Overview of ICSM Stage I Stage II Detailed Descriptions –Development Phase –Production Phase –System Operations Phase Example Project Usage –Continuation of MedFRS example –(Medical First Responder System) 2Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Stage II You can’t just ask the customers what they want and then try to give that to them. By the time you get it built, they’ll want something new. - Steve Jobs Stage II: Incremental development –Development Phase: Procurement, iterative detailed design and development, integration, and test of current- increment components –Production and Operations Phase: System “units” produced, integrated, and put into operations 3Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of ICSM Stage I Stage II Detailed Descriptions –Development Phase –Production Phase –System Operations Phase Example Project Usage –Continuation of MedFRS example –(Medical First Responder System) 4Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering 5Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Ready to Release? 6Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Potential Pitfalls Inadequate budget/schedule Neglecting SCSs Neglecting to take time to fix architecture/foundation s problem Inadequate risk identification Starting development by easiest capabilities Inadequate development monitoring, rescope Inadequate testing Inadequate change monitoring, response Unvalidated, unprioritized capabilities Inadequate Production and Operation plans 7Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Major Risks Optimistic plans, schedules, budgets Technologies not mature COTS do not meet expectations Reuse items not “reusable” Critical engineering staff shortfalls Weak critical links in the vendor support/supply chains Weak manufacturing process or quality controls 8Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of ICSM Stage I Stage II Detailed Descriptions –Development Phase –Production Phase –System Operations Phase Example Project Usage –Continuation of MedFRS example –(Medical First Responder System) 9Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering 10Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Potential Pitfalls and Major Risks  Weak manufacturing process and quality controls  Inadequate source code control or configuration management  Inadequate configuration management of system software and hardware components  Inadequate phase budgets and schedules  Neglecting SCSs  Optimistic plans, schedule  System parts/components late for assembly  Breakdown of manufacturing equip.  Inadequate manufacturing plans or procedures  Component quality/defective parts  Assembly quality  Inadequate transition plans 11Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of ICSM Stage I Stage II Detailed Descriptions –Development Phase –Production Phase –System Operations Phase Example Project Usage –Continuation of MedFRS example –(Medical First Responder System) 12Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering 13Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Potential Pitfalls and Major Risks  Inadequate transition plans and preparations for release  Inadequate budget/schedule for sustainment and user support  Neglecting system stakeholders (users, esp)  Inadequate support and change management  Little/slow response to problems  Inadequate logistics support and spares provisioning  Inadequate plans or budget to deploy upgrades  Inadequate attention to:  How Users use system  User suggestions and complaints  Product recalls  Changing external systems and services 14Fall 2014Copyright (C) USC-CSSE

University of Southern California Center for Systems and Software Engineering Outline Overview of ICSM Stage I Stage II Detailed Descriptions –Development Phase –Production Phase –System Operations Phase Example Project Usage –Continuation of MedFRS example –(Medical First Responder System) 15Fall 2014Copyright (C) USC-CSSE