business requirements document (brd) web viewthe use case may also be represented visually in uml in...

Business Requirements Document (BRD)

Project Management

KEMISTRY - ABSTRACT[Draw your reader in with an engaging abstract. It is typically a short summary of the document. When you’re ready to add your content, just click here and start typing.]

Your NameVersion: 0

Last Updated: 5/05/2023 6:10 AM

Business Requirements Document: Kemistry

Version and ApprovalsVersion HistoryVersion # Date Revised By Reason for change

This document has been approved as the official Business Requirements Document for <project name>, and accurately reflects the current understanding of business requirements. Following approval of this document, requirement changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals.

Document ApprovalsApprover Name Project Role Signature/Electronic Approval Date

Project DetailsProject Name Enter Project Name

Project Type (e.g. New Initiative or Phase II)

Project Start Date

Project End Date

Project Sponsor

Project Manager

Page 1 of 19


1. Contents1. CONTENTS........................................................................................................2

2. INTRODUCTION..................................................................................................4

2.1 Document Purpose.................................................................................................................... 4

2.2 Intended Audience.....................................................................................................................4

3. DOCUMENT RESOURCES....................................................................................4

4. GLOSSARY OF TERMS........................................................................................4

5. PROJECT OVERVIEW..........................................................................................5

5.1 Project Background....................................................................................................................5

5.2 Purpose of Business Requirements...........................................................................................5

5.3 Business Goals/Objectives to be achieved................................................................................5

5.4 Benefits/Rationale......................................................................................................................5

5.5 Project Dependencies................................................................................................................5

5.6 Stakeholders.............................................................................................................................. 5

6. KEY ASSUMPTIONS AND CONSTRAINTS...............................................................6

6.1 Key Assumptions.......................................................................................................................6

6.2 Constraints................................................................................................................................. 6

6.3 References................................................................................................................................. 6

7. SCOPE REQUIREMENTS.....................................................................................6

7.1 Actor Profiles.............................................................................................................................. 6

7.2 Use Cases.................................................................................................................................. 7

7.3 In Scope..................................................................................................................................... 8

7.4 Out of Scope.............................................................................................................................. 9

8. BUSINESS REQUIREMENTS.................................................................................9

8.1 Business Domain....................................................................................................................... 9

Page 2 of 19


8.2 Functional Requirements...........................................................................................................9

9. NON-FUNCTIONAL REQUIREMENTS....................................................................13

9.1 Security Requirements.............................................................................................................13

9.1.1 Authentication...................................................................................................................... 13

9.1.2 Authorization and Access Controls......................................................................................13

9.2 Standards................................................................................................................................. 13

9.3 Usability.................................................................................................................................... 14

9.4 Availability Requirements.........................................................................................................14

9.5 Performance Requirements.....................................................................................................14

9.6 Scalability Requirements..........................................................................................................14

10. DATA REQUIREMENTS..................................................................................14

10.1 Data Architecture..................................................................................................................... 14

11. INTERFACE REQUIREMENTS..........................................................................14

12. APPENDIXES................................................................................................15

12.1 Appendix A – Business Process Flows....................................................................................15

12.2 Appendix B – Business Rules Catalog.....................................................................................15

12.3 Appendix C- Models................................................................................................................. 16

12.4 Use Case Narrative Instructions...............................................................................................16

13. APPROVAL...................................................................................................17

Page 3 of 19


2. Introduction2.1Document PurposeThis document defines the high level requirements [insert project name]. It will be used as the basis for the following activities:

Determining client business requirements? Developing test plans, test scripts, and test cases? Determining project completion? Assessing project success?

2.2 Intended Audience< The main intended audience for this document are the business owners of the proposed system. This document should be readable by business owners of the proposed system. They must be able to verify that their business requirements have been documented here completely, accurately and unambiguously.

Data Architects, Application Architects and Technical Architects would also find the information in this document useful when they need to design a solution that will address these business requirements.

