Lockheed Martin Aeronautics Company Superior Products Through Innovation Validation & Verification of Intelligent and Adaptive Control Systems (VVIACS)

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

Chapter 2 The Software Process
May 17, Capabilities Description of a Rapid Prototyping Capability for Earth-Sun System Sciences RPC Project Team Mississippi State University.
Software Quality Engineering Roadmap
Lockheed Martin Aeronautics Company V&V Technologies Identified by VVIACS  Near-Term V&V Evolution: SW Model-based design now being implemented  Auto-Code.
DoD Systems and Software Engineering A Strategy for Enhanced Systems Engineering Kristen Baldwin Acting Director, Systems and Software Engineering Office.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
What are MRLs ? Alfred W. Clark Dawnbreaker, Inc.
Enterprise Architecture
Developing Enterprise Architecture
Chapter : Software Process
Process: A Generic View
Formal Methods 1. Software Engineering and Formal Methods  Every software engineering methodology is based on a recommended development process  proceeding.
INTEGRATING EHS INTO NEW PRODUCT DEVELOPMENT
SAS_08_AADL_Exec_Gluch MAC-T IVV Model-Based Software Assurance with the SAE Architecture Analysis & Design Language (AADL) California Institute.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
4.x Performance Technology drivers – Exascale systems will consist of complex configurations with a huge number of potentially heterogeneous components.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Chapter 2 The process Process, Methods, and Tools
Independent Verification and Validation (IV&V) Techniques for Object Oriented Software Systems SAS meeting July 2003.
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Software Processes lecture 8. Topics covered Software process models Process iteration Process activities The Rational Unified Process Computer-aided.
Requirements and Operations Team Industry Day Briefing 17 January, 2002.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Software Project Management Lecture # 7. Outline Project Scheduling.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Page 1 Designing for Health; A Methodology for Integrated Diagnostics/Prognostics Raymond Beshears Raytheon 2501 W. University McKinney, TX
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
Slide 1V&V 10/2002 Software Quality Assurance Dr. Linda H. Rosenberg Assistant Director For Information Sciences Goddard Space Flight Center, NASA
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Tools and Technology Development Hardware-in-the-Loop Dennis Culley NASA Glenn Research Center Collaboration Forum Ohio Aerospace Institute August 25,
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Polymorphous Computing Architectures Run-time Environment And Design Application for Polymorphous Technology Verification & Validation (READAPT V&V) Lockheed.
Software Engineering - I
Overview of Portfolio Process Maturity
Chapter 3 Project Management Chapter 3 Project Management Organising, planning and scheduling software projects.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Process: A Generic View
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 Improving the Risk Management Capability of the Reliability and Maintainability Program An introduction to the philosophy behind the AIAA S-102 Performance-Based.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
1 V&V Needs for NextGen of 2025 and Beyond A JPDO Perspective Maureen Keegan JPDO Integration Manager October 13, 2010.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
Advanced Software Engineering Lecture 4: Process & Project Metrics.
SOFTWARE PROCESS IMPROVEMENT
Software Engineering (CSI 321) Software Process: A Generic View 1.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Toward A Framework for Implementing Systems Engineering Development for Complex Systems Karl L. Brunson, GWU Thomas A. Mazzuchi, D.Sc., GWU Shahram Sarhani,
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Slide 3.1 © The McGraw-Hill Companies, 2002 SOFTWARE LIFE-CYCLE MODELS.
Identify the Risk of Not Doing BA
Software Engineering (CSI 321)
Engineering Autonomy Mr. Robert Gold Director, Engineering Enterprise
Presentation transcript:

Lockheed Martin Aeronautics Company Superior Products Through Innovation Validation & Verification of Intelligent and Adaptive Control Systems (VVIACS) Jim Buffington

Lockheed Martin Aeronautics Company 2 Outline Introduction Motivation Approach Assessment Development Evaluation Summary

Lockheed Martin Aeronautics Company 3 Team Vince Crum – AFRL - Government PM Jim Buffington – LM Aero - Contractor PM LM Aero – Greg Tallant, Peter Stanfill LM M&FC - Clinton Plaisted, Barry Frazier, Rich Hull, Guy Rowlands LM SS - Prasanta Bose Carnegie Mellon University - Bruce Krogh General Electric Global Research - Tim Johnson, Hunt Sutherland Scientific Systems Company, Inc - Ravi Prasanth, Sanjeev Seereeram

