Name some requirement gathering techniques

Name some requirement gathering techniques

1. Interviews
- It is one of the strongest mediums for collecting the requirements.

Several types of interviews can be conducted such as:

- Structured (closed) interviews,
- Non-structured (open) interviews
- Oral interviews
- Written interviews
- One-to-one interviews
- Group interviews

2. Surveys
- They are conducted among various stakeholders by querying about the expectation and requirements from the upcoming system.

3. Questionnaires
- It is a document with a pre-defined set of objective questions and respective options which are given to the stakeholders to answer, and are later collected and compiled.

4. Task analysis
- The operations for the new system is analyzed by the team of engineers and developers.
- The requirements of the proposed system are collected if the client already has some software to perform certain operations.

5. Domain Analysis
- Every software falls into some domain category.
- The general and specific requirements are analyzed by the expert people in the domain.

6. Brainstorming
- An informal debate takes place among the various stakeholders and all their inputs are recorded for further requirements analysis.

7. Prototyping
- Prototyping is used for building the user interface without adding any detail functionality for user to interpret the features of intended software product.
- It gives a better idea of requirements.
- A feedback is taken from the client by showing them the prototype.
- The client feedback is an input.

8. Observation
- A team of experts visit the client’s organization or workplace and observe the actual working of the existing installed systems.
- The workflow at client’s end and how execution problems are dealt with are observed. The team draws some conclusions.
Why is easy access to a customer a good thing?
Why is easy access to a customer a good thing? - 1. It helps in taking the clarifications about their requirements on regular basis to avoid making the wrong system..........
When should you end the process of gathering requirements?
When should you end the process of gathering requirements? - Some points that indicate the end of requirement gathering process: ......
Why is a simple change control process necessary for agile projects?
Why is a simple change control process necessary for agile projects? - Change control process necessary for agile projects because requirements change frequently.........
Post your comment