無詞性

需求文件

Requirements documentation describes how individual requirements meet the business need for the project. Requirements may start out at a high level and become progressively more detailed as more is known. Before being baselined, requirements must be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may ·range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing executive summary, detailed descriptions, and attachments.

Components of requirements documentation can include, but, are not limited to:
• Business need or opportunity to be seized, describing the limitations of the current situation and why the project has been undertaken;
• Business and project objectives for traceability;
• F unctional requirements, describing business processes, information, and interaction with the product, as appropriate which can be documented textually in a requirements list, in models,or both;
• N on-functional requirements, such as level of service, performance, safety, security, compliance, supportability, retention/purge, etc.;
• Quality requirements;
• Acceptance criteria;
• Business rules stating the guiding principles of the organization;
• Impacts to other organizational areas, such as the call center, sales force, technology groups;
• Impacts to other entities inside or outside the performing organization;
• Support and training requirements; and
• Requirements assumptions and constraints.

詞條貢獻者： wyr  
 貢獻者按積分從高到低進行排序