HCI Chapter 5
HCI Chapter 5
14
Software process models:
The waterfall model
Requirements
Requirements
specification
specification
Architectural
Architectural
design
design
Detailed
Detailed
design
design
Coding
Coding and
and
unit
unit testing
testing
Integration
Integration
and
and testing
testing
Operation
Operation and
and
maintenance
maintenance
15
• The waterfall model: takes the fundamental process activities of specification,
development, validation, and evolution and
• Represents them as separate process phases such as requirements specification,
software design, implementation, testing, and so on
• It is a sequential design process, in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases
• Each phase must be completed before the next phase can begin and there is no
overlapping in the phases
• It is applicable for well-defined requirements
The life cycle for interactive
systems
Requirements
Requirements
specification
specification
Architectural
cannot assume a linear
Architectural
design
design sequence of activities
as in the waterfall model
Detailed
Detailed
design
design
Coding
Coding and
and
unit
unit testing
testing
Integration
Integration
and
and testing
testing
Requirements
Requirements
specification
Requirements:
specification
focus on all
Architectural
Architectural
Interaction
Interaction stakeholders and
and
and Interface
Interface
design
design Design
Design
their need
18
Another aspects of
interactive design
1. USER FOCUS
• The start of any interaction design exercise must be the intended
user or users. This is often stated as:
• know your users
• The designer should consider the human factors
• The cognitive process
• How the user perceive your system?
• how do you get to know your users?
• Cognition includes basic mental processes such as sensation, attention, and
perception. Cognition also includes complex mental operations such as memory,
learning, language use, problem solving, decision making, reasoning, and
intelligence.
• Who are they?
• The first thing to find out is who your users are.
• Are they young or old, experienced computer users or beginners?
• This question becomes harder to answer if you are designing generic
software, such as a word processor, as there are many different users with
different purposes and characteristics.
• Probably not like you!
• When designing a system, it is easy to design it as if you were the main
user: you assume your own interests and abilities.
• So often you hear a designer say ‘but it’s understandable what to do’.
• “develop as per your user specification not as per your need”
• Talk to them
• It is hard to get yourself inside someone else’s head, so the best thing is usually
to ask them.
• This can take many forms: structured interviews about their job or life, open-
ended discussions, or bringing the potential users fully into the design process.
• Although what people tell you is of the most importance, it is not the whole
story.
• The last of these is called participatory design.
• Watch them
• Watch what people do? Their difficulties,
• Your observation will tell you everything.
• Because of this it is important to watch what people do as well as hear what
they say.
• This may involve sitting and taking notes of how they spend a day, watching
particular activities, using a video camera or tape recorder.
2. Scenarios
• Scenarios are stories for design
• A scenario is a description of a person’s interaction with a system.
• Scenarios may be related to ‘use cases’, which describe interactions
at a technical level.
• Unlike use cases, however, scenarios can be understood by people
who do not have any technical background.
• Scenarios are a resource that can be used and reused throughout the
design process:
• helping us see what is wanted, suggesting how users will deal with the
potential design, checking that proposed implementations will work, and
generating test cases for final evaluation.
3. Navigation
• It is the process of navigating a system , an application or a
website using a dialog box, widgets, hypertexts ….which is
one of the most important aspects of a website.
• Widgets: an element of a graphical user interface
(GUI) that displays information or provides a specific way for
a user to interact with the operating system or an application.
• Screens or windows: you need to find things on the screen,
understand the logical grouping of buttons.
• Navigation within the application : You need to be able to
understand what will happen when a button is pressed, to
understand where you are in the interaction.
• Generally
• The platform for human-computer interaction is offered by
UI.
• There can be different forms of UI.
• On the basis of combination of the hardware and the
software, UI can take any of the forms such as audio based,
text-based, it can be graphical form.
• The following features of the user interface enables to
increase the popularity of the system.
• Attractive
• Simple to use
• Responsive in short time
• Clear to understand
• Consistent on all interfacing screens
Thank you!