Use Case Model

Templates follow the explanatory text.

When doing Use Case Analysis with the Use Case templates, always have your Functional Requirements catalog, Non-Functional Requirements Catalog, Rules Catalog, Issues Catalog, and Glossary open and immediately available at the same time.  When you encounter a requirement, rule, issue, or new term that needs recording, place it in the appropriate catalog.  In addition, the UI Prototype team needs to work closely with the Use Case Analysis team, designing the preliminary UIs while the use cases are being developed.

Remember: CRUD(L).  Create, Read, Update, Delete, and List.

Create:  Steps needed to create a new domain element.  Do not forget to list all of the data elements that go into the creation of a new element.  Use parallel, concurrent steps if needed.
Read:  Steps needed to access a domain element.  May be merged with the Update use case.
Update: Steps needed to access and modify a domain element. Do not forget to list all of the data elements that can be modified for each element.  Use parallel, concurrent steps if needed.
Delete:  Steps need to delete a domain element.
List:  This use case should summarize the possible queries an actor can make on a list of domain elements.  Use parallel, concurrent steps if needed.

Templates:

Use Case Specification   (Doc)                                Explanation of Fields in the Use Case Specification (Doc)

Use Case Specification  (Agile -- Doc)                    Explanation of Fields in the Use Case Specification (HTML)

Use Case Catalog  (Doc)                                        Sample Use Case Specification (Doc)

Actor Catalog   (Doc)                                             Sample Use Case Catalog  (Doc)

Use Case Model Report (Hardwired -- Doc)            Sample Actor Catalog  (Doc)

Use Case Model Report (Master                             Sample Use Case Diagrams (Doc)
Document Format -- Doc)