Requirement Elicitation and Analysis


Requirement Elicitation and Analysis

Requirement Elicitation and Analysis is a process of interacting with customers and end-users to find out about the domain requirements, what services the system should provide, and the other constrains.

It may also involve a different kinds of stockholders; end-users, managers, system engineers, test engineers, maintenance engineers, etc.

Here are the 4 main processes of requirements elicitation and analysis.

Requirement Elicitation and Analysis

Fig: The process of requirements elicitation and analysis

1. Requirements Discovery

  • It’s the process of interacting and gathering the requirements from the stakeholders about the required system.
  • It can be done using some techniques, like interviews, scenarios, prototypes, etc, which help the stockholders to understand what the system will be like.

 

2. Requirements Classification & Organization

  • It’s very important to organize the overall structure of the system.
  • Putting related requirements together, and decomposing the system into sub components of related requirements.
  • Then, we define the relationship between these components.
  • What we do here will help us in the decision of identifying the most suitable architectural design patterns.

3. Requirements Prioritization & Negotiation

  • It is concerned with prioritizing requirements and finding and resolving requirements conflicts through negotiations until you reach a situation where some of the stakeholders can compromise.
  • We shouldn’t reach a situation where a stakeholder is not satisfied because his requirements are not taken into consideration.
  • Prioritizing your requirements will help us later to focus on the essentials and core features of the system.
  • It can be achieved by giving every piece of function a priority level.

 

4. Requirements Specification

  • This is the last stage of the cycle.
  • All formal & informal, functional and non-functional requirements are documented and made available for next phase processing.

you might check :   Requirement Elicitation Techniques


 

129 total views, 0 views today

A Soon-to-be Computer Engineer by profession, he has profound devotion to add Data Scientist as a prefix to his name. He’s been to the nooks of the web (at least of the surface web) and planning to add some real figures in his pocket!

Leave a Reply