Requirements with elicitation Techniques

In requirements enterprise, requirements elicitation is the practice of collecting the requirements of a system from users, customers and other stakeholders. The practice is also sometimes referred to as requirement gathering. We have to understand the requiment in any business analyst profile we should also understand the different types of requirement.

Requirements are categories into two different types as follows:

• Functional Requirement
• Non-Functional Requirement

Basically the types of requirement are most important to understand the functional and non-functional requirements of the project. Any projects requirements need to be understand clearly, thought full and balanced.

• Functional requirements commonly comprised like business rules or terms and conditions, Administrative functions, Authentication, Audit tracking, etc. . . .

Mostly functional requirements specify behaviour or function. 

• Non-functional requirements commonly comprised like performance, capacity, availability, reliability, serviceability, usability recoverability, etc. …..

Mostly Non Functional requirements specify quality attributes or characteristics.

Types of Requirement:

It is a process in which scattered requirement are collect together for validating and sorting the requirement as per requirement.

As a business analyst you should understand the stakeholder’s requirement as a most important role. Identify the business need them into functional and non-functional requirement. As a business owner prioritising the requirement with the help of some of the techniques as follows:

• 100 Doller techniques
• Top 10 requirements
• Numerical assignment

These requirements are prioritise and validating purpose because most of the time requirement could be repeated or same functionality flow or process could be used with different steps.

For prioritising we should understand the Moscow i.e. Must, Should, Could, and would.

For validating requirements we should understand the FURPS: Functionality, Usability, Reliability, Performance, and Supportability.  This model is mostly used by software industry with the name FURPS+

CUCV: Clarity, Understandable, Consistent

CAE: Complete, Accurate, Executable

SMART: Specific, Measurable, Attainable, Realistic, Traceability

Let’s understand the different types of Elicitation technique:

Origin of elicit is from Latin it means to draw or bring out or forth.

We required these techniques under requirement gathering of business analyst profile. As a business analyst it is very important to understand the client requirement. There are many techniques used for understanding the client requirement and gathering the data are as follows:

• Brainstorming
• Document analysis
• Focus Group
• Interface Analysis
• Interviews
• Observations
• Prototyping
• Requirements workshop
• Survey / questionnaire