Question 1: What are the requirement of HCI design, explain each of the following.
1. Functional and Non-Functional Requirement
2. Environment or context of use:
3. Organizational requirements
4. User requirements
5. Usability requirements
Functional Requirements:
The product shall be user friendly
The web application shall be easy to navigate with clear links to information
It shall be clear and concise
It shall afford safety and security for those customers that are doing transactions
Information shall be legible and concise
The services must be available 24/7
The web application shall be able to produce weekly, monthly and yearly reports about tax transactions
such as traffic ticket payment.
Non-Functional requirements
The web application shall be easy to use by all employees including sales representatives and managers
The web application shall be available in at least two languages
The web application shall allow several transactions to be made at the same time without downgrading
performance
Environment or context of use requirements
– Physical: dusty? Noisy? Vibration? Light? Heat?
Humidity? …. (E.g. ATM)
– Social: sharing of files, of displays, in paper, across
Great distances, work individually, privacy for clients
– Organizational: hierarchy, IT department’s attitude and
Remit, user support, communications structure and
Infrastructure, availability of training
User requirements
Users: Who are they?
– Characteristics: ability, background,
Attitude to computers
• System use: novice, expert, casual, frequent
– Novice: step-by-step (prompted), constrained, clear
Information
– Expert: flexibility, access/power
– Frequent: short cuts
– Casual/infrequent: clear instructions, e.g. menu paths
Organizational requirements
There are several organizational issues that affect the acceptance of technology by users and that must
therefore be considered in system design:
Systems may not take into account conflict and power relationships
Those who benefit may not do the work
Not everyone may use systems.
In addition to generic issues, designers must identify specific stakeholder requirements within their
organizational context.
Socio-technical models capture both human and technical requirements.
Soft systems methodology takes a broader view of human and organizational issues.
Participatory design includes the user directly in the design process.
Ethnographic methods study users in context, attempting to take an unbiased perspective.
•Usability requirements
Learnability, throughput, flexibility,
Attitude
User requirements and usability
Requirements refer to different things:
Property of the object (usability) property
Of the user (user)
Question 2: Define GUI-Graphical User Interface, and Importance of GUI
GUI-Graphical User Interface
The graphical user interface, developed in the late 1970s by the Xerox Palo Alto research laboratory and
deployed commercially in Apple’s Macintosh and Microsoft’s Windows operating systems, was designed
as a response to the problem of inefficient usability in early, text-based command-line interfaces for the
average user.
Graphical user interfaces would become the standard of user-centered design in software application
programming, providing users the capability to intuitively operate computers and other electronic
devices through the direct manipulation of graphical icons such as buttons, scroll bars, windows, tabs,
menus, cursors, and the mouse pointing device. Many modern graphical user interfaces feature
touchscreen and voice-command interaction capabilities.
He term "User Interface" refers to the methods and devices that are used to accommodate interaction
between machines and the human beings, users, who use them. User interfaces can take on many
forms, but always accomplish two fundamental tasks: communicating information from the product to
the user, and communicating information from the user to the product.
Importance of GUI
The term “Graphical user interface” (GUI) is the layer where the digital product communicated with
human and human communicated with digital product. A well-designed product can fail with an
unsuccessful interface. Conversely, a product has not good design values can become successful with its
well-designed interface. To get best interaction between digital product and user, the graphical interface
design itself needs to have some design values and requires a systematic approach to the design
process. But, to ensure optimum performance, it also requires a model of interaction to understand
exactly what is going on in the interaction and identify the likely root of difficulties.
To achieve the successful interaction of user and product, there are some principles that should be in
consider (Shneiderman, 1987). The main purpose of this research is to provide a guide for well-designed
digital product by giving some fundamentals about graphical user interface.