Many organizations categorize requirements into which of the following two categories?
A. Project and Product
B. Staffing and Budget
C. Stakeholder and Customer
D. Business and Technical
One Comment on “Many organizations categorize requirements into which of the following two categories?”
Ahmet Can Aykutsays:
Answer is wrong.Please refer to Section 5.2 of PMBOK v5
Requirements can
be grouped into classifications allowing for further refinement and detail as the requirements are elaborated. These
classifications include:
• Business requirements, which describe the higher-level needs of the organization as a whole, such as the
business issues or opportunities, and reasons why a project has been undertaken.
• Stakeholder requirements, which describe needs of a stakeholder or stakeholder group.
• Solution requirements, which describe features, functions, and characteristics of the product, service,
or result that will meet the business and stakeholder requirements. Solution requirements are further
grouped into functional and nonfunctional requirements:
○ Functional requirements describe the behaviors of the product. Examples include processes,
data, and interactions with the product.
○ Nonfunctional requirements supplement functional requirements and describe the environmental
conditions or qualities required for the product to be effective. Examples include: reliability,
security, performance, safety, level of service, supportability, retention/purge, etc.
• Transition requirements describe temporary capabilities, such as data conversion and training
requirements, needed to transition from the current “as-is” state to the future “to-be” state.
• Project requirements, which describe the actions, processes, or other conditions the project needs
to meet.
• Quality requirements, which capture any condition or criteria needed to validate the successful completion
of a project deliverable or fulfillment of other project requirements.
Answer is wrong.Please refer to Section 5.2 of PMBOK v5
Requirements can
be grouped into classifications allowing for further refinement and detail as the requirements are elaborated. These
classifications include:
• Business requirements, which describe the higher-level needs of the organization as a whole, such as the
business issues or opportunities, and reasons why a project has been undertaken.
• Stakeholder requirements, which describe needs of a stakeholder or stakeholder group.
• Solution requirements, which describe features, functions, and characteristics of the product, service,
or result that will meet the business and stakeholder requirements. Solution requirements are further
grouped into functional and nonfunctional requirements:
○ Functional requirements describe the behaviors of the product. Examples include processes,
data, and interactions with the product.
○ Nonfunctional requirements supplement functional requirements and describe the environmental
conditions or qualities required for the product to be effective. Examples include: reliability,
security, performance, safety, level of service, supportability, retention/purge, etc.
• Transition requirements describe temporary capabilities, such as data conversion and training
requirements, needed to transition from the current “as-is” state to the future “to-be” state.
• Project requirements, which describe the actions, processes, or other conditions the project needs
to meet.
• Quality requirements, which capture any condition or criteria needed to validate the successful completion
of a project deliverable or fulfillment of other project requirements.
0
0