AADL and MDA. Early Experience Applied to Aircraft-Weapon Integration. Yves LaCerte

Transcription

1 AADL and MDA Early Experience Applied to Aircraft-Weapon Integration Yves LaCerte 3 February 2005

2 Agenda Introduction Weapon Management System - WMS Embedded Systems Plug and Play Concept Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA 2

3 Introduction The aircraft-weapon integration challenge is part of a larger integration problem, i.e. Independent system-specific models often create unsolvable interoperability problems Tower of Babel Build a tower to the sky Workers speak different languages Cooperation collapsed 3

4 Introduction Semiotics, a field of linguistics A science which studies the role of signs as part of social life * Syntax: structure of signs Semantics: meaning of signs as captured by syntax Pragmatics: adaptable interpretation of signs based on context * Saussure, Ferdinand de, Course in General Linguistics (trans. Roy Harris), London: Duckworth,

5 Agenda Introduction Weapon Management System - WMS Embedded Systems Plug and Play Concept Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA 5

6 POD AVAIL INV STRT TTV XMIT HI SYNC OFF ACPT TGT SLMR SONO SAFE XMIT POD CONTROL SLAM ER POST LAUN CH STA 11 STA 13 CO OP STA 14 STA16 12/ /12 12 /12 12/12 09/12 59:5 9 59:59 59:59 59:59 58: 59 KILL SAFE AIMS SS- 3 FULL SCRN TOO ASUW TRCK MODE PREV TGT RJCT TGT PRE LNCH MASTER AR M BOMB BAY SRC H PWR ON OPEN ON ARM HAZARD RESET AR M HAZARD J E T T I S O N OFF KILL R EADY SONO DISABLE C LOSED J E T T I S O N J E T T I S O N OFF J E T T I S O N INV LATIT UDE: LONGITUDE: ALTIT UDE: AIR SP EED: HEA DI NG: X VELOCITY: Y VELOCITY: Z VELOCITY: AZIMUT H: PITCH: ROLL: WANDER ANGLE: MESSAGE COU NT: SONO NAVIGATION SYSTEM BI T SAFE RIN U BUS BUS RIN U 1 A B 2 N42: W FT 295 KTS 45.0 T LATIT UDE: LONGITUDE: ALTIT UDE: AIR SP EED: HEA DI NG: X VELOCITY: Y VELOCITY: Z VELOCITY: AZIMUT H: PITCH: ROLL: WAN DE R A NGLE: MESSAGE COU NT: KILL SAFE BUS A N42: W FT 295 KTS 45.0 T MESSAGE ERRO RS: 1 MESSAGE ERRO RS: 0 PORT TAC MSN TAP NAV RA D TMPS EO/IR CYZ A/C WIC MC SYS BUS B Definition WING ONLY Mission System Video 1553 Eth Video RINU 1553 Aircraft Discretes 1553 Eth Video Radar RS-232 RS-232 Starboard Port R A 9 R A L R A L R A R A L Starboard Wing Stations Racks 1760 ASI Legacy ASI L A R A R L A R L A R A R Weapons Bay Port Wing Stations Primary electrical, functional and logical interface between the Mission Management Computer(s), weapons, launchers and other equipment used to release and deliver stores 6

7 Motivation Today, $100M (typically)* 40% to 60% is software updates (typically)* Aerodynamics Platform software Mission Planning Misc. * Source: AFRL/MN, 1999 System Eng. Int. & Test 7

8 Test and Integration Challenges Platform Perspective Provide relevant functions and data Weapon Perspective * Identify/define relevant functions and data Observe resource, performance and timing constraints Identify/define resource, performance and timing constraints Do not change platform software * Weapon software does change over time, which may impact the platform 8

9 Cost / Schedule Perspective (Notional) WMS Development Costs Number of Months to Integrate a New Weapon $ No need to take down the whole squadron New WMS Weapon 3 Weapon 3 Weapon 2 Weapon 2 Weapon 1 Weapon 1 Traditional New Traditional New Do not change platform software 9

10 Agenda Introduction Weapon Management System - WMS Embedded Systems Plug and Play Concept Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA 10

11 State of the Art Increasing complexity / decreasing productivity six (or fewer!) lines per day * The inefficiency of the embedded software development process will prevent novel technologies from entering the marketplace in time * Typical of embedded software industry 11

12 Characteristics Resource constrained CPU, memory, size, weight and power Hard Real Time Functional and non-functional aspects Safety Critical Dependable / Certifiable Long Lifetime Several upgrades / increasing complexity 12

13 Embedded Systems: Solutions / Trends Components Less dedication to specific functions Design - Improved abstraction Synthesis - Auto code generation Models - Assess before final implementation Specification languages Unambiguous representation of behavior and constraints - Rigorous semantics Widely accepted 13

14 Embedded Systems: Solutions / Trends Dynamic Reflective Systems Change internal behavior depending upon attached devices Capable of integrating devices which provide new functions Capable of providing unforeseen functionality Foundation of aspect-oriented programming 14

