Summary

In this chapter, we reviewed various elements and components that are important for writing a good BRD. A BRD is a living document, and you learned how to complete the document with stakeholders and project team members iteratively to a point where it is clear and understood by all players. When you reach this stage, you take a baseline and version it. This version shall be your requirement scope for the release. Any changes requested from this point onward need to be compared to the baseline and need approval from the change control board before the BRD can be updated and versioned again. These new updated BRD versions shall go through the same process.

You have now gained insight and tips into what is needed for you to create a BRD that accurately describes the requirements that your stakeholder and project team members can understand.

In the next chapter, we will cover solution design aspects of system requirements. We will cover aspects where a designed solution is...