在Business Analysis中的标准Requirements Types

1. [b]Business Requirements[/b]
较高层面上对企业的目标和需要做的陈述。
Business Requirements are higher-level statements of the goals, objectives, or needs
of the enterprise. They describe such things the reasons why a project is initiated, the
things that the project will achieve, and the metrics which will be used to measure its
success. They are detailed further in the Enterprise Analysis KA.
2.[b]User Requirements[/b] 用户要求
User Requirements are statements of the needs of a particular stakeholder or class of
stakeholders. They describe the needs that a given stakeholder has and how that
stakeholder will interact with a solution. User Requirements serve as a bridge
between Business Requirements and the various classes of solution requirements. They are gathered from stakeholders as described in the Requirements Elicitation KA
and documented using the techniques described in the Requirements Analysis and
Documentation KA.
3.[b]Functional Requirements[/b] describe the behavior and information that the solution
will manage. They describe capabilities the system will be able to perform in terms of
behaviors or operations – a specific system action or response. They are further
described in the Requirements Analysis and Documentation KA.
4. [b]Quality of Service Requirements [/b]capture conditions that do not directly relate to the
behavior or functionality of the solution, but rather describe environmental
conditions under which the solution must remain effective or qualities that the
systems must have. They are also known as [b]non-functional or supplementary requirements.[/b] They are further described in the Requirements Analysis and
Documentation KA.
5. [b]Assumptions and constraints[/b] identify aspects of the problem domain that are not
functional requirements of a solution, and will limit or impact the design of the
solution. They are further described in the Requirements Analysis and Documentation
KA.
6.[b]Implementation requirements[/b] describe capabilities that the solution must have in
order to facilitate transition from the current state of the enterprise to the desired
future state, but that will not be needed once that transition is complete. They are
further described in the Solution Assessment and Validation KA.