15 Embedded Systems: Solutions / Trends Semantic Interface Specification Syntax can be performed by any type of Interface Definition Language (IDL, XML) Assess semantic properties of an interface by an executable interface model Assess interoperability by analyzing provided and required interfaces, and contracts Adapt interface to improve interoperability AADL Semantic Interface Specification 15

16 Embedded Systems: Solutions / Trends Applied to Aircraft-Weapon Integration Integrate new capabilities within a given design space (domain) Prevent waiting for an aircraft upgrade cycle to integrate new weapons But Likely difficult to implement a dynamic system that meets performance constraints Aircraft-Weapon interface standards is a recent development, change is slow 16

17 Agenda Introduction Weapon Management System - WMS Embedded Systems Plug and Play Concept Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA 17

18 The Plug and Play Concept Demonstrate interoperability at design time In terms of Functionality and Data Open system approach via standards In terms of Non-Functional Quality Attributes Safety, real-time, reliability, fault tolerance, security. A system that can exchange information and services with multiple systems is more interoperable than one that can't Semantic Interface Assess the quality of interoperability Specifications Formulate strategies to improve interoperability 18

19 Domain Model Weapon Interface View Platform WMS Missile Select Missile Apply power Initialize Configure Set mission parameters Set missile modes etc Select State Release Jettison Get Status IBIT Get current configuration The WMS accepts generic missile commands. These are subsequently passed on to the missile. 19

20 Domain Model Mission Interface View Platform WMS Missile Set Mission Plan Set Target Acquisition Set Platform Characteristics Set Environment Configure Configure Configure Configure The WMS offers mission services that are non-missile specific. Configuration data is subsequently passed on to the missile. 20

21 Domain Model - Life-Cycle View Start Mission Missile Selected Setup Status Ready Standby Identification IBIT On Mission Configure Initialization IBIT Off Ready for Release System Off Non Operational Mission Committed Executing Mission Release Prepare to Release Hung Flight Failed Disabled Jettison Detonation 21

22 Domain Model - Data View Weapon Launch Acceptability Region 22

23 State Machines Preferred for the specification of controllers Remove_Operational_Power Operational State Progress To Release Prepare For Release Release Useful for Verification against requirements Test-case generation Automatic code generation Off> Apply_Operational_Power Remove_Operational_Power Initialization> Error Non-Operational IBIT Control Progress to Jettison Not Running IBIT> Prepare for Jettison> Running IBIT Jettison> API and events used to cause state changes 23

24 Ports Connectors Contracts Port Connector WMS Provided Interface Power Required Interface Weapon Component Contract <<interface>> Power 115 volts() AC 3 phase Pre and Post conditions Parameter types Synchronization constraints QoS features 115 volts() AC 3 phase «interface» Power Weapon requires power. Power provided by WMS 24

25 Agenda Introduction Planning System Laser Weapon Management - WMS Imaging Embedded Systems Plug and Play Concept System Navigation System Mission Fire Control System External Comm Operator I/F Generic Weapon Management System Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA Power_A 1 553_A D iscr e te_a Power Controller B r _ e w o P Launcher Launcher Launcher B B 3 t e 5 r e c 1 is D Weapon Missile Missile 25

26 Platform Challenge Component models and supporting frameworks often rely on the specifics of the underlying platform There is a need for techniques to handle functional and non-functional properties of components and systems AADL addresses non-functional properties 26

27 AADL Summary Purpose Analyze embedded systems Focus Software system architecture model of an execution platform Software components bound to hardware components Standardization Efforts SAE AS5506 UML profiles 27

28 UML Profiles UML 2.0 Embedded Systems Activity Diagrams Assembly Diagrams AADL SysML Parametric Diagrams Requirement Diagrams 28

29 AADL Components Types UML 1.x and UML 2.0 profile work in progress 29

30 AADL Components Types device Physical devices that interface with an external environment memory Randomly accessible physical storage such as RAM or ROM bus Communication channels that can exchange control and data between processors, memories, and devices processor Abstraction of hardware and software that is responsible for scheduling and executing threads System Composition of software and execution platform components Icons from SAE AS5506 AADL Annex Process Space partitions in terms of virtual address spaces ThreadGroup Structural grouping of threads within a process Thread Units of concurrent execution Data Static data in source text Subprogram Source text that is executed sequentially 30

31 System Example 31

32 System Construction Example system MILSystem end MILSystem ; system implementation MILSystem.MissilePlatform subcomponents connections end MILSystem.MissilePlatform ; subcomponents -- buses Power_A : bus MILPower; -- components WMS1 : system WMS.WMS; FCS : system FireControlSystem.FCS; connections -- bus access bus access Power_A -> Power1.IFPower_A; bus access Power_A -> WMS1.IFPower_A; -- ports port group WMS1.Out1553_A -> Launcher1.In1553_A; 32

