Battle of the Bulge: The Software Challenge of the Mission System Integrator

1. Battle of the Bulge: The Software Challenge of the Mission System Integrator Dennis Frailey, Raytheon, Network Centric Systems, Ground Sensor Integrator Program DJFrailey@raytheon.com (972-344-8366)

2. Program Tiers - What is a Mission System Integrator? Mission System Integrator >$300M LSI >$100M MSI >$100M System Complexity $50M-$100M Subsystem $1M-$50M Component Tier 5 Tier 4 Tier 3 Tier 2 Tier 1 Value ($)

3. Our Customer (Lead System Integrator) Our Internal SW teams GSI (Mission System Integrator) Ultimate Customer (US Army) GSDs GSDs GSDs GSDs (Our Suppliers) Communication Flow

4. Sensors, Suites and Vehicles Sensors (what our suppliers do) Suites (what we do) Vehicles (our customers) EO 2 S1 V1 Dev1 V2 Dev2 V3 Radar 1 S2 V4 Dev3 Dev4 EO 3 S3 V5 S4 V6 EO 1 S5 V7 Detector S6 V8 S7 V9 SPEC Sensors

5. Delivery to Vehicles GSI Software Team (Integration into Suites) SW Oversight and Management Wrapper Lab Tools Wrapper SW Development Simulator Simulator Simulator Simulators Sensor Suite Control Emulator Emulator Emulator Special System Models Sensor Sensor Sensor … I&T IPT Make/Buy GSD #2 V&E IPT GSD #n GSD #1 Software Development and Management Non-deliverable SW The GSI produces or acquires other software needed for integration. Each GSD produces multiple products containing software.

6. ExpandedRisk/Opportunity Management +

7. ExpandedCustomer Relations +

8. ExpandedChange Management +

9. ExpandedProcess Requirements +

10. 6 sigma Process for Improvement CMMI How we do business Integrated Product Development System Standards and Best Practices Why This Isn't Enough Gaps: Our processes assume one program, not multiple tiers of programs

11. Gap Analysis Process Prioritized List of New Artifacts Needed for an MSI Program The Bulge MSI Requirements Organizational Processes • An MSI would need many new artifacts in addition to the organizational processes already in place • Work Instructions, Tools, Procedures • Well established estimating process use to determine the development costs MSI Process Improvement Project

12. Some Examples of New Work Instructions Needed • How to Review and Evaluate Supplier Bids, Plans, Deliverable Documents and Software • How to Control Changes in a Multi-level Hierarchy • How to Manage Software Suppliers • How to Establish Architectural and Design Standards for Multiple Suppliers that Enable Effective Integration but Allow Each Supplier to Use its Own Processes • How to Define Metrics that Each Supplier can Provide within their existing process and can be Consolidated into Meaningful Assessments of Supplier and Program Health • How to Assess “ilities” (safety, supportability, maintainability, etc.) at an overall system level when each supplier has its own systems for defining these things. • How to gain maximum benefit from Reuse when the existing reusable assets are highly diverse

13. Example: Change ManagementConsider the Possibilities … Sensors (what our suppliers do) Suites (what we do) Vehicles (our customers) EO 2 S1 V1 Dev1 V2 Dev2 V3 Radar 1 S2 V4 Dev3 Dev4 EO 3 S3 V5 S4 V6 EO 1 S5 V7 Detector S6 V8 S7 V9 SPEC Sensors

14. CMMI Experience Gave Us Leverage • Our CMMI and Process foundation gave us many tools to approach this challenge • They provided a baseline approach for metrics, work instruction development and review, configuration control, estimation and improvement • Thus we were able to focus on solving the problem rather than defining the approach Estimation Process Peer Review Process and Tools for Work Instructions Continuous Improvement Ingrained in the Organization Metrics Baseline Configuration Control Infrastructure Metrics Collection, Analysis And Storage Templates for Work Instructions

15. Program Needs Program Needs Program Needs New Org Artifacts New Org Artifacts New Org Artifacts New Program Artifacts New Program Artifacts New Program Artifacts Year 1 Year 2 Year 3 Year 4 Multi-Year Approach • We employed a phased approach to tackling this problem • First identify and prioritize emerging program needs • Then develop new, organization-level artifacts • Finally, tailor those to program needs • Artifacts arrive “just in time” to meet program needs

16. Future • Our organizational processes are enriched as we flow MSI Improvement Project artifacts back into the organizational process. Enhanced Integrated Product Development System Organizational Process Enhancements MSI Process Improvement Project

17. Questions

18. Biography Dennis J. Frailey Dennis J Frailey is a Principle Fellow assigned to the Future Combat Systems Ground Sensor Integrator team in Plano, TX. He is currently responsible for many roles on the program such as development and maintenance of the software development plan, chair of the software configuration control board, and sundry duties associated with selection and evaluation of software suppliers. Dr. Frailey, who earned a PhD in Computer Science from Purdue in 1971, has been with Raytheon (and previously with Texas Instruments) for 32 years. His career includes positions ranging from college professor to developer of real-time operating systems, scientific applications, and user interfaces to speechwriter for corporate executives to software process improvement specialist. He has been head of an SEPG and was the software lead on numerous proposals. Dennis is an ACM Fellow and Distinguished Lecturer; an IEEE Senior Member and Distinguished Visitor; and an Engineering Accreditation Evaluator. He served as vice president of ACM, conference chair and program chair for over two dozen major computing conferences, and is the author of over 100 published technical papers. In addition, he serves as an adjunct professor at Southern Methodist University, UCLA and the University of Texas at Austin. Dennis has spoken at many conferences, including keynote addresses at the SIGADA national conference, the Conference on Software Engineering Education, the Euromicro Software Engineering Workshop, and several regional conferences. Dennis can be reached at: 972-344-8366 or DJFrailey@Raytheon.com