8/13/2019 Requiremenents Elicitation

1/2

Per BABOK, Business analyst is the only stakeholderfor the task of documenting elicitationresults

Business analyst is the stakeholder involved in the document elicitation activity Identify stakeholders and then select requirements activities appropriate to them Requirements elicitation defines the generally accepted techniques used to collect the

requirements of the solution

Focus group is the requirement elicitation technique that is used for quickly determiningsubjective stakeholder attitudes and perceptions about a possible new system. Focus groups are

a quick way to generate ideas quickly especially about attitudes and beliefs

Business analyst is the one who performs the business analysis activities no matter what theirjob tile is

Technique used for confirmingelicitation resultso Interviews and observation

Technique limited to capturing the As is state o Document analysiso Observation

Skilled facilitator is required for the following requirements elicitation techniqueo Focus groupso Requirements workshops

Purpose of using interface analysis as a requirements elicitation techniqueo Reaching agreements with stakeholders on what interfaces are needed

Conducting Pre workshop interviews can help you prepare for a requirements workshop A plan for requirement elicitation techniques that needs to be used is done during BAPM

Business analysis planning and monitoring

Element for requirements workshop that can be considered as a strength and usageconsideration

o Facilitators immediate feedback of the requirements to the stakeholderso This is considered as Strength of requirements workshop

Facilitating cross functional sessions refers to the technique of using requirements workshops Likely audience for a survey

o Business domain SMEs Marketing Accounting Operations

Interoperabilityo Discussion on systems communications and how two systems exchange data and

services with stakeholders

Items having stakeholder concerns as Inputo Business caseo Assumptions and constraintso Assess organizational readiness

Evolutionary prototype is rigorous and does extend into a fully functional systems

8/13/2019 Requiremenents Elicitation

2/2

Horizontal prototype is shallow, and models a wide view of systems functionality Vertical prototype is deep and models a narrow slice of systems functionality The proper sequence for using requirements elicitation techniques can be described as

following the business analysis plan for requirements elicitation.

o Requirements plan is part of the preparation and will determine which activities willcome first

Scribes roleo Documenting business requirements in the format determined prior to the meeting

Disadvantage of Interface Analysiso Does not assess internal components

Storyboard depicts interfaces and related elements. Synonyms for Storyboardo Dialog map

An analysis model that illustrates the architecture of the systems user interfaceo Dialog hierarchyo Navigation flow

Requirement elicitation techniques for delivering requirements quicklyo Requirements workshopso Prototype

Outputs of preparing for elicitationo Supporting materialso Scheduled resources

Key elements when conducting elicitation activitieso Tracing requirementso Capturing requirement attributeso Tracking elicitation metrics