One of the best business requirements document examples
November 24, 2019

One of the best business requirements document examples

By Lau

“Write what should not be forgotten.”

— Isabel Allende
Write what should not be forgotten. — Isabel Allende Click To Tweet

It doesn’t matter how much experience you have writing business requirements documents, every company will expect something different from you. In this post, I will share with you one of the best business requirement examples to use in agile environments.

Sometimes the business analyst could reuse the business requirements templates they got in their last company, but most of the time they will need to create new ones according to the new company’s needs.

The following is one of the most used agile business requirements document examples. Due to the new agile paradigm changes, the current requirements documents have become short, concise and they don’t contain many details.


Example:

Version Control

The version control section is where you’re going to keep a record of the changes you make in the business requirements document.
Version DateChangesAuthor
117-11-2019First versionLaura Ojeda

Common vocabulary and acronyms

The common vocabulary and acronyms section refers to the list of terms that you want to make sure everyone will understand.
TermDefinition
CRUDCreate, Read, Update and Delete

Current Issue

Under “Current Issue” is where you will give to the reader a reminder of what you want to be solved.

The Room Booking system does not have the module to create, read, update and delete customers.

User Story

I will make a separate post to explain how to write a user story. For now, think that here is where you describe who has the necessity, what they are asking for and why.

As an operator, I want to be able to create, read, update and delete customers in order to keep a record of customers that make reservations.

Specification

Here is where you will need to be a little bit more specific. In this section, you will repeat the user requirement but this time from the point of view of the functionality rather than from the perspective of the necessity you will be covering as you did when you wrote the user story.
This section must have the functionality’s description and the fields that hey will include and if it was necessary, you will also add here the screen.

It is required to create a new CRUD module where the customer’s data can be organised. This module must have the following fields:

  • Id (Numerical Field)
  • Name (Text Field)
  • Last Name (Text Field)
  • Date of Birth (Date Field)
  • Creation Date (Automatic Field)

*It is recommended to add the screen design  to make the requierment documentation even clearer.

Buttons:

  • Search
  • Add new
  • Edit
  • Delete

Filters:

  • Name (Text Field)
  • Last Name (Text Field)
  • Date of Birth (Calendar Field)
  • Creation Date (Date Field)

Grid results:

  • Id:  id auto generated at the moment of creation of the new customer.
  • Name: customer’s name.
  • Last Name: customer’s last name.
  • Date of Birth: customer’s date of birth.
  • Creation Date: date when the customer was created.

Acceptance Criteria

This is the last section of the document but no less important than the others. Here you will establish the acceptance criteria which are all the validations you want to be included in order for them to be accepted as completed.

Scenarios:

  1. Fields “Date”. Given that I’m filtering the search and modifying the date of birth’s field, the system will:
    • Show a calendar of the current month and 18 years previous to the current month which is set as a default.
    • Allow me to replace the given date for an older one.

This document is an example of what you could do. There are many different ways of documenting software solutions, some more structured than others. But what they all must have in common is that their readers have to be able to clearly understand them.

You might also like to read about all the knowledge that a BA must-have.

And don’t forget to download the FREE Digital Book: The Master Strategy for BA Beginners where you will learn how to get your first BA job by following 3 strategic steps.

See you soon. 😉