Lean Principles Applied to Military Software

1. Lean Principles Applied to Military Software Andy Lay F-16 Deputy Chief Engineer 11 March 2002

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

3. Current Process: Too Long 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. ACC Prime AFMC

4. 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 The Platform Problem ECIU GAC MMC M-Series S/W F-16 Block 50 Avionics Architecture $$$ Federated T-Series S/W Our Objective Is To Remove This Obstacle

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

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

7. The Software Problem Focus on Re-work Avoidance & A Lean Software Development Process • Flight program changes are too costly both intime and money • Software capabilities are not easily “portable” from one type-version to another • Our avionics systems are not “plug ‘n’ play”

8. Solution: Apply Lean Principles • Rapid Development Process • New way to establish requirements • Product Development Streaming • New way develop and deliver the product • Modular Capability Development • New way to build the product

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

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

11. 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: • All of the artifacts for the capability have been completed • 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

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

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

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

15. Summary • 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

16. Lean Principles Applied to Military Software Andy Lay F-16 Deputy Chief Engineer 11 March 2002