Requirements Elicitation

The real problem is mapped to an analogy and the solutions found by the stakeholders are mapped back to the real problem. This RE technique is:

• brainstorming

• change of perspective

• system archeology

• Analogy

Useful if stakeholders can only expressed their knowledge in biased manner or are very opinionated. This RE technique is:

• Change of perspective

• perspective-based reading

• requirements reuse

• brainstorming

Have to prepare questions in advanced and new information can be discussed immediately. This RE technique is:

• Interview

• questionnaire

• field observation

• apprenticing

Use open and /or close questions where large and distributed number of stakeholders can participate. This RE technique is:

• Interview

• questionnaire

• field observation

• apprenticing

Requirements engineer is on location with the specialist or the users of the system to elicit requirements. This RE technique is:

• Change of perspective

• field observation

• apprenticing

• brainstorming

Extracts requirements for new system from documentation or source code of legacy system.

• Interview

• questionnaire

• system archaeology

• apprenticing

Requirements engineer becomes apprentice and actively learns and performs procedures of stakeholder

• Interview

• questionnaire

• system archeology

• apprenticing

Read system documents with particular perspective in mind focusing only particular parts of document

• System archaeology,

• perspective-based reading

• requirements reuse

• questionnaire

Existing requirements of good quality legacy system can be reused.

• System archaeology

• perspective-based reading

• questionnaire

• requirements reuse

This RE technique involve group of 5-10 people collecting ideas from them collaboratively and documenting them.

• Change of perspective

• field observation

• brainstorming

• apprenticing