0% found this document useful (0 votes)
34 views

Use Case Document

This document provides a template for documenting a use case, including sections for describing the use case, pre-conditions, post-conditions, actors, main and alternative flows, related use cases, business rules, user interface notes, a use case diagram, and any prototypes or screens. It includes tables for revision history, pre-conditions, post-conditions, actors, and business rules. The main flow section describes the typical interactions between the user and system, while alternative and exception flows cover special conditions.

Uploaded by

Sujal Javia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
34 views

Use Case Document

This document provides a template for documenting a use case, including sections for describing the use case, pre-conditions, post-conditions, actors, main and alternative flows, related use cases, business rules, user interface notes, a use case diagram, and any prototypes or screens. It includes tables for revision history, pre-conditions, post-conditions, actors, and business rules. The main flow section describes the typical interactions between the user and system, while alternative and exception flows cover special conditions.

Uploaded by

Sujal Javia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Use Case Document <Version No.

>

Use Case Document


<CLIENT NAME>
<Project Name>
<Version Number>

1|Page
<Company Name>
Use Case Document <Version No.>

Document Revision Control Table

Version Date Change Description A/M/D Prepared By Approved By


No. Revised (Add/Modify/ Deleted)

           

2|Page
<Company Name>
Use Case Document <Version No.>

Table of Contents

1. <Use Case Name>


1.2 Description 4
1.3 Pre-condition(s) 4
1.4 Post-condition(s) 4
1.5 Actor(s) 4
1.6 Flow of Events
1.5.1 Main Flow 4
1.5.2 Alternative Flows 5
1.5.3 Exception Flows 5
1.6 Related Use Cases(s) 5
1.7 Business Rules: Use Case 5
1.8 UI Notes 5
1.9 Use Case Diagram 6
1.10 Prototype/UI Screens 6

3|Page
<Company Name>
Use Case Document <Version No.>

<Use Case Name>


1.1 Description

[Describe the use case document while detailing the context and background of the functionality covered within.]

1.2 Pre-condition(s)

[Describe the conditions that must be true before the use case can be started.]

Pre-condition ID: Description

PC1
PC2

PC3

1.3 Post-condition(s)

[Describe the system's state at the conclusion of the use case execution.]

Post-condition ID Description

1.4 Actor(s)

[An actor is a person or other entity external to the system which interacts with the system. Define all the actors of
the use case here.]

Actor Type Role Restriction

1.5 Flow of Events


1.5.1 Main Flow

[Describe system responses that will take place during execution of the use case under normal, expected
conditions.]

User Action System Action


MF.1.1 MF.1.A.1
MF.2.1 MF.2.A.1

4|Page
<Company Name>
Use Case Document <Version No.>

MF.3.1 MF.3.A.1

MF.4.1 MF.4.A.1

MF.5.1 MF.5.A.1

1.5.2 Alternative Flows

[Describe legitimate branches from the main flow to handle extraordinary conditions.]

1.5.3 Exception Flows

[Describe any anticipated error conditions that could occur during execution of the use case.]

1.6 Related Use Cases(s)


[List any other use cases related to this use case.]

Related Use Case(s) Name:

Includes
Extends

1.7 Business Rules: Use Case


[Describe specific rules or conditions that are imposed by the business.]

Source (Code
Business Date Source
Description of Business Rule Section if
Rule ID Defined the Rule
applicable, etc.)

BR.1
BR.2
BR.3

1.8 UI Notes
[Any User interface notes and details will come in here.]

5|Page
<Company Name>
Use Case Document <Version No.>

Screen
Screen Field Label Type Business Definition
Reference

1.9 Use Case Diagram


[Attach the use case diagram that was created concerning the use case document.]

1.10 Prototype/UI Screens


[Include any prototype or screens that were created to aid understanding regarding the use case document.]

6|Page
<Company Name>

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy