1 / 20

Project Management Office Lunch & Learn

Project Management Office Lunch & Learn . Use Case. Agenda. Definition Benefits UCIT Methodology & Use Case Steps to develop use cases Use Case Body Parts References Questions . What is a use case? . Describe goal-oriented set of interactions between the actor and the software

stevie
Télécharger la présentation

Project Management Office Lunch & Learn

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. Project Management OfficeLunch & Learn Use Case

  2. Agenda • Definition • Benefits • UCIT Methodology & Use Case • Steps to develop use cases • Use Case Body Parts • References • Questions

  3. What is a use case? • Describe goal-oriented set of interactions between the actor and the software • A technique used to identify, detail, and clarify software requirements • Focus on WHAT, not HOW • Define the scope/boundary of the software

  4. Use Case Diagram – Membership Sales

  5. Benefits • Put requirements in business context • Easy to understand by business & IT community • Validate scope and requirements • Serve as a basis as scheduling and estimating • Manage complexity • Break software into manageable parts • Re-useable deliverable • Test Cases • User Manual • Future enhancements

  6. UCIT Methodology & Use Case

  7. Steps to develop use case • Identify actor • Identify use case goals for each actor • Identify re-use opportunity

  8. Example – Membership Sales

  9. Steps to develop use case • Create Use Case Index • Validate against requirements • Determine execution approach • Develop high level use case • Create detail use case • Walkthrough & Revise • Package into final document

  10. Body Parts • Summary • Scenarios & Steps • Exceptions

  11. Body Parts - Summary • Use Case Identifier • Unique identifier assigned to use case • Example MS-001, MS-001.1 • Goal/Name • Describe the BUSINESS goal that the use case is intended to achieve • Use active verb to describe the performing action on the goal • Example: Register in an event, Issue an ID Card, Renew a Membership • Actor • Someone or something outside the system that acts on the system • Primary or secondary actors • Person/Role, System, or Time

  12. Body Parts - Scope • Pre & Post Conditions • Pre Conditions – set of criteria must be satisfied before the use can be initiated • Post Conditions – describes the states of the software when the use case ends • Triggers • Event that causes the use case to be initiated • External, Internal, or Temporal • Temporal - Send Payroll Deduction to PeopleSoft • Internal – Apply Client Restriction Automatically • Business vs. System Use case

  13. Example – Renew a Membership

  14. Body Parts - Scenario • Main Scenario • Consists of steps required to achieve the business goals • Happy Day Scenario – most likely case • Alternate Paths • Other possible scenarios • Branch from main scenario when the situation differs

  15. Body Parts - Exceptions • Steps taken to deal with failure • System or human cause • Access to ID Core Service failed • Payment failed to go through Moneris

  16. Example – Sell a Membership

  17. Example – Sell a Membership

  18. More Information • Books • Writing Effective Use Cases • Patterns for Use Cases • Websites • www.usecases.org • en.wikipedia.org/use_case

  19. Questions

More Related