Mangilinan, Aizen Louise V.

​ ​ ​ ​ ​ ​ ​ ​ April 24, 2020

BSIT 1-1 ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ Ms, Meneses

Human Computer Interaction

Week 11 – Interaction Design

With the given source and learning tool, I learned that Interaction design is a process in
which designers focus on creating engaging web interfaces with logical and thought out behaviors and
actions. Successful interactive design uses technology and principles of good communication to create
desired user experiences. Here are concepts that are applied in creating an Interaction Design:

❖​ Goal-driven design: Why does your site or interaction exist? Figure it out and make sure your
application does this one thing exceptionally well.
❖​ Interface as magic: You don’t even really see the best interfaces. “The best interaction
designs don’t exist: they don’t take a long time to load/respond; they don’t make users think;
and they don’t give user’s cause for grief.”
❖​ Usability: “Interfaces which make the state of the underlying system easy to understand and use
are favored.”
❖​ Affordances: “The best (industrial/interaction) designs are those that speak for themselves; in
which, as the saying goes, form follows function.”
❖​ Learnability: “A great deal of what comprises a usable interface is made up of familiar
components. … The best interaction designers don’t reinvent the wheel every time a similar
design challenge comes. Rather, they call upon a set of patterns.”

Week 12 – To understand the structure of the design process and its effectiveness

Human–computer interaction is a specialty in many fields, and is therefore

multidisciplinary, but it has an intrinsic relationship as a subfield to computer science. Most interactive
computing systems are for some human purpose and interact with humans in human contexts.

The notion that computer science is the study of algorithms has virtue as an attempt to
bring foundational rigor, but can lead to ignoring constraints foundational to the design of successful
interactive computer systems. A lesson repeatedly learned in engineering is that a major source of failure
is the narrow optimization of a design that does not take sufficient account of contextual factors factors.
Human users and their contexts are major components of the design problem that cannot be wished
away simply because they are complex to address. In fact, that largest part of program code in most
interactive systems deals with user interaction. Inadequate attention to users and task context not only
leads to bad user interfaces, it puts entire systems at risk.

Week 13 – To understand the maximum usability of the interactive design

 According to the given resource, usability means that the extent to which a product can
be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a
specified context of use.

I learned that a usable interface has three main outcomes:

1.​ It should be easy for the user to become familiar with and competent in using the user interface
during the first contact with the website. For example, if a travel agent’s website is a
well-designed one, the user should be able to move through the sequence of actions to book a
ticket quickly.
2.​ It should be easy for users to achieve their objective through using the website. If a user has the
goal of booking a flight, a good design will guide him/her through the easiest process to
purchase that ticket.
3.​ It should be easy to recall the user interface and how to use it on subsequent visits. So, a good
design on the travel agent’s site means the user should learn from the first time and book a
second ticket just as easily.

Week 14 – To understand the programming support that for the implementation of an interactive system

❖​ Programming tools for interactive systems provide a means of effectively translating abstract
designs and usability principles into an executable form. These tools provide different levels of
services for the programmer.
❖​ Windowing systems are a central environment for both the programmer and user of an
interactive system, allowing a single workstation to support separate user-system threads of
action simultaneously.
❖​ Interaction toolkits abstract away from the physical separation of input and output devices,
allowing the programmer to describe behaviors of objects at a level similar to how the user
perceives them.
❖​ User interface management systems are the final level of programming support tools, allowing
the designer and programmer to control the relationship between the presentation objects of a
toolkit with their functional semantics in the actual application.

Week 15 - To assess the design and test the system to ensure that it meets the requirements

The ability of a system design to meet operational, functional, and system requirements
is necessary to accomplishing a system's ultimate goal of satisfying mission objective. One way to assess
the design's ability to meet the system requirements is through requirements traceability, the process of
creating and understanding the bidirectional linkage among requirements, organizational goals, and
solutions.
 Here are things that should be considered in order to assess the design and to ensure it
meets the requirements:

❖​ Importance of documentation and team commitment.

❖​ Importance of documented and validated findings.

Week 16 - To understand the principle and universal design for support

The 7 Principles of Universal Design were developed in 1997 by a working group of

architects, product designers, engineers and environmental design researchers, led by the late Ronald
Mace in the North Carolina State University. The purpose of the Principles is to guide the design of
environments, products and communications. According to the Center for Universal Design in NCSU, the
Principles "may be applied to evaluate existing designs, guide the design process and educate both
designers and consumers about the characteristics of more usable products and environments." ​

❖​ Principle 1: Equitable Use

❖​ Principle 2: Flexibility in Use

❖​ Principle 3: Simple and Intuitive Use

❖​ Principle 4: Perceptible Information

❖​ Principle 5: Tolerance for Error

❖​ Principle 6: Low Physical Effort

❖​ Principle 7: Size and Space for Approach and Use

Week 17 - To understand the different requirements for support at different times

Users require different types of support at different times.

• Basic requirements

– available but unobtrusive

– accurate and robust

– consistent and flexible

• Design of user support must take account of:

– presentation issues

– implementation issues