1 / 12

UML – Unified Modeling Language

UML – Unified Modeling Language. Use-Case Diagrams. What is UML?. UML  unified modeling language Mainly used for development of OO Used in conjunction with UP Unified process. What is UP?. Inception Elaboration Construction Transition Production. What is a use-case diagram?.

sapphire-ilithya
Download Presentation

UML – 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. UML – Unified Modeling Language Use-Case Diagrams

  2. What is UML? • UML  unified modeling language • Mainly used for development of OO • Used in conjunction with UP • Unified process

  3. What is UP? • Inception • Elaboration • Construction • Transition • Production

  4. What is a use-case diagram? • Depicts the software or system from the end user’s point of view • Steps • Define the actors • Define the goals • Determine who is primary and secondary actors

  5. Use-case (cont) • Basic use-case presents a high-level story that describes the interaction between the actor and the system

  6. Use-Case Scenarios

  7. Use-case template • Use-case • Primary actor • Goal in context • Pre-conditions • Trigger • Scenario • Exceptions • Priority • When available • Frequency of use • Channel to actor • Secondary actors • Channels to secondary actors • Open issues

  8. Users use-case example • Use-case: UsersUseColiseumManagementSystem • Primary actor(s):Coliseum Administration Staff, Web-users, Coaches, Students • Goal in context: To provide users the correct interfaces so that they may use the system • Pre-conditions: Users are not logged in and users are in the database • Trigger: User decides to use the system • Scenario: 1) users observe the interface; 2) the user enteres usrn/pwd 3) the user selects submit 4) observes system to indicate he/she is logged in • Exceptions: 1) user is already logged in; user would just use the system 2) usrn/pwd pair is not recognized and user would try to login again; if user cannot login then it is reported to the helpdesk for a pwd reset 3) usrn/pwd pair is not in the system; Helpdesk would add user to the system 4) user is logged in the next interface is shown 5)user would make selection from possible dashboard options

  9. Use-case example (cont) • Priority: essential, must be implemented • When available: first increment • Frequency of use: many times per day • Channel to actor: intranet/internet interface through web browser • Secondary actors: Helpdesk • Channels to secondary actors: Helpdesk  telephone, live web chat and email • Open issues: 1) should there be a way to log into the system without usrn/pwd 2) should there be any other messages given to the user 3) how many attempts does the user get to login 4) is there a way to logout 5) do all users have to login

  10. Use-case diagram

  11. Requirements Definitions

  12. Requirements Definitions • Purpose • Target Audience • Template

More Related