Sammie Qadri

Fi2979

HCI Assignment 1
Problem 1:
Children:
Use vibrant and colorful layouts to retain the attention.
Big buttons so children can reach them and press them easily.
Maybe more leniency on sensitivity area for said buttons
Simpler vocabulary
Elderly:
High contrast and big font size with simple fonts.
Big buttons with small learning curve in order to use/get a hang of
Little amount of typing for forms
Colorblind:
Different filters for pages that can apply to different types of colorblindness.
Use colors in the same family so as to not confuse and lead colorblind persons
astray. Ex: blue and green and red, use just blues or just greens.
Use Color Oracle to see simulate how colorblind persons see and change color
design in accordance with view.
Dont use color.
Problem 2:
Japan:
Big percentage of users are young adults or teenagers
o Tending to use their cellular phones with fast 3G and 4G to browse web, play
games, music, etc..
o Decent majority of population consists of elderly persons
o Culturally, less direct with information
o More formal:
Call you by last name
Last name, first name
Ex: Qadri Sammie
Ex: Monkey D. Luffy.
Use of honorifics
San, chan, sama, kun

Problem 3:
When it comes to attracting attention:
Use of color
Big flashy text
Popup

Problem 4:
8 Golden Rules of Interface Design

Sammie Qadri
Fi2979
Strive for Consistency
o Easily violated. Try hard to be consistent unless it definitely needs to be
broken, i.e. password echoing. Identical layout, identical code usage for
similar sections.
Cater to Universal Usability
o Design for ultimate plasticity so that your design can be used by many
different types of people. Children friendly, Elderly friendly, disabled
friendly
Offer Informative Feedback
o Provide comments or notes or popups when need be. Like when youre
telling them their password is wrong.
Design Dialogues to yield closure
o Actions should have beginning middle and end. Basically acyclic as opposed
to cyclic actions or networks.
o Ex: Food ordering on a website that takes you to check out and ends with
confirmation page.
Prevent Errors
o UI should be made in a way so that accidentally choosing the wrong choice
or a choice that will cause an error are prevented.
o Ex: Get zip code and use to set their State and City from trusted database.
As opposed to having to rewrite it and possibly get it wrong.
Permit Easy Reversal of Actions
o Actions should be reversible just in case an error is made. Avoid giving the
user an anxiety attack.
o Ex: Adding a review info page before confirming and sending information
so that they can check it and edit it if need be.
Support Internal Locus of Control
o Make user feel like they are in charge of whatever theyre operating or using.
Reduce Short-Term Memory Load
o
People can
remember
seven plus or
minus two
pieces of info,
so
make sure that
all
syntax and
important info is
in
that ballpark!

Problem 5

Sammie Qadri
Fi2979

1. User-interface Requirements
a. Using ethnographic observations to conclude what functions are done best
by computers as opposed to humans in HCI.
2. Guidelines Documents and Process
a. Set of guidelines for the processes, design principles, I/O devices, actions
that the system can perform, and a training tutorial section.
b. Education How to get it?
c. Enforcement Who review?
d. Exemption Who decides?
e. Enhancement How often?
3. User-interface Software Tools
a. Essentially C#, C++, Java SDK, and the likes that programmers can use to
create user-interfaces.
4. Expert Reviews and Usability Testing
a. Pilot tests of sites and programs designed for customers.
b. Getting experts to run through every day scenarios using the site or program
to see if there are mistakes or flaws.

Problem 6
a. Contexual InquiryWatch the check in process. Get some interview with
everyone in charge or part of the check in team. Reception desk personnel,
security personnel, guest check in personnel, emergency check in, reception in
ICU, reception in emergency room, etc.
b. Persona DevelopmentGo through and begin designing fictional personas for
the different types of people coming to check in. This may include handicapped
adults with hard time walking, worried parents with a sick child with varying
sickness, injured personnel with varying injury, elderly persons requiring help
getting to and from room, EMT carried personnel with high level of injury, and
others. Using this variety of personas helps understand the needs of the
prototype.
c. StoryboardingExample below, but essentially list and storyboard all steps that
a user will take to be checked in. Ex: Potential patient walks into hospital to be
checked in -> At quick check in machine, types in all necessary information with
brief explanation of reason for visit. -> Using a scale to calculate where patient
needs to be based on risk, he is forwarded to a waiting nurse from that specific
section or area (ICUcardiology, stomach, brain, etcemergency, etc) ->
Nurse prints tag and places it on patients wrist and puts them in a bed and has

Sammie Qadri
Fi2979
doc come in after taking and noting all vitals.

d. User Environment DesignCreate a kiosk that ties in to Hospital database to

quickly check in new users, frequent users/visitors, etc. Using the storyboard as
a starting point, create a GUI usable by all. ALWAYS have a button for quickly
calling a nurse for emergency or aid if too confusing or status worsens. Add
network tie ins with every department at the Hospital so information is
forwarded quickly and correctly.
e. Interviews and Evaluations with Paper Prototypes and Mock upsGet expert
reviewers to check the kiosks for usability as different types of users.
Afterwards, make a few kiosks and install them in a hospital as optional
attempts to check in and use alpha testers to see how efficient and well they
work. Use the data from these trials to make it better as a beta version and
them look towards finally exporting it out to the consumer market.

Problem 7
Cognitive Walkthroughs
Expert reviewers do ordinary tasks that any user would do to see if there is
anything that is confusing, problematic, or cluttery.
Consistency Inspection
Reviewers check the whole system to confirm that fonts, colors, language, layout,
images, etc. are consistent throughout the system.
Heuristic Evaluation
Reviewers examine the system to see if it goes against any of the design
heuristics.
Eight golden rules

Problem 8
Expert reviews are useful
Some of these methods do not take much time or manpower. One being the
heuristic evaluation.

Sammie Qadri
Fi2979
Similar to an alpha or beta test, allowing the designer to get some feedback on
layout and any problems there may be before publishing the work to the public
Very cheap
Expert reviews have drawbacks
Some review methods take tons of time like the formal usability inspection. These
methods also miss some key points by being narrow visioned.
Opinions. So theyre biased and just opinions. Even if they are expert opinions