If a requirement changes so that only the bank identification code must be entered, what part of your documentation must be updated?

If a requirement changes so that only the bank identification code must be entered, what part of your documentation must be updated?

• A. Chapter describing system states
• B. Goals in the specification
• C. Context diagram
• D. Class model

Answer: (B)

Updating the goals in the specification is essential when a requirement changes, such as modifying which specific data must be entered. The goals reflect the fundamental objectives the project aims to achieve. In this case, since only the bank identification code is now required, this adjustment signifies a shift in the desired functionality of the system. The goals should articulate what the system is meant to accomplish, and if these goals are no longer aligned with the current requirements, they need to be revised accordingly. This ensures that all stakeholders have a clear understanding of the system's objectives based on the latest requirements. Updating other parts of the documentation like the chapter describing system states, context diagram, or class model may also be necessary, but these elements typically elaborate on how the system functions or its structure, rather than directly stating the objectives of the requirements themselves.

Updating the goals in the specification is essential when a requirement changes, such as modifying which specific data must be entered. The goals reflect the fundamental objectives the project aims to achieve. In this case, since only the bank identification code is now required, this adjustment signifies a shift in the desired functionality of the system.

The goals should articulate what the system is meant to accomplish, and if these goals are no longer aligned with the current requirements, they need to be revised accordingly. This ensures that all stakeholders have a clear understanding of the system's objectives based on the latest requirements.

Updating other parts of the documentation like the chapter describing system states, context diagram, or class model may also be necessary, but these elements typically elaborate on how the system functions or its structure, rather than directly stating the objectives of the requirements themselves.