Ada CMM Level 4 and the C-130 J

Ada, CMM Level 4, and the C-130 J Aircraft Presentation for SIGAda 2002 University of Houston, Clear Lake Tuesday, December 10, 2002 Richard Conn, C-130 J Software Process Engineer Approved for Public Release Lockheed Martin Aeronautics Company

Contents Ø About the C-130 J Aircraft Ø Specifications Ø Applications Ø Software Associated with the C 130 J Aircraft Ø Mission Computer Ø Ground-Based Data System Ø Software Development Environment Ø Languages and Tools Ø Achieving Capability Maturity Through Automation Approved for Public Release Lockheed Martin Aeronautics Company at Air Force Plant 6 In Marietta, GA Lockheed Martin Aeronautics Company 2

About the C-130 J Aircraft First named “Hercules, ” the C-130 has become a legend, with more than 2, 100 C-130’s built and purchased by over 60 nations in dozens of variations. The C-130: ØCarries troops, vehicles, and armaments into battle ØDrops paratroopers and supplies ØServes as airborne and ground refuelers ØProvides emergency and humanitarian relief (even acting as hospital ships) ØDoes airborne early warning and maritime surveillance (it even flies into hurricanes) Approved for Public Release First delivery of the C-130 J was to the Royal Air Force The new C-130 J looks like the original on the outside, but it is vastly improved: Ø 21% faster, 40% higher, 40% longer range Ø Reduced manpower (aircrew of 2 instead of 5), operating costs, support costs, lifecycle costs Ø A new propulsion system (29% more thrust with 15% more fuel efficiency) Ø Advanced avionics technology – 50 World’s Lockheed Martin Aeronautics Company Records! 3

About the C-130 J - Advanced Avionics Technology Ø Four multifunctional heads-down Liquid Crystal Display (LCD) instrument readouts for Ø Aircraft Flight Control Ø Operating Internal Systems Ø Navigation Ø Two holographic heads-up displays (HUDs) compatible with night vision imaging systems Ø Full-Authority Digital Aircraft Engine Control (FADEC) Ø Two Mission Computers (MCs) and two backup Bus Interface Units (BIUs) provide dual-redundant aircraft control with integrated diagnostics Approved for Public Release The State-of-the-Art Cockpit of the C-130 J Ø Ground-Based Data System (GBDS) for aircraft analysis and maintenance on the ground Ø More than 50 Computer Software Configuration Items (CSCIs) Lockheed Martin Aeronautics Company 4

Classes of Aircraft Software Ø Block 2 - the 382 J Aircraft Ø Ø The 382 J Aircraft is the base class upon which the C-130 J is based Ø The 382 J Aircraft received FAA Type Certification Ø Block 3 - the basic C-130 J Aircraft Ø Ø Inherits from the 382 J Aircraft Ø Block 2 and Block 3 Domain Engineering was performed since the early 1990’s Ø Block 4 - the Variants of the basic C-130 J Aircraft Ø Unique versions of the C-130 J modified for several customers, including, but not limited to: Ø United States Air Force (2 Variants) Ø Royal Air Force - United Kingdom Ø Royal Australian Air Force Approved for Public Release Block 5 – Maintenance and ECPs as well as more Variants Ø Customer needs change Ø More customers, such as Denmark Each Block (and, in the case of Block 4 and 5, each Variant) is divided into: Ø Air Vehicle CSCIs - provide central computing (MC and BIU) and subsystem (e. g. , FADEC) software on the aircraft Ø Support Systems CSCIs support ground-based laboratories and data collection and analysis system (GBDS) Ø Training Systems CSCIs support training the air crew and aircraft maintenance personnel Lockheed Martin Aeronautics Company 5

C-130 J CSCI Hierarchy C-130 J CSCIs Air Vehicle (AV) CSCIs Ø MC and BIU Operational Flight Program (OFP) CSCIs Ø Subsystem CSCIs Support Systems CSCIs Ø Ground-Based Data System (GBDS) CSCIs Ø Large Aircraft Digital Avionics Simulation and Systems Integration Laboratory (LADASSIL) CSCIs Training Systems CSCIs Ø Aircrew CSCIs Ø Maintenance CSCIs There are more than 50 Air Vehicle CSCIs for each Block. Approved for Public Release Lockheed Martin Aeronautics Company 6

Air Vehicle CSCIs - Introduction Ø The C-130 J Air Vehicle Avionics Architecture Ø Two Mission Computers (MCs) Ø Two Bus Interface Units (BIUs) Ø A number of aircraft subsystem devices known generally as Line. Replaceable Units (LRUs) Ø LMAC has developed the MC Operational Flight Program (OFP) and the BIU OFP CSCIs Ø Perform interconnection and intercommunication between other computing elements Ø Central repository for information on the aircraft subsystems Ø LMAC and 26 suppliers have developed the LRUs and their internal software Approved for Public Release Ø The MC OFP and the BIU OFP CSCIs interact with the 6 Ground-Based Data System (GBDS) CSCIs developed by LMAC Ø Ground Maintenance Program Application Processing (GMPAP) CSCI Ø Ground Maintenance Program Special Processing (GMPSP) CSCI Ø Operational Maintenance Program Mission Computer (OMP-MC) CSCI Ø Operational Maintenance Program Portable Maintenance Aid (OMPPMA) CSCI Ø Router CSCI Ø Memory Loader Verifier (MLV) CSCI Lockheed Martin Aeronautics Company 7

