Lecture 2: Requirements & Elicitation & Analysis

목차

• Query Techniques: Focus Groups
• Query Techniques: Interviews/Questionnaires:

Requirements

A requirement is something the product must do or a quality that the product must have.

Functional Requirements: what the system must do

Non-Functional Requirements: qualities that the system must have e.g. usability, performance, security

Prioritizing requirements: MoSCoW method

 

 

Query Techniques: Focus Groups

Focus groups: group discussions chaired by moderator

Widely used in market research and new product design

Can collect opinions of proposed development or views on current practice 

Would need multiple groups as single group may not be representative

When to use:

- Collecting requirements

- In design process for collecting opinions on logos etc

 

When not to use:

- for reliable detailed usability data

 

Strengths: 

- synergy among groups (rich discussions)

 

Weaknesses:

- depends on the moderator

- may depend on the group

 

Focus groups:

- Good way to generate user requirements

- Don't rely on it to give reliable data on interface usability at a detailed level

 

 

Query Techniques: Interviews/Questionnaires:

Interviews:

- Structured interview (questions developed beforehand): easy to carry out but limited rsponses to the questions

- Semi-structured interview (prepared questions but random topics also fine: data obtained is good but more demanding for the interviewer

- Unstructured interview: when there is no little or background information available

 

 

Questionnaires:

Good when large number of people to be surveyed

Difficult to design an effective questionnaire

 

 

Ethical Issues

Participants should give consent 

Participants should be fully informed about the aims and methods of the study

Any personal data collected should be with permission and should be used for the current study only

For focus groups:

- avoid pressuring participants to speak

- anonymize data