Time Critical Targets Defined

1
RT CCM Kickoff MeetingAvionics Use Cases And
Requirements
David Sharp david.sharp_at_boeing.com 20 August 2002
2
Bold Stroke Operational Flight Program Production
System
Common Library
Desired Pluggable Common Components
Essential Common Components
Project Library
OFP Configurator
Essential Project Specific Plug-ins
OFPs Created Via Component Selection and Wiring
3
Component-Based Product Line Software Developer
Roles
Common
Multiple Developer Roles
Create common components
Project Specific
P1 Configurator
P2 Configurator
Extend common/create plugs for project specific
reqts
Create project specific components
Configure for project deployment
Functional
Extra-Functional
4
System Configuration
Configuration Layer Represents software system
circuit board.
5
Overall Development Process
Assess Required Variability
Common Component Developers
Develop Component Interface Impl
Develop Component Interface Impl
Product Specific Component Developers
Develop Customizations
Specify Hardware Configuration
Specify Component Configuration
Product Specific Component Integrators
Analyze Configuration
Deploy Test Configuration
6
Required Variabilities

• HW Types and Varying HW Architectures
• Processor counts and types
• Networks
• Non-volatile storage, etc
• SW Variations
• Operating systems
• Network protocols
• System Variations
• Responsiveness requirements

7
Resulting Software Architecture Variability
Support

• Standards-based middleware interfaces
• Number and types of components
• System execution modes
• Notification types
• periodic, multiple entry points and correlated
• Component ordering policies
• Threading policies
• Component-to-processor allocation

8
Model-Based Configuration Process
Inter-View Translation
Input Translation
Analysis Interchange Format (AIF)
Fault Tolerance
Event Dependencies
Logical Fault Mgmt
Application Component Library (ACL)
Parse Rose
Timing
Threading
Analysis Translation
Event Dependency
Filter/Translate To XML
Model Components
Invocation Dependency
Model Editor
Component Thread Map.
OEP Configuration
Generate Configuration
GME Importer
Process
Build
Component Allocation
Configuration Translation
Test
Physical Fault Mgmt
Instrumentation
9
Analogous CCM Concepts

• Configurator
• Deployment tool
• Application Component Library
• Component Descriptors
• OEP Configuration
• Assembly Descriptors
• Configuration Modeling Tool
• Assembly Tool

10
Bold StrokeClassic Component Structure

• Based on Facade Design Pattern

ComponentConsumer
ComponentSupplier1
ComponentSupplier2
11
Component Evolution Goals

• Formalize Configuration Specification
• Develop Role-based Interfaces
• Localize Access to
• Distribution
• Persistence
• Configuration
• Execution Dependencies
• Invocation Dependencies

Standardize and Automate System Configuration
12
Component Example

• Focus Here Is On CCM Elements

ltltInterfacegtgt
ComponentEquivalentInterface
Component
GetFacet()
ltltInterfacegtgt
Receptacle
ltltInterfacegtgt
Facet1
Connect()
ComponentConsumer
GetData()
EventSourceAdapter
ltltInterfacegtgt
Facet2
EventSinkAdapter
PointAt()
Home
FindByKey()
ltltInterfacegtgt
Create()
EventSink
Destroy()
ComponentSupplier1
Push()
13
Component Structure Meta-Model
Interfaces Added for Configuration
0..1
1
Application Interface
1
1
0..
1
1
1
0..
1
0..
1
1
0..1
0..1
0..1
0..1
1
Interfaces Added for Infrastructure Connections
14
Product Scenarios

• Currently Available Product Scenarios
• PS 1.x basic single processor
• 1.1 Basic SP
• 1.2 Multi-rate SP
• 1.3 Modal SP
• 1.4 Medium SP
• 1.5 Concurrency SP
• 1.6 Correlation - dynamic presence of suppliers
• 1.7 Correlation - event up-sampling
• 1.8 Persistence SP
• 1.9 Frame overrun SP
• 1.10 Error scenarios SP
• PS 2.x representative single processor
• 2.1 gt400 component instances

Multi-proc
Uni-proc
PS 1.x
Basic
PS 3.x
PS 4.x
PS 2.x
Representative
15
Product Scenarios (cont)

• Current Available Product Scenarios (cont)
• PS 3.x basic distributed processing
• 3.1 Basic MP
• 3.2 Multi-rate MP
• 3.3 Concurrency MP
• PS 4.x representative distributed processing

16
Generic Component Descriptions
Event Supplier
Acts as a
root event/data source
BM__DeviceComponent
for the system.
Is usually timer driven.
Event Supplier
Event Consumer
It is responsible for
BM__ClosedEDComponent
updating its own state and
is not modifiable by a
client (Closed).
20 Component Types Currently Provided
Event Consumer
BM__DisplayComponent
Acts as sink for data
and control. Data it
retrieves is output to the
screen.
17
Generic Component Descriptions (contd)
Event Supplier
BM__LazyActiveComponent
BM__PassiveComponent
BM__DisplayComponent
BM__ClosedEDComponent
BM__ModalComponent
Event Consumer
Event Supplier
Changes modes activated
by a push or client method
call.
Mode change results in a
change of supplied event.
BM__DeviceComponent
18
Product Scenario 1.1

• Simplest Single Processor Scenario
• Hello, World

19
OEP Configuration Specification

• XML structure representing CCM features
• Homes
• Components
• Receptacles/Facets
• Event subscriptions
• Published events
• Plus other configuration policies
• Distribution support
• Persistence configuration
• Concurrency support
• Component variability

20
Product Scenario 1.3 (20Hz)

• Mid-Level Single Processor Scenario

21
Product Scenario 1.3 (1Hz)
22
Product Scenario 3.1

• Simplest Distributed Processor Scenario

23
Current QoS Specifications

• Currently Only A Single QoS-Related Specified In
  OEP Configuration Interface
• Interval Timeout
• Used both to define
• Rate and thread for interval timeout events
• Thread for consumers which differ from their
  supplier

24
Requirement/Goal Summary

• Support For Component-Based Product Line
  Engineering
• Separation of class and instance information
• Component classes specify constraints on qos
  requests
• Instance configurations may or may not further
  constrain qos, also fill in platform specifics
  (e.g. timing)
• Support for Non-CORBA-Centric Components
• E.g. for single processor applications
• Support Middleware As Well As Application
  Configuration
• Possibly derived from application requirements
  and platform execution context

25
Requirement/Goal Summary (cont)

• Support Use Of Domain Specific Services
• E.g. replication, persistence
• Early, Initial Support For Simple Cases
• Static scheduling
• Manual configuration