Authentic IIBA Certification Exam ECBA Questions Answers

While assessing requirements changes, a business analyst (BA) determines the formality of the assessment process based on the governance approach. The governance approach provides the framework within which changes are evaluated and decisions are made regarding the approval or rejection of changes. This approach outlines the processes, roles, responsibilities, and standards that guide how changes are managed, ensuring that changes align with organizational policies and strategic objectives .

During the requirements life cycle management phase, one of the key activities is to trace requirements. This involves ensuring that requirements and designs at different levels are aligned with one another and managing the effects of changes to one level on related requirements and designs. Tracing requirements helps maintain the integrity of the requirements throughout the project’s life cycle, from inception to retirement.

References: The information provided aligns with the tasks described in the BABOK® Guide’s Requirements Life Cycle Management knowledge area, which outlines the importance of tracing requirements to manage and maintain them effectively throughout the project12.

Among the activities performed during the requirements life cycle management phase, tracing requirements stands out as a critical task. It involves tracking and documenting the lineage of each requirement, including its derivation, allocation to solution components, and relationships with other requirements. This process ensures a clear understanding of how requirements influence and are influenced by each other, as well as their relationship to the business objectives and solution components. Effective requirement tracing aids in impact analysis, risk management, and ensuring that changes to requirements are consistently reflected across the project, thus maintaining the integrity and coherence of the solution over time.

References: BABOK Guide v3, Chapter 5.1: Trace Requirements

Derive: relationship between two requirements, used when a requirement is derived from another requirement. This type of relationship is appropriate to link the requirements on different levels of abstraction. For example, a solution requirement derived from a business or a stakeholder requirement.