Model-Based Integration of Reusable Component-Based Avionics Systems

Model-Based Integration of Reusable Component-Based Avionics Systems David Sharp Technical Fellow Phantom Works, Open System Architecture david.sharp@boeing.com 27 May 2003 This work was sponsored by the DARPA/ITO Model-Based Integration of Embedded Software program, under contract F33615-00-C-1704 with Air Force Research Laboratory Information Directorate, Wright-Patterson Air Force Base.

Product Line Component Model Object-Oriented Reusable Application Framework • Single Component Development Policies • Configurable for Product Specific Functionality and Execution Environment • Architecture Specific Service Software • Configurable to variable hardware configurations • Supportive of reusable applications Infrastructure Services • Configurable for Product Specific Component Selection and Distribution Environment • Component Integration Policies Operating System Board Support Package • COTS-based real-time middleware services • Standard Service Software Operator Hardware (CPU, Memory, I/O) Push Control Flow Real World Model Pull Data Flow Avionics Interfaces Infrastructure Services Commercial and Standards-Based Platform Component Integration Model Boeing Bold Stroke Initiative Creation of Highly Configurable Avionics Product Line Via OO Framework Technologies

FacadeClass Class Class ProjectClass ojec ojec CommonClass ass ass ProjectHelperClass Projss Projss HrClass HelperClass HelperClass HrClass Product Line Development Components Integration Common Create common components Project Specific P1 Configurator P2 Configurator Create project specific components Extend common/create plugs for project specific req’ts Configurefor project deployment Functional Systemic

Focus Area Analyze Model Reusable Components Model Composition Model Model Generate Configuration Build Test Build Test Model-Based Component Integration Approach

Process Related Views • Logical Fault Management • Operational and backup modes and components • Components that need replicated backups • Execution Dependencies • Triggers and trigger types • Trigger based dependency graphs • Execution rates for the roots of dependencies • Threads • Threads and their associated rates and priorities

Deployment Related Views • Physical Fault Management • Relationships between fault modes and physical resources • Component Quality of Service • Execution rates • Importance • Resource requirements • Process • System physical resources • Allocation of threads to processes • Component Allocation • Components that are strongly coupled • Allocation of components to processors and processes • Parameters for automatic generation of integration code • Identify and generate CORBA stubs and skeletons as needed

Model-Based Analysis • Execution Dependencies • Identifying cyclic dependencies • Ensuring consistency of dependency graphs • Using dependency graphs to identify execution requirements for timing analysis • Timing Analysis • Schedulability • Utilization • Fault Tolerance • Determine status of components in various fault scenarios • Support allocation of backup components to processors to meet fault-tolerance goals Having models that capture cross-cutting aspects of a system is the basis for analysis

Model-Based Configuration • Automatic Generation of Configuration Code Based on Models Can Yield Increased Speed and Quality and Reduced Cost • Manual creation of integration code is time consuming, tedious and error prone • Much integration code is fully determined by a model of the system configuration • Tools already exist that generate much similar code • CORBA IDL compilers, etc.

U Michigan, Vanderbilt Teknowledge, Vanderbilt Application Component Library (ACL) Analysis Interchange Format (AIF) Vanderbilt, CMU, Honeywell, Southwest Research Model Editor OEP Configuration Well Defined XML Interfaces Enable Tool Integration Instrumentation Resultant Process Inter-View Translation Input Translation Analysis Translation Fault Tolerance Event Dependencies Logical Fault Mgmt Parse Rose Timing Threading Instrumentation Event Dependency Filter/Translate To XML Model Components Invocation Dependency Component Thread Map. Configuration Translation Generate Configuration Model Importer Process Build Component Allocation Test Physical Fault Mgmt

Development Scenario Example Walkthrough

MoBIES-Enabled Process Inter-View Translation Input Translation Analysis Interchange Format (AIF) Fault Tolerance Event Dependencies Application Component Library (ACL) Logical Fault Mgmt Parse Rose Timing VU: ESML Threading Tek: MoBIES Translator Analysis Translation UM: AIRES Event Dependency Filter/Translate To XML Model Components Invocation Dependency Tek: MoBIES XML Exporter Model Editor Component Thread Map. OEP Configuration Generate Configuration GME Importer Process VU: ESML VU: rr2esml SWRI: ASC-Scheduler Build Component Allocation Configuration Translation Test Physical Fault Mgmt

Component Specification • Initial Design of Components Accomplished in Rational Rose • Stereotypes used to express components

Exporting the Component data • Scripts Export The Model Data And Filter Out All Non-Component Related Details

Event/Invocation Dependency Subview Modeling Interaction models must be created in ESML to show the initiating timer object, instances of event types and component types and the connections between them. Component instances are assigned a unique Group and Item Id.

Threading/Process Subview Modeling Assign the priority and rate associated with each thread. In the Configurations folder, define the processors, then double click on them to define the threads and processes running on that processor.

Constraint Checking • Static Errors Are Caught Either During Modeling Or Analysis

AIRES Event Dependency Graphs (EDGs) • Graphs Are Created To Visualize Event Dependencies

Scheduling Analysis • Utilization Is Shown for Each Processor, and Divided Among Tasks Running on the Processor

Configuration Generation • Interfaces Defined Via UML Meta-Models • XML Configuration Files Generated From Models Via Scripts • ESML2Config MC__MediumSP.mga OEP Configuration File Interface Model

Accomplishments • End-To-End Automated Model-Based Configuration • From UML Reusable Component Models to Running Code • Initial Set Of Real-Time Analyses • Configuring Representative Avionics Systems Of Up To • ~20 Component Types • ~400 Component Instances • ~3 Processes / processors • Using • Multiple tools with well-defined XML interfaces • Pervasive meta-modeling

Scalability, Usability… Component-Oriented Design Round-Trip Engineering Tool Integration Instrumentation Standardization Performance Optimization Middleware Configuration Remaining Challenges Component Design Input Translation Analysis Translation Fault Tolerance Logical Fault Mgmt Application Modeling Design Generation Event Dependencies Persistence Parse Rose Event Dependency Timing Analysis Interchange Format (AIF) Model Component Implementations Appl Comp Lib (ACL) Invocation Dependency Component Allocation Filter/Translate To XML Implement Component Configuration Translation Component Thread Map Generate App Config Model Editor Activation Middleware Modeling Model Importer OEP Configuration Process Model Mware Generate Mware Config Threading Build mware config aspect 1… Implement Mware Test Physical Fault Mgmt Instrumentation PIM PSM

Model-Based Integration of Reusable Component-Based Avionics Systems