Requirements Documentation

Abstract

The purpose of the Requirements Documentation is to establish an agreement about what the project is to accomplish. It provides a baseline for validation and verification, and it should reduce the development effort by avoiding omissions, misunderstandings, and inconsistencies early in the design lifecycle. All items in the Requirements Documentation should be consistent with other documentation (e.g., project description, design diagrams, task lists, timelines) but it should be readable as a stand-alone document.