Building Proper Use Cases
Based upon the information gather from both requirements gathering and subject matter experts, we have start to identify what the software must do, who does what, and how it must do it.
The formal process is to build a Use Case. This is a technical document that says who is doing what, how is it being done, and what conditions must exist for it to occur. We’ll also identify what happens if the task is completed successfully as well as if the task had an error involved.
Companies will often use a template, or form, to create this document, and then this goes into the work flow, so developers know what to build. It helps keep them on track, while preventing unnecessary scope creep.
A partial list for this project looks like:
| Use Case | Primary | Preconditions |
|---|---|---|
| Register Account | HR User | None |
| Purchase Service | HR User | HR User must already have an account. |
| Upload Employee List | HR User | HR User must already have an account. Service must be purchased. |
| Employee Fills Out Survey | Employee | Employee List must be uploaded. Employee’s email must be on file. Must be during Survey Open Dates. |
2 Comments