Requirement Elicitation Technique –
- Requirement elicitation technique is the process of taking in dept information from stakeholder.
- Requirement elicitation technique is the process of digging out the information from the stakeholders, Requirement elicitation serves the foundation in documenting the requirement.
- By using Elicitation Techniques, we can find what kind of problem they are facing. And how we can build better software that beneficial for the stakeholder.
Types of Elicitation Techniques –
- Brainstorming – Brainstorming is a group elicitation technique where a problem or topic is presented to the group, and participants are asked to produce as many ideas to solve/address the topic as possible.
- Document Analysis – Document Analysis is a type of requirements elicitation that falls under the category of research. This technique involves examining existing organizational process assets (OPAs) and other material to get background information on the existing business environment or a domain related to an area of interest.
- Reverse Engineering – In the situation where the software is small or outdated documentation and it is necessary to understand what the system actually does, Revers engineering is an elicitation technique that can extract implemented requirements from the software code.
- Focus Groups – A focus group is a means to elicit ideas and attitudes about a specific product, service or opportunity in an interactive group environment. The participants share their Impressions, Preferences an d Needs guided by a moderator.
- Observation – Observing, shadowing users or doing a part of their job, can provide information of existing processes, inputs and outputs. Active approaches and Passive approaches these two are types of observation process.
- Workshop – A requirement workshop is a structured approach to capture requirements. A workshop may be used to scope, discover, define, prioritize and reach closure on requirements for the target system.
- Joint Application Document (JAD) – The goal of a JAD session is to gather the information from the SMES and other IT specialist before the project is started. It is a group activity where the different aspects of the project is discussed and the outcomes are documented and based on the discussions the project is planned.
- Interview – Interview of a user and stakeholders are important in creating software. An interview is a systematic approach where interviewee is going to ask relevant questions related to software and documenting the responses. Structured approaches and Unstructured approaches these are two types of Interview. Open ended questions and Close ended question these are also important part of Interview process.
- Survey – Surveys are the preferred elicitation technique when faced with a large number of stakeholders or when stakeholders are geographically dispersed and you need to gather the same information from them. Surveys can also be used to gather requirements anonymously.
- Questionaries – Questionnaires can be used to collect quantitative and/or qualitative information. A questionnaire is a list of questions or items used to gather data from respondents about their attitudes, experiences, or opinions. We will use it for gathering statistical information about the attributes, attitudes, or actions of population by a structured set of questions.
- Prototyping – Prototyping is an experimental process where design teams implement ideas into tangible forms from paper to digital. Teams build prototypes of varying degrees of fidelity to capture design concepts and test on users. Prototyping is also used for viewing sample how application will look.