human computer interaction introduction

1. I)There are various ways to categorize stakeholders based on their roles and responsibilities in the system.
Some possible categorizations include:
1. User Type: Stakeholders can be classified based on their usage of the system. For example,
primary users are those who interact with the system regularly, while secondary users may only
access it occasionally. Other user types may include power users, casual users, and
administrators.
2. Organizational Level: Stakeholders can be categorized based on their position in the
organizational hierarchy. For example, management level stakeholders may have a strategic role
in the system's development and implementation, while front-line workers may have a more
tactical role.
3. Technical Expertise: Stakeholders can also be categorized based on their technical knowledge and
skills. For example, IT staff and system analysts may have a more specialized technical role in the
system's development and maintenance.
4. Stakeholder Interest: Finally, stakeholders can be categorized based on their level of interest or
involvement in the system. For example, stakeholders with a high level of interest may include
investors, customers, or regulatory bodies that have a significant impact on the system's success.
Overall, categorizing stakeholders can help to identify their needs and expectations for the system, which
can inform the system's design and development.
II)
1. User Interface Requirements: These requirements define the interactions between the system and
its users. They include things like the layout of the user interface, the types of input and output
devices that can be used, and the accessibility features that need to be included.
2. Hardware Interface Requirements: These requirements define the interactions between the system
and the hardware it will be running on. They include things like the minimum hardware
specifications needed to run the system, the types of peripherals that can be used, and any
compatibility requirements.
3. Software Interface Requirements: These requirements define the interactions between the system
and any other software it needs to interface with. They include things like the operating system
requirements, the programming languages and libraries that can be used, and any compatibility
requirements.
4. Communication Interface Requirements: These requirements define the interactions between the
system and any other systems it needs to communicate with. They include things like the
protocols and data formats that need to be used for communication, the network topology and
bandwidth requirements, and any security or encryption requirements.

2. B)
1. Interviews: Conducting one-on-one interviews with potential users of the system can
provide valuable insights into their needs, preferences, and expectations for the interface.
Interviews can be conducted in-person or remotely, and can be structured or unstructured
depending on the goals of the research.
2. Surveys: Surveys can be used to gather input from a large number of potential users.
Surveys can be distributed online or in-person and can be used to gather quantitative and
qualitative data about user preferences and needs.
3. Focus groups: Focus groups bring together a small group of potential users to discuss the
interface design and provide feedback. Focus groups can be used to identify common
themes and issues that need to be addressed in the design process.
4. User testing: User testing involves testing the interface with real users to identify
usability issues and gather feedback on how the interface can be improved. User testing
can be conducted in a lab or in the field, depending on the goals of the research.
5. Prototyping: Prototyping involves creating early versions of the interface to gather
feedback from users. This approach can help to identify potential issues early in the
design process and provide a more iterative and user-centered approach to interface
design.
Overall, gathering requirements from users about a new system interface requires a user-centered
approach that involves engaging users throughout the design and development process. By using
a combination of techniques like interviews, surveys, focus groups, user testing, and prototyping,
designers can ensure that the interface meets the needs and expectations of its users.

3. C)
Yahoo and Google are two of the most popular search engines on the internet, and they have
distinctive characteristics that set them apart from each other. Here are the desirable
characteristics that differentiate them:
Yahoo:
1. Personalization: Yahoo's homepage allows users to personalize their content by selecting
topics that interest them, such as news, finance, sports, and entertainment.
2. Content-rich: Yahoo's homepage is content-rich, featuring news articles, videos, images,
and links to other sites.
3. Integrated services: Yahoo offers a range of integrated services, such as Yahoo Mail,
Yahoo Finance, Yahoo News, and Yahoo Sports, which can all be accessed from the
homepage.
4. Advertising: Yahoo's homepage features a variety of advertising, including display ads
and sponsored content.
5. Trending topics: Yahoo's homepage features a section dedicated to trending topics, which
highlights the most popular searches and news stories.
Google:
1. Simplicity: Google's homepage is famously simple, with a clean design and a focus on
the search box.
2. Speed: Google's homepage is fast to load and search results are delivered quickly.
3. Accuracy: Google's search engine is known for its accuracy and relevance, delivering
high-quality results based on the user's query.
4. Mobile-friendly: Google's homepage is optimized for mobile devices, with a responsive
design that adapts to different screen sizes.
5. Minimal advertising: Google's homepage features minimal advertising, with only a few
discreet ads placed at the top and bottom of the page.
Overall, Yahoo's homepage emphasizes content and personalization, while Google's homepage
focuses on simplicity, speed, and accuracy. These characteristics reflect the different approaches
and priorities of the two search engines, and they appeal to different audiences and use cases.

4. D)
1. Menu-based: This dialogue style presents a list of options to the user, and the user selects
an option by clicking on it. The options are displayed vertically, and the selected option is
highlighted.
2. Command Line: This dialogue style requires the user to type in a command or a keyword.
The system then interprets the command and performs the requested action.
3. Form fill-in: This dialogue style presents a set of fields to the user, and the user fills in the
required information. The user can navigate between fields using the mouse or the tab
key.
4. Natural language: This dialogue style allows the user to interact with the system using
natural language. The system interprets the user's input and responds accordingly.
f) In terms of Norman's principles, the form seems to be well-designed.
1. Visibility: The dialogue styles used in the form are all clearly visible to the user. The user
can easily see the available options, the command line, the form fields, and the natural
language input box.
2. Feedback: The system provides feedback to the user in different ways, depending on the
dialogue style used. For example, when the user selects an option from the menu, the
selected option is highlighted. When the user types a command, the system responds with
an appropriate message. When the user fills in a field, the system displays the entered
value.
3. Mapping: The dialogue styles used in the form are all familiar to most users. The menu-
based and form fill-in styles, in particular, are commonly used in many applications. The
natural language style may require some learning, but it is becoming more popular in
modern interfaces.
4. Constraints: The form provides constraints in different ways. For example, the menu-
based dialogue style restricts the user to select only from the available options. The form
fill-in style may provide constraints on the type of data that can be entered in each field.
The natural language style may provide suggestions or corrections to the user's input.
5. Consistency: The dialogue styles used in the form are consistent with each other and with
common user expectations. For example, the menu-based dialogue style uses a vertical
list of options, which is a common convention. The form fill-in style uses standard form
field labels, such as "First Name" and "Last Name". The natural language style follows
common language conventions, such as subject-verb agreement and basic syntax.