AADL-Modelling of Plug&Play Weapon System...
Transcript of AADL-Modelling of Plug&Play Weapon System...
Military Aircraft
AADL-Modelling of Plug&Play Weapon System Architecture
A. Windisch and H. SchlattEADS Military Aircraft, Systems Engineering
AADL Workshop 2005
Page 2 AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction• Notational Issues and Modelling Approach• The PnP System Architecture• Open Modelling Issues• Conclusion
Page 3 AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Aircraft/Store
ASI
Aircraft
MissionStore
MSI
Page 4 AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Aircraft/Carriage Store/Store
Miniature Mission Stores
ASI
CSSI
Aircraft
CarriageStore
MissionStore
MMSI
CSI
MSI
CSSI
MSCI
Page 5 AADL Workshop, Paris, October 2005
Military Aircraft
Introduction – Reference Architecture
Page 6 AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction• Graphical Notation and Modelling Approach• The PnP System Architecture• Open Modelling Issues• Conclusion
Page 7 AADL Workshop, Paris, October 2005
Military Aircraft
Graphical Notation - Components
PlatformPlatform
CompositeComposite
SoftwareSoftware
Process
Thread
Data
System
Processor
Device
Memory Bus
Page 8 AADL Workshop, Paris, October 2005
Military Aircraft
Graphical Notation - Features
ConnectionsConnectionsSubprogramsSubprograms
PortsPorts
<name>
Data Port
Event Port
Event Data Port
Immediate
Delayed
client server
Client / Server
Page 9 AADL Workshop, Paris, October 2005
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 10 AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction• Graphical Notation and Modelling Approach• The PnP System Architecture• Open Modelling Issues• Conclusion
Page 11 AADL Workshop, Paris, October 2005
Military Aircraft
Physical Architecture
A/C Platform
Air Data Link (e.g. Link16)
Avionics Bus (e.g. 1553)
Comms IFComputer
MissionComputer
Store MgmtSystem
Store #1(Weapon)
• 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 12 AADL Workshop, Paris, October 2005
Military Aircraft
Physical Architecture (cont’d)
A/C Platform
Store #n(Weapon)
Store #1(Weapon)
Air Data Link (e.g. Link16)
Avionics Bus (e.g. 1553)
Store Bus
Comms IFComputer
MissionComputer
Store MgmtSystem
CarriageStore
Page 13 AADL Workshop, Paris, October 2005
Military Aircraft
A/C Functions
Functional Architecture
Store Control Protocol <abstract>
MissionProcess
SMSProcess
StoreProcess
Store Control APIInitialiseTransfer DataRelease…
Store Control APIInitialiseTransfer DataRelease…
• Communication between system functions is based on abstract store control protocol which provides API
SDFile
Page 14 AADL Workshop, Paris, October 2005
Military Aircraft
Store Control Protocol <refined>
Store Control Protocol
Store Communication Protocol <abstract>
Store Control Protocol <abstract>
StoreControl
FSM
StoreControl
FSM
StoreControl
FSM
Store Communication APIStore Communication API
refined to
Page 15 AADL Workshop, Paris, October 2005
Military Aircraft
Store Communication Protocol
Store Communication Protocol <abstract>
refined to
Store Communication Protocol <pre-lauch>
LL Store Comms Protocol <1553>
StoreComms
FSM
StoreComms
FSM
StoreComms
FSM
StoreComms
FSM
Page 16 AADL Workshop, Paris, October 2005
Military Aircraft
Store Communication Protocol (cont’d)
Store Communication Protocol <abstract>
refined to
Store Communication Protocol <post-launch>
LL Store Comms Protocol <link16>
StoreCommsFSM2
StoreCommsFSM2
Page 17 AADL Workshop, Paris, October 2005
Military Aircraft
Abstract Physical Architecture
A/C Platform
Store #n(Weapon)
Store #1(Weapon)
Air Data Link
Avionics Bus
Store Bus
Comms IFComputer
MissionComputer
Store MgmtSystem
CarriageStore
Abstract ProcessorsCommunication services are provided as subprogram features
Abstract ProcessorsCommunication services are provided as subprogram features
LL Store Comms API (1)Messages via avionics bus.
LL Store Comms API (1)Messages via avionics bus.
LL Store Comms API (2)Messages via air data link.
LL Store Comms API (2)Messages via air data link.
Message RouterTransparent routing of all store communication messages between avionics & weapon bus
Message RouterTransparent routing of all store communication messages between avionics & weapon bus
Page 18 AADL Workshop, Paris, October 2005
Military Aircraft
PnP Systems ArchitectureA/C Functions
Store ControlProtocol
Store #n(Weapon)
Store #1(Weapon)
Air Data Link (e.g. Link16)
Avionics Bus (e.g. 1553)
Store Bus
Comms IFComputer
MissionComputer
Store MgmtSystem
CarriageStore
Store Communication Protocol
Store CommsProtocol Router
SDFile
Page 19 AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction• Graphical Notation and Modelling Approach• The PnP System Architecture• Open Modelling Issues• Conclusion
Page 20 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 21 AADL Workshop, Paris, October 2005
Military Aircraft
Open Modelling Issues – Integration Perspective
Aircraft Store System
Store #n(Weapon)
Store #1(Weapon)
Air Data Link (e.g. Link16)
Avionics Bus (e.g. 1553)
Store Bus
Comms IFComputer
MissionComputer
Store MgmtSystem
CarriageStore
SDFile
Potentially a tool issue rather than a languageaspect
Syntactically incorrect AADL specification !
Syntactically incorrect AADL specification !
Page 22 AADL Workshop, Paris, October 2005
Military Aircraft
Contents
• Introduction• Graphical Notation and Modelling Approach• The PnP System Architecture• Open Modelling Issues• Conclusion
Page 23 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