From SysML to UML Does SysML improve Software Components Design in a System Engineering Project?

1. From SysML to UML Does SysML improve Software Components Design in a System Engineering Project? http://liuppa.univ-pau.fr Nicolas BELLOIR Associate Professor at the University of Pau, France

2. About the Speaker • Nicolas Belloir • Is Associate Professor at the UPPA • Is actually studying an integrated approach based on SysML and UML • Has done his Ph. D. on the semantic of Component Composition in UML • Has worked on RT project in Industry • Latecoere (Human centrifuge) • Airbus (Integration and Development Flight Simulator) Not a native speaker!!

3. About the Document • Targeted audience • Master Degree or Ph. D. students • Basic knowledge in UML • Format • Short speaking (3H) • Special Thanks to • Jean-Michel Bruel, Professor ,Toulouse University • Laurent Nonne, Teacher, Blagnac IUT • Pascal Roques, Senior consultant, ARTAL Inc.

4. About Pau

5. The University of Pau (UPPA) A network of four campuses Bordeaux Mont-de-Marsan Bayonne Anglet Toulouse Pau Tarbes

6. The LIUPPA LaboratoryResearchOrganization Computer Science Laboratory Director : Pr Conduc Pham 2 Research Teams 5 Project-Teams • Software Engineering and Distributed Systems • Software Engineering and Distributed Systems • Information Processing and Interactions

7. LIUPPASoftware Engineering and Distributed Systems • Model-Driven Engineering (MDE) • Agents, Components & Software Services • Security, Time-Stamping, Digital Right Management • Communication Protocols, High-Speed Networks, Congestion Control • Wireless Sensor Networks (WSN) • Multimedia and Quality of Service

8. LIUPPA Software Engineering and Distributed Systems Application Domains Time-Stamping Infrastructure UML 2 - SysML Multimedia Supervision Platform Congestion Control For GBIT/S Networks, Optimized TCP Service-Oriented Computing and Autonomic Computing Java Management Extension (JMX) Management of Wireless Mobile Devices Learning Grid Infrastructure Deny of Service, Intrusion Detection System Video Transport On WSN

9. Need of modeling • “Essentially, all models are wrong, but some are useful” • Professor George E. P. Box (1987) • But… Modeling is still a key feature • To increase systems • Reliability • Adaptability • To make generative programming realistic • To increase reusability

10. Use of DSM to Modeling Systems • Domain Specific Modeling • Tends to support higher-level abstractions than General-Purposemodelinglanguages • Requireless effort to specify a system • UML to define DSM • UML includes the profile mechanismto be constrained and customized for specific domains and platforms • Stereotypes • Tagged values • Constraints • SoaML for web service engineering • SysML for System modeling WSML

11. Content • Part I • Introduction to System Engineering • Introduction to SysML • From UML to SysML • Part II • Case studies • From SysML to UML • Use of Software Components in System Engineering • Questions and discussions

12. System Engineering • Not Software Engineering… • …Before Software Engineering! • Historically • In the development process

13. A Complex System • Set of human and material elements composed of various technologies • Computer, Hydraulic, Electronic,… • Integrated to provide services to it environment corresponding to the system finality • Interacting between themselves and the environment A complex system is very different of a simple software system

14. Systems of Systems • A system • Should manage interactions between parts • Support expected behavior • Handle unexpected ones

15. System System Modeling Functional and/or Behavioural Model Requirements Take Off Ground Structural Model OK ? Other Engineering Analysis Models Performance Model Flying Command Engine Security Model Cost Model Landing Flying Data Acquisition Equations Brakes Flaps … Business Model Reactions 15

16. SE Practices for Describing Systems • Specifications • Requirement Definition • System Design • Analysis • Test Plans Generate lot of writing work Not adapted to discuss within a multi-domain team Before After MovingfromDocument centric To Model centric

17. UML for modeling systems? • UML 1.x, not really: • Mainly for Information Systems • Poor link between diagrams • Poor link between models and requirements • UML 2.x, neither, although: • Implication of Systems Eng. in the definition • Composite structure diagram

18. UML for modeling systems (cont.)? • UML a good basis • De facto standard in Software Engineering • Provides a lot of useful concepts to describe a complex system • Stable and extensible - can be adapted for the SE needs • Lot of available tools • But… • Lack of several key concepts of SE • UML vocabulary is too « software-like » to be used by System Engineers • Too many diagrams (13 different kinds)

19. System Engineering • Any question?

20. Content • Part I • Introduction to System Engineering • Introduction to SysML • From UML to SysML • Part II • Case studies • From SysML to UML • Use of Software Components in System Engineering • Questions and discussions

21. UML capabilities for SE modeling • UML 1.x fails to support SE • UML 2 increases UML 1.x capabilities for SE modeling • Collaboration between SE and the OMG • Allowing hierarchical modeling of both structural and behavioral features • Composite structure diagram • But No support for : • Linking models to requirements • Need other software like Doors • Modeling continuous flows • … SLIDE 21

