Product Line Engineering (PLE)

Transcription

1 Advances in Product Line Engineering for Aerospace & Defense: Featuring Lockheed Martin Susan Gregg, Principal Engineer, Lockheed Martin Charles Krueger, CEO, BigLever Software IBM Systems and Software Engineering Symposium Philadelphia, PA. September 10, 2013 Product Line Engineering (PLE) Definition: The disciplined engineering of a portfolio of related products using a common set of shared assets and a common means of production. Full name: Systems and software product line engineering 2 1

2 Product Line Engineering (PLE) The systems are built and maintained in a way that - respects the variations in capability and function that they each need to provide to their respective users - takes maximum advantage of the commonality they share. 3 An Efficient Means of Production for Systems and Software Product Lines 4 2

3 Shared assets are like the factory s supply chain. 5 Features describe capabilities that vary among products

4 Assets are configured according to the feature profiles of the products you want build Features come in. A product comes out. Assets are configured. Just like a factory. 8 4

5 The Challenge of Product Line Engineering: Harnessing Complexity Processes, tools and techniques Processes, tools and techniques cannot overcome the cannot overcome the exponential complexity. exponential complexity A A new approach is is required... O(N 2 ) Engineering Complexity! Time! 9 The Gears PLE Lifecycle Framework Shared PLE Assets 10 5

6 Does PLE work in Aerospace and Defense? Conventional wisdom says: - Programs can t spend money outside their own silos - Program managers don t invest in the future - Individual systems have highly demanding requirements -- building superset assets is infeasible 11 Does PLE work in Aerospace and Defense? Conventional wisdom says: - Programs can t spend money outside their own silos And yet... - AEGIS transitioned from the Navy to the Coast Guard That is, the Coast Guard invested in the Navy s AEGIS program 12 6

7 Does PLE work in Aerospace and Defense? Conventional wisdom says: - Program managers don t invest in the future And yet... The Navy has encouraged the AEGIS product line approach to more quickly field capability and minimize cost and schedule for delivery of updates. 13 Does PLE work in Aerospace and Defense? Conventional wisdom says: - Individual systems have highly demanding requirements -- building superset assets is infeasible And yet... - Systems don t get any more demanding than this: The Aegis destroyer USS Hopper (DDG 70) launches a missile to intercept a short-range ballistic missile. 14 7

8 Outline Overview of Product Line Engineering Lockheed Martin and Aegis Applying PLE to Aegis Results Integrated weapons system for 100 ships With Gears... Entire family managed with a single set of requirements and a single set of source code. US Navy Aegis Cruisers & Destroyers US Navy Littoral Combat Ships US Coast Guard Nat l Security Cutter Aegis Ships for International Navies 16 8

9 9/11/13 Design Cornerstones Continuous Availability Surveillance Coverage Reaction Time Firepower Environmental Resistance Aegis The Shield of the Fleet ASCM High Diver BMD Shoot the Archer CVN Land Launch ASCM ASCM Sea Skim and Pop-up DDG Self Defense Area Air Defense Long Range Air Defense And BMD Aegis Combat Systems Architecture Radar System AN/SPY-1 Command and Decision System Aegis Display System Vertical Launching System Mark 41 Fire Control System Mark 99 Weapon Control System Standard Missile-2 SM-3 VLA TLAM ESSM Aegis Combat Training System Mark 50 Operational Readiness Test System 9

10 Aegis Computing Architecture Evolution Implementing Open Architecture Infrastructure: Common Services and APIs Flexibility to Support Forward-Fit and Back-Fit Track Mgmt Display Command & Control Sensor Mgmt Infrastructure Services Weapon Mgmt Vehicle Control Componentized Objective Architecture: Common Reusable Components Platform Specific Components Data Model Extensible to the Future Common Computing Environment: Standards-based Interfaces to network Commercial Mainstream Products and Technologies Middleware Operating System Hardware Decouple Hardware (H/W) from Software (S/W) Open Architecture provides ability to layer in capability and supports variation 10

