Requirements Elicitation

Problems During Elicitation Techniques, Basics of Knowledge

Acquisition, Knowledge Acquisition Techniques
 Requirements Elicitation
• Definition: Requirements elicitation is the process of
gathering, documenting, and managing the
requirements of a system from stakeholders. It involves
communication between the development team and
stakeholders to understand their needs, expectations,
and constraints.
 Techniques for Requirements Elicitation
• Interviews:
• Conducting one-on-one or group interviews with stakeholders to gather information about their
needs and expectations.
• Surveys/Questionnaires:
• Distributing surveys or questionnaires to a large number of stakeholders to collect feedback and
requirements.
• Observation:
• Directly observing users and their interactions with the existing system or the environment to
identify requirements.
• Prototyping:
• Developing a prototype or a mock-up of the system to help stakeholders visualize and provide
feedback on the desired features.
• Workshops:
• Organizing collaborative workshops with stakeholders to discuss and define requirements
collectively.
 Problems During Elicitation:
• Incomplete Requirements:
• Stakeholders may not provide a comprehensive set of requirements, leading to gaps in
understanding.
• Ambiguous Requirements:
• Vague or unclear statements from stakeholders can result in misinterpretation and confusion.
• Changing Requirements:
• Stakeholder needs may evolve over time, leading to changes in requirements during the
development process.
• Conflicting Requirements:
• Different stakeholders may have conflicting needs or priorities, requiring careful negotiation and
resolution.
• Lack of User Involvement:
• If key stakeholders, especially end-users, are not actively involved, it can result in requirements
that don't meet their actual needs.
 Basics of Knowledge Acquisition
• Definition: Knowledge acquisition is the process of capturing, organizing,
and formalizing information from various sources to enhance an
organization's understanding and decision-making capabilities.
• Key Concepts:
• Explicit vs. Tacit Knowledge:
• Explicit knowledge is codified and can be easily communicated, while tacit
knowledge is personal and often difficult to formalize.
• Knowledge Representation:
• Techniques for representing knowledge, such as ontologies, conceptual models, or
semantic networks.
• Knowledge Codification:
• The process of converting tacit knowledge into explicit knowledge for easier
sharing and management.
 Knowledge Acquisition Techniques:
• Interviews and Surveys:
• Similar to requirements elicitation, these methods help gather information from
experts or stakeholders.
• Document Analysis:
• Reviewing existing documents, reports, and manuals to extract relevant
knowledge.
• Observation:
• Directly observing experts or processes to understand and capture tacit
knowledge.
• Brainstorming:
• Collaborative sessions where individuals generate ideas and insights collectively.
• Prototyping:
• Building prototypes or models to capture and refine knowledge in a tangible
form.
• Collaborative Tools:
• Using collaborative platforms and tools to facilitate knowledge sharing among
team members.

(Effective requirements elicitation and knowledge acquisition are critical

for the success of any project, ensuring that the delivered system meets
the needs and expectations of stakeholders while leveraging valuable
knowledge within an organization.)