Lockheed Martin Aeronautics Company 4 Scope Safety-Critical Flight Systems Military Certification Advanced Controls System Development All Development Phases Process, Tools, and Methods Verification & Validation

Lockheed Martin Aeronautics Company 5 Emerging Software Size and Complexity Projected Exponential Increase in SW Size and Complexity Inter-System Communication & Dependencies F-16 IDF YF-22 F-22 JSF CDA UAV - Projected F-35 – Est Block 60 Increasing system integration requirements and Complexities  Advanced system attributes (on-board intelligence and adaptive control laws) will be required to accommodate emerging functional requirements.  This will increase the size and complexity of control systems beyond the capability of current V&V practices.

Lockheed Martin Aeronautics Company 6 Emerging System Costs Size and Complexity Increase Costs  SW size and system complexity lead to growth system development and certification costs  Test automation insufficient for emerging control systems

Lockheed Martin Aeronautics Company 7 Compressed Development Schedules Emerging Program Requirements Increase Risk Customers requiring 12 to 36 month development schedules Baseline is 48 months to first flight

Lockheed Martin Aeronautics Company 8 Purpose GOAL: Enable affordable development of future safety-critical flight systems with prescribed levels of safety and reliability. OBJECTIVE: Study, develop, and demonstrate effective V&V technologies for advanced safety-critical control system flight certification. APPROACH: Use extensive experience-base and diverse team to develop innovative concepts Evaluate concepts in a realistic framework to maximize transition success Classify emerging safety-critical control systems according to fundamental attributes Develop and demonstrate preliminary V&V strategies that focus on critical flight certification schedule and cost points Identify high-payoff V&V process, tool, and method technologies for further development

Lockheed Martin Aeronautics Company 9 Tasks  Task 1  Emerging Control System Study  Task 2  Control Characteristics and V&V Needs Study  Task 3  Innovative Flight Certification Strategies Development  Task 4  Proof of Concept  Task 5  Technology Development Planning and Reporting 1. Assessment 2. Development 3. Evaluation

Lockheed Martin Aeronautics Company 10  Emerging Control Systems Study  Develop control system project database  Down select to subset of projects for additional analysis  Control Characteristics and V&V Needs Study  Analysis to define emerging fundamental properties  Identification of V&V drivers  System Development Model  System Development impact assessment Tasks 1 & 2 – Assessment V&V NEEDS

Lockheed Martin Aeronautics Company 11 Task 1 – Emerging Control Systems DESCRIPTION Integrated Management, Adaptive Control Intelligent Autonomy Polymorphous Computing Architectures Autonomous Control Bio-inspired Multi-vehicle Control Adaptive Failure Management Optimal Trajectory Generation Intelligent Failure Management Model-based Health Management Distributed Multi-vehicle Control ECS PROJECT AIMSAFE / RESTORE ICARUS PCA LOCAAS Swarm Intelligence XACT Software Enabled Control Autonomous Propulsion System Tech Intelligent Engine PHM Distributed Space Systems Characterized 10 Emerging Control System (ECS) projects 6 ECS projects used to form the Single-Vehicle ECS (AIMSAFE/RESTORE, PCA, LOCAAS, XACT, Autonomous Propulsion System, and Intelligent Engine PHM) 5 ECS projects used to form the Multi-Vehicle ECS (ICARUS, PCA, Swarm Intelligence, Software Enabled Control, and Distributed Space Systems)

Lockheed Martin Aeronautics Company 12 Task 2 - Emerging Systems Analysis Extensible Analysis Framework based on Fundamental Properties Identified 100+ fundamental properties (FPs) for the ECS projects Categorized FPs in 5 Views: Requirements, System, Algorithm, SW, HW Identified 28 FPs as Emerging Fundamental Properties (EFPs) Identified 4 primary V&V Drivers Difficulty, Complexity, Unfamiliarity, External factors System development model Based on LM Process Multiple levels Contains over 800 tasks MS Project / Excel

Lockheed Martin Aeronautics Company 13 Task 2 - Impact Analysis Results Significant Cost/Schedule Increase Projected Due to Complexity Single-Vehicle ECS Increases Development Costs ~ 50%, V&V Costs ~ 100%, and Critical Path Length ~ 50% Multiple-Vehicle ECS Increases Development Costs ~ 100%, V&V Costs ~ 150%, and Critical Path Length ~ 125% Software: Single-Vehicle 100% Increase and Multiple-Vehicle 200% Increase in V&V Costs Test: Single-Vehicle 150% Increase and Multiple-Vehicle 250% Increase in V&V Costs

