1 / 14

Lecture 10 Other UML Notations

BK - Spring 2006. Software Design . 2. UML Activity Diagrams. Used to document workflows:Modelling business activities or systemsModelling activities within/between use-casesDetailed description of operations in classesSimilar notation to UML statechart diagrams:Activities (action states)StatesTransitions.

vahe
Télécharger la présentation

Lecture 10 Other UML Notations

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. BK - Spring 2006 Software Design 1 Lecture 10 Other UML Notations Activity Diagrams Documenting workflows Basic Notation ATM Case Study: withdrawal use-case Packages and Subsystems Implementation Diagrams (very briefly) Component diagrams Deployment diagrams

    2. BK - Spring 2006 Software Design 2 UML Activity Diagrams Used to document workflows: Modelling business activities or systems Modelling activities within/between use-cases Detailed description of operations in classes Similar notation to UML statechart diagrams: Activities (action states) States Transitions

    3. BK - Spring 2006 Software Design 3 Activity Diagrams & State Diagrams Notationally, very similar Important to distinguish purpose/use State diagrams: behaviour of individual objects/components show state transitions triggered by events Activity diagrams: behaviour within systems/organizations transitions between activities (work flows)

    4. BK - Spring 2006 Software Design 4 Activity Diagrams: Basic Notation

    5. BK - Spring 2006 Software Design 5 Activity Diagrams: Decision Points

    6. BK - Spring 2006 Software Design 6 Activity Diagrams: Swimlanes

    7. BK - Spring 2006 Software Design 7 ATM Case Study: Workflow for Withdrawal Use-Case

    8. BK - Spring 2006 Software Design 8 ATM Case Study: Elaborated Use-Case Description

    9. BK - Spring 2006 Software Design 9 ATM Case Study: Activity Diagram for Withdrawal

    10. BK - Spring 2006 Software Design 10 Packages and Subsystems Package: a collection of model elements: grouping semantically related elements analysing system architecture hiding irrelevant detail on a diagram Subsystem: special sort of package: representing units of the physical system developing components of the design

    11. BK - Spring 2006 Software Design 11 Packages: Organising Model Elements

    12. BK - Spring 2006 Software Design 12 ATM Case Study: Layered Architecture

    13. BK - Spring 2006 Software Design 13 UML Component Diagrams

    14. BK - Spring 2006 Software Design 14 UML Deployment Diagrams

    15. BK - Spring 2006 Software Design 15 Summary Activity diagrams: Model workflows Transitions between activities Use-case modelling/business modelling Packages Group logically related units Implementation diagrams: Component diagrams document physical elements Deployment diagrams document hardware elements

More Related