1. Introduction to UML Hazleen Aris Software Eng. Dept., College of IT, UNITEN. hazleen@uniten.edu.my …Unified Modeling Language

2. What is UML? UML is a language for: Visualising Specifying Constructing Documenting UML is NOT a visual programming language.

3. What is it for? Describing a system at a high level of abstraction A model of the system Used for requirements and specifications

4. Why UML? Use graphical notation to communicate more clearly than natural language (imprecise) and code (too detailed). Help acquire an overall view of a system. UML is not dependent on any one language or technology. UML moves us from fragmentation to standardization.

5. Its Use? In software-intensive areas like: Enterprise information system Banking and financial Telecommunications Transportation Defense and aerospace Retail Medical electronics Scientific Distributed web-based services

6. Its Use? … However, it is expressive enough to model non-software systems.

7. The History

8. The History …

9. Standard: Its Importance

10. Software Development Life Cycle

11. Vocabulary of UML The vocabulary of the UML comprises three kinds of building blocks: Things Relationships Diagrams

12. The Things Structural things The nouns of UML models. Behavioural things The verbs of the models. Grouping things The organisational parts of the models. Annotational things The explanatory parts of the models.

13. Structural Things (1 of 7) Use case A description of a set of sequence of actions that a system performs that yields an observable result of value to a particular actor.

14. Structural Things (2 of 7) Collaboration A collaboration defines an interaction and is a society of roles and other elements that work together to provide some cooperative behaviour that is bigger than the sum of all the elements.

15. Structural Things (3 of 7) Class A description of a set of objects that share the same attributes, operations, relationships and semantics.

16. Structural Things (4 of 7) Interface A collection of operations that specify a service of a class or component.

17. Structural Things (5 of 7) Active class A class whose objects own one or more processes or threads and therefore can initiate control activity.

18. Structural Things (6 of 7) Component A physical and replaceable part of a system than conforms to and provides the realisation of a set of interfaces.

19. Structural Things (7 of 7) Node A physical element that exists at run time and represents a computational resource, generally having at least some memory and, often, processing capability.

20. Behavioural Things (1 of 2) Interaction A behaviour that comprises a set of messages exchanged among a set of objects within a particular contact to accomplish a specific purpose. display

21. Behavioural Things (2 of 2) State machine A behaviour that specifies the sequences of states an object or interaction goes through during its lifetime in response to events, together with its responses to those events.

22. Grouping Things (1 of 1) Package A general purpose mechanism for organising elements into groups.

23. Annotational Things (1 of 1) Note A symbol for rendering constraints and comments attached to an element or a collection of elements.

24. The Relationships There are four kinds of relationships in UML: Dependency Association Generalisation Realisation

25. Dependency A semantic relationship between two things in which a change to one thing may affect the semantics of the other thing.

26. Association A structural relationship that describes a set of links, a link being a connection among objects.

27. Generalisation A specialisation/generalisation relationship in which objects of the specialised element (the child) are substitutable for objects of the generalised element (the parent).

28. Realisation A semantic relationship between classifiers, wherein one classifier specifies a contract that another classifier guarantees to carry out.

29. The Diagrams Use case diagram Class diagram Object diagram Sequence diagram Collaboration diagram State diagram Activity diagram Component diagram Deployment diagram

30. The Diagrams … Class diagram Object diagram Component diagram Deployment diagram Use case diagram Sequence diagram Collaboration diagram State diagram Activity diagram static dynamic

31. The Diagrams … Class diagram* Object diagram Component diagram Deployment diagram Use case diagram* Sequence diagram* Collaboration diagram* State diagram* Activity diagram

32. Summary Introduction to UML What? Why? History Basics of UML Notations Relationships Diagrams