Business Requirements Definition

<Requirement Name>

Information in this document is subject to change without notice.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any
purpose, without the express written permission of TEMENOS HEADQUARTERS SA
Copyright 2018 TEMENOS HEADQUARTERS SA. All rights reserved.
Business Requirements Document

Document History
Date Version Author Section(s) Amended

Document Sign Off

Date Version Name Company / Position

BSDD Reference (if applicable)

Name Version Date

<Date of BRD> Page 2 of 10 v1.3

Business Requirements Document

Table of Contents
1 Purpose ............................................................................................................................................ 4
2 Overview / Scope of Functional Requirements ............................................................................... 5
2.1 Requirements Overview .......................................................................................................... 5
2.1.1 In Scope .............................................................................................................................. 5
2.1.2 Out of Scope ....................................................................................................................... 5
2.2 Summary of Requirements ..................................................................................................... 5
2.3 Assumptions ............................................................................................................................ 5
3 Detailed Description of Functional Requirements ........................................................................... 6
3.1 Requirement BRD01-01 .......................................................................................................... 6
3.2 Requirement BRD01-02 .......................................................................................................... 6
3.3 Requirement BRD01-03 .......................................................................................................... 6
4 Detailed Description of Non-Functional Requirements .................................................................... 7
4.1 Volumes .................................................................................................................................. 7
4.2 Performance ............................................................................................................................ 7
4.3 Security ................................................................................................................................... 7
4.4 Migration.................................................................................................................................. 7
4.5 Data Requirements ................................................................................................................. 7
4.6 GDPR ...................................................................................................................................... 7
4.7 Others (amend heading) ......................................................................................................... 7
5 Use Cases ....................................................................................................................................... 9
5.1 Use Cases for Requirement BRD01-01 .................................................................................. 9
5.2 Use Cases for Requirement BRD01-02 .................................................................................. 9
5.3 Use Cases for Requirement BRD01-03 .................................................................................. 9
6 Glossary ......................................................................................................................................... 10

<Date of BRD> Page 3 of 10 v1.3

Business Requirements Document

1 Purpose
The purpose of this document is to gather the Client’s business requirements, both functional and
non-functional

The scope of the document is limited to collecting the requirements from the Client. We do not
recommend that any designs are included in this document.

The Client may have an existing methodology and associated templates for capturing business
requirements. If this is the case, then we need to ensure that the Client’s standard documents
contain the information described in this BRD. If not, then, this template should be used.

<Date of BRD> Page 4 of 10 v1.3

Business Requirements Document

2 Overview / Scope of Functional Requirements

ALL TEXT IN ITALICS IS TO BE REMOVED WHEN THE FIRST DRAFT IS COMPLETED

2.1 Requirements Overview

MANDATORY

A brief description of the Client and the nature of the Client’s business should be included here.

In addition to this, describe this functionality in overview and describe how it fits into the day-to-day
operations.

Describe what is in the scope of the requirements and, if known, what is not.

2.1.1 In Scope
Replace this text with your own.

2.1.2 Out of Scope

Replace this text with your own.

2.2 Summary of Requirements

MANDATORY

The summary table should be used to summarise all requirements in this document; each
requirement will then be described in detail later in the document.

Requirement Requirement Title Summary Description

Reference
BRD01-01 Replace this text with Replace this text with your own.
your own.
BRD01-02 Replace this text with Replace this text with your own.
your own.
BRD01-03 Replace this text with Replace this text with your own.
your own.

2.3 Assumptions
Document any assumptions to ensure that they are understood by all.

Replace this text with your own.

<Date of BRD> Page 5 of 10 v1.3

Business Requirements Document

3 Detailed Description of Functional Requirements

MANDATORY

This section must be repeated for each of the components of the functionality that is covered in this
document. Explain the proposed functionality in detail (the description should not be in any Temenos
product terms – Core Banking, Insight, TAP, WM, etc.). This section does NOT talk about deltas, it
simply states what is required by the Client.

Highlight the salient features of the required functionality. A diagrammatic representation of the
workflow indicating the different departments involved may be useful. This should be complemented
with the business rules to be applied for the processing. These should be taken from the BSDD and
referred to.

Please be clear and remember to document any outputs such as reports, enquiries, customer
advices.

Each sub-section below should relate back to a requirement in the summary Section 2.2 Summary of
Requirements

3.1 Requirement BRD01-01

Replace this text with your own.

3.2 Requirement BRD01-02

Replace this text with your own.

3.3 Requirement BRD01-03

Replace this text with your own.

<Date of BRD> Page 6 of 10 v1.3

Business Requirements Document

4 Detailed Description of Non-Functional Requirements

4.1 Volumes
OPTIONAL

Provide the volumes (of transactions, etc.) that will make use of the functionality in this BRD.

Replace this text with your own.

4.2 Performance
OPTIONAL

Describe any performance requirements.

Replace this text with your own.

4.3 Security
OPTIONAL

Describe any security requirements, for example authentication requirements for internet / mobile
banking.

Replace this text with your own.

4.4 Migration
OPTIONAL

Any migration-related requirements should be documented here.

Replace this text with your own.

4.5 Data Requirements

MANDATORY for BI Requirements

Any data-related requirements should be documented here, for example definitions of inbound and
outbound data..

Replace this text with your own.

4.6 GDPR
OPTIONAL

Any GDPR-related non-functional requirements.

Replace this text with your own.

4.7 Others (amend heading)

OPTIONAL

Any other non-functional requirements (ensure that the heading above is amended to reflect the
content here).
<Date of BRD> Page 7 of 10 v1.3
Business Requirements Document

Replace this text with your own.

<Date of BRD> Page 8 of 10 v1.3

Business Requirements Document

5 Use Cases
MANDATORY (see notes below)

This section contains the associated Use Cases. These should be present for each functional
requirement to ensure that the requirement is fully explained in detail and to minimise the possibility of
a requirement being misunderstood. These are a useful method of enhancing the description of
requirements when there is a lot of interaction between the system and one or several users (i.e.
Front End requirements, integration of various products, etc.). For some types of requirements, Use
Cases may not be applicable, if in doubt seek assistance from Temenos.

PLEASE NOTE: these are Use Cases not Test Cases

5.1 Use Cases for Requirement BRD01-01

Replace this text with your own.

5.2 Use Cases for Requirement BRD01-02

Replace this text with your own.

5.3 Use Cases for Requirement BRD01-03

Replace this text with your own.

<Date of BRD> Page 9 of 10 v1.3

Business Requirements Document

6 Glossary
Term Description
BRD Business Requirements Document
BSDD Business Solutions Design Document

<Date of BRD> Page 10 of 10 v1.3