What is an activity of the process Specify information requirements?

Question

Options

• Adecision-making about the execution of changes
• Bidentifying IT-solutions
• Cvalidating and approving specifications

• A
  14% (2)
• B
  7% (1)
• C
  79% (11)

Explanation

Validating and approving specifications (C) is correct because the core purpose of the "Specify information requirements" process is to define, document, and confirm what information the business needs - culminating in validated, approved specs that can guide development or procurement.

Option A (decision-making about executing changes) belongs to a change management process, not requirements specification - it concerns whether and how to implement a change, not what the requirements are.

Option B (identifying IT solutions) belongs to a design or architecture process; specifying requirements deliberately avoids prescribing solutions so that needs are captured independently of technology.

Memory tip: Think of "Specify" as the what, not the how or whether. Validating and approving specs is the natural endpoint of defining requirements - you write them, then you sign them off. Anything about choosing technology (B) or greenlighting changes (A) happens after requirements are locked.

No community discussion yet for this question.