requirements-elicitationlisted

# Requirements Elicitation Skill ## Overview This skill provides structured techniques for gathering, analyzing, and documenting software requirements from stakeholders and existing systems. ## Elicitation Techniques ### 1. Structured Interviews Use predefined question sets organized by category: - Start with open-ended questions to understand context - Follow with specific questions to gather details - End with validation questions to confirm understanding ### 2. Adaptive Questioning Dynamically adjust questions based on: - Previous answers provided - Domain context discovered - Gaps identified in requirements - Stakeholder role and expertise level ### 3. Document Analysis Extract requirements from existing: - Business process documents - User manuals - Training materials - Support tickets and feedback ### 4. Observation Understand requirements by observing: - Current system usage - User workflows - Pain points and workarounds ## Requirement Categories ### Functional Requirements (FR) What the system must DO: - Features and capabilities - Business rules and logic - Data processing requirements - User interactions ### Non-Functional Requirements (NFR) How the system must BEHAVE: #### FURPS+ Model - **Functionality**: Security, compliance - **Usability**: Accessibility, learnability - **Reliability**: Availability, fault tolerance - **Performance**: Response time, throughput - **Supportability**: Maintainability, testability - **+Constraints**: Design, implementatio