SRS > Use Case Suite

Release Information

Project: PROJECT-NAME
Internal Release Number: X.Y.Z
Related Documents:
LINKS-TO-RELEVANT-STANDARDS
LINKS-TO-OTHER-DOCUMENTS
Process impact: A use case suite is simply a table of contents for the individual use cases. Much like a test suite, organizing the suite of use cases by priority, feature area, actor, business object, or release can help identify parts of the system that need additional use cases.
TODO: Before writing individual use cases, list the use cases that you think you will need. Organize them in lists or tables that leave visible blanks on this page if you are missing use cases. If a blank section of the tree or table does not need use cases, explicitly mark it "N/A", otherwise, mark it "TODO". Choose one or more of the organizations shown below. See the use case format reference page for more tips on specifying use cases and use case suites.
TIP: Refer back to the user stories in your user needs document. Use them for ideas and make sure that you cover all of them. Remember that use cases are more precise than user stories, and there may be several use cases for a given user story.

Use Cases by Feature Area

  • Administration
    • UC-00 Configure the site
  • User account management
    • UC-01 Register as a new user
    • UC-02 Request new password
    • UC-03 Edit user profile
  • Shopping
    • UC-10 Browse to product description
    • UC-11 Put product in cart
    • UC-12 Remove product from cart
  • Product catalog management
    • UC-20 Create product record
    • UC-21 Delete product record
    • UC-22 Put product on sale
  • Product reviews and ratings
  • Store department management
    • UC-22 Put product on sale
    • TODO: need more use cases here
  • Refunds and exchanges
    • TODO: need to write use cases here
  • FEATURE-AREA
  • FEATURE-AREA
  • FEATURE-AREA

Use Cases by Stakeholder

This information is shown in the use case diagram, but it is shown here as a nested list so that missing use cases are more noticeable. The set of stakeholders comes from the user needs document.

  • All Stakeholders
    • UC-01 Register as a new user
    • UC-02 Request new password
    • UC-03 Edit user profile
    • UC-10 Browse to product description
  • Administrators
    • UC-00 Configure the site
    • UC-20 Create product record
    • UC-21 Delete product record
  • Consumers
    • UC-11 Put product in cart
    • UC-12 Remove product from cart
  • Store department manager
    • UC-22 Put product on sale
  • Executives
    • N/A: this stakeholder never directly interacts with the system
  • Vendors
    • TODO: need to write use cases here
  • STAKEHOLDER
  • STAKEHOLDER
  • STAKEHOLDER

Use Cases by Priority

  • Essential
    • UC-00 Configure the site
    • UC-01 Register as a new user
    • UC-10 Browse to product description
    • UC-11 Put product in cart
    • UC-12 Remove product from cart
    • UC-20 Create product record
    • UC-21 Delete product record
    • UC-30 NAME OF USE CASE
    • UC-31 NAME OF USE CASE
    • UC-40 NAME OF USE CASE
    • UC-41 NAME OF USE CASE
  • Expected
  • Desired
    • N/A: There are no use cases with Priority = Desired
  • Optional

Use Cases by Business Object and Actor

TODO: Check for words of wisdom for additional advice on this template.
Company Proprietary
Copyright © 2003-2004 Method Labs. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.