Architecting System-of-Systems

Transcription

1 Architecting System-of-Systems from basic concepts towards a SoS profile & supporting tools paolo lollini university of florence, italy p. arun babu resiltech s.r.l, italy

2 Slides can be found at 2

3 Overview 0. Introduction 1. Introduction to the AMADEOS conceptual model for SoS 2. The AMADEOS SysML profile Introduction to MDE and SysML basic modeling constructs The AMADEOS SysML profile introduction, overview, and role in MDE Example AMADEOS profile applications, demos, and exercises 3. AMADEOS architectural framework 4. AMADEOS supporting facility for designing SoS Goals Google Blockly Supporting facility using Blockly Customization... 3

4 Model driven engineering What? Figure: Difference between a model and a system A model could be: a small scale version of a system, software simulation, 3d design, UML/SysML design, etc. Usually, Model is not equivalent to System 4

5 Model driven engineering Why? Low cost Easily understood Easy to test in a controlled environment Easy to modify the model if not satisfied 5

6 Model driven engineering Why? Low cost Easily understood Easy to test in a controlled environment Easy to modify the model if not satisfied 6

7 Example of models (in general) Model organism. Human (system) & Guinea pig (model) Lab mouse (model) Simulation software (model) 7

8 Other examples of general models Finance models Earthquake models Tsunami models Lots of models in Physics and Chemistry! 8

9 Model V&V, accuracy, complexity, and cost Validating the model There should be some way to validate a model! (using constraints). 9

10 Model V&V, accuracy, complexity, and cost Validating the model There should be some way to validate a model! (using constraints). Verifying the models If tests on model passes, its not necessary it will pass on system! However, if tests on model fails, its quite unlikely that it will pass on system. 10

11 Model V&V, accuracy, complexity, and cost Validating the model There should be some way to validate a model! (using constraints). Verifying the models If tests on model passes, its not necessary it will pass on system! However, if tests on model fails, its quite unlikely that it will pass on system. In general cost and complexity accuracy 11

12 For pure software based systems Things are little different If there exist a model system converter (code generator). The more accurate the model, the better. 12

13 Model driven engineering Notation 1. Is the notation generic enough? 2. How much details can be added in the model? 3. Can we simulate/execute the model? Important! Models will go through refinement and reviews. Hence, the notations must be simple, modular and easy to review! 13

14 SysML Systems Modeling Language 1. Is a generic notation for modelling systems (System-of-Systems). 2. Tool independent (but compatibility between tools is still an issue). 14

15 Tools (Open source) UML Dia Umbrello : download.kde.org/stable/umbrello/latest PlantUML: (Both tool and online) jsuml2: (Online) draw.io: (Online) SysML 1. Modelio 2. Eclipse/Papyrus (both UML/SysML) 15

16 Using Dia Install If you prefer to install Dia: Try online 16

17 Using Dia Install If you prefer to install Dia: Try online Quick SysML examples Just enough SysML to understand the AMADEOS profile! 17

18 Quick SysML examples... 1 Figure: Profile Figure: Model 18

19 Quick SysML examples... 2 Figure: Various relations 19

20 Quick SysML examples... 3 <<Requirement>> System_Specification +id = 1 <<Requirement>> Architecture +text = Requirements for architecture +id = 2 <<Requirement>> Communication +text = Requirements for communication +id = 1.1 <<Requirement>> Architecture_Req_1 +text = Requirement 1 for architecture +id = 2.1 <<Requirement>> Communication_Req_1 +text = Requirement 1 for communication +id = 1.2 <<Requirement>> Architecture_Req_2 +text = Requirement 1 for architecture +id = 2.2 <<Requirement>> Communication_Req_2 +text = Requirement 2 for communication Figure: Requirements diagram 20

21 Quick SysML examples... 4 Figure: Flow ports 21

22 Quick SysML examples... 5 Figure: Sequence diagrams 22

23 SysML Issues Spaghetti diagrams 23

24 SysML Good practice 24

25 Viewpoints Its not necessary to view the entire model all the time. Because its difficult to focus, when we see the whole diagram One user may not be expert in all areas (e.g. one user is expert in security other in communication. Its good to have different viewpoints). 25

26 Viewpoint example 26

27 Difference between drawing & modelling in SysML Drawing 1. Not formal, just a diagram on paper 2. Difficult to validate diagrams 3. Need to use third party tools to do any further processing Modelling 1. Diagrams can be validated 2. Code generation is possible for simulation/stub-creation 27

28 Model transformation Though, UML/SysML was meant to be tool independent, Tool vendors may use different formats for storing UML/SysML 28

29 Model transformation Though, UML/SysML was meant to be tool independent, Tool vendors may use different formats for storing UML/SysML XMI is supposed to solve this problem. But not fully yet! The process of transforming one model format to another is known as model transformation 29

30 Model transformation Though, UML/SysML was meant to be tool independent, Tool vendors may use different formats for storing UML/SysML XMI is supposed to solve this problem. But not fully yet! The process of transforming one model format to another is known as model transformation Useful if we have to add new features which do not exist in the SysML standard 30

31 PlantUML PlantUML is a textual representation to draw UML Its very portable and can be easily convertable to other formats. (also vice-versa) Demo: Online demo Auto generation of sequence diagrams! Plug-ins for PlantUML 31

32 Conclusion SysML is a generic notation for modelling systems (or SoS) In practice, there is a huge difference between drawing and modelling 32

33 Conclusion SysML is a generic notation for modelling systems (or SoS) In practice, there is a huge difference between drawing and modelling Models will get bigger over time Spaghetti diagrams must be avoided Modularizing models is important It is not necessary to view the entire model all the time... use of viewpoints is highly recommended! 33

34 Conclusion SysML is a generic notation for modelling systems (or SoS) In practice, there is a huge difference between drawing and modelling Models will get bigger over time Spaghetti diagrams must be avoided Modularizing models is important It is not necessary to view the entire model all the time... use of viewpoints is highly recommended! Model transformations are needed to deal with incompatabilities between tools 34