1. Avionics Software Challenges Briefing to the DoD Software Engineering Science & Technology Summit Los Angeles, CA 7 August, 2001 Don C. Winter Manager – Research & Development Programs Boeing Phantom Works don.c.winter@boeing.com

2. Avionics Software Situation Accounts for a growing percentage of system complexity and cost Increasing instances of cost/schedule overruns More errors slipping through to fielded systems Software has become the pacing element in the development and modernization of military avionics systems The Challenge: Provide affordable, maintainable, high- integrity software within budget and delivery constraints

3. Problem Statement Technology trends in weapon systems are driving exponential growth in software complexity –Autonomous systems, adaptive systems, fault-tolerant systems… Traditional approaches and processes do not scale well –Program-specific architectures, languages, tools –Unaligned with commercial practices High turnover in defense software workforce –Ad-hoc knowledge management for legacy systems –Constantly climbing the learning curve Current technology, practices and culture of the industry cannot cope with the emerging environment

4. Where to Look First - the Commercial Sector Product Lifetimes are getting Shorter 0 5 10 15 20 25 30 35 40 45 1985198719891991199319951997 Production (MILLIONS) Pentium 286 386 486 ArchitectureProduct LifePartsSystem 0 5 10 15 20 25 30 Years Military Commercial Trend Product Cycle - Military Vs Commercial COTS market appears to be getting the job done, but: - System turnover rates are much higher - Systems are fielded with bugs - Deadline-driven culture vs. “getting it exactly right” culture - Systems are not as capacity-limited Inherently greater leverage of automation and re-use

5. Where are the Technology Voids? COTS supports the code/debug/unit test stages of development well but many voids exist: “Front end” of process –Model-based tools for requirements/design capture –Automated configuration and integration of components “Back end” of process –Simulation-based testing Support for hard real-time embedded systems is limited –Quality-of-service requirements expression/guarantees Hardware/OS/application software isolation –Application software must remain stable in the face of iterating run-time platforms –Advanced middleware technologies must be tailored for real-time, high-confidence systems Legacy system constraints –Infusing new technology into resource-limited, “closed” systems

6. Cultural Challenges DoD acquisition culture presents impediments as well –“Silo” approach to planning/funding system modernization –“Wasn’t invented here” mindset in platform programs –Inability to trade front-end investment for life-cycle returns, even when business case is compelling –Support structure based on single fielded configuration –T&E community resistance to tailored re-qualification Synergy with COTS industry will always be limited without cultural transformation To achieve technology transition, the risk must be “bought down” to a level the platform developers can tolerate

7. Summary Boeing has a major, ongoing commitment to a new product line strategy for avionics software –Founded in COTS, open systems architecture –Over $100M IR&D invested to date –Early returns show that reductions in software development cost and cycle time of >60% are achievable Government/industry partnership is needed to realize the full potential –Complementary sustaining investments in product and process technologies must be made The pace of commercial IT advancement never slows –Acquisition reform must continue to enable transition to DoD systems