SDPs - Tier I and Tier II Ø Management of such a complex set Ø LMAC has created two Air Vehicle of software created by LMAC and a Tier II SDPs - one for the MC and myriad of suppliers is a formidable BIU OFP CSCIs and one for the 6 task GBDS CSCIs Ø The management starts with the Tier Ø These SDPs address I Software Development Plan (SDP): management and technical issues, including, but not Ø Is the controlling document for limited to, the issues of: managing the software aspects of the C-130 J program Ø overall management Ø Overviews the management and Ø aircraft safety and security technical processes necessary to Ø software process definition satisfy the requirements of the Cand management 130 J program Ø Requirements- and reuseØ Provides directions for creating oriented software processes the Tier II SDPs, provided by have been developed in LMAC and each supplier accordance with the LMAC Standard Software Process Framework (SSPF), which is compliant with SEI CMM Level 3, ISO 9001, and IEEE/EIA 12207 Approved for Public Release Lockheed Martin Aeronautics Company 8

Level 1 C-130 J MC Software Development Process System Definition Software Requirements System Maintenance Test Readiness Review Software Design Code/ Unit Testing Requirements-Based Testing Qualification Test Preparation Software Integration SEPD Build Formal Qualification Test Preparation Documentation Production Software Delivery Each process in these boxes is expanded in a Level 2 diagram (not shown in this presentation). There are over 110 processes total (21 November 2002). Approved for Public Release Lockheed Martin Aeronautics Company 9

Software Development and Reuse Ø Domain Engineering (DE) is performed on Ø the C-130 J program (has been since the early 1990’s) Ø The C-130 J domain was defined in terms of the Air Vehicle, Support, and Training Systems, emphasizing the MC and BIU OFP CSCIs: Ø MC and BIU Architecture definition was designed to support the addition, removal, and modification of classes of LRU devices to the aircraft Ø Design templates for 5, and now 8, classes of devices were created and used; today, we call this Template. Based Design (TBD) and use the templates to add new devices/LRUs Ø Ø Ada-based Design Approach for Real. Time Systems (ADARTS) was used to create the templates Approved for Public Release Requirements-Based Engineering (RBE) is performed on the C-130 J program Ø Requirements are defined in a more precise, specific form using Co. RE (Consortium Requirements Engineering) tables Ø Qualification criteria (testability) for requirements is defined when the requirements themselves are defined Ø This leads to Requirements. Based Testing (RBT) DE, ADARTS, TBD, RBE, RBT, and Co. RE are employed with the support of the Software Productivity Consortium (SPC) Lockheed Martin Aeronautics Company 10

Process Change and Product Lifecycle Management Ø Process changes and product lifecycles are managed using an automated rule-based, closed-loop change control process driven by the Process Configuration Management System (PCMS) tool Ø All work products, not just baselined products, are controlled Ø The program personnel are given roles that specify their abilities to affect the products being controlled Ø Parallel development efforts are facilitated (8 C-130 J Blocks/Variants are currently in various stages of development) Ø Accurate, current, and complete status accounting is a by-product of the use of the PCMS-based process Ø The automated process backed by tool support reduces administrative support and clerking overhead Ø Electronic Online Software Change Requests (OSCRs) and an electronic Software Development Change Control (SDCC) board are a key part of this process Ø OSCRs are controlled like any other work product, and they have a lifecycle Submit Analysis SDCC Review Requirements Implementation Integration and Testing Code Implementation Ready for Build Hold Reject Approved for Public Release OSCR Lifecycle Lockheed Martin Aeronautics Company Closed 11

Corporate Perspective Cumulative Percentage Life Cycle Cost 100% 85% 90% 80% 70% 60% t to s Co 3 -6 X 50% 40% cts 500 -1000 X efe D ct a xtr 20 -100 X Production/ E 10% 0% Test Phase Operations Through Disposal 100% 30% 20% 95% Committed Costs Concept Phase 8% Design Phase 15% Development 50% 20% Time Full Program Expenditures Presented at the Lockheed Martin Joint Symposium 2001 by Dr. Vance Coffman, Chairman Approved for Public Release Lockheed Martin Aeronautics Company 12

Software Development Environment – Trapping Defects Through Lines of Defense Requirements Ada Compilers and Tool Platforms RTM and Requirements Analysis Code Path Coverage Analyzer Software Product Evaluations Test Scripts SPARK Examiner and Robustness Analyzers Processes and Metrics Requirements-Based Testing and Lab Tests Audits/Assessments Other Products Approved for Public Release Lockheed Martin Aeronautics Company 13

Automated Software Product Evaluations Planning Preparation/ Conduct Review Overview Inspection/ Conclude Rework Follow-Up and Lock 3 rd Hour/ Process Improvement = optional Process Flow Approved for Public Release Lockheed Martin Aeronautics Company 14

Automated SPEs (continued) Server Side SPE Controller Client Side IWeb Browser (IE or Netscape) IPT Configuration SPE Data Store Containing Several Datasets SPE Starter 4 with Code Counter Ft Worth (Automet ) IPT Configuration Approved for Public Release SPE Information Assistant Lockheed Martin Aeronautics Company 15

Client Side – PCs and Suns Automated SPEs (concluded) Web Browser, SPE Starter 4, or IA (Data Collection) Information Assistant (IA) (Data Analysis) Windows or UNIX Operating System (SS 4, IA run only under Windows) UNIX Operating System Server Side - Sun HTTP Daemon (Web Server) DCS 3 SPE Controller DCS 3 Data Store Approved for Public Release Lockheed Martin Aeronautics Company 16

Questions? Looking for More Information? Ø LM and LMAC Public Websites Ø http: //www. lockheedmartin. com Ø http: //www. lmaeronautics. com/ Ø My University Websites Ø http: //unicoi. kennesaw. edu/~rconn Ø Paper in Crosstalk Ø Paper in IEEE Software Ø http: //cs. spsu. edu/rconn Ø My email Ø Richard. L. Conn@lmco. com Approved for Public Release Lockheed Martin Aeronautics Company 17