Military Aircraft
AADL-Modelling of Plug&Play Weapon
System Architecture
A. Windisch and H. Schlatt
EADS Military Aircraft, Systems Engineering
AADL Workshop 2005
Military Aircraft
Contents
• Introduction
• Notational Issues and Modelling Approach
• The PnP System Architecture
• Open Modelling Issues
• Conclusion
Page 2
AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Aircraft/Store
Aircraft
ASI
MSI
Mission
Store
Page 3
AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Aircraft/Carriage Store/Store
Aircraft
ASI
CSI
Carriage
Store
CSSI
CSSI
MSI
Mission
Store
MSCI
MMSI
Miniature Mission Stores
Page 4
AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Reference Architecture
Page 5
AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction
• Graphical Notation and Modelling Approach
• The PnP System Architecture
• Open Modelling Issues
• Conclusion
Page 6
AADL Workshop, Paris, October 2005
Military Aircraft
Data
Device
Thread
Memory
Process
Processor
Software
Software
Platform
Platform
System
Composite
Composite
Page 7
AADL Workshop, Paris, October 2005
Bus
Graphical Notation - Components
Military Aircraft
Graphical Notation - Features
Data Port
Immediate
Event Port
Event Data Port
Delayed
Ports
Ports
Client / Server
client
<name>
Subprograms
Subprograms
Page 8
Connections
Connections
AADL Workshop, Paris, October 2005
server
Military Aircraft
Modelling Approach
• The PnP technical architecture defines several
protocol layers which provide the means for
network transparent control and communication
between the aircraft and the weapon systems
• A concise system model should reflect this generic
hierarchical layered communication infrastructure
and not put any constraints on the actual physical
architecture of the aircraft/weapon system
• Modelling approach suggested in this presentation
is based on abstract buses (protocols) and abstract
processors (virtual machines) which are currently
developed as part of the AADL
Page 9
AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction
• Graphical Notation and Modelling Approach
• The PnP System Architecture
• Open Modelling Issues
• Conclusion
Page 10
AADL Workshop, Paris, October 2005
Military Aircraft
Physical Architecture
A/C Platform
Avionics Bus (e.g. 1553)
Comms IF
Computer
Mission
Computer
Store Mgmt
System
Store #1
(Weapon)
Air Data Link (e.g. Link16)
• Dynamic connectivity, i.e. air data link used for communication
with weapon after release
• Can be modelled in terms of modes (omitted in graphics)
Page 11
AADL Workshop, Paris, October 2005
Military Aircraft
Physical Architecture (cont’d)
A/C Platform
Avionics Bus (e.g. 1553)
Comms IF
Computer
Mission
Computer
Store Mgmt
System
Carriage
Store
Store Bus
Store #1
(Weapon)
Air Data Link (e.g. Link16)
Page 12
AADL Workshop, Paris, October 2005
Store #n
(Weapon)
Military Aircraft
Functional Architecture
A/C Functions
SDFile
SMS
Process
Mission
Process
Store
Process
Store Control Protocol <abstract>
Store
StoreControl
ControlAPI
API
Initialise
Initialise
Transfer
TransferData
Data
Release
Release
…
…
Page 13
• Communication between system functions
is based on abstract store control protocol
which provides API
AADL Workshop, Paris, October 2005
Military Aircraft
Store Control Protocol
Store Control Protocol <abstract>
refined to
Store Control Protocol <refined>
Store
Control
FSM
Store
Control
FSM
Store Communication Protocol <abstract>
Store
StoreCommunication
CommunicationAPI
API
Page 14
AADL Workshop, Paris, October 2005
Store
Control
FSM
Military Aircraft
Store Communication Protocol
Store Communication Protocol <abstract>
refined to
Store Communication Protocol <pre-lauch>
Store
Comms
FSM
Store
Comms
FSM
Store
Comms
FSM
LL Store Comms Protocol <1553>
Page 15
AADL Workshop, Paris, October 2005
Store
Comms
FSM
Military Aircraft
Store Communication Protocol (cont’d)
Store Communication Protocol <abstract>
refined to
Store Communication Protocol <post-launch>
Store
Comms
FSM2
Store
Comms
FSM2
LL Store Comms Protocol <link16>
Page 16
AADL Workshop, Paris, October 2005
Military Aircraft
Abstract Physical Architecture
A/C Platform
LL
LLStore
StoreComms
CommsAPI
API(2)
(2)
Messages
via
air
data
link.
Messages via air data link.
Avionics Bus
Comms IF
Computer
Mission
Computer
LL
LLStore
StoreComms
CommsAPI
API(1)
(1)
Messages
via
avionics
bus.
Messages via avionics bus.
Store Mgmt
System
Carriage
Store
Store Bus
Abstract
AbstractProcessors
Processors
Communication
Communicationservices
servicesare
are
provided
as
subprogram
provided as subprogram
features
features
Store #1
(Weapon)
Store #n
(Weapon)
Message
MessageRouter
Router
Transparent
Transparentrouting
routingof
ofall
all
Air Data Link store
communication
store communication
messages
messagesbetween
between
avionics
&
weapon
avionics & weaponbus
bus
Page 17
AADL Workshop, Paris, October 2005
Military Aircraft
A/C Functions
PnP
Systems Architecture
SDFile
Store Control
Protocol
Store Comms
Protocol
Router
Store Communication
Protocol
Avionics Bus (e.g. 1553)
Comms IF
Computer
Mission
Computer
Store Mgmt
System
Carriage
Store
Store Bus
Store #1
(Weapon)
Air Data Link (e.g. Link16)
Page 18
AADL Workshop, Paris, October 2005
Store #n
(Weapon)
Military Aircraft
Contents
• Introduction
• Graphical Notation and Modelling Approach
• The PnP System Architecture
• Open Modelling Issues
• Conclusion
Page 19
AADL Workshop, Paris, October 2005
Military Aircraft
Open Modelling Issues
• I01: The hierarchical refinement of protocols into
systems requires a generic specification of
protocol layers which is unfolded at instantiation
time (e.g. see VHDL generics)
• I02: The system boundaries of the presented
model show the layered architecture of the
distributed system, however, an “integration”
perspective might be desirable where the system
boundaries reflect the borders of the physical
systems
• I03: The graphical representation of binding
between layers requires an huge amount of
arrows. This could be reduced by means of a
deployment view.
Page 20
AADL Workshop, Paris, October 2005
Military Aircraft
Open Modelling Issues – Integration Perspective
SDFile
Avionics Bus (e.g. 1553)
Comms IF
Computer
Mission
Computer
Store Mgmt
System
Carriage
Store
Store Bus
Store #1
(Weapon)
Store #n
(Weapon)
Air Data Link (e.g. Link16)
Aircraft
Page 21
AADL Workshop, Paris, October 2005
Store System
Syntactically
Syntactically
incorrect
incorrectAADL
AADL
specification
specification!!
Potentially
a tool issue
rather than
a language
aspect
Military Aircraft
Contents
• Introduction
• Graphical Notation and Modelling Approach
• The PnP System Architecture
• Open Modelling Issues
• Conclusion
Page 22
AADL Workshop, Paris, October 2005
Military Aircraft
Conclusion
• This presentation showed a first approach of a
PnP system architecture which focuses on the
layered approach taken by the PnP technical
architecture
• Modelling was based on the notion of abstract
buses (protocols) and abstract processors (virtual
machines)
• The approach allows for the explicit specification
of all network transparent APIs, i.e. the store
control API and the store communication API
Page 23
AADL Workshop, Paris, October 2005