22. UML and SE • UML a good basis • De facto standard in Software Engineering • Provides a lot of useful concepts to describe a complex system • Stable and extensible - can be adapted for the SE needs • Lot of available tools • But… • Lack of several key concepts of SE • UML vocabulary is too « software-like » to be used by System Engineers • Too many diagrams (13 different kinds) SLIDE 22

23. SysML: identity card • Date of birth: 2001! • Current version: 1.1 (03/12/2008) • Father: OMG/UML • Leading authors • Conrad Bock • CrisKobryn • Sanford Friedenthal

24. SysML Objectives • Based on UML 2 : but must be able to design a large panel of systems (hw, sw, data, …) • Standard : provide a modeling language for SE in order to: • Analyze, specify, design and verify complex systems • Allowing information exchange throughout tools • Bringing the semantic gap between all SE disciplinary • Simple : • easy to learn for system engineers • Supported by designing tools • Extensible : for specific domains (automotive, aerospace …)

25. SysML: Who is behind? • Industry • American Systems, BAE Systems, Boeing, Deere & Company, EADS Astrium, Eurostep, Israel Aircraft Industries, Lockheed Martin, Motorola, NIST, Northrop Grumman, oose.de, Raytheon, Thales • Tools Companies • Artisan, EmbeddedPlus, Gentleware, IBM, I-Logix, Mentor Graphics, PivotPoint Technology, Sparx Systems, Telelogic, vitech • Academia, organizations • AP-233, INCOSE, Georgia Institute of Technology, AFIS SLIDE 25

26. SysML, a UML2 profile? SysML extention to UML SysML is not really only a profile nor a language UML 2 SysML UML Part not used by SysML UML Part reused by SysML (UML4SysML) SLIDE 26

27. 20 décembre 2007 Requirement Diagram Parametric Diagram From UML2 to SysML Block Definition Diagram Internal Block Diagram

28. SysML overview • Diagram notation • Structure diagrams • Behavioral diagrams • Cross-cutting constructs

29. SysML diagram frames • Each SysML diag. represents a model element • Each SysML diag. must have a Diagram Frame • Diagram context is indicated in the header: • Diagram kind (req, act, bdd, ibd, sd, etc.) • Model element type (package, block, activity, etc.) • Model element name • User defined diagram name or view name • A separate diagram description block is used to indicate if the diagram is complete, or has elements elided

30. bruel@irit.fr SysML diagram frames (e.g.) header content diag. type diag. name

31. Structural Diagrams SLIDE 31

32. Package Diagrams (pkg) • Same as UML • to organize the model • name space • Model can be organized in multiple ways: • System hierarchy • e.g., enterprise, system, component • Diagram kind • e.g., requirements, use cases, behavior • Use viewpoints to augment model organization

33. Package Diagrams (e.g.)

34. Package Diagrams (links)

35. Block Definition Diagrams (bdd) • Classes are dead… welcome to blocks! • Can be anything (System, Hardware, Software, Data, Procedure, Facility, Person) • Satisfy Systems Engineers

36. Block Definition Diagrams (bdd) • Compartments • Properties • Operations • Constraints • Allocations • Requirements • User defined!

37. Block Definition vs. Usage • Block DefinitionDiagram(BDD) • Describes relations between blocks (composition, inheritance…) • Internal Block Diagram (IBD) • Describes block internal structure withparts, ports et connectors.

38. Block example

39. Block Definition Diagram (e.g.)

40. Internal Block Diagram (ibd)

41. SysML Ports (cont.) • Standard • Flow

42. SysML Ports (delegation) • to preserve encapsulation of block • interactions at outer ports are delegated to ports of child parts • ports must match • same kind, type, direction, etc. • connectors can cross boundary without requiring ports at each level of nested hierarchy

43. Software Interface signal Hydraulic flow Power flow SysML Port (e.g.) 2008/2009 bruel@irit.fr 43 Master Technologies de l'Internet - 2ième année 43 SLIDE 43

44. Parametric Diagrams • To express constraints between value properties • equations • support for engineering analysis (e.g., performance) • identification of critical performance properties • Constraint block captures equations • Expression language can be formal (e.g., MathML, OCL) • Computational engine is not provided by SysML • Parametric diagram • usage of the constraints in an analysis context SLIDE 44

45. Parametrics (e.g. 1)

46. Parametrics (e.g. 2)

47. Example : constraining radio emission SLIDE 47

48. Dynamical Design SLIDE 48

49. ActivityDiagrams (act) • To specify • controlled sequence of actions • the flow of inputs/outputs • control, including sequence and conditions for coordinate activities • Swimlanes • to show responsibility of the activity

50. ActivityDiagrams (cont.) • Improvements from UML: • Continuous or discrete flow • Control operators • to start/stop other actions • Overwrite and NoBufferports • for continuous flows • Probabilities on transitions or parameters