Lockheed Martin Aeronautics Company 14 Task 2 - Pareto Analysis  Single-Vehicle ECS V&V Cost Impact  80%: TEST, SW  90%: 80% + TTD  TEST largest component (41%) followed by SW (28%)  Single-Vehicle ECS V&V Duration Impact  80%: SW, TEST  90%: 80% + TTD  SW dominates at 53% Pareto Analysis Identifies the Critical Functional Disciplines

Lockheed Martin Aeronautics Company 15 Task 3 – Flight Certification Strategies Development  Requirements Development  Requirements/Guidelines  V&V Drivers Mapping  Flight Certification Refinement  Current Process Development  Evolution of Process Development for V&V  V&V Methods Development  Identify Current V&V Methods  Recommend Approaches V&V STRATEGY EVOLUTIONS

Lockheed Martin Aeronautics Company 16 Near-Term (1-3 yrs) Evolution: System Model-based design now being implemented  Auto-Code  Auto-Test  Rapid Prototyping  System Model-Based  Automated Verification Management  Simulation-Based design Mid-Term (4-6 yrs) Evolution: Formal Foundations in advanced development Formal Requirements Specs Requirements and Traceability Analysis Formal Methods Computer-Aided System Engineering Far-Term (7-9 yrs) Evolution: V&V Awareness throughout  still in research Run-Time V&V Rigorous Analysis for Test Reduction Requirements & Design Abstraction Probabilistic/Statistical Test Testing Metrics Task 3 – Strategy Evolutions

Lockheed Martin Aeronautics Company 17 Task 4 – Advanced Technology Impact to System Development  System Development Cost Reductions:  Baseline: 25%  Single-Vehicle: 33%  Multi-Vehicle: 35%  System Development Critical Path Reductions:  Baseline: 12%  Single-Vehicle: 29%  Multi-Vehicle: 30%

Lockheed Martin Aeronautics Company 18 Task 5 – Technology Development Planning and Reporting  Risk Waterfall Planning  ROM Development Cost  EFP Coverage Analysis + Task 4 System Development Impact  Net Benefit  Priority of V&V technologies was established on the basis of a cost-benefit analysis performed on each technology  Cost-Benefit Ratio (CBR) = ROM Development Cost/Net Benefit  All near-term technologies except Automated Verification Management were eliminated from the CBR analysis because these technologies are relatively mature (moderate technical risk) and significant industry investment in these technologies is ongoing and is expected to continue.

Lockheed Martin Aeronautics Company 19 Task 5 – Technology Cost / Benefit  ROM Cost – Risk Waterfall Analysis  Net Benefit is defined as the product of the technology’s EFP Coverage Benefit and the System Development Benefit  B NET = B EFP B SD  EFP Coverage Benefit is a measure of the technology’s applicability across the set of EFPs (large B EFP implies good coverage)  System Development Benefit is a measure of the technology’s impact on system development cost and schedule

Lockheed Martin Aeronautics Company 20 Task 5 – Final Prioritized Technologies Based on Cost-Benefit Analysis 1.Automated Verification Management 2.Formal Requirements Specifications 3.Requirements and Traceability Analysis 4.Formal Methods 5.Probabilistic / Statistical Test 6.Requirements and Design Abstraction 7.Run-Time V&V 8.Testing Metrics 9.Rigorous Analysis for Test Reduction 10.Computer-Aided System Engineering Increasing Cost-Benefit Ratio Near-Term (1-3 years) Technology Mid-Term (4-6 years) Technology Far-Term (7-9 years) Technology EFP weighting: W EFP = 1 (all equal) ECS weighting: 10% Baseline 50% Single-vehicle 40% Multi-vehicle

Lockheed Martin Aeronautics Company 21 Summary  Developed emerging control system (ECS) database and populated with an extensive set of past, present, and future ECS projects.  Assessed impact of future systems on current development process and identified “long-pole” functional disciplines with highest adverse impact (i.e., SW, TEST, TTD).  Identified 15 key V&V technologies to address system development impact and characterized in terms of near- (1-3 years), mid- (4-6 years), and far-term (7-9 years) strategy evolutions.  Demonstrated effectiveness of each strategy evolution using the system development model and the system development impact assessment tool (i.e., cumulative 25% reduction in V&V cost and 12% reduction in V&V effort for all strategies).  Developed technology maturation plans for each V&V technology identified, and prioritized the technologies by performing a cost-benefit analysis.