Industrial Applications of AADL
“AADL Avionics Case Studies and Concepts
for Integrating AADL into System Development”
January 29, 2007
Prepared by John Mettenburg, Advanced Technology Center
jjmetten@rockwellcollins.com
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
Agenda
Introduction
Case Studies
Concepts for Integration
Summary & Lessons Learned
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
CPU Load
Bus Load
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
A
B
C
Schedule
Integrate, then build.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
2
Advanced
Technology
Center
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
Business Profile
Communications and Aviation Electronics Systems for
Commercial and Military Applications Worldwide
2006 Sales
$4.2 Billion
Government
~ 52%
Commercial
~ 48%
Government Systems
Commercial Systems
• Integrated Systems
• Sensor Systems
• Displays
• Communication Systems
• Air Transport
• Business & Regional
• Cabin Systems
• eFlight
Engineering & Technology
Advanced Technology Center
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
4
Advanced Technology Center Organization
Advanced Technology
Center
J. W. (John) Borghese
Vice President
Communications &
Navigation Systems
Embedded Information
Systems
Advanced Radio
Systems
B. S. (Bruce) Kloster
Dr. R. A. (Ray) Kamin
Dr. K. P. (Krishna) Pande
Sr. Director
Sr. Director
Sr. Director
Business
Development
Program Management
K.H. (Keith) Diefenderfer
Director
S.S. (Steve) Pernetti
Director
Business
Development
C.J. (Chris) Loeffelholz
Director
Finance & Business
Administration
Lynn S. Schmidt
Senior Financial Analyst
Lab Resources
K.M. (Ken) Strong
Manager
The Advanced Technology Center (ATC) identifies, acquires, develops and transitions
value-driven technologies to support the continued growth of Rockwell Collins.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
5
Embedded Information Systems
Automated System Analysis /
Verification
§
§
§
Predictive Tools for Complex Architectures
Information Flow Modeling & Analysis
Model-Based Verification
Intel LT/VT
Demanding C&A
Secure Computing Systems
N
I
AAMP7
cPCI
HA
App
HA MTE
N
I
C
C
§
§
§
U
App
OS 1
OS 2
LynxSecure Hypervisor
Gigabit Encryption
Assured Information Sharing
System Level Anti Tamper
Persistent ISR
§
§
§
N
I
C
TS
App
System Framework
Knowledge Management
Information Analysis & Fusion
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
N
I
C
Sensory
Output
Task Command
Input
World
Modeling
Sensor
Processing
Simulator
Predictor
Predictions
Recognize
Filter
Compute
Group
Window
Confidence
Value
Judgment
Observations
Sensory
Input
N
I
C
Value
Knowledge
Database
Images
Maps
Entities
Events
States
Attributes
Tentative
Plan
Behavior
Generation
Cost
Value
Judgment Benefit
Task Decomposition
Planner
Expected
Results
PLAN
PLAN
PLAN
Executer
Executer
Executer
Subtask
Command
Subtask
Command
Subtask
Command
Feedback
6
Predictive Tools for Complex Architectures
Project Goals and Key Issues
Allow System Developers to Design the System Architecture &
Predict Its Behavior from Bid and Proposal through Maintenance
•
What Needs to be Predicted?
– Performance, capacity, latency, safety, security, …
•
Architecture
Architecture
Design
Logical
What Needs to be Modeled?
– Logical and physical architecture,
– CPU cycles, bus bandwidth, …
•
How is the Analysis Done?
– Custom Tools, commercial tools, open source tools, …
•
Architecture
Analysis
Physical
How Can We Add Value?
CPU
-4 0+4
-8 +8
G
Bus
Memory
-4 0+4
-8 +8
-4 0+4
-8 +8
… Y … R
– Focus on back end analysis, build competitive advantages,…
•
What is the Transition Path to Product Areas?
– Use existing tools, open standards, use existing editors on front end, …
Integrate, then Build.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
7
Systems Development Process Context
Focusing on Design Phase with the intent to Support
“Early Integration” through Predictive Analysis
Manage Project
Design and Develop System
Support System
Capture Originating
Requirements
Establish Aquisition
Agreement
Assess Project
Define Operational
Concepts
Define System
Requirements
Design System
Dispose System
Validate System
Verify System
Integrate System
Implement System
Maintain System
Operate System
Transition System
Manage Enterprise
Environment
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
8
Agenda
Introduction
Case Studies
AADL IMA System Analysis (2004)
SE Tool Study (2005)
AADL Integration Pilot (2006)
AADL “Forms IO” Evaluation (2006)
Concepts for Integration
Summary & Lessons Learned
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
CPU Load
Bus Load
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
A
B
C
Schedule
Integrate, then build.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
9
Processor
Power Supply
I/O H/W
ARINC/
Discretes/
Analogs)
MFD Display Manager
EICAS Manager
Left Outbrd MFD
ASL Node
System Manager
Data Concentration Unit
Planning
Processor
I/O H/W
LCD
(ARINC)
Low-Level
ASL Node
I/O, Keyboard
Power Supply
Processing
Resource
Power Supply
Built-In Test
Left CDU
Signal
Processor
I/O H/W
(misc)
Graphics
Display
Processor
I/O H/W
ARINC/
Discretes/
Analogs)
LCD
Graphics
MFD Display Manager
EICAS Manager
Left InBrd MFD
ASL Node
CDU Display Mngr
Planning
Comm. Manager
Processor
CDU I/O Manager
Flight Manager
ASL Node
Graphics
Built-In Test
I/O, Keyboard
CDU Display Mngr
Comm. Manager
CDU I/O Manager
Flight Manager
I/O H/W
(misc)
ASL Node
Power Supply
Power Supply
Processing
Resource
Right CDU
Processor
Digital
Signal
Switch
Low-Level
Digital
LCD
(ARINC)
Switch
I/O H/W
ASL Node
Display
Processor
I/O H/W
ARINC/
Discretes/
Analogs)
LCD
Graphics
MFD Display Manager
EICAS Manager
Right Inbrd MFD
ASL Node
Planning
Processor
I/O H/W
(misc)
ASL Node
Display
Processor
Power Supply
I/O H/W
ARINC/
Discretes/
Analogs)
LCD
Graphics
MFD Display Manager
EICAS Manager
Right Outbrd MFD
ASL Node
Flight Management Unit
DME Manager
Planning
Processor
Flight Director
10
AADL IMA System Analysis - Display System Architecture
LCD
Graphics
“Analyzable and Reconfigurable AADL Specifications for IMA System Integration”
Display
- Not modeled for this AADL example
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
ASL Node
SAE World Aviation Congress, Nov 2004 by David Statezni, RCI Advanced Technology Center
I/O H/W
(video/misc)
AADL IMA System Analysis for Trade Studies
Display System Graphical AADL
CPM
s_CDU_L_Software :
system
CDU_Processor_Software
.Impl
<ndo>_to_<destcpm>_<sw>_Out_Socket
<ndo>_from_<srccpm>_<sw>_In_Group
system
Display.Impl
Node
s_CDU_L_PN : system
Processor_Node_CDU.Impl
ASL_SW_L:
device
ASL_Switch.Impl
b_CDU_L_from_
Switch_Left
Switch
Node_In_SW_L
<ndo>_to_<destcpm>_<sw>_Out_Socket_Inv
Original
Configuration
from AADL
New
Configuration
b_CDU_L_to_
Switch_Left
Node_Out_SW_L
<ndo>_from_<srccpm>_<sw>_In_Inv
<vmr>_<ndo>_from_<srccpm>_<sw>
<ndo>_to_<destcpm>_from_Node_<srccpm>
<vmr>_<ndo>_to_<destcpm>_<sw>
<ndo>_from_<srccpm>_to_Node_<destcpm>
Notes:
Switch_Out_Port
Identifiers with angle-bracketed terms are
replicated for each unique set of terms,
where terms are defined as:
<cpm> : Common processing machine name
<cpmid>: Longer name of cpm
<ndo>: Network data object name
<sw>: ASL switch side identifier
<vmr>: Virtual machine and rate, indicating thread name
s_<cpm>_Software :
system
<cpmid>_Processor_Software
.Impl
<ndo>_to_<destcpm>_<sw>_Out_Socket
Switch_In_Port
s_<cpm>_PN : system
Processor_Node_<cpmid>.Impl
b_<destcpm>_from_
Switch_Left
Node_In_<sw>
<ndo>_to_<destcpm>_<sw>_Out_Socket_Inv
b_<srccpm>_to_
Switch_Left
Node_Out_<sw>
<ndo>_from_<srccpm>_<sw>_In_Group
<ndo>_from_<srccpm>_<sw>_In_Inv
<vmr>_<ndo>_from_<srccpm>_<sw>
<ndo>_to_<destcpm>_from_Node_<srccpm>
<vmr>_<ndo>_to_<destcpm>_<sw>
<ndo>_from_<srccpm>_to_Node_<destcpm>
Automated Analysis
5 CPMs
13 Virtual Machines
90 Threads
165 End-End Flows
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
11
SE Tools Study
•
UML Based
–
–
–
–
–
MBSD is
Investigating
These Tools
•
Artisan Realtime Studio from Artisan (UML 2.0/OO)
Enterprise Architect (UML 2.0/OO)
Rhapsody from Ilogix (UML 2.0/OO)
Tau from Telelogic (UML 2.0/OO)
System Architect/SW Modeler from Rational/IBM (UML 2.0/OO Eclipse)
Other
–
–
–
–
–
–
–
–
–
ARIS from Ids Scheer
CORE from Vitech (DoDAF)
Metis from Computas (Zachman/DoDAF/UML 2.0)
MIAA (Military Information Architecture Acceleration) from Ptechinc
(DoDAF/CADM)
NetViz form NetViz (DoDAF)
Proforma from Proforma (Business model focus /UML/DoDAF/OO/Structured
Decomposition)
TeamCenter Architect from UGS (Partial UML, DoDAF, PIM/PSM)
VisualSim from Mirabilis Design
Cradle from 3SL (UML, DoDAF, PIM/PSM)
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
12
SE Tools Study – UGS Teamcenter Architect
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
13
SE Tools Study - UGS Teamcenter Architect
AADL Visio Stencil Integration
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
14
SE Tools Study - AADL UML Profile
«AAD LSyste m_T ype »
AutonomousVe hicle _Syste m
Note the Introduction
of AADL Stereotypes
Vehicle_ Sta te
Veh ic le_ Sta te
SYSTEMS
Containers for Hierarchy
1
«AAD LSyste m_T yp e »
Vis io nSystemLt:Visi onS ys te mS lic e
Ob st ac le
O bstacle
1
«AAD LSyste m_T ype »
VisionSyste mRt:VisionSyste mSlice
AADL Provides Backbone to UML
For Real-Time Embedded Systems…
Ob st ac le_D a ta
Vis io nO bs tic alD ataL t
Visio nO bsticalD ataR t
Ve hicle State _D ata
Ve hicle State
1
1
«AAD LD e v ice _T ype »
G PS_IM U
«AAD LD e v ice _T ype»
Ve hic le Sen so r
1
«AAD LP roce ssor_T ype »
Veh ic leP ro ce sso r_O :VehiclePro ce ss or
G PS _IM U
G PS_IM U _O u t
G PS_IM U _D ata
Ve hicle Se nsor
Ve hicle Se nsor_D ata
Veh ic leS ensor
Ve hicle C ontrol
Ve hic le C ontrolC o mmands_D ata
DEVICES
1
VehicleC ontrol
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
PROCESS
«AAD LD e v ice _T ype»
Ve hicle C ontrol
15
AADL Integration Pilot
Evaluation of End-End Latency
Architecture Visualization
Teamcenter
Physical Architecture Capture
XML
Database
Architecture Analysis
XML
OSATE
system
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
16
AADL Integration Pilot
Latency Allocation & Validation Using AADL
Latency Budget
Comm 2 + SW Time 2 + Switch Delay + SW Time 1 + Comm 1
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
17
AADL Integration Pilot
(OSATE) CDU Key Press Analysis
Analyze Latency…
Analyze Latency…
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
18
AADL Integration Pilot
UGS Teamcenter (Alternative Flow Analysis/Visualization)
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
19
AADL Integration Pilot - Conclusion
•
Realized the value of a intermediate architecture form
–
Instead of publishing the internal schema of the tool
•
–
To simply document the semantics (as part of the translator)
•
–
Office integration proved workable and valuable
•
–
–
–
e.g Reuse of existing Spreadsheets, replication of existing diagrams & reports
Usable version control
Much more capability than needed for visualization
Lack of syntax and semantics at this level could be a benefit (“dumbed down diagrams”)
Demonstrated the value of Eclipse
–
–
–
•
Communication & Automation
Realized the power of Teamcenter
–
•
Correctness, Visualization, Modularization & Analysis Infrastructure
QVT showing some promise
•
•
Promotes a common understanding and best practices (common AND unique)
Found AADL to be well-matched for the task
•
–
This is the AP/STEP approach
Reused the latency analysis plug-in (OSATE)
Analysis plug-ins were easy to develop
But still need a scripting language…
Need to watch Scalability & Scope
–
–
–
For example, XML is verbose (DOM XML parser approach is inadequate)
One size does NOT fit all (focus on IMA helped)
Need to incorporate modularity in Exchange mechanism to support the “24 hr turn”
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
20
AADL “Forms IO” Evaluation
SEI Forms Based AADL Import/Export Concept
Input
Data
Excel
Templates
Access
Tables
XML
OSATE
AADL
XML
Reformat Existing Data
into Excel Worksheets
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
Process using the
Forms IO Tools
Analyze/Operate using
The AADL IDE (OSATE)
21
Agenda
Introductions
Case Studies
Concepts for Integration
Summary & Lessons Learned
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
CPU Load
Bus Load
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
A
B
C
Schedule
Integrate, then build.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
22
Concepts for Integration
Architecture Modeling & Analysis - Business Adoption
Top-Down
–
Subsystems are the common denominator
•
•
ce
s
Middle-Out
Good place to standardize the notation
Meta-Data
e
tur
uc
Str
•
Proof of Concept
Pursuit Strategy (cost & schedule)
Innovative People
Communities of Practice
y&
–
–
–
–
Se
rvi
Bottom-Up
erf
ac
es
&
•
Enterprise Initiatives
Product Line
Customer Requirements/Constraints
ch
rar
Hie
–
–
–
Behavior
Int
•
Underneath
–
AADL provides common solution space for Architecture models
•
Build DSL on top
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
23
Concepts for Integration - AADL at Rockwell Collins
o
o
o
o
Actively participates in the AADL standards development
Rockwell Collins published AADL papers and a modest AADL example model
(www.aadl.info)
AADL XML is used for architecture exchange behind on-going programs
AADL Based Analysis/Deployment Tools
o AADL Integration Into the Development Process…
o
o
o
Standards & Open Source
Common Architecture Model
Interface Data Specification
o AADL Tool Integration Efforts
o
o
o
UML
SimulinkTM
Custom Tools
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
24
Concepts for Integration
Accelerating Design using Standards & Open Source
•
Benefits of Standards
–
–
–
–
–
Enable communication between tools in a
framework
Provide stability to an architecture framework.
I.e. they shield against tool obsolescence and its
impact.
Protect intellectual property
Promote Innovation
Supports use of “best fit” tool across disciplines,
design cycle & life cycle
AADL is a Key Sta
ndard
•
Open Source
–
–
–
–
–
–
Accelerating Standards Adoption
Reducing Cost of Technology
Reinforces need for standards
Eclipse Platform
Domain Specific Languages
Internal Open Source
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
25
Concepts for Integration - Common Architecture Model
TODAY
SW/HW
Design
Tools
TOMORROW
SW/HW
Design
Tools
Architecture Template
Translators
SYS
Design
Tools
Integrate &
Deploy
Analysis
Tools
External
Customers
Problem
Ad-hoc approach to design and
implementation of translators
discourages reuse, couples tool
versions and prevents change
SYS
Design
Tools
Integrate &
Deploy
Analysis
Tools
External
Customers
Solution
Standardized Architecture Exchange
approach provides standardized
template, minimizes number of
translators and promotes agility
Emphasis on Standard Languages and Translators – Not tools
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
26
Concepts for Integration - Common Architecture Model
Approach
•
Standards based approach
– AADL as an intermediate form (reference meta-model)
– UML (Unified Modeling Language) Meta-Models
– XML/XMI (metamodel representation)
– QVT (model transformation language)
– MARTE approach for a Property Model
•
Declarative mappings
– Human understandable/checkable
– Defined as high level QVT transformations
•
Automated Report Generation (Translator Spec)
•
Path to Model based Transformations
– ATL, Express-X …
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
27
Concepts for Integration - Common Architecture Model
•
Challenges
–
Number of mappings to be defined
–
Lack of documentation and a well defined
semantics for many of the models to be
mapped
–
Potentially significant mismatches between
meta-models, at a conceptual level
–
Development of a process for
maintenance/evolution of metamodels &
mappings over time
–
Scaleability for large models/mappings →
incremental updates
–
AP233/SysML Integration
It’s a lot of work…
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
28
Concepts for Integration - Common Architecture Model
•
Benefits
– Interoperability between processes and tools
• Internal processes and tools
• Industry standard, external processes and tools
– Common representation for analysis
– A Reference for common, well-defined semantics
– Ability to more easily evolve models and mappings
– Ability to adapt models and model generated code to specific domains,
platforms, applications, etc.
Lower the Cost and Improve Quality
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
29
Concepts for Integration - Interface Data Specification
•
Interface design data can be captured and exchanged with AADL
–
–
–
XML is popular as exchange format
Property support is well suited for the problem
Text & Graphicals forms are readable
•
•
–
•
Extensible Data Editor
Report Generator
Issues
–
–
–
•
Ease of Integration with System and Software Models
Standardized Views are possible
–
–
•
Documentation, Review
Debug and Integration
Not Invented Here
Verbosity
XML with a robust schema is not light weight
AADL currently “under the covers” for an Enterprise, component modeling toolset
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
30
Concepts for Integration - Interface Data Specification
AADL Types
Data Dictionary Level
Data Representation Level
AADL Implementations
The Data Dictionary is the information requirement
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
31
Concepts for Integration - Interface Data Specification
data ReceiverMode
properties
DD_Properties::Initial_Value => "State1";
DD_Properties::Element_Type => MLEnumeration;
DD_Properties::Element_Values => ("State1", "State2", … "State10");
end ReceiverMode;
Data Dictionary
Implementation(s)
data implementation ReceiverMode.serial
subcomponents
rcvrmode: data INT16 {
Element_Properties::Initial_Value => "0";
Element_Properties::Element_Enum_Values => (1, 2, 3, 4, 5, 10);
};
properties
Element_Properties::Version => "12.2.a";
end ReceiverMode.serial;
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
32
Concepts for Integration - Interface Data Specification
data Latitude
properties
DD_Properties::Numeric_Type => Float;
end Latitude;
Data Dictionary
Implementation(s)
Rep
r
Lon esentati
gitud
o
e is n of
th e
sam
e…
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
data implementation Latitude.format2
subcomponents
field1: data {
Element_Properties::Length => 16 Bits;
Element_Properties::Word_Offset => 0 W;
Element_Properties::LSB_Position => 0 W;
Element_Properties::LSB_Weight => value(Constants::M_PI_Div_2_15);
Element_Properties::Element_Units => RADIANS;
};
field2: data {
Element_Properties::Length => 16 Bits;
Element_Properties::Word_Offset => 1 W;
Element_Properties::LSB_Position => 0 W;
Element_Properties::LSB_Weight => value(Constants::M_PI_Div_2_31);
Element_Properties::Element_Units => RADIANS;
};
properties
Element_Properties::Is_Packed => true;
end Latitude.format2;
data implementation Longitude.format2
extends Latitude.format2
end Longitude.format2;
33
Concepts for Integration
Collaboration & Model Organization
data Latitude
properties
Data_Dictionary::data_type => FLOAT;
end Latitude;
Data Dictionary
data latitude extends pl_dd_components::latitude
end latitude;
data implementation latitude.format1
Shared Data Definitions, properties
Element::Data_Type => FIXEDPT;
Or Implementations
end latitude.format1;
data implementation message1.format1
subcomponents
header : data header;
field1 : data pl_data_defs::latitude.format1;
Shared Message Definitions,
field2 : data pl_data_defs::latitude.format2;
Or Implementations
end message1.format1;
“pl” == Product Line
system implementation icd.rs422
subcomponents
hdr : data pl_common::Copyright_String;
ICD Composition
Independent Files for CM
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
msg1 : data pl_sp_messages::message1.format1;
msg2 : data pl_sp_messages::message2.format1;
properties
ICD::version => "1.0";
end icd.rs422;
34
Concepts for Integration – Custom Tools
Multi-Objective System Trade-off and Analysis (MOSTA)
Architecture Description Language
JCAT/JNAT
p −1
∑b + ∑∑(b − r ⋅ d )+ max(s )
port type implementation IO_Types.others is
attributes
Actuator_Data_
Type'SourceDataSize:= 12 B;
Sensor_Data_
Type'SourceDataSize:= 12 B;
end IO_Types.others;
(7)
d =
j∈C p
i
i
i
q =1 i∈Cq
p
Input and Output Envelopes
6
r
4
for p = 1, 2, ..P
p −1
R−
r> p
Cumulative Traffic (By tes)
j
port type IO_Types is
Actuator_Data_Type : type;
Sensor_Data_Type : type;
end IO_Types;
∑∑r
2
i
0
q =1 i∈Cq
1
0
1
2
3
Scheduler Workload (when positive)
channel Fiber is
end Fiber;
processor ADA95_Network_Switch is
Chan01_In : channel Fiber;
Chan01_Out : channel Fiber;
Chan02_In : channel Fiber;
Chan02_Out : channel Fiber;
Chan03_In : channel Fiber;
Chan03_Out : channel Fiber;
Chan04_In : channel Fiber;
Chan04_Out : channel Fiber;
;
end ADA95_Network_Switch
4
5
Input Envelope A*
Output Envelope B*
with port type IO_Types;
system ASL_and_IO_HW is
end ASL_and_IO_HW;
F(t) with d = 0
2
0
2
tem es
s
Sy alys
An
0
2
4
Time
6
8
10
Critical Points
Sum B(t) - t R
Critical Time,Tc
MOSTA
Integrated
System
Software Code
Generation and
Testing
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
on
i
t
la tion
u
m a
Si alid
V
Hardware
Development
and Testing
/*$*************
SCADE_CG V4.1.0
**************
**Command :
**lustre2C ./../TESTS/
AltitudeMngmt
.lus-node PFD
**-noexp
@ALL@
**-static
**-noassert
**-const
**-opt_
bool
_loc
**-opt_
bool
_ctx
**-opt_
bool
_glob
**-opt_
io
**-loc_ctx
**-opt_
const
**date of generation (MM/DD/YYYY): 09/06/2001
**last modification date for ./../TESTS/
AltitudeMngmt
.l us(MM/DD/YYYY): 09/06/2001
************************************************$*/
#include
"PFD.h"
/* ============== */
/* INITIALISATION */
/* ============== */
voidTempo_
init(_C_Tempo
*_C_)
{
(_C_->_M_
init_0_PFD)true
=;
}
voidState_
init(_C_State
*_
C_)
{
(_C_->_M_
init_0_PFD)true
=;
}
OPNET
35
Concepts for Integration
AADL Tool Integration Efforts – UML & Simulink
•
UML
–
–
–
–
•
AADL profile validation/integration (Rhapsody)
AADL <-> UML w/AADL Profile Translator (XMI2.1 w/vendor adaptors)
SysML & Domain Specific Profiles
Component Integration
SimulinkTM
– Custom Integration
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
36
Agenda
Introductions
Case Studies
Concepts for Integration
Summary & Lessons Learned
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
CPU Load
Bus Load
100
90
80
70
60
50
40
30
20
10
0
10
20
30
40
50
60
A
B
C
Schedule
Integrate, then build.
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
37
AADL Applications Summary - Lessons Learned
“Standard” sounds good to a funding source
–
–
•
Do not under-estimate change to a Business area
–
–
–
•
Common Property Model is the real work…
Source & Destination Schema Shared Ownership
Translators
–
–
–
Transfer what you need, Develop Role based views
Break up the transform if necessary
Make performance a requirement
Current Focus
Future Work
–
–
Extend the CAM “down” for Component Modeling Integration
Extend the CAM “up” for Functional Architecture using AP233
•
–
AADL
•
Let the customer decide
Common Architecture Model (CAM)
–
–
•
Sometimes they are the last ones we ask
Evaluation and Pilot
–
•
Look for allies (not just once! periodically)
Incremental, while less efficient, is more practical
Find the brief periods of intense pain – and exploit them
Know the Users
–
•
But maybe not so good for the funding target, Definitely not so good for some vendors
Be prepared to pay for it…
AP233
•
Requirements, Functional Architecture, Configurations
Formal Methods Integration
© Copyright 2007 Rockwell Collins, Inc.
All rights reserved.
38