ECBA · Question #49
The approach that defines how requirements will be re-used is the:
The correct answer is C. information management approach. Option C is correct because the Information Management Approach (from BABOK v3) specifically defines how business analysis information - including requirements artifacts - will be stored, organized, and reused across initiatives. It governs the lifecycle of BA information…
Question
The approach that defines how requirements will be re-used is the:
Options
- Agovernance approach.
- Bapproach to identifying business analysis improvements.
- Cinformation management approach.
- Dbusiness analysis approach.
How the community answered
(21 responses)- A5% (1)
- C95% (20)
Explanation
Option C is correct because the Information Management Approach (from BABOK v3) specifically defines how business analysis information - including requirements artifacts - will be stored, organized, and reused across initiatives. It governs the lifecycle of BA information beyond a single project.
Why the distractors are wrong:
- A (Governance) defines how decisions are made, changes are controlled, and escalations are handled - it's about oversight, not reuse.
- B (Identifying BA improvements) looks retrospectively at lessons learned to improve the BA process itself, not at how requirements artifacts are shared or reused.
- D (Business analysis approach) is the high-level plan for how BA work will be performed on an engagement - scope, methods, and timing - not information lifecycle management.
Memory tip: Think of Information Management like a library system - a library decides how books (requirements) are catalogued, stored, and checked out for reuse. If you're asking "where do our requirements live and how do we reuse them?", that's an information management question.
Topics
Community Discussion
No community discussion yet for this question.