Scribd
Upload
98 views

UML - Use Case Template

This document is a project use case specification that outlines the key details of a use case, including a description, actors, assumptions, constraints, priority, pre-conditions, basic and alternative flows, exception flows, included use cases, post-conditions, business rules, special requirements, artifacts, glossary, and signatures approving the specification. It provides a template for documenting a specific use case in a standardized format.

Uploaded by

Marko Marulić
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
98 views

UML - Use Case Template

This document is a project use case specification that outlines the key details of a use case, including a description, actors, assumptions, constraints, priority, pre-conditions, basic and alternative flows, exception flows, included use cases, post-conditions, business rules, special requirements, artifacts, glossary, and signatures approving the specification. It provides a template for documenting a specific use case in a standardized format.

Uploaded by

Marko Marulić
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Project Use Case Specification

Project Name: Use Case Name: Unique Identifier:


Create links to referenced documents (e.g., Link_To_ ) by using Insert Hyperlink on your toolbar.

1. Description (Provide a brief description of this Use Case)

2. Actors (add lines as needed)


Actor 1: Actor 2:

3. Assumptions
1. 2.

4. Constraints
1. 2.

5. Priority (Select from High (Central to the purpose of this application; failure would bring the

system down), Medium (Important; Failure would cause significant disruption but the application can still be used) or Low (Failure would cause minor disruption in use of the system)):

6. Pre-Conditions (What conditions must be present before this Use Case can be used?
triggers the Use Case?): 1. 2.

What

Page 1 of 4

7. Basic Flow (Describe the most common version of this Use Case.
Flow Identifier: Step 1 2 3 4 <Enter flow name and brief descriptor here> User Action

Add lines as needed):

System Response (optional)

8. Alternative Flows (Describe other allowed variations of the Primary Use Case.
flow identifier blocks as needed): Flow Identifier: Step 1 2 3 4 Flow Identifier: Step 1 2 3 4 <Enter alternative flow name and brief descriptor here> System Response (optional) User Action <Enter alternative flow name and brief descriptor here> System Response (optional) User Action

Add additional

9. Exception Flows (Describe Error Conditions.


Step 1 2 3 4 User Action

Add additional flow identifier blocks as needed): System Response (optional)

Flow Identifier: <Enter error flow name and brief descriptor here>

10. Includes Use-Cases (list use cases that are included in the flows listed above)
1. 2.

Page 2 of 4

11. Post-Condition (list state of system and outputs at end of this use case)
This use case can end with any one of the following post-conditions: 1. 2.

12. Business Rules (Provide link to business rules that pertain to this use case)
Link to Business Rules

13. Special Requirements


1. 2.

14. Artifacts (list all outputs created by this use case)


1. 2.

15. Use-Case Glossary - (Glossary may be specific to this use case or general to the project.)
Link to Glossary

16. Comments/Concerns/Issues/Notes

17. Project Use-Case Specification Form / Signatures


Project Name: Project Manager:
I have reviewed the information contained in this Project Use-Case Specification Form and agree: Name Title Signature Date
(MM/DD/YYYY)

Page 3 of 4

17. Project Use-Case Specification Form / Signatures

The signatures above indicate an understanding of the purpose and content of this document by those signing it.

Page 4 of 4

You might also like