REQUIREMENT ENGINEERING

Question 1

Interviews

Answer 1

conduct stakeholder interviews, either formally or informally, with individuals or small groups. Keep sessions small to maximize information. Designate a note-taker, use open-ended questions to foster discussion, and limit closed-ended questions to confirm facts. Interview diverse stakeholders for varied perspectives, consider their expertise, and recognize that interviews may not always lead to consensus but are effective for gathering information.

Question 2

Requirement Workshops

Answer 2

Requirements workshops are used to gather and prioritize system requirements. Relevant stakeholders attend to provide feedback, leading to increased clarity on software functionality. Approach workshops with a clear agenda, focusing each session on a specific aspect. Designate a facilitator and note-taker, and ensure an optimal number of participants to prevent slowdowns or information gaps. If stakeholders can’t all attend one session, consider holding multiple workshops on the same topic.

Question 3

Brainstorming

Answer 3

Brainstorming sessions gather spontaneous thoughts from a group, providing a fun and productive way to gather system requirements. Invite relevant stakeholders, considering multiple sessions for large groups. Ensure diverse stakeholder representation for varied perspectives. Hold sessions in a relaxed environment to encourage participation, with a designated facilitator to guide the discussion. Avoid criticism of ideas to maintain a positive atmosphere. If discussions veer off-topic, steer them back on track. Document ideas on a visible whiteboard and set a time limit for the session.

Question 4

Observation

Answer 4

Observation involves studying stakeholders in their work environment to understand current processes, especially when replacing existing systems. It helps identify overlooked requirements and nuances not mentioned through other techniques. Observers may passively take notes or engage in dialogues with stakeholders. However, it can be time-consuming and disruptive to stakeholders’ work. Despite limitations, observing various scenarios remains crucial for software requirements.

Question 5

Focus Groups

Answer 5

A focus group is a formal technique where a group of participants, such as system users or experts, provide feedback. Moderated by a neutral facilitator, open-ended questions encourage discussion. Responses are typically spoken, not written. While faster than individual interviews, focus groups risk groupthink and may deter some from sharing ideas in a group setting.

Question 6

Surveys

Answer 6

Surveys are effective for gathering stakeholder information with a clear purpose. Multiple short surveys may be preferable to lengthy ones, covering different aspects of the system. Questions should be well-structured and concise, often closed-ended for easier analysis. While open-ended questions are possible, they require more effort to analyze compared to closed ones, which can be automatically processed in tools like Microsoft Forms.