Entry Certificate in Business Analysis Requirements Documentation and Traceability 2 — Questions and Answers
Question 1: What is the purpose of a glossary in requirements documentation?
- To define domain-specific terms and ensure shared understanding (Correct answer)
- To list all project risks
- To track requirement approval status
- To document test results
Correct answer: To define domain-specific terms and ensure shared understanding
A glossary reduces ambiguity by providing agreed-upon definitions for terms used throughout requirements documents.
Question 2: A solution requirement differs from a stakeholder requirement because it:
- Specifies characteristics the solution must have to meet stakeholder needs (Correct answer)
- Describes high-level business goals
- Lists project constraints and assumptions
- Defines acceptance test criteria
Correct answer: Specifies characteristics the solution must have to meet stakeholder needs
Solution requirements translate stakeholder needs into specific capabilities, behaviors, or qualities the solution must possess.
Question 3: Which of the following is an example of a non-functional requirement?
- The system shall respond to search queries within 2 seconds (Correct answer)
- Users can add items to a shopping cart
- The system shall generate monthly sales reports
- Managers can approve purchase orders online
Correct answer: The system shall respond to search queries within 2 seconds
Non-functional requirements define quality attributes such as performance, security, and scalability rather than specific system behaviors.
Question 4: Requirements are considered 'traced' when:
- Each requirement is linked to related requirements, tests, and design components (Correct answer)
- All requirements have been approved by stakeholders
- Requirements are stored in a version control system
- The project manager has reviewed the requirements document
Correct answer: Each requirement is linked to related requirements, tests, and design components
Tracing establishes bidirectional relationships between requirements and other project artifacts, enabling impact analysis and completeness checks.
Question 5: Which document captures the conditions and capabilities that a solution must meet or possess to satisfy a contract, standard, or business need?
- Requirements specification (Correct answer)
- Project charter
- Change control log
- Stakeholder register
Correct answer: Requirements specification
A requirements specification formally documents agreed-upon requirements in sufficient detail to guide solution design and testing.
Question 6: Requirement 'completeness' means that:
- The requirement contains all necessary information for implementation and testing without needing further clarification (Correct answer)
- All stakeholders have signed off on requirements
- The solution has been fully built
- Every use case has been identified
Correct answer: The requirement contains all necessary information for implementation and testing without needing further clarification
A complete requirement is self-contained and provides sufficient detail so that implementers and testers can proceed without ambiguity.
What is the purpose of a glossary in requirements documentation?