Understanding solution design
In the previous chapter, we successfully documented the business requirements in our business requirements document (BRD) in business-understandable and system-agnostic terminology. Solution design enables us to dissect high-level business requirements. In this section, we are going to refine them and deconstruct them into more granular details in the form of functional and non-functional requirements. These detailed requirements are documented in the solution design document, which is also called a functional design document (FDD) or a functional specification document (FSD).
The following steps define the hierarchy of the flow of requirements:
- We start with a prioritized list of business (stakeholder) requirements.
- We further slice the requirements and add a little bit more clarity and details, and capture the requirements in a BRD. The approved BRD will contain our baseline requirements that have been approved and agreed upon by the stakeholders...
