This presentation delivered for undergraduate students under the university relations programme of 99X Technology. This presentation covers basic concepts of Unified Modelling Language including some hands-on activities.

1. 1
Application of Unified Modelling Language
Rasan Samarasinghe (Software Engineer)

2. Introduction to Modelling and UML
2

3. Why modelling is important?
• Ensure building the right system
• Understand the effective way to do that
• Bring out the meaning / purpose
3

4. Which aspects of a system should be
modelled?
• Business aspect
• Structure of the system
• Behavior of the system
4

5. Unified Modeling Language
A standard way to visualize software systems
5

6. History of UML
6

7. Hierarchy of UML diagrams
7

8. Structure Diagrams
8

9. Class diagram
• A static structure of an object oriented model.
• Shows classes and their internal structures and their
relationships.
9

10. Notations of class diagram
10

11. Benefits of Class diagram
• Describing the static view of the system.
• Describing the functionalities performed by the system.
• Construction of software applications using object oriented
languages.
11

12. Component diagram
• Model physical aspects of a system.
• These physical aspects are the elements like executables,
libraries, files, documents etc which resides in a node.
12

13. Notations of component diagram
13

14. Benefits of component diagram
• Model executables of an application.
• Model system's source code.
• Visualize the relationships of the components.
14

15. Behavior Diagrams
15

16. Use case diagram
• Graphical representation of a user's interaction with the system.
• Capturing the dynamic aspect of a system.
16

17. Notations of use case diagram
17

18. Benefits of use case diagram
• Gather requirements of a system.
• Get an outside view of a system.
• Model the context of a system.
• Understand the project scope.
18

19. Sequence diagram
• Describe types of interactions among the different elements
in the model.
• Sequence diagram emphasizes on time sequence of
messages.
19

20. Notations of sequence diagram
20

21. Collaboration diagram
• Emphasizes on the structural organization of the objects that
send and receive messages.
21

22. Notations of collaboration diagram
22

23. Benefits of interaction diagrams
• Capture dynamic behavior of a system.
• Describe the message flow in the system.
• Describe structural organization of the objects.
• Describe interaction among objects.
23

24. Activity diagram
• Flow chart to represent the flow of activities.
• An activity can be described as an operation of the system.
24

25. Notations of activity diagram
25

26. Benefits of activity diagram
• Modeling business requirements.
• High level understanding of the system's functionalities.
• Draw the activity flow of a system.
• Describe the parallel, branched and concurrent flow of the
system.
26

27. Recycling Machine
27

28. Recycling machine
1. Class diagram
2. Component diagram
3. Sequence diagram
4. Collaboration diagram
5. Use case diagram
6. Activity diagram
28

29. StarUML
1. Downloading StarUML
2. Installing StarUML
3. User interface
4. Starting a new project
5. Design to code conversion
6. Code to design conversion
29

30. Additional resources
30

31. Thank You!www.99xtechnology.com
31