Purpose: Determine suitable requirements techniques to gather requirements.
Stakeholders: Sponsor, Domain SMEs, Project manager, Regulator.
Inputs
1.
Requirements context
2.
System scope
3.
1.
Elements
Understand different types of requirements to be gathered, for example conscious, unconscious, and subconscious.
2.
Determine suitable requirements techniques to gather requirements.
Outputs
1.
Identified requirements techniques
Tools and Techniques: Brainstorming, Requirements engineering techniques chart.
Main goal of all elicitation techniques is in supporting the requirements engineer in ascertaining requirements.
Elicitation techniques serve the purpose of identifying the conscious, unconscious, and subconscious stakeholder requirements. Combining techniques lower risks. Important influencing factors when choosing the appropriate elicitation techniques are:
1.
Constraints critical to the project, time and budget constraints.
2.
Distinction between conscious, unconscious, and subconscious requirements to be elicited,
3.
Desired level of detail,
4.
availability of the stakeholders, location and time-zone
5.
experience of the requirements engineer and stakeholders with elicitation techniques,
6.
Chances and risks of the project - Distinction between fixed price contracts and service contracts,
7.
Type of project - Whether the system to be built is a new development or an extension of a legacy system, and availability of the stakeholders.
8.
Complexity of the system.
Page 1