Requirement Elicitation Techniques

What is a requirement? –

“A requirement serves as the foundation of system or the system components. It can be something that is demanded or obligatory; a property that  is essential for the system to perform its functions”

It can be like - A NEED (e.g. a taxi services co. looking to get a mobile App) 

A GOAL TO MEET (e.g. Reduce invoice processing time for an A/c firm) 

AN OBJECTIVE (e.g. Improve the customer journey on eCommerce website ) –

Requirement Elicitation -

“It is the process of digging out the information from the stakeholders”.

Requirements elicitation serves the foundation in documenting the requirements. Since it is the process of digging the information, well there are multiple techniques of doing this.  

–Brainstorming 

- Document analysis

–Reverse engineering 

–Focus groups

–Observation 

–Workshop

–JAD sessions

–Interview

BRAINSTORMING-

–Brainstorming can be done either individually or in groups. The ideas collected can then be reviewed/analyzed and wherever relevant included within the system requirements. –The ideas can come from what users / stakeholders have seen (e.g IT events, exhibitions) or experienced elsewhere (during the prior experience).

Advantages & Disadvantages of Brainstorming

Advantages: One can come up with very innovative ideas and requirements. It can be an efficient way for users / stakeholders to define their requirements. 

Disadvantages: People can not easily brainstorm ideas when required to do so.

STEPS:

Document Analysis -

Document analysis is used if the objective is to gather details of the "As Is" environment such as existing business rules, entities, and attributes that need to be included in a new system or need to be updated for the current system There can be an existing documentation about the current system which could provide some of the inputs for the new system requirements.

Such documentation (if exists) could include interface details, user manuals and s/w vendor manuals.

Advantages & Disadvantages of Documents Analysis

Advantage: It could be a lot of information and easy to transfer to a new system requirements document.

Disadvantage: Existing documentation may often be old and out of date. Systems, interfaces, processes and reports may have changed out of all recognition. Care needs to taken, as it may not reflect what you need from a new system.