Presentation on Requirement Elicitation Analysis

1. Requirement Elicitation and Analysis
Submitted by: Rozeep Rai
Submitted to: Er.Pradip Aryal

2. Table of contents:
• Introduction
• Techniques for eliciting requirements
• Process of requirement elicitation and
analysis
• Requirements elicitation Activities
• Problems of Elicitation and Analysis
• Solutions to Overcome Challenges

3. Introduction
• It’s 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 constraints.
• It is a process that involves
gathering, researching, defining,
structuring, and clarifying the
requirements of a product.
• As a result of elicitation, a Business
Analyst creates a set of project
objectives.

4. Techniques for eliciting requirements:

5. The requirements elicitation and analysis has 4
main process:

6. 1.Requirements Discovery
It’s the process of interacting with, and gathering the requirements from, the
stakeholders about the required system and the existing system (if exists).
2. Requirements Classification & Organization
Putting related requirements together, and decomposing the system into sub-
components of related requirements. Then, we define the relationship between
these components.
3. Requirements Prioritization & Negotiation
This activity 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.
4.Requirements Specification
It’s the process of writing down the user and system requirements into a
document. The requirements should be clear, easy to understand, complete, and
consistent.

7. Requirements elicitation Activities:
Requirements elicitation includes the subsequent activities. Few of
them are listed below –
• Knowledge of the overall area where the systems is applied.
• The details of the precise customer problem where the system are
going to be applied must be understood.
• Interaction of system with external requirements.
• Detailed investigation of user needs.
• Define the constraints for system development.

8. Problems of Elicitation and Analysis
• Getting all, and only, the right people involved.
• Stakeholders often don't know what they want
• Stakeholders express requirements in their terms.
• Stakeholders may have conflicting requirements.
• Requirement change during the analysis process.

9. Solutions to Overcome Challenges in Eliciting Requirements:
• Maintaining proper documentation.
• Trying to understand from a stakeholder’s perspective.
• Establishing proper communication with stakeholders.
• Identifying conflicting requirements from the stakeholder side.
• Establishing structured and insightful discussions with end-users.
• Performing proper market research and competitor analysis.

10. References:
• Software Engineering, 9th edition, Chapter 4, Ian Sommerville — A highly
recommended comprehensive textbook on software engineering.
• C. Slamet, A. Rahman, M. A. Ramdhani, and W. Darmalaksana,“Clustering
the Verses of the Holy Qur’an Using K-Means Algorithm,” Asian J. Inf.
Technol., vol. 15, no. 24, pp. 5159–5162, 2016.
• https://www.codingninjas.com/codestudio/library/requirement-elicitation-
and-analysis
• https://www.simplilearn.com/what-is-elicitation-article

11. Thank you