Elicitation gathers information; analysis turns that information into shared understanding. The BA moves repeatedly between listening, modeling, questioning, validating, and refining until needs are clear enough to support decisions and delivery.
Discover the real need, resolve ambiguity, and make requirements testable and valuable.
No elicitation technique is universally best. Match the method to the audience, uncertainty, sensitivity, number of participants, and stage of the work.
Analysis is iterative: new evidence often sends the team back to clarify or model again.
A host marketplace asks for an Instant Book button to reduce abandoned booking requests.
Interview hosts and guests to uncover trust and response-time concerns.
Analyze abandonment data and current eligibility rules.
Map normal, ineligible, payment-failure, and cancellation scenarios.
Validate a prototype and testable acceptance criteria with product, engineering, and QA.
The requirement evolves from a button request into a rule-based capability for verified guests, with clear exception handling and measurable adoption targets.
Open each answer, then practice saying it naturally in your own words.
Adapt the technique, create psychological safety, use evidence and examples, ask open and probing questions, and confirm understanding through models rather than relying on meeting notes alone.
Drawing out information, needs, constraints, and knowledge.
Behavior or capability the solution must provide.
A quality expectation such as security, performance, or accessibility.
The ability to follow a requirement from its source through delivery and testing.
Answer all three questions. Score 2 out of 3 to pass this section and update your course progress.
Choose one answer for every question, then submit your quiz.