Upload
hangoc
View
224
Download
0
Embed Size (px)
Citation preview
© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
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 [email protected]
2© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Agenda
Introduction
Case Studies
Concepts for Integration
Summary & Lessons Learned
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
CPU Load
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
Bus LoadABC
Schedule
Integrate, then build.
© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Advanced
Technology
Center
4© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Business Profile
Government
~ 52%
Commercial
~ 48%
Communications and Aviation Electronics Systems for Commercial and Military Applications Worldwide
Commercial Systems• Air Transport
• Business & Regional
• Cabin Systems
• eFlight
Government Systems• Integrated Systems
• Sensor Systems
• Displays
• Communication Systems
Engineering & Technology
Advanced Technology Center
2006 Sales
$4.2 Billion
5© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Advanced Technology Center Organization
Advanced Technology
CenterJ. W. (John) Borghese
Vice President
Embedded Information
SystemsDr. R. A. (Ray) Kamin
Sr. Director
Communications &
Navigation SystemsB. S. (Bruce) Kloster
Sr. Director
Advanced Radio
SystemsDr. K. P. (Krishna) Pande
Sr. Director
Lab ResourcesK.M. (Ken) Strong
Manager
Business
DevelopmentS.S. (Steve) Pernetti
Director
Program ManagementK.H. (Keith) Diefenderfer
Director
Business
DevelopmentC.J. (Chris) Loeffelholz
Director
Finance & Business AdministrationLynn S. Schmidt
Senior Financial Analyst
The Advanced Technology Center (ATC) identifies, acquires, develops and transitions value-driven technologies to support the continued growth of Rockwell Collins.
6© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Secure Computing Systems§ Gigabit Encryption§ Assured Information Sharing§ System Level Anti Tamper
Persistent ISR § System Framework § Knowledge Management§ Information Analysis & Fusion
Embedded Information Systems
Automated System Analysis / Verification
§ Predictive Tools for Complex Architectures§ Information Flow Modeling & Analysis§ Model-Based Verification
Task DecompositionPlanner
KnowledgeDatabase
ImagesMaps
EntitiesEventsStates
Attributes
BehaviorGenerationWorld
ModelingSensor
Processing
Recognize
FilterCompute
GroupWindow Value
Judgment
PLAN PLAN PLAN
Executer Executer Executer
Observations
Confidence
Value
PredictionsSimulator
Predictor
Feedback
ExpectedResults
SensoryInput
Sensory
Output
TentativePlan
CostBenefit
Subtask
Command
Subtask
CommandSubtask
Command
Task CommandInput
Value
Judgment
Value
Judgment
NIC
Intel LT/VT
TSApp
UApp
OS 1 OS 2
Demanding C&A
HAApp
AAMP7cPCI
HA MTE
N
I
C LynxSecure Hypervisor
NIC
NIC
NIC
7© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Predictive Tools for Complex Architectures
Project Goals and Key Issues
• What Needs to be Predicted?
– Performance, capacity, latency, safety, security, …
• 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, …
• How Can We Add Value?
– 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, …
Allow System Developers to Design the System Architecture &
Predict Its Behavior from Bid and Proposal through Maintenance
Integrate, then Build.
-8-4
+8+40
Memory
Y -8-4
+8+40
Bus
R-8-4
+8+40
CPU
G …
ArchitectureLogical
Physical
ArchitectureDesign
ArchitectureAnalysis
…
8© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Dispose System
Maintain System
Operate System
Transition System
Design and Develop System
Manage Project
Establish AquisitionAgreement
Manage EnterpriseEnvironment
Support SystemCapture Originating
Requirements
Define Operational
Concepts
Assess Project
Validate System
Verify SystemDefine System
Requirements
Design System Integrate System
Implement System
Focusing on Design Phase with the intent to Support “Early Integration” through Predictive Analysis
Systems Development Process Context
9© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
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
Agenda
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
CPU Load
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
Bus LoadABC
Schedule
Integrate, then build.
10
©C
opyrig
ht 2
00
7 R
ockw
ell C
ollin
s, In
c.
All rig
hts
reserv
ed.
AA
DL
IMA
Sys
tem
An
aly
sis
-D
isp
lay S
ys
tem
Arc
hite
ctu
re
Po
wer S
up
ply
I/O H/W
(misc)
ASL Node Graphics
ASL Node
Planning
Processor
LCD
Right Inbrd MFD
Po
wer S
up
ply
Display
Processor
I/O H/W
(misc)
ASL Node Graphics
ASL Node
LCD
EICAS Manager
Right Outbrd MFD
MFD Display Manager
Planning
Processor
Flight Management Unit
Flight Director
Po
wer S
up
ply
Low-Level
Signal
Processor
I/O H/W
(ARINC)
Graphics
ASL Node
Processing
Resource
LCD
I/O, Keyboard
Built-In Test
CDU I/O Manager
Comm. Manager
Left C
DU
CDU Display Mngr
Flight Manager
Po
wer S
up
ply
Low-Level
Signal
Processor
I/O H/W
Graphics
ASL Node
Processing
Resource
LCD
I/O, Keyboard
Built-In Test
CDU I/O Manager
Comm. Manager
Rig
ht C
DU
CDU Display Mngr
Flight Manager
Display
Processor EICAS Manager
MFD Display Manager
Po
wer S
up
ply
I/O H/W
(misc)
ASL Node Graphics
ASL Node
Planning
Processor
LCD
Left InBrd MFD
Display
Processor EICAS Manager
MFD Display Manager
Po
wer S
up
ply
Display
Processor
I/O H/W
(video/misc)
ASL Node Graphics
ASL Node
LCD
EICAS Manager
Left Outbrd MFD
MFD Display Manager
Planning
Processor
System Manager
Data Concentration Unit
(ARINC)
-N
ot m
ode
led
for th
is A
AD
L e
xam
ple
I/O H/WARINC/Discretes/
Analogs)
Sw
itch
Dig
ital
Sw
itch
Dig
ital
I/O H/W
ARINC/
Discretes/Analogs)
I/O H/W
ARINC/Discretes/
Analogs)
I/O H/W
ARINC/Discretes/Analogs)
DME Manager
“A
naly
zab
le a
nd
Reco
nfig
ura
ble
AA
DL
Sp
ecific
atio
ns fo
r IMA
Syste
mIn
teg
ratio
n”
SA
E W
orld
Avia
tion
Co
ng
ress, N
ov 2
004 b
y D
avid
Sta
tezn
i, RC
I Ad
van
ced
Tech
no
log
y C
en
ter
11© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL IMA System Analysis for Trade Studies
Display System Graphical AADL
Original Configuration from AADL
New Configuration
s_<cpm>_PN : system
Processor_Node_<cpmid>.Impl
ASL_SW_L:
device
ASL_Switch.Impl
Switch_In_Port
systemDisplay.Impl
b_<srccpm>_to_Switch_Left
Node_Out_<sw>
Switch_Out_Port
b_<destcpm>_from_Switch_Left
Node_In_<sw>
<vmr>_<ndo>_to_<destcpm>_<sw>
s_<cpm>_Software :
system
<cpmid>_Processor_Software
.Impl
<ndo>_to_<destcpm>_<sw>_Out_Socket <ndo>_to_<destcpm>_<sw>_Out_Socket_Inv
<ndo>_from_<srccpm>_<sw>_In_Inv
<vmr>_<ndo>_from_<srccpm>_<sw>
<ndo>_from_<srccpm>_<sw>_In_Group
<ndo>_to_<destcpm>_from_Node_<srccpm>
<ndo>_from_<srccpm>_to_Node_<destcpm>
s_CDU_L_PN : systemProcessor_Node_CDU.Impl
b_CDU_L_to_Switch_Left
Node_Out_SW_L
b_CDU_L_from_Switch_Left
Node_In_SW_L
<vmr>_<ndo>_to_<destcpm>_<sw>
s_CDU_L_Software :
system
CDU_Processor_Software.Impl
<ndo>_to_<destcpm>_<sw>_Out_Socket <ndo>_to_<destcpm>_<sw>_Out_Socket_Inv
<ndo>_from_<srccpm>_<sw>_In_Inv
<vmr>_<ndo>_from_<srccpm>_<sw>
<ndo>_from_<srccpm>_<sw>_In_Group
<ndo>_to_<destcpm>_from_Node_<srccpm>
<ndo>_from_<srccpm>_to_Node_<destcpm>
Notes:
<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
Identifiers with angle-bracketed terms are
replicated for each unique set of terms,
where terms are defined as:
Automated Analysis
5 CPMs
13 Virtual Machines
90 Threads
165 End-End Flows
CPM Node
Switch
12© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
SE Tools Study
• UML Based– 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)
MBSD is Investigating These Tools
13© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
SE Tools Study – UGS Teamcenter Architect
14© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
SE Tools Study - UGS Teamcenter Architect
AADL Visio Stencil Integration
15© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AutonomousVehicle_System
«AAD LSystem_T ype»
Vis ionSystemLt:VisionS ystemS lice
1 «AADLSyste m_Type»Vehicle_State Obstac le
VisionSystemRt:VisionSystemSlice
1 «AAD LSystem_T ype»Veh ic le_State
Obstac le_Data
Obstacle
GPS_IM U
1 «AAD LDevice_Type» GPS_IM U_Out
Veh ic leP ro cesso r_O :VehiclePro ce ssor
1 «AADLP rocessor_Type »VehicleState_Data
VehicleState
GPS_IM U_Data
GPS _IM U
VehicleSensor
Vehic leControlCommands_Data
VehicleControl
Vis ionObsticalDataL tVisionObsticalDataRt
VehicleControl
1 «AADLDevice_T ype»
VehicleControl
Vehic leSen sor
1 «AADLDevice_Type» VehicleSensor_Data
Veh ic leS ensor
SE Tools Study - AADL UML Profile
DEVICES
SYSTEMS Containers for Hierarchy
Note the Introduction of AADL Stereotypes
PROCESS
AADL Provides Backbone to UML
For Real-Time Embedded Systems…
16© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Integration Pilot
Evaluation of End-End Latency
XMLTeamcenter XML OSATE
Physical Architecture Capture Architecture AnalysisArchitecture Visualization
Database
system
17© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Integration Pilot
Latency Allocation & Validation Using AADL
Latency Budget Comm 2 + SW Time 2 + Switch Delay + SW Time 1 + Comm 1
18© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Integration Pilot
(OSATE) CDU Key Press Analysis
Analyze Latency…
Analyze Latency…
19© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Integration Pilot
UGS Teamcenter (Alternative Flow Analysis/Visualization)
20© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Integration Pilot - Conclusion
• Realized the value of a intermediate architecture form– Instead of publishing the internal schema of the tool
• This is the AP/STEP approach
– To simply document the semantics (as part of the translator)• Promotes a common understanding and best practices (common AND unique)
– Found AADL to be well-matched for the task• Correctness, Visualization, Modularization & Analysis Infrastructure
– QVT showing some promise• Communication & Automation
• Realized the power of Teamcenter– 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– 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”
21© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
SEI Forms Based AADL Import/Export Concept
AADL “Forms IO” Evaluation
Input Data
Excel Templates
AccessTables
XML OSATE
AADL
XML
Reformat Existing Data
into Excel Worksheets
Process using the
Forms IO Tools
Analyze/Operate using
The AADL IDE (OSATE)
22© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Agenda
Introductions
Case Studies
Concepts for Integration
Summary & Lessons Learned
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
CPU Load
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
Bus LoadABC
Schedule
Integrate, then build.
23© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for IntegrationArchitecture Modeling & Analysis - Business Adoption
• Top-Down
– Enterprise Initiatives
– Product Line
– Customer Requirements/Constraints
• Bottom-Up
– Proof of Concept
– Pursuit Strategy (cost & schedule)
– Innovative People
– Communities of Practice
• Middle-Out
– Subsystems are the common denominator
• Good place to standardize the notation
• Underneath
– AADL provides common solution space for Architecture models
• Build DSL on top
Inte
rfaces &
Serv
ices
Hie
rarc
hy &
Stru
ctu
re
Behavior
Meta-Data
24© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for Integration - AADL at Rockwell Collins
o AADL Integration Into the Development Process…
o Standards & Open Source
o Common Architecture Model
o Interface Data Specification
o AADL Tool Integration Efforts
o UML
o SimulinkTM
o Custom Tools
o Actively participates in the AADL standards development
o Rockwell Collins published AADL papers and a modest AADL example model
(www.aadl.info)
o AADL XML is used for architecture exchange behind on-going programs
o AADL Based Analysis/Deployment Tools
25© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
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
• Open Source– Accelerating Standards Adoption
– Reducing Cost of Technology
– Reinforces need for standards
– Eclipse Platform
– Domain Specific Languages
– Internal Open Source
AADL is a Key Standard
26© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Integrate &
Deploy
SW/HW
Design
Tools
External
Customers
Analysis
Tools
SYS
DesignTools
Problem
Ad-hoc approach to design and
implementation of translators
discourages reuse, couples tool versions and prevents change
Solution
Standardized Architecture Exchange
approach provides standardized
template, minimizes number of translators and promotes agility
Concepts for Integration - Common Architecture Model
Emphasis on Standard Languages and Translators – Not tools
Integrate &
Deploy
SW/HW
Design
Tools
External
Customers
Analysis
Tools
SYS
DesignTools
Translators
Architecture Template
TODAY TOMORROW
27© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
• 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 …
Concepts for Integration - Common Architecture Model
Approach
28© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
• 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…
Concepts for Integration - Common Architecture Model
29© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
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
30© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
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• Documentation, Review
• Debug and Integration
– Ease of Integration with System and Software Models
• Standardized Views are possible– Extensible Data Editor
– Report Generator
• Issues– Not Invented Here
– Verbosity
– XML with a robust schema is not light weight
• AADL currently “under the covers” for an Enterprise, component modeling toolset
31© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for Integration - Interface Data Specification
Data Dictionary Level
Data Representation Level
The Data Dictionary is the information requirement
AADL Types
AADL Implementations
32© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for Integration - Interface Data Specification
Data Dictionary
Implementation(s)
data ReceiverModepropertiesDD_Properties::Initial_Value => "State1";DD_Properties::Element_Type => MLEnumeration;DD_Properties::Element_Values => ("State1", "State2", … "State10");
end ReceiverMode;
data implementation ReceiverMode.serialsubcomponentsrcvrmode: data INT16 {Element_Properties::Initial_Value => "0";Element_Properties::Element_Enum_Values => (1, 2, 3, 4, 5, 10);};
propertiesElement_Properties::Version => "12.2.a";
end ReceiverMode.serial;
33© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for Integration - Interface Data Specification
Data Dictionary
Implementation(s)
data implementation Latitude.format2subcomponents
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;};
propertiesElement_Properties::Is_Packed => true;
end Latitude.format2;
data implementation Longitude.format2extends Latitude.format2
end Longitude.format2;
data Latitudeproperties
DD_Properties::Numeric_Type => Float;end Latitude;
Representation of
Longitude is the same…
34© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
data implementation message1.format1subcomponents
header : data header;field1 : data pl_data_defs::latitude.format1;field2 : data pl_data_defs::latitude.format2;
end message1.format1;
Concepts for Integration Collaboration & Model Organization
system implementation icd.rs422subcomponentshdr : data pl_common::Copyright_String;
msg1 : data pl_sp_messages::message1.format1;msg2 : data pl_sp_messages::message2.format1;
properties
ICD::version => "1.0";end icd.rs422;
data latitude extends pl_dd_components::latitude
end latitude;
data implementation latitude.format1properties Element::Data_Type => FIXEDPT;
end latitude.format1;
data LatitudepropertiesData_Dictionary::data_type => FLOAT;
end Latitude;Data Dictionary
Shared Data Definitions,Or Implementations
Shared Message Definitions,Or Implementations
ICD Composition
“pl” == Product Line
Independent Files for CM
35© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
(7)
( ) ( )
∑∑
∑∑∑
−
= ∈
>
−
= ∈∈
−
+⋅−+
=1
1
1
1
max
p
q Ci
i
rpr
p
q Ci
iii
Cj
j
p
q
qp
rR
sdrbb
d for p = 1, 2, ..P
port type IO_Types is
Actuator_Data_Type : type;
Sensor_Data_Type : type;
end IO_Types;
port type implementation IO_Types.others is
attributes
Actuator_Data_Type'SourceDataSize:= 12 B;
Sensor_Data_Type'SourceDataSize:= 12 B;
end IO_Types.others;
with port type IO_Types;
system ASL_and_IO_HW is
end ASL_and_IO_HW;
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; 0 2 4 6 8 10
2
0
2
Critical Points
Sum B(t) - t R
Critical Time,Tc
F(t) with d = 0
Time
Schedule
r W
ork
load
(w
hen p
osi
tive
)
Architecture Description Language
1 0 1 2 3 4 50
2
4
6
Input Envelope A*
Output Envelope B*
Input and Output Envelopes
Cum
ula
tive T
raff
ic (
By
tes)
HardwareDevelopmentand 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.lus(MM/DD/YYYY): 09/06/2001************************************************$*/#include "PFD.h"/* ============== *//* INITIALISATION *//* ============== */void Tempo_init(_C_Tempo*_C_){(_C_->_M_init_0_PFD) = true ;}void State_init(_C_State*_C_){(_C_->_M_init_0_PFD) = true ;}
Software CodeGeneration andTesting
IntegratedSystem
Simulatio
n
Validatio
n
Syste
m
Analyses
MOSTA
JCAT/JNAT
OPNET
Concepts for Integration – Custom ToolsMulti-Objective System Trade-off and Analysis (MOSTA)
36© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Concepts for IntegrationAADL 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
37© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
Agenda
Introductions
Case Studies
Concepts for Integration
Summary & Lessons Learned
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
CPU Load
0
10
20
30
40
50
60
70
80
90
100
10 20 30 40 50 60
Bus LoadABC
Schedule
Integrate, then build.
38© Copyright 2007 Rockwell Collins, Inc. All rights reserved.
AADL Applications Summary - Lessons Learned
• “Standard” sounds good to a funding source– But maybe not so good for the funding target, Definitely not so good for some vendors– Be prepared to pay for it…
• Do not under-estimate change to a Business area– 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– Sometimes they are the last ones we ask
• Evaluation and Pilot– Let the customer decide
• Common Architecture Model (CAM)– 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
• Future Work– Extend the CAM “down” for Component Modeling Integration– Extend the CAM “up” for Functional Architecture using AP233
• Requirements, Functional Architecture, Configurations
– Formal Methods Integration
AA
DL
AP
233
Current Focus