UML- Unified Modeling Language
Download as PPT, PDF36 likes16,432 views
The document discusses UML (Unified Modeling Language) as a versatile modeling language used for specifying, visualizing, constructing, and documenting software systems. It outlines various UML diagrams such as use case, class, interaction, activity, and state diagrams, detailing their purposes and relationships within software modeling. Additionally, it highlights the significance of UML in the unified software development process and its historical context.
UML- Unified Modeling Language
- 1. UML, The Art of Software Modeling By: Shahzad Sarwar
- 2. "UML is not dessert topping and floor wax." - Grady Booch - on the versatility of UML.
- 3. Introduction UML - language and notation for specification, construction, visualisation and documentation of models of software systems. UML is not: programming language a CASE tool method UML modelling language. Methods: modelling language + process Modelling language : Notation that methods use to express design Process: Steps in doing a design Associate with UML is Unified Software Development Process. Object Management Group an industry standards body requested standard object modelling language (1996). UML: Developed by Grady Booch, Ivar Jacobson, James Rumbaugh
- 4. History
- 5. Diagrams
- 6. Diagrams
- 7. Use Case Diagrams Use case: Describes a task that a user can perform using the system. Describes requirements for the system Task described by a use case is composed of activities Use case can have different variations called scenarios Should not be used for functional decomposition ! Actors: Actor is an external entity which is involved in the interaction with the system described in a use case. Actors = roles Actors can be also dialogs, and external systems
- 8. Use Case Diagrams Generalisation and specialisation of actors
- 9. Use Case Diagrams Use Case Diagrams Shows the relationships between a set of use cases and the actors involved in these use cases. Tool for requirement determination Use case describes those activities which are to be supported by the software under development Relationships between use cases Include: base use case includes the functionality of included use case Extend: a use case is optionally extended by functionality of another use case Generalisation: sub use case inherits behaviour and semantics from super use cases
- 12. Class Diagram Class Attributes: Represent named properties of a UML class Attribute declaration may include visibility, type and initial value: +attributeName : type = initial-value Class Operations: Represent named services provided by a UML class Operation may include visibility, parameters, and return type: +opName(param1 : type = initial_value) : return-type Class Visibility: Three levels of class, attribute and operation visibility: Private (-), available only to the current class Protected (#), available to the current and inherited classes Public (+), available to the current and other classes
- 13. Class Diagram Class Objects: Each class represents a set of objects that share the same attributes, operations, relationships, and semantics
- 14. Class Generalization: Represent a relation between a parent (a more abstract class) and a child (a more specific class) Generally referred to as a “is-a-kind-of” relationship Child objects may be used instead of parent objects since they share attributes and operations; the opposite is not true
- 15. Class Association: Represent a structural relationship between class objects and may be used to navigate between connected objects Association can be binary, between two classes, or n-ary, among more than two classes Can include association name, direction, role names, multiplicity, and aggregation type
- 16. Class Aggregation Represent a specific, whole/part structural relationship between class objects Composition (closed diamond) represents exclusive relationship between two class objects (e.g., a faculty cannot exist without nor be a part of more than one university) Aggregation (open diamond) represents nonexclusive relationship between two class objects (e.g., a student is a part of one or more faculties)
- 17. Example
- 18. Interaction Diagrams Represent interaction between class objects based on conditions and operations Can also represent a use case scenario of interaction between actors and the system Two main subtypes: sequence and collaboration diagrams Sequence diagrams emphasize the temporal order of interaction and show lifetime of each object
- 22. Collaboration diagrams Emphasize layout and show interaction as numbering of steps in a scenario
- 24. Object Diagram Shows an example of objects with slots and links that could be instantiated from defined classes and relationships Validates class diagrams
- 25. Package Diagram Decomposes system into logical units of work Describe the dependencies between logical units of work Provide views of a system from multiple levels of abstraction
- 26. Composite Structure Diagram Shows the internal structure of a classifier, including its interaction points to other parts of the system More useful for modeling hardware, real-time systems,integrated device modeling
- 27. Activity Diagram Shows a procedural flow for a process Useful for workflow modeling Supports parallel behavior for multithreaded programming
- 29. Communication Diagram Provides an alternative view to the sequence diagram in a format based on structure rather than time Emphasizes how objects interact with each other More efficient use of space
- 30. State Diagram Describes how an object changes its state that govern its behavior in response to stimuli from the environment A statechart diagram is a finite automaton extended with Output (combinaton of Moore and Mealy automaton)
- 32. Component Diagram Describes software components that make up a system,their interfaces (optional) and relationships
- 34. Deployment Diagram Describes the configuration of hardware in a system in terms of nodes and connections Describes the physical relationships between software and hardware Displays how artifacts are installed and move around a distributed system
- 35. Reference: http://www.objectsbydesign.com – UML and OO links, forums, and resources http://www.devx.com/uml/ – UML developer zone http://www.sdmagazine.com/ – Magazine with many UML related articles http://www.omg.org – The UML Specification and other UML resources