Use Case Specification: Prepared By: Date: (AD) Reviewed By: Date: (Architect/AD)

<Project Name> Application Vision Statement Page - 1 of 6
Use Case Specification
For
<USE CASE NAME>
Prepared by : Date :
(AD)
Reviewed by : Date :
(Architect/AD)
NTL INTERNAL VERSION <1.0> Date of release: <date>

Revision History
Date Version Description Author

TABLE OF CONTENTS
1. DESCRIPTION........................................................................................................................ 4
1.1. USE CASE MODEL....................................................................................................... 4
1.2. REFERENCE TO TECHNICAL DOCUMENTATION....................................................................4
1.3. CHARACTERISTIC INFORMATION.............................................................................4
2. FLOW OF EVENTS................................................................................................................ 4
2.1. BASIC FLOW OF EVENTS.................................................................................................. 4
2.2. ALTERNATIVE FLOWS........................................................................................................ 4
2.2.1. Other conditional flows................................................................................................ 4
2.2.2. Error flows................................................................................................................... 4
2.2.3. Business Rules............................................................................................................ 5
3. EXTENSION POINTS............................................................................................................. 5
4. SPECIAL REQUIREMENTS................................................................................................... 5
5. RELATED INFORMATION (OPTIONAL).................................................................................5
6. ASSUMPTIONS...................................................................................................................... 6
7. DEPENDENCIES.................................................................................................................... 6
8. CHANGE CASES (OPTIONAL).............................................................................................. 6
9. ATTACHMENTS (OPTIONAL)................................................................................................ 6
10. APPENDIX A........................................................................................................................... 6
11. APPENDIX B........................................................................................................................... 6

Use Case Specification: <Use Case Name>

1. DESCRIPTION
<The description briefly conveys the role and purpose of the use case. A single
paragraph will suffice for this description>
1.1. USE CASE MODEL

<Draw the Use case diagram here>
1.2. REFERENCE TO TECHNICAL DOCUMENTATION

Document Name Description
1.3. CHARACTERISTIC INFORMATION
Scope < System boundaries for this use case >

Preconditions [Input] < Expected state of the system at the start of this use case >
Success End <The state of the system upon successful completion>
Condition [Output]
Failed End Condition <The state of the system if goal abandoned>
Primary Actor <A role name for the primary actor, or description>
<The action upon the system that starts the use case, may be
Initiated/Activated time event>
When
2. FLOW OF EVENTS
2.1. BASIC FLOW OF EVENTS

Step Actor Action System Response
No.
# <The description of the Actor action <The response of the system to this
which starts this use case> stimulus i.e. goal delivery >
2.2. ALTERNATIVE FLOWS
2.2.1. Other conditional flows

No.
2.2.2. Error flows


No.
2.2.3. Business Rules
3. EXTENSION POINTS
<Put here their extensions, one at a time, each referring to the step of the Basic flow>
Altered Condition System Response
Step
No.
# < Condition > < Action or sub.use case >
4. SPECIAL REQUIREMENTS
<A special requirement is typically a nonfunctional requirement that is specific to a use
case, but is not easily or naturally specified in the text of the use case's event flow. >
Additional
Functionality
Legal and regulatory
requirements
Performance
requirements
Design constraints
Security
Considerations
5. RELATED INFORMATION (OPTIONAL)

Priority: <How critical to your system / organization>
Frequency <How often it is expected to happen>
Use Case Relationships
(i) Super ordinate Use <Name and link of use case that includes this one>
Case
(ii) Subordinate Use < Depending on tools, name and links to sub-use cases>
Cases
Interaction point to <e.g. interactive, static files, database>
Primary Actor
Secondary Actors <List of other systems needed to accomplish use case>
Interaction point to <e.g. interactive, static, file, database, timeout>
Secondary Actors
Complexity of the Use <The analyst is to grade the use case as Complex (C) ,
case Moderate (M) or Simple (S) as per the functionality and the

level of the use case>
6. ASSUMPTIONS
< Any assumptions made at this point. By the time the use case is finalized, this section
should vanish. >
Assumption # Description
7. DEPENDENCIES
Dependency # Description
8. CHANGE CASES (OPTIONAL)

<Defines cases within the Main Flow where a step is expected to change in the future.
This requirement will not be implemented with the Use Case but should be considered
during design. >
Change Case # Description
9. ATTACHMENTS (OPTIONAL)
<Any figures or diagrams referenced within the body of the event flow or any alternative
flows. These diagrams could be visualizations of the user interface or use case
diagrams. >
10. APPENDIX A
<[OPTIONAL]: if UI prototype has been done, you can describe it here by providing
links to prototype. >
11. APPENDIX B
<[OPTIONAL] Paste a Process flow related to this Use Case here e.g. a Visio diagram
depicting the flow of events related to this Use Case>

Use Case Specification: Prepared By: Date: (AD) Reviewed By: Date: (Architect/AD)

Uploaded by

Copyright:

Available Formats

Use Case Specification: Prepared By: Date: (AD) Reviewed By: Date: (Architect/AD)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Use Case Specification: Prepared By: Date: (AD) Reviewed By: Date: (Architect/AD)

Uploaded by

Copyright:

Available Formats

<Project Name> Application Vision Statement Page - 1 of 6

Use Case Specification

<USE CASE NAME>

NTL INTERNAL VERSION <1.0> Date of release: <date>

NTL INTERNAL VERSION <1.0> Date of release: <date>

5. RELATED INFORMATION (OPTIONAL).................................................................................5

8. CHANGE CASES (OPTIONAL).............................................................................................. 6

10. APPENDIX A........................................................................................................................... 6

11. APPENDIX B........................................................................................................................... 6

NTL INTERNAL VERSION <1.0> Date of release: <date>

Use Case Specification: <Use Case Name>

1.1. USE CASE MODEL

1.2. REFERENCE TO TECHNICAL DOCUMENTATION

1.3. CHARACTERISTIC INFORMATION

Scope < System boundaries for this use case >

2.1. BASIC FLOW OF EVENTS

2.2. ALTERNATIVE FLOWS

2.2.1. Other conditional flows

2.2.2. Error flows

NTL INTERNAL VERSION <1.0> Date of release: <date>

Step Actor Action System Response

2.2.3. Business Rules

5. RELATED INFORMATION (OPTIONAL)

NTL INTERNAL VERSION <1.0> Date of release: <date>

level of the use case>

8. CHANGE CASES (OPTIONAL)

NTL INTERNAL VERSION <1.0> Date of release: <date>

You might also like