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.

Slides:



Advertisements
Similar presentations
ATML Readiness For Use Phase II. Phase II Readiness For Use The ATML: Phase II will build on the Core phases, adding additional ATML components and features.
Advertisements

Advanced Processing Systems Honeywell Proprietary1 12/04/2003 Honeywell UF HCS & Honeywell DSES Opportunities Presented by Advanced Processing Systems.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Azad Madni Professor Director, SAE Program Viterbi School of Engineering Platform-based Engineering: Rapid, Risk-mitigated Development.
SWE Introduction to Software Engineering
© Copyright Richard W. Selby and Northrop Grumman Corporation. All rights reserved. 0 Systems of Systems Acquisition and Management Critical Success.
Software Engineering CSE470: Systems Engineering 35 Computer System Engineering Computer System Engineering is a problem-solving activity. Itemize desired.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Case Studies Instructor Paulo Alencar.
Page - 1 Rocketdyne Propulsion & Power Role of EASY5 in Integrated Product Development Frank Gombos Boeing Canoga Park, CA.
Enterprise Architecture
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Sage User Network 11 th June 2009 Andrew Credland - Product Development Manager.
Effective Methods for Software and Systems Integration
Security and Privacy Services Cloud computing point of view October 2012.
What is Software Engineering?. Software engineering Multi-person construction of multi-version software (David Parnas) An engineering discipline whose.
CLEANROOM SOFTWARE ENGINEERING.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Wednesday, September 16, 2015 The Challenge for. An SDK for this is the challenge!!! Various type of devices & peripherals DR-DOS, MS-DOS, PALM, PocketPC,
COMP-14: Automating your deployments using ANT Gary S Clink Business Consultant.
General Theme In general work in teams combining architects, compiler developers, performance and tools engineers, and application experts –Note this extends.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Copyright © 2011 EMC Corporation. All Rights Reserved. MODULE – 6 VIRTUALIZED DATA CENTER – DESKTOP AND APPLICATION 1.
SPACE TELESCOPE SCIENCE INSTITUTE Operated for NASA by AURA COS Pipeline Language(s) We plan to develop CALCOS using Python and C Another programming language?
Future Airborne Capability Environment (FACE)
Configuration Management (CM)
Panel Three - Small Businesses: Sustaining and Growing a Market Presence Open Interfaces and Market Penetration Protecting Intellectual Innovation and.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
Paul E. Sollock1 FOUR DECADES OF EVOLUTION TOWARD FLEXIWARE ( From the perspective of an Apollo, Shuttle, ISS and Shuttle Upgrades Veteran) Definitions.
1 Performance Optimization In QTP Execution Over Video Automation Testing Speaker : Krishnesh Sasiyuthaman Nair Date : 10/05/2012.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 3 Identification and Selection of Development Projects.
Software Engineering Spring (C) Vasudeva VarmaClass of 32 CS3600: Software Engineering: Process and Product* *Most of the Content drawn.
Lockheed Martin Aeronautics Company Candidate Collaborative Projects for Net-Centric Application Michael F. Siok, PE Lockheed Martin Aeronautics Company.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
Computing Infrastructure for Large Ecommerce Systems -- based on material written by Jacob Lindeman.
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)
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
XStream: Rapid Generation of Custom Processors for ASIC Designs Binu Mathew * ASIC: Application Specific Integrated Circuit.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
PRJ566 Project Planning & Management Software Architecture.
Confidential Continuous Integration Framework (CIF) 5/18/2004.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
IBM Software Group ® Software Distribution of ClearCase Artifacts with Tivoli Software Eitan Shomrai, IBM Software Group – Rational Yuval Kimel, IBM Software.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Tackling I/O Issues 1 David Race 16 March 2010.
NASA Orion Avionics Architecture Joseph Moholt All Points Logistics © 2015 Lockheed Martin Corporation. All Rights Reserved.
March 2004 At A Glance The AutoFDS provides a web- based interface to acquire, generate, and distribute products, using the GMSEC Reference Architecture.
University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering &
©Ian Sommerville 2007COTS-based System Engineering Slide 1 COTS-based System Engineering.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
Structured Container Delivery Oscar Renalias Accenture Container Lead (NOTE: PASTE IN PORTRAIT AND SEND BEHIND FOREGROUND GRAPHIC FOR CROP)
Making Choice Possible in the Acquisition of Machinery Control Systems Program Executive Office Integrated Warfare Systems (PEO IWS)
Chapter 6: Securing the Cloud
Open Systems Architecture / Data Rights Key Implementers
IT Architecture Technical blueprint for evolving a corporate infrastructure resource that can be shared by many users and services processing systems hardware.
Multi-Purpose Reconfigurable Training System (MRTS) Overview
Software Requirements
EIN 6133 Enterprise Engineering
Chapter 25: Architecture and Product Lines
Many-core Software Development Platforms
The performance requirements for DSP applications continue to grow and the traditional solutions do not adequately address this new challenge Paradigm.
Chapter 11: Software Configuration Management
XML Based Learning Environment
CS310 Software Engineering Lecturer Dr.Doaa Sami
OPEN SOURCE AND FREEWARE SUITABLE FOR GOVERNMENT
Perspectives on Transforming DT and OT Industry-Government Roundtable
Presentation transcript:

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