SAB7#38 Collect Requirements Process

SAB7#38 Collect Requirements Process

1. stakeholder requirements oriented

   • Working arrangements
   • Capacity of stakeholders
   • Quality
   • Processes

2. Management plan stakeholders

3. Interest groups techniques

   • Reviewing Historical Records
     • Historical records can provide details of the reporting requirements.
   • Interviews
     • Interviews of experts in the team.
   • Focus group
     • It helps to get a specific set of stakeholders or experts in the field the opinions and requirements for the product or aspect of the Project.
   • Facilitated Workshops
     • Bring together actors with different perspectives (eg , product designers and end users ) to talk about the product and , ultimately , define requirements.
   • Brainstorming
     • The purpose of brainstorming is not so much getting individual thoughts to encourage participants to build on the ideas of others. Someone mentioned an idea to solve a problem or , in this case, determine its scope . This idea generates an idea of ​​another participant , which leads to another idea, and so on. After all the ideas have been captured , the group can evaluate and sort through the technique of group analysis or multi-criteria decision nominal , as described in the following sections.
   • Nominal Group Technique
     • It takes place during the same session as brainstorming . The meeting participants categorized the most useful ideas generated during brainstorming session.
   • Multi-criteria Decision Analysis
     • With this technique , applicants quantify requirements using a decision matrix based on factors such as the expected level of risk , time estimates , and some estimates of benefits.
   • Mind Maps
     • It is a diagram of ideas or notes to help generate , sort, or registration information.
   • Affinity Diagrams
     • Ideas generated from most any other requirements gathering techniques are grouped by similarities.
   • Questionnaires and Surveys
     • Questionnaires or surveys are typically used for large groups .
   • Observation
     • This technique generally involves job shadowing see a potential user product at work and in some cases , participation in the work to help identify.
   • Prototypes
     • The prototype stakeholders is presented for feedback. The prototype can be updated several times to incorporate feedback until the requirements for the product solidified.
   • Benchmarking
     • Another way to help identify and define the requirements is to watch what the competition is doing.
   • Context diagrams
     • Also known as a data flow diagram context level , it is frequently used to define the scope and model.
   • Group decision Making
     • It is essential to resolve these conflicts and review, analyze , accept or reject , and prioritize the requirements before writing to the project documents .
   • Requirements Documentation
     • Balancing Stakeholders Requirements
     • Resolving Competing Requirements
       • Troubleshooting together
     • Requirements traceability matrix

4. Troubleshooting found

   • Continued Process
   • Traceability matrix
   • Requirements Plan

Bilder und Dateien der Mindmap