| The Requirements Document provides a solid foundation for the end product, and provides the first view of what the intended product must do and clear descriptions of how the automated system should perform. The Requirements Document also provides a basis for design, and serves as a foundation for testing and user acceptance of the end product. Included in the Requirements Document are business requirements, which are statements of the functions or program needs that must be met in order to accomplish the business objectives of the IT project. Also included are functional and nonfunctional requirements, which are lower-level requirements that further define the expectations for the end product. Functional requirements are actions or expectations of what the automated system will take or do, and are measured by concrete means like data values, decision-making logic and algorithms. Nonfunctional requirements are behavioral properties that the automated system must have. The Requirements Document also provides traceability information that identifies dependencies between requirements, or between the requirements and the requirement sources and other documentation.The Requirements Document contains the business and technical capabilities and constraints of the IT project or automated system to be developed. The primary purpose of the Requirements Document is to clearly communicate the goals, needs, and objectives of the user(s) and/or organization (i.e., customer requirements) to the technical community who will specify and build the end product (e.g., automated system). |
|
BRD ELEMENTS
- PROCESS INFORMATION
- SIPOC DIAGRAM
- SIPOC METRICS
- PROCESS DIAGRAM
- “INPUTS” DETAIL
- “OUTPUTS” DETAIL
- IMPROVEMENT OPPORTUNITIES
- FUNCTIONAL REQUIREMENTS
- NOTES/COMMENTS
- FLOOR PLAN
- ACTIONS/ISSUES
|
