Requirement Elicitation Process

Taylor Emma
1 Min Read
Disclosure: This website may contain affiliate links, which means I may earn a commission if you click on the link and make a purchase. I only recommend products or services that I personally use and believe will add value to my readers. Your support is appreciated!

Requirement elicitation process can be depicted using the folloiwng diagram:

Description: Requirement elicitation process

●      Requirements gathering – The developers discuss with the client and end users and know their expectations from the software.

●      Organizing Requirements – The developers prioritize and arrange the requirements in order of importance, urgency and convenience.

●      Negotiation & discussion – If requirements are ambiguous or there are some conflicts in requirements of various stakeholders, if they are, it is then negotiated and discussed with stakeholders. Requirements may then be prioritized and reasonably compromised.

●      The requirements come from various stakeholders. To remove the ambiguity and conflicts, they are discussed for clarity and correctness. Unrealistic requirements are compromised reasonably.

●      Documentation – All formal & informal, functional and non-functional requirements are documented and made available for next phase processing.

 

Share This Article
A senior editor for The Mars that left the company to join the team of SenseCentral as a news editor and content creator. An artist by nature who enjoys video games, guitars, action figures, cooking, painting, drawing and good music.
Leave a review