Techniques and Process of Requirement Elicitation

Business Analyst

A business analyst is an individual who has the primary responsibility to gather requirements elicit analyze the document and validate the needs of the stakeholders.

BA acts as the bridge between customers and the developers’ team. BA does the bidirectional communication to cover up the requirements risk. The business analyst communicates with the project manager and communicates with the development team and with the testers and the project sponsor.

Function and Responsibilities of Business Analyst

A business analyst plans the required approach for the requirement engineering process.
The business Analyst identifies the stakeholders who give us the requirement about the targeted system.
The business Analyst identifies the elicitation techniques and elicits the requirements.
Business Analyst analyzes the requirement and handles conflict.
The business Analyst documents the requirement and makes the formal document for requirements which is an SRS document.
The business Analyst communicates the requirement between all the stakeholders.
The business Analyst leads the requirement validation process.
Business Analyst facilitates requirements prioritization.
Business Analyst manages requirements and approved requirements.

Who can be a business User?

Former User of the Organization

We can make the former user of the organization or ex-employee of the organization the business analyst

Pros

Pros for making the former employee of the organization a business analyst.
Former user of the organization under the working environment of the organization.
Former user speaks the language of the organization.
Former user knows the existing system.

Cons

Cons for making the former employee of the organization a business analyst.
Former users maybe not be well in software engineering concepts.
Former users may be having less technical knowledge.
Former users might not consider input from joiner’s staff.

Former developers /testers of the Organization

We can make the former developers and testers of the organization business analysts.

Pros

Pros for making the former developers and testers of the organization business analysts.
Understand how the system is in development.
Software engineering concepts may be betters.
Developers or testers are good at finding errors and bugs in underdeveloped systems.

Cons

Developers and testers usually lack communication skills. Focus more on the functionality of the system and ignore the customer choice that leads to the overlooked stakeholder.

Former project manager of the Organization

We can make the former project manager of the organization a business analyst.

Pros

Pros in making a project manager as the business analyst.
Former project managers have a lot of experience in working with teams.
Strong organizational skills and strong communication skills.
Cons
Cons in making project manager as the business analyst.
Formers project manager lack in software engineering concepts.
Former project manager lack modeling skill.

Subject matter expert

We can make the subject matter expert of the organization a business analyst subject matter expert also known as a domain expert.

Pros

Pros in making SME as the business analyst.
SME has a lot of experience.
SMEs have a lot of understanding of the domain.
Cons
Cons in making SME as the business analyst.
SMEs may not give an innovative idea.
SMEs in old the requirement according to their preference.

Rookie

We can make a rookie a business analyst rookie is a fresh graduate.

Pros

Pros in making Rookie as the business analyst.
No preconceived notions (No idea) clean about the statement.
Rookie gives Innovative ideas.
Cons
Rookie has no experience in the domain.