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
  3% (1)
• B
  5% (2)
• C
  92% (34)

Explanation

Validating and approving specifications (C) is correct because "Specify information requirements" is fundamentally about defining, refining, and confirming what information a system or process needs - and validation/approval is the quality gate that closes that specification loop, ensuring stakeholders agree the requirements are complete and accurate.

Why the distractors are wrong:

• A (decision-making about executing changes) belongs to a change management process, not requirements specification. Deciding whether to execute a change happens after requirements are already established.
• B (identifying IT-solutions) is part of solution design or architecture activities. Specification of information requirements intentionally avoids prescribing solutions - it captures what is needed, not how to build it.

Memory tip: Think of "Specify" as a three-step loop - draft → validate → approve. Option C maps directly onto the last two steps. If an answer sounds like managing change (A) or picking technology (B), it's from a different process entirely.

No community discussion yet for this question.