A.10. Use Case Definitions
In this section we describe the essential system-level use cases, identifying key interactions with the TRRS system.
The essential interactions with the TRRS system involve the following actors and transactions:
UC001 Product Information Retrieval Session
Key Actor: Information Technology User (IT User).
Key Transaction: Retrieving product information and experience reports from the TRRS system.
UC002 Product Information Entry Session
Key Actor: Vendor.
Key Transaction: Entering product information into the TRRS system.
UC003 Experience Report Entry Session
Key Actors: Solution Providers and Testers.
Key Transaction: Entering experience reports into the TRRS system.
This first set of use cases can be diagrammed as shown in ...
Get Software Architect Bootcamp now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.