COEPD – Center of Excellence for Professional Development Happy Learning
Blog writing 2
Requirements, Types of Requirements and Elicitation Techniques
What is Requirements
The definition of Requirements in Business Analysis is the needs of term of the stakeholder. When the stakeholder raised requirement the business analyst analyse, define, validate the prioritize the requirement.
When Business problems or needs typically will state by the stakeholder. Then the business analyst will find the solution by defending the problem, Analysing the problem, validating the problem and prioritize the problem.
Business Analyst will take that problem as a Requirement.
Types of requirements
- Business Requirement
Defending the wants and needs what they want in organization
For example, Implementing and developing application of customer service to communicate and manage customer calls.
- Stakeholder Requirement
Business Analyst should satisfies the business requirement by gathering information from user perspective.
For Example, The Record calls and the calls should able receive by the Representative of customer service
- Transition Requirement
The present state of an organisation to the future state of organization. The purpose which only used to serve and we don’t required.
For Example, Application of online complaint for the customer.
- Solution Requirement
The launching of new product, Creating dashboard, Comes with solution of building a new application
- Functional Requirement
The Functional Requirement is should building the features of an system to satisfies the requirement of user.
For example, How can we able to receive different network calls.
- Non-Functional Requirement
The solution which not directly related to the functionality or behaviour is the one is known as Non- functional Requirement
The system must have the quality attribute in Non-functional requirement
For Example, In this If possible the application of customer service should be available 24/7 without down time
What are different elicitation Techniques?
The business analyst uses the elicitation techniques.
In Business analyst, Elicitation is one of the area that both extremely complex and extremely simple.
Simply, The discovering process of the requirements is known as elicitation. The project requirement details and scope comes stakeholders to understand their expectations and needs to engaging in particular elicitations.
The Elicitation Techniques
Here the list of Business analyst used primary techniques of elicitation :
1.Brainstorming –
It is to generating new solution or ideas from free form discussion.
2.Analysis of Document –
It is to understand the requirements of potential by Existing Documentation Analysis.
- Focus Groups-
For getting feedbacks from the stakeholders external to the organization by conducting small group discussions with stakeholders.
4.Analysis of interface –
For enable integration by understating future state requirements and current state requirements by analysing the interface between the systems or between the system and user.
5.Interviews –
Focusing conversations by asking specific questions of requirements to an individual stakeholders or group of stakeholders.
6.Observation –
To understating the process details, by observing completing business process or job functions of a stakeholder.
- Prototyping –
To elicit requirement, is there any conformation or any new ideas with stakeholders by reviewing possible solutions by creating visual representation.
- Workshop requirements –
The documentation requirements to designed to discover, analyse and validate by meetings which more longer time duration like minimum half day and can spent some days, which high level structured and more formal.
- Questionnaire or Survey –
The specific questions of a answer in feedback a request for a unstructured or structured. The useful information gather from the large number of stakeholders and the decision by which potential impact to discover information.
Here, So many Business analysts worried about who are new they should use all techniques but they are not getting right elicitation, and in this areas they are thinking about their experience and it shows that the reviews and casual conversations for getting information about needs of stakeholders takes more time.
This is the area business analyst should have relevant experience. And also even senior most business analysts are also can’t stop improving in this area.
