Business Analysis Requirements Elicitation 2 — Questions and Answers
Question 1: What is the main purpose of using prototyping as a requirements elicitation technique?
- To create the final deliverable for stakeholders
- To help stakeholders visualize and react to a proposed solution to clarify requirements (Correct answer)
- To replace the need for written requirements
- To test the performance of the system under load
Correct answer: To help stakeholders visualize and react to a proposed solution to clarify requirements
Prototyping gives stakeholders a tangible model to interact with, making it easier for them to identify what they want and don't want in the final solution.
Question 2: Which elicitation technique is most suitable when stakeholders have difficulty articulating their needs verbally?
- One-on-one interviews
- Surveys
- Prototyping (Correct answer)
- Benchmarking
Correct answer: Prototyping
Prototyping gives stakeholders something concrete to react to, which is especially useful when they struggle to describe abstract requirements in words.
Question 3: What does 'document analysis' as an elicitation technique involve?
- Reviewing existing documentation such as business rules, procedures, and systems to identify requirements (Correct answer)
- Creating new documentation based on stakeholder interviews
- Analyzing project charters to determine scope
- Writing test plans based on use cases
Correct answer: Reviewing existing documentation such as business rules, procedures, and systems to identify requirements
Document analysis involves reviewing existing materials (policies, manuals, reports, workflows) to extract requirements and understand the current state.
Question 4: What is the primary advantage of using brainstorming as an elicitation technique?
- It produces highly structured, validated requirements
- It encourages creative thinking and generates a wide variety of ideas quickly (Correct answer)
- It is best suited for validating existing requirements
- It replaces the need for stakeholder interviews
Correct answer: It encourages creative thinking and generates a wide variety of ideas quickly
Brainstorming encourages free-flowing idea generation without judgment, making it effective for exploring possibilities and uncovering a broad range of potential requirements.
Question 5: What is 'interface analysis' used for in requirements elicitation?
- Analyzing user interface design aesthetics
- Identifying and defining how a system will interact with other systems, users, and external entities (Correct answer)
- Documenting internal system architecture
- Measuring system performance at integration points
Correct answer: Identifying and defining how a system will interact with other systems, users, and external entities
Interface analysis identifies all the touchpoints where a system interacts with external entities — users, other systems, or hardware — and defines the requirements for those interactions.
Question 6: In requirements elicitation, what are 'tacit requirements'?
- Requirements that are explicitly stated by stakeholders in writing
- Unstated assumptions or expectations that stakeholders take for granted (Correct answer)
- Requirements that have been formally approved and baselined
- Requirements derived from regulatory compliance obligations
Correct answer: Unstated assumptions or expectations that stakeholders take for granted
Tacit requirements are implicit needs that stakeholders assume are understood and therefore do not explicitly state, making them easy to miss during elicitation.
Question 7: Which elicitation technique is best used to understand the precise sequence of steps a user follows to accomplish a business goal?
- Mind mapping
- Task/workflow analysis (Correct answer)
- Benchmarking
- Surveys
Correct answer: Task/workflow analysis
Task or workflow analysis breaks down user activities step-by-step to reveal how work is actually done, exposing procedural requirements and potential inefficiencies.
Business Analysis Requirements Elicitation 2
What is the main purpose of using prototyping as a requirements elicitation technique?