Copyright © 2002 by Lockheed Martin Corporation All Rights Reserved This material may be reproduced by or for the U. S. Government pursuant to the copyright license under the clause at Defense/Federal Acquisition Regulations (DFARS) (October 1988 ). Lean Principles Applied to Military Software Andy Lay F-16 Deputy Chief Engineer 11 March 2002 Andy Lay F-16 Deputy Chief Engineer 11 March 2002

© 2002 Lockheed Martin Corporation The Bottom Line Software Costs Too Much, Takes Too Long and Doesn’t Always Do What They Want it to. to new software on the stick” $ “It takes 5-9 years from money on the table

© 2002 Lockheed Martin Corporation Current Process: Too Long ACC Prime AFMC Requirement Evaluation & Prioritization System Requirement Definition Software Design, Code & Test System DT&E System OT&E System Fielding 5 to 9 Years Process iterations cost time, extend schedules and complicate development which may compromise quality.

© 2002 Lockheed Martin Corporation The Platform Problem  To date, choice has been one path or the other  Once on a path, high cost to migrate  Both paths are headed to a technological dead-end F-16 Block 50 Avionics Architecture M-Series S/W Federated T-Series S/WGAC MMC ECIU $$$ Our Objective Is To Remove This Obstacle

© 2002 Lockheed Martin Corporation Platform Solution  Several Commercial Technologies Are Now Mature And Can Be Leveraged u PowerPC è Processing to Burn u High Speed Networking è Fast Enough to Act In Lieu Of MMC Back-plane u Software Design è Auto Code Generators Allow Repeatable Process to Target OOD S/W to Multiple Computers F-16 Block 50 Avionics Architecture M-Series S/W Federated T-Series S/WGAC MMC ECIU COTS H/W Insertion Common Modular S/W Bottom Line... H/W & S/W Are Independent

© 2002 Lockheed Martin Corporation COTS H/W Infrastructure GAC MMC ECIU COTS Technology Integrate COTS Technology into Existing Volumes Maintain Commonality of Modules Between LRUs Change Support Infrastructure To Commercial Refresh Strategy RESULTS: Greater Performance Greater Performance More Capacity More Capacity Ability to Put Latest Ability to Put Latest Capability in Legacy A/C Capability in Legacy A/C Demonstration Flight at LM Aero - Fort Worth COTS-Based Mission Processor Demo Completed: July 2000

© 2002 Lockheed Martin Corporation The Software Problem Focus on Re-work Avoidance & A Lean Software Development Process  Flight program changes are too costly both in time and money  Software capabilities are not easily “portable” from one type-version to another  Our avionics systems are not “plug ‘n’ play”

© 2002 Lockheed Martin Corporation Solution: Apply Lean Principles  Rapid Development Process u New way to establish requirements  Product Development Streaming u New way develop and deliver the product  Modular Capability Development u New way to build the product

© 2002 Lockheed Martin Corporation Capability Selection Based on Completed Development Customer Pull Rapid Development Process On-going Requirements Evaluation & Prioritization by Customer Continuous System Requirements Definition ACC Prime AFMC Streaming Software Design, Code & Test System DT&E System OT&E System Fielding Release to Field Determined by Length of Customer Evaluation

© 2002 Lockheed Martin Corporation Re-work Avoidance Makes It Better  Don’t design before it’s time u Wait for all design elements to mature before proceeding u Incrementally design the capability  Rapid design process provides all the delivery products u Eliminates re-work of in-process deliverables  Develop software to exploit the hardware rather than conserve it u Software re-work to fit in allocated memory and throughput is eliminated

© 2002 Lockheed Martin Corporation Software Capability Database  A capability database is a repository of all the software and documentation that were developed in order to make the capabilities usable on an F-16  Functions are designated as capabilities by LM Aero  A capability is added to the database when: u All of the artifacts for the capability have been completed u The capability has been adequately tested with the baseline software in target hardware  A “customer pull” includes the desired capabilities, the baseline version necessary to support the desired capabilities, the OS, and middleware for the target hardware on the target aircraft configuration

© 2002 Lockheed Martin Corporation Preprocessor Build Process Version 1 OFP Preprocess for Version 1 Ada Preprocessor Compiler / Linker Compilation & Link Build Process Version 2 OFP Version 1 = Baseline + Capability A Version 2 = Baseline + Capability B Preprocess for Version 2 Compilation & Link Baseline Capability Source Code Software Development Library Capability A Source Code Capability B Source Code Ada Source Code Files... PCMS Tgt OS and Middleware

© 2002 Lockheed Martin Corporation Auto Code Build Process Baseline Capability Capability A Capability B Version 1 = Baseline + Capability A Version 2 = Baseline + Capability B (with Automatic Code Generation) Platform 1 Compiler / Linker Compilation & Link Compilation & Link Compilation & Link Platform 2 Compiler / Linker Auto Code Generation for Version 1 Platform 1 Auto Code Generator Auto Code Generation for Version 2 Platform 2 Auto Code Generator Auto Code Generation for Version 2 Version 1 OFP Version 2 OFP Platform 1 Version 2 OFP Platform 2 Build Process Software Development Library (Database) IOOA OOA Models... Automatic Code Generator Replaces Preprocessor One Analysis Database Reused across Multiple Platforms

© 2002 Lockheed Martin Corporation Software Technology Makes It Cheaper  Modular capability database for portability and reuse u Software capabilities developed by one customer can be offered to all customers  Auto-code to eliminate errors and reduce testing u Configuration managed models and auto-code generator will allow for “good code” to be inserted without regression testing  Predictable pricing u Based on frequency and amount of software needed at customer pull point

© 2002 Lockheed Martin CorporationSummary  The advanced COTS avionics H/W architecture and the modular S/W capability database concept are synergistic  Applying lean concepts to software provides reduction in cost and allows more flexibility in the development cycle  Avionics upgrades can be faster and cheaper, and be better able to meet the needs of the war fighter  Software design database provides common capabilities across multiple platforms

Copyright © 2002 by Lockheed Martin Corporation All Rights Reserved This material may be reproduced by or for the U. S. Government pursuant to the copyright license under the clause at Defense/Federal Acquisition Regulations (DFARS) (October 1988 ). Lean Principles Applied to Military Software Andy Lay F-16 Deputy Chief Engineer 11 March 2002 Andy Lay F-16 Deputy Chief Engineer 11 March 2002