“Need of the client is defined as requirement, in the role of a BA we can define it as a “need of the stakeholder “. Once this requirement has been raised by the stakeholder it is the BA’s role to further define, analyze, validate and prioritize the requirement.
In real life, the stakeholder will typically state their business problem or need and as a BA it is our responsibility to transform it into a solution by defining, analyzing, validating and prioritizing the requirement.
Types of Requirement
1. Business Requirement
Describe the need of the organization what they want. Documented in BRD
2. Stakeholder Requirement
BA required gathering the information from user prospective which satisfies the Business Requirement.
3. Transition Requirement
Current state of an organization to a future state.
4. Solution Requirement
Functional Requirement
Functional Requirement is system feature that must build into the system to satisfy the user requirement.
Non Functional Requirement
Nonfunctional Requirement is the one that do not directly relate to the behavior or the functionality of the solutions.
Non Functional Requirement is a quality attribute that system must have.
Documented in FRD
Different Elicitation Technique
1. Brainstorming
2. Document Analysis
3. Focus Group
4. Interface Analysis
5. Interviews
6. Observations
7. Prototyping
8. Questionnaire