SAB7#38 Collect Requirements Process

Annotations:

• Historical records can provide details of the reporting requirements.

Annotations:

• Interviews of experts in the team.

Annotations:

• 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.

Annotations:

• Bring together actors with different perspectives (eg , product designers and end users ) to talk about the product and , ultimately , define requirements.

Annotations:

• 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.

Annotations:

• It takes place during the same session as brainstorming . The meeting participants categorized the most useful ideas generated during brainstorming session.

Annotations:

• 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.

Annotations:

• It is a diagram of ideas or notes to help generate , sort, or registration information.

Annotations:

• Ideas generated from most any other requirements gathering techniques are grouped by similarities.

Annotations:

• Questionnaires or surveys are typically used for large groups .

Annotations:

• This technique generally involves job shadowing see a potential user product at work and in some cases , participation in the work to help identify.

Annotations:

• The prototype stakeholders is presented for feedback. The prototype can be updated several times to incorporate feedback until the requirements for the product solidified.

Annotations:

• Another way to help identify and define the requirements is to watch what the competition is doing.

Annotations:

• Also known as a data flow diagram context level , it is frequently used to define the scope and model.

Annotations:

• It is essential to resolve these conflicts and review, analyze , accept or reject , and prioritize the requirements before writing to the project documents .

1. Balancing Stakeholders Requirements
2. Resolving Competing Requirements
   1. Troubleshooting together
3. Requirements traceability matrix