Requirements Document

Jump to navigation Jump to search

A Requirements Document is a specification document that describes the system requirements of a designed system.



    • Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform. ... The purpose of requirements management is to assure the organization documents, verifies and meets the needs and expectations of its customers and internal or external stakeholders. Requirements management begins with the analysis and elicitation of the objectives and constraints of the organization. Requirements management further includes supporting planning for requirements, integrating requirements and the organization for working with them (attributes for requirements), as well as relationships with other information delivering against requirements, and changes for these.




  • (Kaiya & Saeki, 2006) ⇒ Haruhiko Kaiya, and Motoshi Saeki. (2006). “Using Domain Ontology as Domain Knowledge for Requirements Elicitation.” In: Proceedings of the 14th IEEE International Requirements Engineering Conference (RE 2006). doi:10.1109/RE.2006.72





  • (Bell & Thayer, 1976) ⇒ T. E. Bell and T. A. Thayer. 1976. "Software requirements: Are they really a problem?.” In: Proceedings of the 2nd International Conference on Software engineering (ICSE 1976).
    • QUOTE: ... The Military Standard set MIL- STD 490/483 recognized this newer approach by specifying a system requirements document, a "design-to" requirements document that is created in response to the system requirements, and then a "code-to" requirements document for each ...