Since the requirements are documented here in Technology-independent manner, the end-users of the system should be able to comprehend the requirements fairly easily from this document. >

3. Document ResourcesName Business Unit Role<Identify all stakeholders and resources involved in gathering requirements>E.g. Stefan

4. Glossary of TermsTerm/Acronym Definition<Identify any terms and acronyms used within this document>

Page 4 of 19


5. Project Overview5.1 Project Background<This information can be taken from the Project Charter. This is a brief description of what the project is about. It includes the current situation, the problem and the objectives. This section serves as the vision statement for the requirements. Each requirement should bring the project closer to the vision.>

< This section describes if these Business Requirements are as a result of any previous meetings, correspondence, legislation etc.>

5.2 Purpose of Business RequirementsThis section describes the purpose of the Business Requirements.

Business requirements for major enhancements to an existing application.

Business requirements for new application development.

Business requirements for replacement application development.

Business requirements for a request for proposals (RFP).

5.3 Business Goals/Objectives to be achievedThis section describes the major goals/objectives to be achieved with the implementation of the Business Requirements.

5.4 Benefits/RationaleThis section describes the major benefits to be achieved with the implementation of the Business Requirements.

5.5 Project Dependencies<List any related known projects that relate in whole or in part, or has a dependency on this project.>

5.6 StakeholdersThe following comprises the internal and external stakeholders whose requirements are represented by this document:

# Stakeholders

Page 5 of 19


6. Key Assumptions and Constraints6.1 Key Assumptions

# AssumptionsA001 List any assumptions the requirements are based onA002A003

6.2 Constraints# ConstraintsC001 List any constraints the requirements are based onC002C003

6.3 References<This section lists the references to previous documentation, correspondence etc , if any, that are related to these Business Requirements.>

7. Scope Requirements< The primary purpose of the Use Case is to capture the required system behavior from the perspective of the end-user in achieving one or more desired goals. A Use Case contains a description of the flow of events describing the interaction between actors and the system. The use case may also be represented visually in UML in order to show relationships with other the use cases and actors>.

7.1 Actor ProfilesActor Name Actor Type Access Type needed Comments

Stakeholder Primary Actor Supporting

Actor

Create Print Read

Export Update

Others Delete


Actor

Create Print Read

Export Update

Others

Page 6 of 19


Delete


Actor

Create Print Read

Export Update

Others Delete

7.2 Use Cases<Each Use Case should be documented using this template. Refer to the Appendix for Use Case Narrative instructions>

Use Case ID:Use Case Name:Created By: Last Updated By:Date Created: Date Last Updated:Actors:Description:Pre-conditions:Post-conditions:Normal Course:Alternative Courses:Exceptions:Includes:Priority:Frequency of Use:Business RulesSpecial Requirements:Assumptions:Notes and Issues:Use Case Graphic

Example of a completed use case:

Use Case ID: 1Use Case Name: View Interactive Campus MapCreated By: Dan Sward Last Updated By:Date Created: 4/19/09 Date Last Updated:

Actors: UserDescription: This use case describes the main way this interactive campus map will

be used – as a web browser accessed application. The user accesses the appropriate URL and interacts with the functionality made available.

Page 7 of 19


Preconditions: Web browser opened, and interactive campus map URL accessed.Postconditions: User navigates from interactive campus map web site.Normal Course: 1. Open browser

2. Navigate to campus map URL3. Interact with the campus map using available functionality

Alternative Courses: NoneExceptions: NoneIncludes:Priority: HighFrequency of Use: Once per visit.Business Rules TBD…Special Requirements: 24/7 access

Response times comparable to common web mapping solutions (e.g. Google Maps)

U of M accessibility requirements U of M eCommunications requirements

Assumptions:Notes and Issues:Use Case Graphic

7.3 In Scope<Scope List>

7.4 Out of Scope<List of activities out of scope>

Page 8 of 19


8. Business Requirements8.1 Business Domain<What is the client’s business domain all about? Who is his/ her target audience? What are the expectations of this target audience vis-à-vis the client’s business? What are the performance metrics of the website to be built?>

