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
  10% (7)
• B
  6% (4)
• C
  84% (57)

Explanation

Option C is correct because determining priority relative to other modifications is a planning or change management concern, not part of specifying information requirements. Prioritization happens in a separate process after requirements are defined, where competing demands are weighed and scheduled.

Option A is wrong because functional requirements for IT are a core output of specifying information requirements - this process exists precisely to translate business needs into what the IT system must do.

Option B is wrong because assessing the impact on the user organization is an essential part of requirements specification, helping stakeholders understand what changes will mean in practice for the people who use the systems.

Memory tip: Think of "Specify" as answering "What do we need and what will it affect?" - requirements (A) and impact (B) both answer that question. Priority answers "When do we do it compared to everything else?" - that's a scheduling/governance question that happens after specification is complete.

No community discussion yet for this question.