Detailed User Requirements Template

http://BATemplates.com

2
Contents
1
2
3

Introduction.........................................................................................4
Approvals.............................................................................................5
Business Processses.............................................................................6
3.1 As-Is Business Processes.....................................................................6
3.2 To-Be Business Processes....................................................................6
4 Business Processes...............................................................................7
4.1 As-Is Business Processes.....................................................................7
4.2 To-Be Business Processes....................................................................7
5 Functional Requirements......................................................................8
5.1 Permissions Matrix (in place of Use Case Diagrams)................................8
5.2 Use Cases..........................................................................................9
5.2.1 Use Case 1...................................................................................9
5.2.2 Use Case 2...................................................................................9
5.2.3 Use Case 3...................................................................................9
5.2.4 Use Case N..................................................................................9
6 Non Functional Requirements.............................................................10
6.1 Performance.....................................................................................10
6.2 Reliability.........................................................................................10
6.3 Security...........................................................................................10
6.4 Capacity..........................................................................................10
6.5 Backup and Recovery........................................................................10
6.6 Auditing...........................................................................................10
6.7 Accessibility.....................................................................................10
6.8 Compatibility....................................................................................10
6.9 Redundancy.....................................................................................10
6.10
Scalability.....................................................................................10
6.11
Stress and Throughput...................................................................10

http://BATemplates.com

1 INTRODUCTION

http://BATemplates.com

2 APPROVALS
Approved by:

Date:
Name: Bob Jamison, CFO
Department: Finance

Approved by:

Date:
Name
Department

Approved by:

Date:
Name
Department

Approved by:

Date:
Name
Department

Approved by:

Date:
Name
Department

http://BATemplates.com

3 BUSINESS PROCESSSES
3.1

As-Is Business Processes

3.2

To-Be Business Processes

http://BATemplates.com

4 BUSINESS PROCESSES
4.1

As-Is Business Processes

4.2

To-Be Business Processes

http://BATemplates.com

5 FUNCTIONAL REQUIREMENTS
5.1

Permissions Matrix (in place of Use Case Diagrams)

User Groups
ADM Business Administrator
APP Approver
USR User
MAP Materials Approver
MAC Materials Control
REQ Requestor
VO View Only

X Indicates user group involvement in a use case.

Use
Use
Use
Use
Use
Use
Use
Use
Use
Use

Case
Case
Case
Case
Case
Case
Case
Case
Case
Case

Use Case
1 - Description
2 - Description
3 - Description
4 - Description
5 - Description
6 - Description
7 - Description
8 - Description
9 - Description
10 - Description

http://BATemplates.com

RAM
X
X
X
X
X
X

APP

USR

User Group
MAP
MAC
X

X
X
X
X
X

X
X

REQ
X

VO

5.2
5.2.1

Use Cases
Use Case 1

The use case elements below can be used to develop your use cases. Use only the elements your
project requires. Screen mock-ups and field definitions can be included for each of the use cases if
required.

Use Case ID Unique identifier for the use case.

Use case name descriptive name of the use case.
Version Normally indicates number of iterations the use case has had.
Goal Describes what actor is trying to achieve.
Summary Quick description of the normal flow of events of the use case.
Actors An actor is a person or other entity external to the system who interacts with
the system to perform the use cases. (not required if you are completing the
permissions matrix)
Trigger What causes the UC to begin
Preconditions What conditions have to be true before trigger can fire to cause the UC
to execute?
Post conditions What changes are guaranteed in the state of the system after UC
completion (only guaranteed if no exceptions occur)
Normal Flow The most common, or most desired path to follow to achieve the stated
use case goal.
Alternative flows - shows one of two things
o Different path that an actor can follow to achieve the stated use case goal. Post
conditions are still guaranteed in this case.
o User intentionally decides to abandon the goal before completing the UC (eg.
user decides to choose cancel instead of ok in a confirmation dialogue box).
Post conditions are not guaranteed in this case.
Exceptions Shows what the system should do if things go wrong. Post conditions are
not guaranteed if exception occurs.
Business Rules are declarative statements that cannot be violated by the system (i.e.
BR states what the rule is, not how/when/where/by who the rule is enforced)
Frequency of Use Estimate the number of times this use case will be performed by
the actors per some appropriate unit of time.
Assumptions What assumptions were made in the development of this use case.
Priority Indicate the relative priority of implementing the functionality required to
allow this use case to be executed.
Includes Indicate which other use cases are included in the execution of this use case.
Notes and Issues - List any additional comments about this use case or any remaining
open issues that must be resolved.

5.2.2

Use Case 2

5.2.3

Use Case 3

5.2.4

Use Case N

http://BATemplates.com

6 NON FUNCTIONAL REQUIREMENTS

6.1

Performance

6.2

Reliability

6.3

Security

6.4

Capacity

6.5

Backup and Recovery

6.6

Auditing

6.7

Accessibility

6.8

Compatibility

6.9

Redundancy

6.10 Scalability
6.11 Stress and Throughput
Etc.

http://BATemplates.com