7.0 KiB
Project:
Internal Release Number:
::X.Y.Z
Related Documents:
- SRS > Use Case Suite
- Project proposal > User needs
- SRS > Feature set
- Use case format
- ::LINK TO USE CASE DIAGRAM
- ::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, functional 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 a way that will purposely leave visible blanks on this page if you are missing use cases. E.g., see "Scalability and availability". Choose one or more of the organizations show below.
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.
TIP: The use case suite can be organized into nested lists according to other coverage criteria, e.g., by actor. Or, it can be organized into tables that consider two aspects at a time, e.g., business objects vs. actor. If a certain section of the tree or table does not need use cases, explicitly mark it "N/A". Otherwise, mark it "TODO".
Use Cases by Functional Area
- ::User account management
- ::Course management
- ::Course enrollment
- ::Scalability and availability
- ::N/A: These features are completely automated and internal, users never interact with them
- ::Facilities management
- ::Grading and transcripts
- ::TODO: need to write use cases here
- ::FUNCTIONAL AREA SEVEN
- ::FUNCTIONAL AREA EIGHT
- ::FUNCTIONAL AREA NINE
Use Cases by Stakeholder
This information is shown in the use case diagram, but it is shown here as a list or table so that missing use cases are more noticeable.
- ::All Stakeholders
- ::Students
- ::Instructors
- ::UC-04 View user profile
- ::Administrators
- ::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
- Expected
- Desired
- ::N/A: There are no use cases with Priority = Desired
- Optional
Use Cases by Business Object and Actor
| BO \ Actor | All | ::Student | ::Instructor | ::Admin |
|---|---|---|---|---|
| ::Student record | ::N/A | ::View user profile | ::N/A | |
| ::Course | ::View catalog description | ::TODO | ||
| ::Room | ::View room description | ::N/A | ::N/A | ::Assign room |