What is not a subject of the process Specify information requirements?

Question

Options

• Athe functional requirements for the IT
• Bthe impact on the user organization
• Cthe priority with respect to other modifications

• A
  7% (2)
• B
  14% (4)
• C
  79% (22)

Explanation

Option C is correct because determining priority relative to other modifications is a separate activity that belongs to a prioritization or change management process - not to "Specify information requirements." That process is focused on what is needed, not when or in what order compared to competing requests.

Why the distractors are wrong:

• A (functional requirements for IT) is wrong because specifying what the IT system must functionally do is a core output of this process - you're defining what the system needs to deliver.
• B (impact on the user organization) is wrong because understanding how a change affects users is essential context when specifying requirements - you can't properly define needs without knowing who is impacted and how.

Memory tip: Think of "Specify information requirements" as answering "What do we need and what does it affect?" - functional specs (A) and organizational impact (B) both answer that question. Priority against other items (C) is a scheduling/governance decision that happens after requirements are defined, in a separate process.

No community discussion yet for this question.