Organizing Requirements
How to package and present the requirements?
|
The main purpose of the Organize Requirements activity is to organize the requirements and to produce a User Requirements document. Reference Number Every Business Requirement would have now been classified into various categories. To better organize requirements we must now assign a reference number that the requirement will be assigned for the life of the project. (e.g. FR-0010, NR-0025). Requirement reference numbers will assist in aligning future development artifacts (functional designs, modules, test scripts, etc.) to the original requirements. This will ensure traceability back to the original requirement. There are many software tools available which will support the organization of Business Requirements. These tools will even assign the reference numbers automatically. clearlyPUT’s Requirementing includes an Organizing Requirements activity. Business requirements Document There have been many names used to describe the Requirements document.
Some of these names can be misleading and contradictory depending on who you talk to. I like to keep things simple so I will use the term “Business Requirements Document” The main purpose of this document is to facilitate the presentation and signoff of the Business Requirements that have been captured and agreed upon. The Business Requirements Document also describes the overall Business objectives and goals. Here is a sample format that could be used.
Summary
The organize requirements activity is concerned with organizing the business requirements by assigning them unique reference numbers. These reference numbers will be used for traceability. The Business Requirements Document will be created to communicate the requirements and to facilitate signoff.
|