Chapter 10
Functional requirement is something that the product must do in order to operate the product.
Level of Detail or Granularity
The ease to understand the requirement also depends upon how is it written. If the requirement is written in single line with a single verb then it becomes easy to test it and it reduces the chance of misunderstanding it. Moreover, it increases consistency for stakeholders to define what the product is supposed to do.
For example: Bell MTS Fibe TV is maintaining the signal stability.
Description and Rationale
Description is something that tells what the product is doing. But, it is strongly suggested to add a rationale to prove why the requirement exist or why the product is performing a certain action.For example:
Description: Bell MTS Fibe TV is maintaining the signal stability.
Rationale: To increase the customer satisfaction.
Functional Business Requirements -
ReplyDeleteFunctional requirements specify what the product must do t satisfy the needs of work, business and stakeholders. They do not rely on any sort of technology used by the product. It is very important for a business analyst to find these functional requirements because they provide a clear vision to them about the functionality of the product. Requirements should be written as a single active sentence with one verb and they must be measure able.
Grouping Requirements -
Functional requirements should be grouped on the basis of use case or features and by doing so it is easy to discover the related group of requirements and test their functionalities. We group the requirements for three reasons mention below:
1. to be able to involve stakeholders with different depths, breadths and focuses of interest
2. to help you discover the atomic requirements in the first place
3. to be able to deal with volume and complexity