1. Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to SysML (Chapters 5, 6) –UML, Metodologias e Ferramentas CASE (Chapter 6)

2. Modelação2 Program T01-T02 – Module 1 –Introduction to Systems Modelling T03-T06 – Module 2 –Conceptual Modelling – Domain T07-T11 – Module 3 –Conceptual Modelling – Behaviour T12-T15 – Module 4 –Ontology T16-T19 – Module 5 –Conceptual Modelling – Architecture T20-T21 – Module 6 –Conceptual Modelling – Metodologies T22-T23 – Module 7 –Ontology: Advanced T24-T25 –Conceptual Modelling – Revisions; Exercices, …

3. Systems and conceptual modelling A system is… a thing! Systems are made of things (systems are made of systems…) In conceptual modelling we assume that the systems are made of entities, relationships and concepts A conceptual model of a system is made of the structural model and of the behavioural model of that system Modelação3

4. Conceptual Modelling A conceptual model of a system is made of: structural model: the description of the entities, relationships and concepts of a systems behavioural model: the actions that the system can perform and the valid changes in the domain Modelação4

5. Conceptual Modelling A conceptual model of a system is made of: structural model: the description of the entities, relationships and concepts of a systems behavioural model: the actions that the system can perform and the valid changes in the domain Modelação5 We’ll address this now!!! We’ll address this later…

6. The Structural Model of a system: domain The set of concepts of a particular system are part of the domain of that system A domain diagram of a system is a visual representation of the domain of that system, with the representation of the concepts and the relationships between them Modelação6

7. Structural diagrams in UML and SYsML Modelação7

8. Focus for today… Modelação8

9. Packages (UML / SysML) Package diagrams depict the organization of model elements into packages and the dependencies amongst them Modelação9

10. Packages and project’s structure Modelação10

11. Concepts in UML: Classes A class is a description of a set of objects that share the same attributes, operations, methods, relationships and semantics. A Class can use a set of interfaces to specify collections of operations it provides to its environment Modelação11

12. Modelação12 (Domain) Class Diagrams

13. Classes e relations Modelação13

14. Associations Association is the general relationship type between elements. Associations can be 1-to-1 or n-Ary Modelação14

15. Generalization A generalization is used to indicate inheritance. Modelação15

16. Aggregation An Aggregation shows that an element contains or is composed of other elements Modelação16

17. Composite Aggregation A Composite Aggregation is used to depict an element that is made up of other elements. A component can be included in a maximum of one composition at a time. Modelação17

18. Association Class An Association Class connector enables an Association connector to have attributes and operations (features). Modelação18

19. More on Associations… Modelação19 Images from http://www.agilemodeling.com/artifacts/classDiagram.htm IndicatorMeaning 0..1Zero or one 1One only 0..*Zero or more 1..*One or more nOnly n (where n > 1) 0..nZero to n (where n > 1) 1..nOne to n (where n > 1)

20. More on Connectors… Modelação20 Images from http://www.agilemodeling.com/style/classDiagram.htm

21. Concepts in SysML: Blocks Blocks are in SysML modular units of system description. Each block defines a collection of features to describe a system or other element of interest. These may include both structural and behavioral features, such as properties and operations, to represent the state of the system and behavior that the system may exhibit. Blocks provide a general-purpose capability to model systems as trees of modular components. The specific kinds of components, the kinds of connections between them, and the way these elements combine to define the total system can all be selected according to the goals of a particular system model. SysML blocks can be used throughout all phases of system specification and design, and can be applied to many different kinds of systems. These include modeling either the logical or physical decomposition of a system, and the specification of software, hardware, or human elements. Modelação21

22. Notations for blocks Modelação22 > Car Compartments can be used to model (textual or graphically) multiple aspects of the block

23. Data types as blocks Blocks can represent not only physical entities, as also abstract Modelação23

24. bdd – Block Definition Diagram Modelação24

25. Associations between blocks… Modelação25

26. “ibd – Internal Block Diagram” Modelação26

27. An “ibd” can detail the system at multiple levels Modelação27

28. Blocks and interfaces Modelação28 Algumas imagens retiradas de http://www.system-modeling.com/ (acompanhamento ao livro “Systems Engineering with SysML UML”

29. Blocks and interfaces Modelação29 Algumas imagens retiradas de http://www.system-modeling.com/ (acompanhamento ao livro “Systems Engineering with SysML UML”

30. Associations in Block Definition diagrams… Modelação30