Download to read offline
Uploaded byRasan Samarasinghe
Application of Unified Modelling Language
The document discusses the importance and applications of Unified Modeling Language (UML) in software engineering. It outlines various types of UML diagrams, including class diagrams, component diagrams, use case diagrams, sequence diagrams, collaboration diagrams, and activity diagrams, highlighting their functions and benefits in modeling systems. Additionally, it provides insights on using StarUML for modeling projects.
More Related Content
Similar to Application of Unified Modelling Language
More from Rasan Samarasinghe
Application of Unified Modelling Language
- 1. 1 Application of UnifiedModelling Language Rasan Samarasinghe (Software Engineer)
- 2. Introduction to Modellingand UML 2
- 3. Why modelling isimportant? • Ensure building the right system • Understand the effective way to do that • Bring out the meaning / purpose 3
- 4. Which aspects ofa system should be modelled? • Business aspect • Structure of the system • Behavior of the system 4
- 5. Unified Modeling Language Astandard way to visualize software systems 5
- 6.
- 7. Hierarchy of UMLdiagrams 7
- 8.
- 9. Class diagram • Astatic structure of an object oriented model. • Shows classes and their internal structures and their relationships. 9
- 10. Notations of classdiagram 10
- 11. Benefits of Classdiagram • 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 • Modelphysical 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 componentdiagram 13
- 14. Benefits of componentdiagram • Model executables of an application. • Model system's source code. • Visualize the relationships of the components. 14
- 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 usecase diagram 17
- 18. Benefits of usecase 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 • Describetypes of interactions among the different elements in the model. • Sequence diagram emphasizes on time sequence of messages. 19
- 20. Notations of sequencediagram 20
- 21. Collaboration diagram • Emphasizeson the structural organization of the objects that send and receive messages. 21
- 22. Notations of collaborationdiagram 22
- 23. Benefits of interactiondiagrams • 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 • Flowchart to represent the flow of activities. • An activity can be described as an operation of the system. 24
- 25. Notations of activitydiagram 25
- 26. Benefits of activitydiagram • 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.
- 28. Recycling machine 1. Classdiagram 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.
- 31.