SRE Elicitation - ISB26404 PDF

ISB26404 SOFTWARE REQUIREMENTS ENGINEERING Sugi   What is Requirements Elicitation?  Why is Requirements Elicitation Important? Content  Elicitation Activities  Elicitation Techniques Overview  Challenges in Elicitati...

ISB26404 SOFTWARE REQUIREMENTS ENGINEERING Sugi   What is Requirements Elicitation?  Why is Requirements Elicitation Important? Content  Elicitation Activities  Elicitation Techniques Overview  Challenges in Elicitation Activities 2  Definition: Requirements elicitation is What is the process of identifying Requireme and understanding nts stakeholders needs to Elicitation define software ? requirements. 3  Key Aspects: Collaboration with What is stakeholders. Requireme Discovering explicit and nts Elicitation implicit requirements. ? Iterative and ongoing throughout the project lifecycle. 4  Key Aspects: Explicit requirements --- What is clearly stated Requireme features/functionalities nts Implicit requirements --- Elicitation ? which are not stated, need to elicit further. 5   Forms the foundation for system design and Why is development. Requireme  Helps in identifying potential nts risks early. Elicitation  Ensures alignment with Important business goals and user ? expectations.  Reduces costly rework in later stages. 6   Preparation: Planning and selecting techniques.  Elicitation: Gathering Elicitation information from stakeholders. Activities  Documentation: Recording and organizing elicited requirements.  Validation: Ensuring the requirements meet stakeholder needs. 7   Preparation  Tasks:  Identify stakeholders Elicitation  Select the elicitation Activities techniques  Define objective elicitation  Prepare questions/checklist/doc for stakeholders 8  Elicitation: Tasks: Elicitation Implement elicitation Activities techniques Output from elicitation: data / info – BA to do further analysis 9  Documentation : Tasks: Elicitation Analyse the data/info – Activities proper format Organize requirements – FR,QR,CR Document in relevant format-SRS 10  Validation : Tasks: Elicitation Review sessions – gain Activities feedback from stakeholders 11  Interview Survey / Questionnaire Elicitation Technique Brainstorming s Workshop Overview Observation Document Analysis 12  Availability of stakeholders Communication issues Challenges in BA + BA, SH + BA, SH + Elicitation SH Activities Complex business process Stakeholders not sure what they want 13  Effective requirements elicitation minimizes risks, reduces rework, and leads Conclusion to the delivery of high- quality software that satisfies users and stakeholders. 14