Requirements Verification Quiz

Which of the following best describes the relationship between verification and validation?

• A) Verification is about ensuring correctness, while validation is about ensuring usefulness.

• B) Verification occurs after validation.

• C) Verification and validation are the same processes.

• D) Validation is only about technical correctness.

What can be a consequence of poorly defined requirements?

• A) Increased stakeholder satisfaction

• B) Clearer project scope

• C) Miscommunication and project delays

• D) Higher quality deliverables

Which of the following is NOT a component of a high-quality requirement?

• A) Clarity and ease of understanding

• B) Alignment with stakeholder needs

• C) Complexity and technical jargon

• D) Proper representation of reality

What does it mean for a requirement to be "atomic"?

• A) It is part of a larger requirement.

• B) It can stand alone and be understood independently.

• C) It is broken down into multiple sub-requirements.

• D) It is vague and open to interpretation.

Which characteristic ensures that requirements are aligned with stakeholder needs?

• A) Consistent

• B) Concise

• C) Atomic

• D) Testable

What does it mean for a requirement to be "complete"?

• A) It contains all possible information.

• B) It is detailed enough for further work to continue.

• C) It is free from errors.

• D) It is simple and easy to understand.

Which of the following best defines a "concise" requirement?

• A) Contains all relevant details, even if extraneous.

• B) Clear and to the point, without unnecessary content.

• C) Uses complex language to convey meaning.

• D) Includes multiple perspectives on the requirement.

What does it mean for a requirement to be "feasible"?

• A) It is perfect and requires no modifications.

• B) It can be realistically implemented within given constraints.

• C) It is the most complex requirement.

• D) It is the most expensive option available.

Why is it important for a requirement to be "unambiguous"?

• A) To allow for multiple interpretations of the requirement.

• B) To ensure clarity on whether the requirement has been met.

• C) To reduce the time spent on project documentation.

• D) To allow stakeholders to modify the requirement easily.

What does "testable" refer to in the context of requirements?

• A) The requirement can be quantitatively analyzed.

• B) The requirement can be verified to confirm fulfillment.

• C) The requirement is easy to implement.

• D) The requirement can be negotiated with stakeholders.