1 / 20

Use Case Development

This document outlines the fundamentals of use case development, emphasizing its importance for system analysis, requirement elicitation, and alignment of collective efforts within the IDESG. It distinguishes between high and low-level use cases and discusses recent progress, including the creation of a use case template. The document also provides a roadmap for future workshops and collaboration efforts, aiming to produce a draft set of use cases within nine months. Stakeholder engagement and contributions are crucial for this initiative.

avent
Download Presentation

Use Case Development

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. Use Case Development Cathy Tilton, Daon Scott Shorter, Electrosoft Services 7 February 2013

  2. Outline • What is a use case • Purpose of use cases • Levels of use cases • What’s been done so far • General approach • Timeline • Workshop plans • What can be done between now and then

  3. What is a use case? • Different for engineers than for business owners, users, or other species • I like this one: • a methodology used in system analysis to identify, clarify, and organize system requirements • the use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal

  4. Purpose of use cases (within the IDESG) • Basis for the development of other work products – provides context • Method of eliciting requirements • Helps define the problem(s) we are trying to solve • “Determine commonalities so as to be able to design services” • Guide our collective efforts – keep us aligned

  5. Levels • Target – “scenario” level: What & Why • Once defined, progressively lower level use cases can be derived as needed • Lower levels may have a specific focus (e.g., privacy, security, user experience,…) High Level WHY HOW Low Level (diagram inspired by Writing Effective Use Cases, Alistair Cockburn)

  6. What has been done so far • Use case template • Draft list of potential use cases • Began to identify sources of existing use cases • Generated sample use cases • Began collection effort

  7. Use case template • Title & brief description • Category • Contributor • Actors • Goals • Assumptions • Requirements • Process flow • Success scenario • Error conditions • Citations

  8. Use Case Template

  9. Use Case Template - Terms

  10. Use Case Template - Categories

  11. User Level Example –Two-Party Delegation

  12. General Approach • Collection phase • Filter • Analyze and abstract • Create deliverable set (v1)

  13. Potential collaboration process (general) Concept -> draft outline Steward ROW Wiki Existing Sources Advertise Initial/sample content Jumpstart Moderate (format, apply criteria) Contributions Expanded content Review & Comment Refined content Snapshot for Formalization (adoption) From stakeholders (including groups, workshops)

  14. Where do use cases come from? • Existing sources • e.g., NIST, OASIS • Stakeholder (& stakeholder rep) contributions

  15. How are they to be developed? • Multiple suggestions • AHG with online meetings • Each committee create their Top-3 • Series of joint meetings • Wiki (anyone in IDESG) • Distributed small group sessions • “Analyst group”

  16. Timeline • Goal: Within 9 months, have an initial draft set of use cases • Near term: February March April Wiki launched Populate Wiki Wiki design Collection Filter Draft criteria Workshop NOTE: Notional – not socialized

  17. (Proposed) May Workshop • Desired outcome: Agreed set of use cases for analysis (~10) • Review filtered set of use cases • Apply criteria • Refinements • Preconditions • Agree set of criteria • Committees, plenary members submit candidate use cases by 1 April

  18. Needed • Criteria to be applied • Priorities • Levels • Relevance • Cross section • How? • Solicit inputs • Joint meeting (or AHG) to review & define list

  19. Between now and then • Get Wiki setup and operational • Continue collection • Agree criteria • Detailed workshop planning • Content & process • We need you • Committees • Work with us on above • Individuals • Work with us on above

  20. Questions?

More Related