8.2 Functional RequirementsThe following sections document the various business requirements of this project.

Requ

irem

ent T

ype

ID –

Pre

fix ?

?ID

– N

umbe

r

Function – Feature - Requirement

Use

Cas

e Re

fere

nce

Requ

ired

Desir

able

?? ??

Comments

Business User Requirements

F0001

F0002

F0003

F0004

F0005

F0007

Page 9 of 19


F0007

F0008

Reporting Requirements

F0001

F0002

F0003

F0004

F0005

F0006

F0007

F0008

User Access/Security Requirements

F0001

F0002

F0003

Page 10 of 19


F0004

F0005

F0007

F0007

F0008

Service Level/Performance Requirements

F0001

F0002

F0003

F0004

F0005

F0007

F0007

F0008

Scalability Requirements

Page 11 of 19


F0001

F0002

F0003

F0004

F0005

F0007

F0007

F0008

Support and Maintenance Requirements

F0001

F0002

F0003

F0004

F0005

F0007

Page 12 of 19


F0007

F0008

9. Non-functional requirementsThis section describes the non-functional requirements part of the Business Requirements.

<A non-functional requirement is typically a special requirement that is not easily or naturally specified in the text of the use case’s or function’s event flow. Examples of non-functional requirements include legal and regulatory requirements, application standards, and quality attributes of the system to be built including usability, reliability, performance or supportability requirements. These requirements define the overall qualities or attributes of the resulting Website. They place restrictions on the Website being developed, the development process, and specify external constraints that the site must meet. Examples are and not limited to safety, usability, reliability and performance requirements. Others can include supportability and being business critical.>

9.1 Security RequirementsThis section describes the Security requirements part of the Business Requirements.

9.1.1 Authentication<This section describes the Authentication requirements part of the Business Requirements. Authentication is the process of verifying the genuineness of claims that a person/group makes to establish identity/eligibility for access to services. In order to ascertain the Authentication requirements of the Application, it is required to analyse the type of transactions that different Use cases/Business Functions trigger within the Application.>

9.1.2 Authorization and Access Controls <Authorization is the process of determining if the person/group, once identified through the “Authentication process”, is permitted to have access to certain services.>

<See Actors in Scope section if you used Use Cases otherwise define the authorised access here.>

9.2 Standards<Adhering to any standards?>

Page 13 of 19


9.3 Usability<Usability is the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of system or component. Usability requirements include but not limited to: Informative error messages, Well-formed graphical user interfaces with consistency in mind. Usability metrics can be used to analyse user-interface design requirements, including user needs and design principles>

9.4 Availability Requirements<When should the website functions be available and to who when?>

Use Case / Business Function Name

Availability Requirements- Regular work hours- 24x7- Any other (please describe)

9.5 Performance Requirements This section describes system performance expectation levels (response times).

9.6 Scalability Requirements<This section describes how the system is expected to scale to new higher or lower levels. Both user and application scalability requirements are described here. >

10. Data RequirementsThis section describes the Data requirements part of the Business Requirements.

10.1 Data ArchitectureThis section describes the Data Architectural requirements part of the Business Requirements.

<Insert High level ERD>

11. Interface RequirementsThis section describes User Interface requirements for the proposed system.

Page 14 of 19


12. Appendixes12.1 Appendix A – Business Process Flows<Describe the current existing process workflow using flow diagrams (i.e. Visio Flowcharts) and/or a detailed narrative.>

12.2 Appendix B – Business Rules Catalog<Instructions: Use the following template for each business rule. >

Business Rule Name: <The name should give you a good idea about the topic of the business rule.>

Identifier <Defines unique identifier.> EXAMPLE: BR1Description <Defines the rule in detail.> EXAMPLE: “All employee labor is tracked,

reported and billed in 15 minute increments.”Example <(Optional) An example of the rule>Source <Source of the rule. E.g. stakeholder>Related Rules <List of related rules, to support traceability>

