Business Requirement Qualities

Easy reading is damn hard writing!

A good Business Requirement Document must include quality requirements such as:

  • Attainable – To be attainable, the requirement must be technically feasible. If uncertain about whether a requirement is technically feasible, then it is essential to conduct an analysis to determine its feasibility. Even if a requirement is technically feasible, it may not be attainable due to budget, schedule, or other constraints. There is no point in documenting a requirement for something you cannot attain – stakeholders and developers alike must be reasonable.
  • Clear – Each requirement should express a single thought, be concise, and simple. It is important that the requirement not be misunderstood.
  • Consistent – Requirements should not use conflicting terminology when referring to the same system element or call for different forms of logical or data structure. For example: One requirement may state that all lights shall be red; while another states that all lights shall be yellow.
  • Necessary – If there is any doubt about the necessity of a requirement, then ask: What is the worst thing that could happen if this requirement were not included? If you do not find an answer of any consequence, then you probably do not require the requirement. Analytically prioritizing the requirements helps avoid this trap.
  • Testable – All requirements in the document should be well defined so that they can be easily tested and validated. Each requirement can have its own verification and validation criteria. This provides a high level quality cross-reference for each requirement and its corresponding Design that spreads across the entire project’s development process. Begin writing test cases early in requirements development. Writing conceptual test cases against the requirements clarifies the vision of how the solution should behave under certain conditions. This practice helps reveal ambiguities and missing information. It will also lead to a BRD that supports comprehensive test case generation.
  • Traceable – Traceability in this context means tracing each requirement.
  • Requirement-to-Testing traceability provides a means to-
    • Clarify what must be designed and tested
    • Force thought on how development and testing will be done
    • Crystallize the requirement and ensures that they are testable
    • Ultimately ensures that each requirement has been accounted for, designed and tested.
  • The benefit of traceability is that you will be able to answer the following questions-
    • What is the impact of changing a requirement?
    • Are all requirements and designs accounted for?
    • Is this requirement necessary?
    • What acceptance tests will be used to verify the requirements?
  • Verifiable –  When capturing requirements, it will become necessary to verify the delivery and quality of the Design. To be verifiable, the requirement must state something that can be verified by examination, analysis, test, or demonstration.
Last modified on Tuesday, 21 March 2017 03:09
Share this article

267 comments

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.

Contact info

About us

Newsletter

Join the network: We are Business Folks, analyzing IT projects.
Top
We use cookies to improve our website. By continuing to use this website, you are giving consent to cookies being used. More details…