ESTEC, June 9 th, 2016

Transcription

1 System Concept Simulation for Concurrent Engineering Final Presentation Stephan Kranz ESTEC, June 9 th, 2016 Telespazio VEGA Deutschland

2 Overview SYSTEM CONCEPT SIMULATOR Study Logic Use Cases / User Requirements Architectural Design Workbench Prototype Validation & Verification Conclusions 2

3 Study Logic STUDY LOGIC TPZV J-CDS / RHEA Main contract, planned: 14 month Management Extension, planned: 11 month Management CCN Requirements Consolidation + Preliminary Design Design Verification by Demonstration Implementation Sprint 1 to 5 Implementation Sprint 6 + Software V & V Implement. Sprint Implement. Sprint 9 Software V & V KO 1 PDR CDR AR1 KO2 AR2 07/ / / / / /2016 3

4 High Level Use Cases HIGH LEVEL USE CASES CDF Support (0/A) time frame! Support to Mission Study Teams (A/B1) Support to S/C project teams (B) Mission profile presentation at Kick Off Online and offline session support Reporting and presentation of results (data postprocessing and visualisation) 4

5 User Requirements from Stakeholder Interviews (RHEA) SIMULATION SETUP Create or extend models Import models Simulation Engineer Setup simulation Create or reuse setup Configure simulation Import data (IDM) Provide Models Input for setup System Engineer Configure visualisation Schedule simulation Domain Engineer 5

6 User Requirements from Stakeholder Interviews (RHEA) SIMULATION EXECUTION Simulation M&C Control visualisation Simulation Engineer Run simulation Debug models Batch mode Create breakpoints Monitor simulation Support simulation System Engineer Runtime Analysis Record & replay Domain Engineer 6

7 User Requirements from Stakeholder Interviews (RHEA) SIMULATION RESULTS CAPTURING Store results Store meta information Simulation Engineer Capture/ share results Data for visualisation Data for analysis Data for post processing Import results Post processing System Engineer Filter data Export data (IDM) Domain Engineer 7

8 Lesson learned from Previous Projects USER INTERFACE + DATAMODEL Project Test Bed (PTB) + Simple datamodel and very easy implementation (C-code) + Very flexible - Lack of model catalogue concept (common vs. mission specific models) - Limited number of verified and validated models for reuse. - Different tools with manual data transfer in-between SimVis + Separation of type from instance (SMP2) -> reuse possible + Easy implementation (C++ code with skeleton generator) - (too) complex data model - Confusing integration - Different tools with manual data transfer in-between SCS: + SMP2 subset only (dataflow) + Diagram based Integration (Simulink alike) + Integrated into a single tool / UI + User (J-CDS) in development loop with Design Verification 8

9 System Concept Simulator Design SCS FUNCTIONAL COMPONENTS Engineering model Database (OCDT) Simulation Results Modelling Mission Management Simulation Execution Data Processing Model Development Setup Management Simulator Environment Plotting Auto Coding Model Import Simulation Composition Simulation Initialisation Debugging Monitoring and Control Surface Maps 3D Visualisation Validation Timeline Recording Playback Simulation Artefacts Repository 9

10 SCS Workbench Prototype SCS PROTOTYPE COMPONENTS Engineering model Database (OCDT) Simulation Results Modelling Mission Management Simulation Execution Data Processing Model Development Setup Management Simulator Environment Plotting Auto Coding Model Import Simulation Composition Simulation Initialisation Debugging Monitoring and Control Surface Maps 3D Visualisation Validation Timeline Recording Playback Simulation Artefacts Repository 10

11 SCS Workbench Prototype SOFTWARE COMPONENTS Java based Eclipse rich client application + EMF SMP2 standard (Dataflow flavour only) ESA Universal Modelling Framework (UMF) Eclipse Sirius based UI Eclipse C/C++ Development Tool using GCC Compiler and GDB Debugger ESA SimSat Simulation Runtime Environment Eclipse Public Licenses + ESA licenses Eclipse CDT MinGW, GCC, GDB SCS Workbench Eclipse Sirius ESA UMF Eclipse EMF Eclipse RCA SMP2 ESA SimSat C++ 11

12 SCS Workbench Prototype MODEL DEVELOPMENT CATALOGUES 12

13 SCS Workbench Prototype CODE GENERATOR AND EDITOR 13

14 SCS Workbench Prototype SIMULATION COMPOSITION 14

15 SCS Workbench Prototype SIMULATION CONFIGURATION 15

16 SCS Workbench Prototype SIMULATION SCHEDULING 16

17 SCS Workbench Prototype SETUP SCENARIO SIMULATION 17

18 SCS Workbench Prototype SIMULATION EXECUTION 18

19 SCS Workbench Prototype SIMULATION DEBUGGING 19

20 Design Verification by Demonstration (RHEA) VERIFICATION FROM USER PERSPECTIVE Testing Description Step Name Section in SUM Version 1 Testing Description Comments for testing step execution Testing Results 1 Defining a Mission 5.1 Added 6 mission during Quick and easy to define new pass high high high Validate chosen approach, design choices and implementation robustness combined testing with mission simulation testing - setup and from a user perspective get simulation running using provided Counter-example, and trying to (re-)create Counter Basic Tests example 2 Defining an Assembly 5.2 Added various assemblies using already available models in Quick and easy to define new assembly pass high high high Deployment and Installation Test Pass/Fail Flexibility User Friendline ss catalogues 2.1 Create assembly 5.2 For each mission, create on Quick and easy to create new pass high high high average 2 assemblies assembly 2.2 Link Catalogues to 5.2 For each mission, link to Quick and easy to define link, only Use Case Testing Mission Counter-model catalogue, and requires single action pass high high high possibly other available catalogue 2.3 Add Models to 5.2 Add models to assembly by Adding models as needed from pass high high high Assembly drag-and-drop available catalogues; for Counterexample Counter and Reset-model 2.4 Create Field Links 5.2 Create links between outputs Inputs and outputs connected of pass high mediu high between Models and inputs Counter-models Counter and Reset m according to example setup 3 Defining a Setup 5.3 Create and edit setup Define default setup with purpose to pass high high high get to deployment quickly 3.1 Create Setup 5.3 Create with default Scenario, All defaults used pass high high high Configuration, Simulation and Schedule 3.2 Deploy to SimSat 5.3 deploy to SimSat and run Minor point: information missing in pass N.A. mediu high simulation SUM, running simulation requires m code to be already generated. If this is done, and code is correct, in principle a simulation can be run. Posted Issue for missing step of generating code. Questions and bugs were reported and handled in JIRA + Basic design considered sufficient and acceptable + Time requirements can be met - Missing Management Layer (User access rights) +/- Data handling scaleability -> additional filtering Usage of UI 20

21 Software Verification and Validation JIRA ISSUE TRACKING Created Resolved : 83% at AR2 21

22 Conclusions CONCLUSIONS + NEXT STEPS Achieved: Specification of SCS use cases SCS Architectural design Implementation of SCS Workbench prototype Design Verification Further Proof of Concept: Interface to OCDT Integration and Management of external models Visualisation / Monitoring Recording & Playback 22

23 Outlook REUSE IN OTHER PROJECTS NGT-ATB Configuration Tool 23

24 THANK YOU FOR YOUR ATTENTION Telespazio VEGA Deutschland 24