12.3 Appendix C- Models<Insert models here>

Page 15 of 19


12.4 Use Case Narrative Instructions<Instructions for completing the Use Case Narrative are included here. Remove these instructions from the completed Business Requirements Document>.

Use Case Field Name DefinitionUse Case ID Give each use case a unique numeric identifier, in hierarchical form: X.Y.

Related use cases can be grouped in the hierarchy. Functional requirements can be traced back to a labeled Use Case.

Use Case Name State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to accomplish using the system. Include an action verb and a noun. Some examples:

View part number information. Manually mark hypertext source and establish link to target. Place an order for a CD with the updated software version

Created By Include the name of the person who initially documented this Use Case.Date Created Enter the date on which the use case was initially documentedDate Last Updated Enter the date on which the use case was most recently updatedLast Updated By Include the name of the person who performed the most recent update to

the use case description.Actor Enter the person or other entity external to the software system being

specified who interacts with the system and performs use cases to accomplish tasks. Different actors often correspond to different user classes, or roles, identified from the customer community that will use the product. Name the actor(s) that will be performing this Use Case.

Description Provide a brief description of the reason for and outcome of this use case, or a high-level description of the sequence of actions and the outcome of executing the Use Case.

Preconditions List any activities that must take place, or any conditions that must be true, before the Use Case can be started. Number each precondition. Examples:

User’s identity has been authenticated. User’s computer has sufficient free memory available to launch

taskPost conditions Describe the state of the system at the conclusion of the use case

execution. Number each post condition. Examples: Document contains only valid SGML tags. Price of item in database has been updated with new value

Normal Course Provide a detailed description of the user actions and system responses that will take place during execution of the use case under normal, expected conditions. This dialog sequence will ultimately lead to accomplishing the goal stated in the use case name and description. This description may be written as an answer to the hypothetical question, “How do I <accomplish the task stated in the use case name>?” This is best done as a numbered list of actions performed by the actor, alternating with responses provided by the system.

Alternative Courses Document other, legitimate usage scenarios that can take place within this use case separately in this section. State the alternative course, and

Page 16 of 19


describe any differences in the sequence of steps that take place. Number each alternative course using the Use Case ID as a prefix, followed by “AC” to indicate “Alternative Course”. Example: X.Y.AC.1

Exceptions Describe any anticipated error conditions that could occur during execution of the use case, and define how the system is to respond to those conditions. Also, describe how the system is to respond if the use case execution fails for some unanticipated reason. Number each exception using the Use Case ID as a prefix, followed by “EX” to indicate “Exception”. Example: X.Y.EX.1

Includes List any other use cases that are included (“called”) by this use case. Common functionality that appears in multiple use cases can be split out into a separate use case that is included by the ones that need that common functionality.

Priority Indicate the relative priority of implementing the functionality required to allow this use case to be executed. The priority scheme used must be the same as that used in the software requirements specification.

Frequency of Use Estimate the number of times this Use Case will be performed by the actors per some appropriate unit of time.

Business Rules List any business rules that influence this Use Case.

Special Requirements Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to be addressed during design or implementation. These may include performance requirements or other quality attributes.

Assumptions List any assumptions that were made in the analysis that led to accepting this use case into the product description and writing the use case description.

Notes and Issues List any additional comments about this use case or any remaining open issues or TBDs (To Be Determined) that must be resolved. Identify who will resolve each issue, the due date, and what the resolution ultimately is.

Page 17 of 19


13. ApprovalThis document has been approved as the official Business Requirements Document for the Project Management project.Following approval of this document, changes will be governed by the project’s change management process, including impact analysis, appropriate reviews and approvals, under the general control of the Master Project Plan and according to Project Support Office policy.

Prepared by Signature Date

Author's Name

[Title][Organization]

Approved by Signature Date

[Client Acceptor’s Name][Title][Organization]

Page 18 of 19

business requirements document (brd) web viewthe use case may also be represented visually in uml in...

Documents