1. 1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi

2. Outline 1. Introduction to UML 2. Basic UML Modeling Steps 3. UML Diagrams 4. Summary 2

3. Unified Modeling Language (UML) Lecture: 2 3

4. 1. Introduction Unified Modeling Language (UML) is a standardized general-purpose modeling language The standard is managed, and was created, by the Object Management Group in 1997 UML includes a set of graphic notation techniques to create visual models of object-oriented software UML is used to specify, visualize, modify, construct and document the artifacts of a software It can be used with all processes, throughout the software development life cycle, and across different implementation technologies 4

5. Introduction (Continue…) UML has become de facto industry standard UML models may be automatically transformed to other representations (e.g. Java) UML is extensible, with two mechanisms for customization: profiles and stereotypes UML 2.2 has 14 types of diagrams divided into two categories  Seven diagram types represent structural information  Seven diagram types represent general types of behavior Four that represent different aspects of interactions 5

6. Introduction (Continue…) 6

7. Basic UML Modeling Steps Use Cases  Capture requirements Domain Model  Capture process, key classes Design Model  Capture details and behaviors of use cases and domain objects  Add classes that do the work and define the architecture 7

8. Class Diagram UML class diagrams show the classes of the system, their inter-relationships, and the operations and attributes of the classes 8

9. Class Diagram (Continue…) 9

10. Component Diagram UML component diagrams shows the dependencies among software components, including the classifiers that specify them (for example implementation classes) and the artifacts that implement them; such as source code files, binary code files, executable files, scripts and tables. 10

11. Component Diagram (Continue…) 11

12. Deployment Diagram UML deployment diagrams show the hardware for your system, the software that is installed on that hardware, and the middleware used to connect the disparate machines to one another. 12

13. Deployment Diagram (Continue…) 13

14. Object Diagram UML Object diagrams (Instance diagrams), are useful for exploring real world examples of objects and the relationships between them. It shows instances instead of classes. 14

15. Object Diagram (Continue…) 15

16. Package Diagram UML Package diagrams simplify complex class diagrams, it can group classes into packages. A package is a collection of logically related UML elements. Packages are depicted as file folders and can be used on any of the UML diagrams. 16

17. Package Diagram 17

18. Composite-Structure Diagram UML Composite structure diagrams used to explore run-time instances of interconnected instances collaborating over communications links. It shows the internal structure (including parts and connectors) of a structured classifier or collaboration. 18

19. Composite-Structure Diagram (Continue…) 19

20. Profile Diagram Profile diagram is structure diagram which describes lightweight extension mechanism to the UML by defining custom stereotypes, tagged values, and constraints. Profiles allow adaptation of the UML metamodel for different platforms and domains. 20

21. Profile Diagram (Continue…) 21

22. Activity Diagram UML Activity diagrams helps to describe the flow of control of the target system, such as the exploring complex business rules and operations, describing the use case also the business process. It is object-oriented equivalent of flow charts and data-flow diagrams (DFDs). 22

23. Activity Diagram (Continue…) 23

24. Use Case Diagram UML Use case diagrams describes the behavior of the target system from an external point of view. Use cases describe "the meat" of the actual requirements. 24

25. Use Case Diagram (Continue…) 25

26. State Machine Diagram UML State machine diagrams can show the different states of an entity also how an entity responds to various events by changing from one state to another. The history of an entity can best be modeled by a finite state diagram. 26

27. State Machine Diagram (Continue…) 27

28. Sequence Diagram UML Sequence diagrams models the collaboration of objects based on a time sequence. It shows how the objects interact with others in a particular scenario of a use case. 28

29. Sequence Diagram (Continue…) 29

30. Communication Diagram UML Communication diagrams used to model the dynamic behavior of the use case. When compare to Sequence Diagram, the Communication Diagram is more focused on showing the collaboration of objects rather than the time sequence. 30

31. Communication Diagram (Continue…) 31

32. Interaction Overview Diagram UML Interaction overview diagrams focuses on the overview of the flow of control of the interactions. It is a variant of the Activity Diagram where the nodes are the interactions or interaction occurrences. 32

33. Interaction Overview Diagram (Continue…) 33

34. Timing Diagram shows the behavior of the objects in a given period of time. Timing diagram is a special form of a sequence diagram. The differences between timing diagram and sequence diagram are the axes are reversed so that the time increase from left to right and the lifelines are shown in separate compartments arranged vertically. 34

35. Timing Diagram (Continue…) 35

36. 36 Summary Any Questions?