Role of Business Analyst in Requirement Engineering
Today lets try to Understand what is Requirement
Requirement engineering this in itself is a Ocean ….
Let’s try to make it simple and understand in a better way
What is a Requirement?
Hmm, It’s look like a pretty straight forward subject however the answer would be numerous.. Lets try to understand the same as we term it as a Requirement, others may have their own way to express it such as
- need of Stakeholder / Client
- condition to solve a problem or to achieve an objective
- function that system does
- Feature we intend to achieve
- constraint (Business, User, System, Technical, Project)
One need to understand there are two types of Requirements
- Business Requirement
- General Requirement
- Technical Requirement
- Solution Requirement
- Functional Requirement
- Non-Functional Requirement
In real world we expect Solution Requirement however we could receive the Business requirements at times. This is not because of any GAP ANALYSIS or something. It is simple because Stakeholder understands normal communication language and hence they might end up with Business Requirement.
Further, stakeholders might not even think about non-Functional requirements such as Capacity, Performance and so on … And so we need to probe such Requirements…
This further gives rise to TACIT KNOWLEDGE with the stakeholders..
Difference between Tacit Knowledge and Explicit Knowledge
- Explicit Knowledge: This type of knowledge is known by everyone in the Project, can be termed more of Documented Knowledge… such as Job Description, Policies, Procedures and so on
- Tacit Knowledge: This type of knowledge is always with Stakeholders and so we may need to extract the Requirement from the Stakeholders by using Various Elicitation Techniques…. This type of knowledge could be Skills, Culture and many more
This Gives rise to Requirement Engineering Framework
As you could see the above Diagram, it is easy to understand
Requirement Elicitation: We extract all the Requirement from the Stakeholders let it be Tacit Knowledge or Explicit Knowledge …. All the Requirements need to be addressed as In-scope …To elaborate you may need to use Various Investigation Technique such as Interview, Workshops, Prototyping, Questionnaire, Sampling, Observation etc… You need to understand every technique has it’s own pros and cons and hence it is crucial to understand which technique to use when…
Requirement Analysis: We analyze the entire requirement if they are Clear, Concise, Consistent, Unambiguous, Testable, and Traceable and so on
Requirement Validation: This Stage is crucial as all the Requirements need to be validated not only by Business but also by IT team (which some might miss). To check if requirement is as per their need, Testable, Traceable and the list goes on…
Requirement Documentation: We have to Document All the Requirements. You organization may have their own template and / or way of documenting such as UML, USE CASE Documentation, Functional Requirement Document (FRD), Requirement Catalogue, USER Stories etc
Requirement Management: This is a very Crucial Stage as any changes come needs to be addressed in Requirement Management. Hence we follow Vertical Traceability and Horizontal Traceability for the same.
Types is Requirement to be Addressed
Business Requirements: These are high level Requirements which could be given by Stakeholders can be further classified as
General Requirements – general or business requirements refer to business policies that are elaborated and expanded in the non-functional and functional requirements. These are critical activities of an organization that must be performed to meet the enterprise objectives. These could be related to Branding, Legal or so on
Technical Requirements – This type of requirements are again Business Requirements such as Hardware, Software, Internet and so on
Solution Requirements – Solution Requirements are further classified into Functional and non- functional requirements.
Functional Requirement – usually describes what the system must do; the capabilities, behavior and information about system or solution. Processing the inputs, data entry and retrieval type of statements classified under this group.
Non – functional Requirements – are also called as quality of service requirements. Usually these requirements define the attributes of the system functions. Usually these requirements describe the conditions and constraints under which solution must operate.
To get detailed knowledge about Requirement Engineering why not JOIN OUR COURSE TODAY. CLICK HERE