Applying SysML to Analyze and Design Large Complex Systems

1. 2008 Frontiers in Design & Simulation Workshop Georgia Institute of Technology May 2008 Applying SysML to Analyze and Design Large Complex Systems John Watson MS2, Moorestown, NJ May 2008

2. Objective • To share with you our experience: • How SysML can be used to capture System Engineering artifacts including system Structure, Behavior and Requirements • How SysML/UML models can be hierarchically related and interconnected • How the models are used to derive and allocate requirements producing a specification to drive lower level models • How information can be extracted from the models to other tools, such as Performance Simulation tools, to refine and update model artifacts • An Example of extracted data relative to Performance and Deployment Analysis May 2008

3. Shipboard Combat System ..* May 2008

4. Transition to Model Driven Environment Trade Studies, R&D, Simulation, Specification Reviews, etc. UC UC UC UC UC . . . . . . . . . . Trade Studies, R&D, Simulation, Specification Reviews, etc. Trade Studies, R&D, Simulation, Specification Reviews, etc. . . . Comp 1 Software Comp X Software • System-of-System Level • 1st Level Of Decompositions • How Our System Contributes to the Overall Mission System 2 Spec System 1 Spec Mission Concept of Operations Behavior, Structure & Requirements • System Level • Derives Subsystems • Allocates Requirements to Subsystems Sub System 2 Spec Sub- System 1 Spec . . . A-Spec • Subsystem Level • Derives Hardware and Software Components • Allocates Requirements to Components Behavior, Structure & Requirements SW Comp X Spec SW Comp 1 Spec . . . B-Spec Behavior, Structure & Requirements Component Design & Implementation Level May 2008

5. Component Domain Model 2 … … S/W S/W H/W S/W S/W Model Tree SoS Analysis System of Systems Model - System Specification Spec S1 System Analysis Combat System Model - Subsystem Specification Spec 1 Spec 2 Spec n ... Weapon Control Subsystem Model Subsystem Analysis Radar Subsystem Model Display Subsystem Model …. …. Spec 1 Spec 2 Spec 3 Spec 4 Spec 5 Spec 6 Spec 1 Spec 1 Spec n Spec n • Component • Specification Component Analysis - Design - Implementation Component Domain Model 1 May 2008

6. Block Definition Diagram System Decomposition Process Combat System Sequence Diagram Control UC UC Sensor * 1 5 Combat System Execute Service . . . . . . . . . . Control Sensor Weapon User Sensor Subsystem Test Weapon HMI Record Status Review Results 5 Comms 1 3 Control Subsystem Weapon Subsystem Comm Subsystem Internal Block Diagram 3 Sensor 1 Control Trade Studies, R&D, Simulation, Specification Reviews, etc. 1 Weapon Analyze System Level Requirements Input Analyze System Services Identify the Substructure Analyze SubstructuresCollaboration to Satisfy the System Services Incorporate Additional Analysis as Needed Derive and Allocate Requirements to Sub-Structure The Subsystem shall .... Derived Requirements Yes Continue? No Complete Substructure Specs May 2008

7. System Sequence Diagram Engmt Control Sensor Execute Service Control Sensor User Weapon Test Weapon R1 R2 R3 Record Status Review Results Engmt Control Engmt Control Weapon User Sensor Execute Service User Sensor Weapon The Connect Specification Behavior Structure Context R4 R5 Requirements May 2008

8. Regional Defense Mission Satellite Satellite Control Engage Detect Weapons Targets Weapon Platform Sensor Platform Tactical Ops Center May 2008 May 2008

9. System of System Use Case – “Defend Region” May 2008

10. System of System Use Case Use Case – “Defend Region” Tac Ops Center Weapon Platform Sensor Platform Satellite Satellite Weapon Target 1. Reflect Energy Maximum Messages/Sec 2. Process Reflections 3a. Forward Detection 4a. Process Detection 3b. Forward Detection 4. Evaluate Track 5. Engage Target 5. Fire Weapon 6. Guide Weapon 7. Kill Target # of Simultaneous System Targets Delay from Detection to Weapon Guidance May 2008

11. Driving Down Through the Models UC UC UC UC . . . . . . . . . . Simulation Task: - SW Component Deployment - Closed Loop Response Times - Computer Utilizations - Simultaneous Engagements Trade Studies, IR&D, Simulation, Reviews, etc. • System-of-System Level • 1st Level Of Decompositions • How Our System Contributes to the Overall Mission Weapon Platform Spec System 1 Spec Behavior, Structure & Requirements • Weapon Platform System • Derives Subsystems • Allocates Requirements to Subsystems Sub- System 1 Spec . . Engagement Subsystem Spec • Engagement Subsystem • Derives Hardware and Software Components • Allocates Requirements to Components Behavior, Structure & Requirements Component Design & Implementation Level May 2008

12. Engagement Subsystem Level – Use Case Sequence Diagram Launcher A1 Engagement Mgr A3 Acquisition Component A2 Engagement Component B1 Missile Component A4 Sensor Boundary Sensor Engage Launch (Now Launch T1 Launch Xn Component = Node 1 Missile Away (Time) Report Launch Status Report Launch Time Xn Component = Node 2 Request Missile Data Request Missile Data Xn Component = Node 3 [ Until Intercept at X Hertz] Loop Process AMR T2 Forward Guidance Information Guide Missile Architectural Attributes Need to be added: We Capture Message Sequencing and Component Deployment Using Infrastructure Modeling Assemblies (IMAs) May 2008

13. D0 MW Prcl MW/S MW/S MW/S MW MW MW Prcl Dn S/MW S/MW S/MW S/MW D1 T T T I I I O O O O O O The Simulation Palette Imitates The Engagement Sequence Using IMAs B1 Launch A1 Engage A2 Launch (Now) Launcher T1 1b A1 • Architectural Attributes: • Msg Rate: • Msg Items: • Msg Size: • Schedule Method: • Msg Ack: • Proc Time: • Destination Node: B1 Missile Away C1 Sensor Response A3 Request Missile Data A2 A4 A2 A4 Gx Sensor Periodic 2b 2a Reusable Design Palette of Infrastructure Modeling Assemblies (IMA) S Switch End UDP/IP Protocol Only Delay Out MW Appl Only Out MW & Protocol In MW In/Out MW & Protocol In MW & Protocol 1a Tn Tn Application IMAs Gx Middleware Only Latency Probe Periodic Message Generator Time Tn May 2008

14. Deployment Analysis Assumes a Distributed Computing Architecture How many Missile components per CPU? Node 2 Missile Component P R O T O C O L How many Engagement components per CPU? Node 1 Middle -ware Missile Component P R O T O C O L Network Switch & Router Engagement Component Middle -ware Engagement Component Engagement Component Engagement Component Node 3 Missile Component P R O T O C O L Middle -ware Missile Component What is the impact of Middleware, Protocol and Switch Latencies? Engagement Component Simulations Use The LM-ATL Proprietary IMAs With The CSIM Event Driven Tool May 2008

15. Summary • These modeling techniques and procedures are being used at MS2 today • Significant areas of the system have been successfully re-engineered without impacting other areas • UML model artifacts are being used to drive CSIM Simulations for analysis and deployment of time critical threads • Future: • Parametric Diagrams to Feed the CSim Simulation Tool • MARTE – Timing Specifications • Leverage Pockets of MBSD across Lockheed May 2008