ReadySetGit/Use-Case-Suite.md

149 lines
7.0 KiB
Markdown
Raw Normal View History

2021-08-01 13:15:57 +00:00
<!-- markdownlint-disable MD033 -->
2023-03-24 16:29:16 +00:00
<!-- markdownlint-disable-next-line first-line-h1 -->
2018-08-23 17:23:45 +00:00
##### Project
2018-08-24 10:30:24 +00:00
2018-08-23 17:23:45 +00:00
::[PROJECT-NAME](Home)
2018-08-14 12:48:17 +00:00
2018-08-23 17:23:45 +00:00
##### Internal Release Number
2018-08-24 10:30:24 +00:00
2018-08-14 12:48:17 +00:00
::X.Y.Z
2018-08-23 17:23:45 +00:00
##### Related Documents
2018-08-24 10:30:24 +00:00
2018-08-14 22:37:52 +00:00
- [SRS](SRS) > Use Case Suite
- [Project proposal](Proposal) > [User needs](User-Needs)
- [SRS](SRS) > [Feature set](Feature-Set)
- [Use case format](Use-Case-Format)
2018-08-14 12:48:17 +00:00
- ::LINK TO USE CASE DIAGRAM
- ::LINKS TO RELEVANT STANDARDS
- ::LINKS TO OTHER DOCUMENTS
2018-08-24 10:30:24 +00:00
2018-08-14 12:48:17 +00:00
---
**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.
2023-03-24 16:29:16 +00:00
_TODO: Before writing individual use cases, list the use cases that you
2018-08-14 12:48:17 +00:00
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
2023-03-24 16:29:16 +00:00
show below._
2018-08-14 12:48:17 +00:00
2023-03-24 16:29:16 +00:00
_TIP: Refer back to the user stories in your [user needs](User-Needs)
2021-08-01 13:15:57 +00:00
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
2023-03-24 16:29:16 +00:00
may be several use cases for a given user story._
2018-08-14 12:48:17 +00:00
2023-03-24 16:29:16 +00:00
_TIP: The use case suite can be organized into nested lists according to
2018-08-14 12:48:17 +00:00
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
2023-03-24 16:29:16 +00:00
cases, explicitly mark it "N/A". Otherwise, mark it "TODO"._
2018-08-14 12:48:17 +00:00
### Use Cases by Functional Area
- ::User account management
2018-08-14 22:37:52 +00:00
- ::[UC-00](Use-Cases#UC-00) Configure the site
- ::[UC-01](Use-Cases#UC-01) Register as a new user
- ::[UC-02](Use-Cases#UC-02) Request new password
- ::[UC-03](Use-Cases#UC-03) Edit user profile
- ::[UC-04](Use-Cases#UC-04) View user profile
2018-08-14 12:48:17 +00:00
- ::Course management
2018-08-14 22:37:52 +00:00
- ::[UC-10](Use-Cases#UC-10) Create course
- ::[UC-11](Use-Cases#UC-11) View catalog description
- ::[UC-31](Use-Cases#UC-31) Assign course to room
2018-08-14 12:48:17 +00:00
- ::Course enrollment
2018-08-14 22:37:52 +00:00
- ::[UC-20](Use-Cases#UC-20) Enroll in course
- ::[UC-21](Use-Cases#UC-21) Drop course
2018-08-14 12:48:17 +00:00
- ::Scalability and availability
2018-08-24 10:30:24 +00:00
- ::N/A: These features are completely automated and internal, users never interact with them
2018-08-14 12:48:17 +00:00
- ::Facilities management
2018-08-14 22:37:52 +00:00
- ::[UC-30](Use-Cases#UC-30) View room description
- ::[UC-31](Use-Cases#UC-31) Assign course to room
2018-08-14 12:48:17 +00:00
- ::Grading and transcripts
- ::TODO: need to write use cases here
- ::FUNCTIONAL AREA SEVEN
2018-08-14 22:37:52 +00:00
- ::[UC-70](Use-Cases#UC-70) NAME OF USE CASE
- ::[UC-71](Use-Cases#UC-71) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
- ::FUNCTIONAL AREA EIGHT
2018-08-14 22:37:52 +00:00
- ::[UC-80](Use-Cases#UC-80) NAME OF USE CASE
- ::[UC-81](Use-Cases#UC-81) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
- ::FUNCTIONAL AREA NINE
2018-08-14 22:37:52 +00:00
- ::[UC-90](Use-Cases#UC-90) NAME OF USE CASE
- ::[UC-91](Use-Cases#UC-91) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
### Use Cases by Stakeholder
This information is shown in the [use case diagram](LINK-TO-DIAGRAM),
but it is shown here as a list or table so that missing use cases are
more noticeable.
- ::All Stakeholders
2018-08-14 22:37:52 +00:00
- ::[UC-11](Use-Cases#UC-11) View catalog description
- ::[UC-30](Use-Cases#UC-30) View room description
2018-08-14 12:48:17 +00:00
- ::Students
2018-08-14 22:37:52 +00:00
- ::[UC-01](Use-Cases#UC-01) Register as a new user
- ::[UC-02](Use-Cases#UC-02) Request new password
- ::[UC-03](Use-Cases#UC-03) Edit user profile
- ::[UC-20](Use-Cases#UC-20) Enroll in course
- ::[UC-21](Use-Cases#UC-21) Drop course
2018-08-14 12:48:17 +00:00
- ::Instructors
2018-08-14 22:37:52 +00:00
- ::[UC-04](Use-Cases#UC-04) View user profile
2018-08-14 12:48:17 +00:00
- ::Administrators
2018-08-14 22:37:52 +00:00
- ::[UC-00](Use-Cases#UC-00) Configure the site
- ::[UC-10](Use-Cases#UC-10) Create course
- ::[UC-31](Use-Cases#UC-31) Assign course to room
2018-08-14 12:48:17 +00:00
- ::Executives
- ::N/A: this stakeholder never directly interacts with the system
- ::Vendors
- ::TODO: need to write use cases here
- ::STAKEHOLDER
2018-08-14 22:37:52 +00:00
- ::[UC-70](Use-Cases#UC-70) NAME OF USE CASE
- ::[UC-71](Use-Cases#UC-71) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
- ::STAKEHOLDER
2018-08-14 22:37:52 +00:00
- ::[UC-80](Use-Cases#UC-80) NAME OF USE CASE
- ::[UC-81](Use-Cases#UC-81) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
- ::STAKEHOLDER
2018-08-14 22:37:52 +00:00
- ::[UC-90](Use-Cases#UC-90) NAME OF USE CASE
- ::[UC-91](Use-Cases#UC-91) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
### Use Cases by Priority
- Essential
2018-08-14 22:37:52 +00:00
- ::[UC-00](Use-Cases#UC-00) Configure the site
- ::[UC-01](Use-Cases#UC-01) Register as a new user
- ::[UC-10](Use-Cases#UC-10) Create course
- ::[UC-11](Use-Cases#UC-11) View catalog description
- ::[UC-20](Use-Cases#UC-20) Enroll in course
- ::[UC-21](Use-Cases#UC-21) Drop course
- ::[UC-30](Use-Cases#UC-30) Assign course to room
- ::[UC-31](Use-Cases#UC-31) Assign course to room
2018-08-14 12:48:17 +00:00
- Expected
2018-08-14 22:37:52 +00:00
- ::[UC-02](Use-Cases#UC-02) Request new password
- ::[UC-03](Use-Cases#UC-03) Edit user profile
- ::[UC-04](Use-Cases#UC-04) View user profile
- ::[UC-70](Use-Cases#UC-70) NAME OF USE CASE
- ::[UC-71](Use-Cases#UC-71) NAME OF USE CASE
- ::[UC-80](Use-Cases#UC-80) NAME OF USE CASE
- ::[UC-81](Use-Cases#UC-81) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
- Desired
- ::N/A: There are no use cases with Priority = Desired
- Optional
2018-08-14 22:37:52 +00:00
- ::[UC-30](Use-Cases#UC-30) View room description
- ::[UC-90](Use-Cases#UC-90) NAME OF USE CASE
- ::[UC-91](Use-Cases#UC-91) NAME OF USE CASE
2018-08-14 12:48:17 +00:00
### Use Cases by Business Object and Actor
<!-- Hint: turn off text wrap for this large table -->
2023-03-24 16:29:16 +00:00
| BO \ Actor | All | ::Student | ::Instructor | ::Admin |
| ---------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------- | --------------------------------------------------------------------------------------------- |
| ::Student record | ::N/A | <ul><li>::[Register as new user](Use-Cases#uc-01)</li><li>::[Request new password](Use-Cases#uc-02)</li><li>::[Edit user profile](Use-Cases#uc-03)</li></ul> | ::[View user profile](Use-Cases#uc-04) | ::N/A |
| ::Course | ::[View catalog description](Use-Cases#uc-11) | <ul><li>::[Enroll in course](Use-Cases#uc-20)</li><li>::[Drop course](Use-Cases#uc-21)</li></ul> | ::TODO | <ul><li>::[Create course](Use-Cases#uc-10)</li><li>::[Assign room](Use-Cases#uc-31)</li></ul> |
| ::Room | ::[View room description](Use-Cases#uc-30) | ::N/A | ::N/A | ::[Assign room](Use-Cases#uc-31) |