MTG1023

HUMAN COMPUTER INTERACTION

Exercise for Chapter 5 : Design Process

MUHAMMAD ZULHAZRI BIN MAHMUD
D20101038716
MOHAMAD FADHIL BIN CHE MUSA
D20101039402

Group: A
Lecturer: Puan Nur Saadah Binti Fathil

1.
 SUCCESSFUL USER INTERFACES

User Guidelines User-interface Expert

Interface Documents Software Reviews
Requirements & Tools &
Process Usability
Testing

Ethnographic Theories Algorithms Controlled

Observation &Models &Prototypes Experiments

Description

First pillar : User interface Requirements

- Soliciting and clearly- to success in any development activity.
- To elicit and reach agreement- differ across organizations and
industries.
- Laying out-overall requirements development and management
process.
- System requirement- clearly stated, specified and agreed upon.
- Success or failure of software- depends on precision and
completeness of the understanding.
- Succesful method- ethnographic observation, monitoring the context
and environment of real users in action.
Second pillar: Guidelines Documents and Processes
User interface architect-generate, require other people to generate, a set
of working guidelines.
- Example:Microsoft’s Window Vista User Experience Guidelines
(provide a good starting point and an educational experience).
- Guidelines should considered:
• Words, icons, and graphics
• Screen-layout issues
• Input and output devices
• Action sequences
• Training
- Provide a social process- help it gain visibility and built support.
- Promotes consistency and completeness.
- Procedures should established- ensure enforcement, allow
exemptions.
- Must living text- to changing needs and refined through experience.
- Three level (Acceptance):
• Rigid standards
• Accepted practices
• Flexible guidelines
- “Four Es”- creating a living document:
• Education
• Enforcement
• Exemption
• Enhancement

Third pillar: User-interface Software tools

- In designing interactive systems- customers and users may not
have a clear idea.
- Users may not realize the implications of design decisions.
- Difficult, costly, and time-consuming.
 - Early stage- customers an users can be given a realistic impression
of what the final system will look like
- Prototypes developed simple drawing or word-processing tools
- Examples:
• PowerPoint slide shows and other animation.
• Flash is a multimedia authoring and delivery platform for
embedded web content.
• Ajax is a combination of technologies for interactive web pages.
- Evaluate tool capabilities, ease of use, ease to learn, cost, and
performance.

Fourth pillar: Experts Reviews and Usability Testing

- Extensive rehearals and previews for critics- ensure a successful
opening night.
- Example:
• Aircraft designers- carry out wind- tunnel tests, build plywood
mock-ups of the cabin layout, construct complete simulations of
the cockpit-- thoroughly flight-test the first prototype.
- Expert review methods- tests with the intended users, surveys, and
automated analysis tools are proving to be valuable.
- Procedure vary greatly- goals of the usability study, number of
expected users, dangers of erros, and level of invesment
2.
Items Ethnographic Participatory Scenario Social Impact
Observation Design Development Statement for
Early Design
Review

Method
Join work or More user Druin’s model
home Involvement Construtive
environments brings more Some critism and
to listen and accurate scenario take guidelines for
observe information a further step design could be
carefully, and helpful in
about tasks .
sometimes procedure reversing the
stepping videotapes to long history of
forward to ask convey their incorrect credit
questions and intentions histories,
participate in dislocation
activities. Other through de-
scenarios is skiling or layoffs,
User- interface describe how and deaths from
designers gain users explore flawed medical
insight into a system, instruments.
individual such as
behavior and optimistic Address
the vision concerns and
organizational potential barriers

Ethnographic Outline the

methods have development
been applied to process
office work, air
traffic control
and other
domains

User involve All of users Diverse users, Users and internal or

ranging from managers external software
children to older developers,
adults.

Goals To obtain the To direct Can represent To influence the

necessary data to involvement of Common or project schedule,
influence interface people in the emergency system
redesign collaborative situations with requiredments,
design of the both novice and
things . experts users.
Benefit Can increase Preventing
trustworthiness problem that
and credibility could be
expensive to
repair, and
creating more
satisfying work
environments.

Disadvantage Generate
antagonism from
People who are
not involved or
whose
suggestions are
rejected .