You are on page 1of 3

WIF2002 SRE - Tutorial 3

Part 1: Answer all questions

1. The Kano model describes that dissatisfiers (basic factors) are hard to find. What is the
best elicitation technique for dissatisfiers? (1 answer)
a. Interview
b. Questionnaire
c. Field observation
d. Low-fidelity prototyping
e. Brainstorming

2. Which two aspects have to be most likely taken into consideration in the choice of
suitable elicitation techniques for a product data management software system? (2
answers)
a. Availability of the stakeholders
b. Age of the stakeholders
c. Project deadlines and budget
d. Tools applied
e. Business the system is to be applied in

3. What are the two key advantages of using questionnaires for requirements elicitation? (2
answers)
a. A high number of participants are possible.
b. Statistically relevant statements on requirements can be made.
c. Questionnaires allow for validating the participants‘ understanding.
d. Questionnaires provide insights on delighters (excitement factors).
e. Questionnaires provide insights on dissatisfiers (basic factors).

4. You have to elicit requirements for a sales software that shall operate worldwide. In the
initial elicitation of requirements, participants from all 30 branches should be involved.
Project management has decided that for the documentation of the initial requirements a
wiki system is to be used. Which of the following statements is most likely correct? (1
answer)

Remark: A wiki system is a web-based system that allows several people to work on one
document collaboratively. The respective revisions are visible for all people involved. A
prominent example of a wiki system is the online encyclopedia Wikipedia.
a. The approach makes no sense as a wiki system is no requirements management tool.
b. The approach makes sense as all people involved can collaboratively write down and
comment on the initial requirements.
c. The approach makes no sense as the initial requirements analysis has to be performed
by a requirements engineer in form of interviews.
d. The approach makes sense as wiki systems provides a history (of the modifications
made).

Part 2: Open-ended Questions


WIF2002 SRE - Tutorial 3

5. A big regional railway company with 70 railway stations must get a new communication device for railway
station workers. Name three investigation techniques that are suitable to be used for the requirements
elicitation and explain why the techniques are selected.

Part 3: Sources of Requirements

Identify the elicitation techniques that are mentioned in the process description. Classify each
technique into one of the five types of requirements elicitation techniques.

Use the following table to document the requirements sources and corresponding types. Please also refer to
lines in the process description, in which requirements sources and elicitation techniques are mentioned, in
order to keep the traceability to the text.

No Elicitation Technique Elicitation Technique type Line Reference


.
1

2

WIF2002 SRE - Tutorial 3

A new information system shall be installed at University of Malaya to improve the course registration
process. Brian heads a team of requirements engineers (Brian, May, Michael, Lee, Alice and Chris)
responsible for specifying the requirements of the new system. They started the requirements engineering
process in Faculty of Computer Science and Information Technology (FCSIT).

May is assigned the task of conducting a workshop that involves ten representative students from
different departments. The workshop starts with a brainstorming session to uncover and collect an initial set of
goals for the new system. Next, the ten students are asked to discuss what they do not want in the new
system. Besides conducting the workshop, May also designs a questionnaire and distributed the
questionnaire to collect the feedback from lecturers and students regarding what they have in mind in the new
system.

Michael is in charge to interview a few experienced lecturers as representative of this user group. He
records audio for all the interview sessions. One of the lecturer mentioned that University of Malaya has a
legacy system called “UMPortal”. This system has some limitations in supporting the course registration
process. Martin informed Brian about this legacy system that he found. The registrar in the faculty offers to
demonstrate how registrars and students actually use “UMPortal” in the course registration. On site, Michael
observes how the registrar and students use the existing system to register the courses.

Alice received a copy of the UMPortal user manual, which includes detailed descriptions of the
functionalities of the system. She is assigned to analyse this user manual to find out the core user functions,
the databases, software and hardware specifications involved in this system. She documents all the basic
functionalities supported by UMPortal.

Brian receives an email from the Dean of the FCSIT. He has a clear vision about the tasks and goals
of the new course registration system. Additionally, Brian also received responses from the legal unit that
pointed out that the new system must compliance with Malaysia Personal Data Protection Act.

A few weeks later, Brian, Lee and Chris organised a brainstorming and invite a group of lecturers,
students, administrative officers to join the discussion. During the brainstorming session, they applied the
technique of the Six Thinking Hats to take different new viewpoints from the participants about the new
functionalities for the system. They record video for the brainstorming session.

You might also like