Author Topic: Elicitation Techniques in Business Analysis  (Read 7561 times)

1190953311

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #45 on: December 16, 2019, 06:58:20 pm »
1. what are the requirement elicitation techniques?

2. when requirements questions?

1192357311

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #46 on: December 17, 2019, 05:30:19 pm »
Various elicitation techniques used by the business analyst are:

1. Brainstorming
2. Document Analysis
3. Focus Groups
4. Interface Analysis
5. Interviews
6. Observation
7. Prototyping
8. Requirements Workshops
9. Survey/Questionnaire[/li][/list]

1191214910

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Elicitation Techniques in Business Analysis
« Reply #47 on: December 29, 2019, 07:43:02 pm »
Elicitation techniques is to give the perfect,exact and correct proper solutions.
They are some elicitation techniques used by business Analyst as follows
1. Brainstorming
2. Document Analysis
3. Focus Groups
4. Interface Analysis
5. Interviews
6. Observation
7. Prototyping
8. Requirements Workshops

1200182002

  • Global Moderator
  • Newbie
  • *****
  • Posts: 14
Re: Elicitation Techniques in Business Analysis
« Reply #48 on: April 11, 2020, 01:46:37 pm »
Different types of Elicitation Techniques are

1. Brainstorming
Prepare for Brainstorming
Conduct Brainstorming
Wrap-up Brainstorming

2. Document Analysis
Prepare for document analysis
Analyze the documents
Post Document Analysts wrap-up

3. Reverse Engineering
Black Box Reverse Engineering
White Box Reverse Engineering

4. Observation
Passive/invisible
Active/Visible

5. Workshop

6. Joint Application Development (JAD)

7. Interview

8. Prototyping

9. Questionnaire

10. MoScoW




1202988702

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #49 on: May 05, 2020, 03:49:47 pm »
Different Types Of Elicitation Technique are :
Brainstorming : Brainstorming can be done individually or in a group. Users or stakeholders can come up with ideas or requirements that they have seen or experienced. These ideas can be reviewed and the relevant ones can then be included in the system requirements.

Document analysis : This is helpful in understanding the current process & can provide the inputs for the new system requirements.
Documents like user manuals, software vendor manuals, BRD, Features Documents, Functionality documents.

Reverse engineering : If an existing system has outdated documentation, it can be reverse engineered to understand what the system does. This is an elicitation technique that can extract implemented requirements from the system. There are two types of reverse engineering techniques.
   Black box reverse engineering: The system is studied without examining its internal structure    (function and composition of software).
   White box reverse engineering: The inner workings of the system are studied (analyzing and    understanding of software code).

Focus Group : A focus group are basically the End Users, these are the people who would be using the system in future upon project completion. The focus group is a means to elicit ideas & attitudes about a specific product, service or opportunity in an interactive group environment. The participants share their impressions, preferences & needs, guided by a moderator. There are 2 types of focus groups
Homogeneous: Based on similar characteristics. 
Heterogeneous: Different background people.
Observation : This elicitation technique helps in collecting requirements by observing users or stakeholders. This can provide information about the exiting process, inputs and outputs. There are two kinds of observations — active and passive.
In active (Visible) observation, the business analyst directly observes the users or stakeholders,
In passive (Invisible) observation, the business analyst observes the subject matter experts.
Workshop : Workshops comprise a group of users or stakeholders 6 or more in numbers working together to identify requirements. Workshops are used to scope, discover, define, and prioritize requirements for the proposed system. These are usually conducted by the client.
They are the most effective way to deliver high-quality requirements quickly. Workshops tend to be of a defined duration, rather than outcome & may need to be briefly repeated in order to clarify or obtain further details.
JAD (Joint Application Development) : Joint Application Development (JAD) technique is an extended session to the workshop. In the JAD session stakeholders and project team works together to identify the requirements. These sessions allow the business team to gather and consolidate large amounts of information. The JAD team includes business process owners, client representatives, users or stakeholders, business analysts, project managers, IT experts (developers, quality assurance, designers, and security).
Interview : An interview is a systematic approach to elicit information from a person or group of people in an informal or formal setting by talking to the person. In this case, the business analyst acts as an interviewer. An interview provides an opportunity to explore and/or clarify requirements in more detail. Without knowing the expectations and goals of the stakeholders it is difficult to fulfil requirements.
Prototyping : Screen mockups can support the requirement gathering process, when introduced at the correct time. Mockups help stakeholders visualize the functionality of a system. This can be an advantage to business analysts and stakeholders since this allows them to identify gaps/problems early.
Surveys/Questionnaires : Questionnaires are useful when there is a lot of information to be gathered from a larger group of stakeholders. This enables the business team to gather requirements from stakeholders remotely. The design of the questionnaire is very important, since it can influence the answers that people provide.

1200473701

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #50 on: May 11, 2020, 10:50:36 am »
Here are the 9 elicitation techniques defined by the BABOK for business analysts:

Brainstorming
Document Analysis
Focus Groups
Interface Analysis
Interviews
Observation
Prototyping
Requirements Workshops
Survey/Questionnaire

1190952411

  • Global Moderator
  • Newbie
  • *****
  • Posts: 10
Re: Elicitation Techniques in Business Analysis
« Reply #51 on: May 15, 2020, 05:24:37 pm »
Elicitation refers to requirement gathering.

There are various elicitation techniques which are used by business analyst to gather information they are;
1. Document analysis
2. Self Observation
3. Brainstorming
4. Requirement workshops
5. Interface Analysis
6. Focus Groups
7. Interviews
8. Prototyping
9. Survey/Questionnaire
 

1202894803

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Elicitation Techniques in Business Analysis
« Reply #52 on: June 04, 2020, 11:20:28 pm »
Elicitation Techniques in Business Analysis:
?Brainstorming
?Document Analysis
?Focus Groups
?Interface Analysis
?Interviews
?Observation
?Prototyping
?Requirements Workshops
?Survey/Questionnaire

1192091407

  • Global Moderator
  • Newbie
  • *****
  • Posts: 11
Re: Elicitation Techniques in Business Analysis
« Reply #53 on: June 05, 2020, 06:11:17 pm »
what are the mostly used elicitation techniques used practically in a company?

1202988602

  • Global Moderator
  • Newbie
  • *****
  • Posts: 5
Re: Elicitation Techniques in Business Analysis
« Reply #54 on: June 06, 2020, 12:58:36 am »
Requirements Elicitation is the process of digging out the information from the stakeholders.
The different types of elicitation techniques are as follows:
Brainstorming
Documentation analysis
Reverse Engineering
Observation
Focus Groups
workshop
JAD(Joint Application Development)
Interview
Prototyping
Questionnaire