Kids N Toys

Business Requirements Definition

[Project Name]

Author:
Date:
Version:

[Author]
[yyyymmdd]
[#.#]

Operator notes:
All instructional text is displayed in blue font colour in the template. These should be deleted prior to
the document being distributed for review and approval.
Update text within square brackets which is placeholder text with relevant text.
E.g. [yyyymmdd] should be changed to latest date 20130305
Use this basic structure and type sizing for all your covers. Do not manipulate or rescale any of the
graphic components. Use initial caps in your headings with capital letters for proper nouns only.
Update all sections as needed. If the section is not relevant to the project type N/A or Not Applicable,
do not delete the section.

[Project Name]

Document Control
Document location

Location

Author

Position

Name

Contact no

Revision history

Version

Issue date

Author/editor

Description/Summary of changes

Name

Position

Reviewed by

Version

Issue date

Review date

Approvals
Approval refers to the approvers acceptance of the content and overall intention of this document, including
acceptance of any commitments described in order to successfully deliver the initiative. The approver, where
relevant, also confirms that this document complies with relevant strategies, policies and regulatory
requirements.

Version

Issue date

Name

Business Requirements Definition Template v1.0

Position

Approval date

Page 2 of 11

[Project Name]

Version

Issue date

Name

Position

Approval date

Related documents

Document

Business Requirements Definition Template v1.0

Location

Page 3 of 11

[Project Name]

Table of Contents
1

INTRODUCTION ........................................................................................................................................ 6
1.1

Document Purpose ............................................................................ Error! Bookmark not defined.

1.2

Objectives .......................................................................................................................................... 6

1.3

Background ........................................................................................................................................ 6

SCOPE ....................................................................................................................................................... 6
2.1

Inclusions ........................................................................................... Error! Bookmark not defined.

2.2

Exclusions .......................................................................................... Error! Bookmark not defined.

2.3

Context............................................................................................... Error! Bookmark not defined.

CURRENT SYSTEM .................................................................................................................................. 6

3.1

Current Process ................................................................................................................................. 6

3.2

Issues................................................................................................................................................. 6

PROPOSED SOLUTION/ SYSTEM........................................................................................................... 7

4.1

Process Definition .............................................................................................................................. 7

4.1.1

Process Description

4.1.2

Process Swim Lane

4.1.3

Business rules

4.2

Scenarios ........................................................................................................................................... 7

4.3

Special Considerations ...................................................................................................................... 7

REQUIREMENTS....................................................................................................................................... 8
5.1

Business Requirements ..................................................................................................................... 8

5.2

Functional Requirements ................................................................................................................... 8

5.2.1

Common Features

5.2.2

Reporting

5.2.3

{}

5.3

System Requirements ....................................................................................................................... 8

5.3.1

Hardware

5.3.2

Software

5.3.3

Documentation

5.3.4

Support

Business Requirements Definition Template v1.0

Page 4 of 11

[Project Name]

5.4

Non- Functional Requirements .......................................................................................................... 9

5.4.1

Usability

5.4.2

Reliability

5.4.3

Performance

5.4.4

Security

5.4.5

Data Integrity

5.4.6

Compatibility

5.4.7

Capacity

10

5.5

Use Cases ....................................................................................................................................... 10

5.6

Requirements Traceability Matrix .................................................................................................... 10

5.7

Exceptions ....................................................................................................................................... 10

5.8

Acceptance Criteria ......................................................................................................................... 10

CONSTRAINTS........................................................................................................................................ 11

ASSUMPTIONS ....................................................................................................................................... 11

DEPENDENCIES ..................................................................................................................................... 11

RISKS ....................................................................................................................................................... 11

10 SOLUTION DESIGN ................................................................................................................................ 11

11 REFERENCES ......................................................................................................................................... 11
11.1

Acronyms and Definitions ................................................................................................................ 11

11.2

Interviews ......................................................................................................................................... 11

11.3

Other ................................................................................................................................................ 11

Business Requirements Definition Template v1.0

Page 5 of 11

[Project Name]

1
1.1

Introduction
Objectives

A description of the objectives that will be used to measure the success of the project and the products/services
proposed. Ensure that the objective meets the SMART criteria i.e. Specific, Measurable, Attainable, Results
Oriented, Time bound.

1.2

Background

An overview of what the current system is, if any exists, and what the user(s) expect the new system to deliver
and the project background.

2 Scope
A definition of the scope of the project requirements. What needs to be fulfilled?.

3 Current System
3.1

Current Process

Explain the organisation and business environment (use section 4.1 below as a template)

3.2

Issues

Business Requirements Definition Template v1.0

Page 6 of 11

[Project Name]

4 Proposed Solution/ System

4.1

Process Definition

Define the proposed solution

4.1.1 Process Description

Item

Description

Name

<Process/function name>

Owner

<process/function owner>

Description

Summary of process

Directives
Pre-Conditions
Post-Conditions
Trigger
Outcome
Frequency of Execution
Number of Participants
Metrics
Forms
Roles
Notes

4.1.2 Process Swim Lane

Include Swim Lanes

4.1.3 Business rules

ID
BU-01

Description

BU-02
BU-03

4.2

Scenarios

4.3

Special Considerations

Include design considerations, non-functional, legal, regulatory etc

Business Requirements Definition Template v1.0

Page 7 of 11

[Project Name]

5 Requirements
All requirements are defined in point form and are rated either Mandatory (M) or Highly Desirable (HD) or
Desirable (D), dependent on business need and University Policy.

5.1

Business Requirements

Requirement

Preference

1.1.1.1
1.1.1.2
1.1.1.3

5.2

Functional Requirements

5.2.1 Common Features

Requirement

Preference

1.1.1.4
1.1.1.5
1.1.1.6

5.2.2 Reporting
ID

Requirement

Preference

1.1.1.7
1.1.1.8
1.1.1.9

5.2.3 {}
ID

Requirement

Preference

1.1.1.10
1.1.1.11
1.1.1.12

5.3

System Requirements

5.3.1 Hardware
ID

Requirement

Preference

1.1.1.13
1.1.1.14
1.1.1.15

5.3.2 Software
ID

Requirement

Preference

1.1.1.16
1.1.1.17
1.1.1.18

Business Requirements Definition Template v1.0

Page 8 of 11

[Project Name]

5.3.3 Documentation
ID

Requirement

Preference

1.1.1.19
1.1.1.20
1.1.1.21

5.3.4 Support
ID

Requirement

Preference

1.1.1.22
1.1.1.23
1.1.1.24

5.4

Non- Functional Requirements

5.4.1 Usability
ID

Requirement

Preference

1.1.1.25
1.1.1.26
1.1.1.27

5.4.2 Reliability
ID

Requirement

Preference

1.1.1.28
1.1.1.29
1.1.1.30

5.4.3 Performance
ID

Requirement

Preference

1.1.1.31
1.1.1.32
1.1.1.33

5.4.4 Security
ID

Requirement

Preference

1.1.1.34
1.1.1.35
1.1.1.36

5.4.5 Data Integrity

ID

Requirement

Preference

1.1.1.37
1.1.1.38
1.1.1.39

5.4.6 Compatibility
ID

Requirement

Preference

1.1.1.40
1.1.1.41
1.1.1.42
Business Requirements Definition Template v1.0

Page 9 of 11

[Project Name]

5.4.7 Capacity
ID

Requirement

Preference

1.1.1.43
1.1.1.44
1.1.1.45

5.5

Use Cases

Insert as many use cases as relevant to the project

Use Case ID:
Use Case Name:
Created By:
Date Created:

Last Updated By:

Date Last Updated:

Actor:
Description:
Preconditions:
Postconditions:
Priority:
Frequency of Use:
Normal Course of Events:
Alternative Courses:
Exceptions:
Includes:
Special Requirements:
Assumptions:
Notes and Issues:

5.6

Requirements Traceability Matrix

Include the ID number that relates to each of the relevant columns

Business Rule

5.7
ID
EX-01

Business Requirement

Functional/ Non Functional Requirement Use Case

Exceptions
Description

EX-02
EX-03

5.8
ID
AC-01

Acceptance Criteria
Description

AC-02
AC-03
Business Requirements Definition Template v1.0

Page 10 of 11

[Project Name]

6 Constraints
Constraints that inhibit the projects ability to deliver the requirements.

7 Assumptions
Any assumptions made, in conjunction with the user(s), which may become apparent at the later stages of the
specification process. For example, the Functional Specification may show certain requirements not to be
feasible.

8 Dependencies
Any dependency to which the projects completion is contingent upon.

9 Risks
Any quantifiable losses that might arise.

10 Solution Design
Proposed solution of the new system. This will be obtained from the development team for inclusion in this
report.

11 References
11.1

Acronyms and Definitions

An explanation of any specific terms / acronyms used in this document.

Acronym or Term

11.2

Definition

Interviews

Details of the users or groups of users interviewed, in order to gather the information required to prepare this
document. This could include names, dates, and a brief summary of what was discussed.

11.3

Other

Any other general comments which may be considered as related to the requirements of the user(s).

Business Requirements Definition Template v1.0

Page 11 of 11