11 Outline Overview of Product Line Engineering Lockheed Martin and Aegis Applying PLE to Aegis Results 2010 Common Product Line (CPL) Strategy Hardware Upgrade TI 12 Baseline 9 A,B,C,D.E 2012 DDG CG Hardware Upgrade TI 16 Future ACB 2016 DDG Hardware Upgrade TI 20 Future ACB 2020 DDG DDG One Common Product Line Includes all Baseline 9 Products Con7nuous computer program builds every four months Coordinated, planned and configura7on controlled for all stakeholders Defects fixed once vice mul7ple 7mes One Common Source Library Phased Capability and Con9nuous So:ware Fixes Bld 6 Bld 7 Bld 8 Baseline 9 SoSware Builds 6, 7, 8, 9, 10, Baseline 9 A,C,D,E Future ACB Capabili7es / LCS 1-5 Future Aegis BMD 5.0 Upgrades Future Interna7onal Programs CPL Establishes a Continuous Sustainment Model 11

12 CPL Phases of Design and Implementation Design in Requirements for Capabilities and Upgrades Across Programs Implement Requirements in CPL Software Architecture Using Capability Based Variation Techniques Build Capability In or Out Programs Will Identify How to Partition Testing of Requirements Which are "Core and Non- Core and What is Regression Based Product Team Organization 12

13 Lockheed Martin s Product Line Approach CPL, Gears, DOORS, Requirements, Source code Design for CSL early in the product lifecycle Established Product Architects at the System Product and Component Level Drive Product evolution by maximizing core Implement consistent CSL requirements and software engineering design practices Ensure consistent use of tools, and application of CSL variation techniques, methods and practices. Develop Gears variation points New capability for Littoral Combat Ship and USCG National Security Cutter Implement variation in the requirements and source code Define Product Capabilities A software product development approach is dependent on a combination of Conventional and Product Based configuration management approaches Maximize Core capability as Program Content Increases Vary by Capability Rather than Baseline or Platform Gears variation points demark code features to be removed pre-compile time Tools at Work Gears in Action Product Marketing! Product A! Feature Profiles! System Engineers! Require- ments! GEARS Variation Points Provide for Encapsulation Of Product Unique Developers! Differences Simplicity of a Single System! GEARS Feature Profiles defines the Product Configuration Source Code! DOORS Clearcase Gears Product! Configurator! Product Specific! Instances! Require- ments! Source Code! Require- ments!... Source Code! Require- ments!... Source Code! Common Reusable Core Assets! Features/Profiles Are Under CM Control BL9A-E LCS-3 USCG NSC 13

14 Software Variation Toolbox of Techniques Layered Open Architecture Provides the Foundation for Variation CPL Product Based Test Approach Aegis System Element Product Line Product Configuration Baseline Configuration SPY C2 SPY ADS C2 Baseline 9 A CG ADS WCS SPY ADS C2 WCS Core Non-Core WCS ADS C2 LCS-3 SPY ADS C2 Baseline 9 C DDG Product Core and Non- Core WCS SPY ADS C2 WCS SPY ADS C2 WCS Baseline 9 D DDG Baseline 9 E Aegis Ashore Test levels 1and 2 Test level 3 Test level 4-5 Product Line Architecture and Variation Supports CPL Configurations 14

15 Outline Overview of Product Line Engineering Lockheed Martin and Aegis Applying PLE to Aegis Results Results Lockheed Martin Product Line Development Benefits summary Past Aegis Baselines were developed, tested and certified as separate and distinct Baseline development efforts Baseline 9 Common Product Line is the Aegis Modernization Baseline foundation for Cruisers, Destroyers, Land Based BMD, LCS, USCG National Security Cutter, International - Navy planning multiple variants using Baseline 9 as the underlying Computer Program foundation - Maintain, update and add new requirements to a Single Doors database using Gears variation features for all stakeholders eliminates SC Requirement Capture efforts for all branched programs - CSL-based development approach will implement new capabilities and continuous computer program defect corrections - Implement new capability in CSL software using Capability Based Variation Techniques - Reduces the effort to implement capability and CPCR solutions - Risk reduction Benefits of sharing: e.g., early defect discovery and sharing the fixes - Opportunistic addition of new members US Coast Guard and International opportunities Features not for export can be identified and varied - System test will partition Testing of Functionality based on analysis of functional areas that have been changed, enabling targeted regression and delta Cert testing 15

16 Second Generation Product Line Engineering in Aerospace and Defense It s here. It s working. It s growing. It s providing significant, measurable benefits. Gears and IBM tools such as DOORS, Rhapsody, and ClearCase are proving successful working together in A&D. More success stories are on the way