33 System Construction Example Black Box WMS Port Provided Interface Connector Power Required Interface Weapon Component Contract <<interface>> Power 115 volts() AC 3 phase Pre and Post conditions Parameter types Synchronization constraints QoS features «interface» Power 115 volts() AC 3 phase system FireControlSystem features IFGeneric: requires bus access MILGeneric; InMission: port group Rx_Port; OutMission: port group Tx_Port; end FireControlSystem; system implementation FireControlSystem.FCS end FireControlSystem.FCS ; 33

34 System Construction Example Black Box system WMS features -- Buses IF1553_A: requires bus access MIL1553; IFGeneric: requires bus access MILGeneric; IFPower_A: requires bus access MILPower; IFDiscrete_A: requires bus access MILDiscrete; -- Ports port group Rx_Port In1553_A: port group Rx_Port; features Out1553_A: port group Tx_Port; Rx: in data port; InDiscrete_A: port group Rx_Port; inverse of Tx_Port OutDiscrete_A: port group Tx_Port; end Rx_Port; OutPower_A: port group Tx_Port; InMission: port group Rx_Port; port group Tx_Port OutMission: port group Tx_Port; features end WMS ; Tx: out data port; end Tx_Port; 34

35 WMS System Implementation Example White Box Factory Pattern system implementation WMS.WMS subcomponents connections modes end WMS.WMS ; subcomponents --- processors --- processes --- bindings connections --- port groups modes MainMode: initial mode; BackupMode: mode; 35

36 Process process PlugandPlayDispatcher features InGeneric: port group Rx_Port; OutGeneric: port group Tx_Port; InLauncher: port group Rx_Port; OutLauncher: port group Tx_Port; InWeapon: port group Rx_Port; OutWeapon: port group Tx_Port; end PlugandPlayDispatcher; 36

37 Process Implementation process implementation PlugandPlayDispatcher.WMS subcomponents Bus_Listener: thread Listener.Bus_Listen; PnP_Dispatcher: thread PnPDispatcher.WMS; connections port group InGeneric -> Bus_Listener.Bus_Listener; port group Bus_Listener.Buffer_Update -> PnP_Dispatcher.InPnP; port group PnP_Dispatcher.OutLauncher -> OutLauncher; port group InLauncher -> PnP_Dispatcher.InLauncher; port group PnP_Dispatcher.OutWeapon -> OutWeapon; port group InWeapon -> PnP_Dispatcher.InWeapon; end PlugandPlayDispatcher.WMS; 37

38 Time-Space Partitioning A Process Processor Partition 1 Partition 2 Partition n B Process N Process Processor PPC End PPC; Processor implementation PPC.two Subcomponents partition1: processor RMA.impl; partition2: processor RMA.impl; End PPC.two; System implementation ESys.impl Subcomponents platform: processor PPC.two; app: system userapp; Properties Binding => platform applies to app; End ESys.impl; 38

39 Thread Producer Consumer thread Dispatcher features Buffer_Listener: port group Rx_Port; Bus_Dispatcher: port group Tx_Port; Buffer_2: requires data access Buffer; properties Source_Text => "abc"; Source_Code_Size => 100 kb; Source_Data_Size => 10 kb; Source_Stack_Size => 10 kb; Source_Heap_Size => 10 kb; Dispatch_Protocol => periodic; Period => 100 ms; Deadline => 100 ms; Compute_Execution_Time=> 5ms; 39

40 Trade-offs Producer Consumer Event-Driven with Publish-Subscribe 40

41 Tools - OSATE Open source AADL tool environment Software Engineering Institute Set of plug-ins on top of Eclipse 41

42 OSATE Plug-ins Analysis Schedulability System scalability Safety End-to-end flow analysis AADL support from UML vendors 42

43 Agenda Introduction Weapon Management System - WMS Embedded Systems Plug and Play Concept Architecture Analysis and Description Language - AADL Model Driven Architecture - MDA 43

44 Approach to MDA Core Reusable Corporate Assets Domain Requirements Application Requirements Platform Requirements Platform Independent Model Platform Independent Model T E Platform Specific Model C G Executable System V E Validated System Domain Application Product Instance Executable Product Validated Product TE = Transformation Engine CG = Code Generator VE = Validation Engine 44

45 Approach to MDA / AADL Derive system properties Platform Requirements UML Model C G Executable System Prove system properties Product Instance Executable Product Platform Requirements T E AADL Model C G Executable System A A D L Validated System Product Executable Validated Instance Product Product 45

46 MDA Work Products Application Requirements Platform Independent Model Context View Requirements View Analysis View Design View Queries Application Platform Requirements Guidelines and Rules Platform Model Libraries Patterns T E Platform Specific Model Product Instance AADL Model ready for analysis UML Model ready for code generation 46

47 MDA / AADL Expectation Development Costs for New Weapons Development Costs for New Weapons $ W i t h o u t M D A New WMS $ M D A New MWS Weapon 3 Weapon 3 Weapon 2 Weapon 2 Weapon 1 Weapon 1 Traditional New Traditional New 47