When an application doesn’t work or crashes
When an application doesn’t do what the user wants it to do
When users’ expectations are not met
When an application does not provide sufficient information to let the user know
what to do
When error messages pop up that are vague or condemning
When the appearance of an interface is too noisy, gimmicky or patronizing
Section B
[37 Marks]
Question 1. Elaborate on five (5) types of non-functional requirements. Provide an example
for each.
[15 Marks]
2 Marks each, 1 mark for each example.
Sample solution
Functional requirements — capture what the product should do.
Data requirements — capture the type, volatility, size/amount and value of the
required data.
Environmental requirement or context of use — circumstances in which the
interactive product will be expected to operate.
User Requirements — capture the characteristics of the intended user groups.
Usability requirements — usability goals and associated measures for a particular
product.
Question 2. Once the data gathering session has been conducted, interpretation and analysis
can begin. Answer the questions that follow regarding data interpretation and analysis.
a. What is the aim of data interpretations?
[2 Marks]
Sample answer
To begin structuring and recording descriptions of requirements
. Elaborate of the two (2) task description flavors. Provide an example for each.
[6 Marks]
3 marks each; 1 mark for naming, 1 mark for elaboration
Sample answer
Scenarios
Informal narrative description. This describes human activities or tasks in a story
that allows exploration and discussion of contexts, needs, and requirements.
Use cases
Focus on user goals, but emphasize on user-system interaction rather than user’s
task itself.
For what purpose are task analysis techniques used for?
[2 Marks]
Sample answer
They help to investigate existing systems and current practices.