1 / 19

Unified Modeling Language

Unified Modeling Language. What is it and why do I need to know. What is UML. OMG defines UML like this

lilah-melendez
Download Presentation

Unified Modeling Language

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Unified Modeling Language What is it and why do I need to know

  2. What is UML • OMG defines UML like this • “The Unified modeling language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. The UML offers a standard way to write a system’s blueprints, including conceptual things such as business process and system functions as well as concrete things such as programming language statements, database schemas, and reusable software components.”

  3. History of UML • Late 20th century “method wars” • Number of modeling languages • Many overlapping languages • The “three amigos” emerge at Rational • Booch, OMT, and OOSE methods merge • Result is RUP and UML • Standardized under OMG • UML 0.9 release 1996, V1.0 submitted to OMG in 1997, revised to V1.1 later same year

  4. Problem Domain Models • Use Case Model • Collaboration (Interaction) Model • Dynamic Model • Class (Logical) Model • Physical Component Model • Physical Deployment Model

  5. Defining User Requirements Discovering the use cases

  6. Use Case Model • Use cases define how a user (human or non-human) will use the system • Components • Actors • Use Cases • Relationships

  7. An Actor Uses the System • Any external entity that makes use of the system • A human user • An external software or hardware component that makes use of the system • For example – POS would an EZ-Views actor

  8. Use Case Defines an Activity • Each use case is a single activity • Log on • Create order • Use cases interact with other entities to define the features of the system

  9. Relationships • Represented by lines and arrows on the diagram • Examples: • Uses • Extends and includes • Flow (of data or control) • Can be adorned with other descriptive information

  10. Attributes • Description – general text about the entity • Responsibilities – what it must do, the heart of the functional spec • Constraints – limitations, either before, after or throughout an activity • Scenarios – text descriptions of the flow of events

  11. Use Case Big Picture

  12. Collaboration Model How entities interact to get the job done

  13. Teamwork Among Entities

  14. Pieces of the Diagram • More than just actors and use cases • Physical entities, such as a web page • Relationships show how each piece is used.

  15. Dynamic Model Showing the system in motion

  16. Logical Model Fleshing out the design

  17. Component Model Packaging the entities

  18. Deployment Model How will we deliver it?

  19. Questions • References • www.sparxsystems.com.au • UML Distilled

More Related