2HCEYE

Developing a system requires initial research, which must be conducted thoroughly from a user perspective. In order to optimize the interaction between the system and the user, it is necessary to know the user needs and characteristics, usage context, preceding systems and the competitive system aspects(Center for Usability Research and Engineering, n.d.). For an interactive software or application that focuses on user experience, it is important to consider and assess the functions that the user will activated directly through interaction and that are significant in understanding certain aspects of the user experience. Requirements analysis basically establishes the goal for the development of a system from the viewpoint of the target users.

• Requirement Analysis

• User Analysis

• Scenario and Tasking Model

• Interface Selection and Consolidation

This design process reinforces the original requirements analysis to satisfy potential system use more comprehensively. This also prioritizes user experience and usability standards. Its results will always reflect to the original requirements, which could identify supplementary user interface (UI) requirements.

• User Analysis

• Requirement Analysis

• Scenario and Task Modeling

• Interface Selection and Consolidation

This design process is the most important part of interaction modeling. It involves the identification of the application task structure and the sequential relationship between the different elements of the program or a system. Beginning with a simple task model, it is easier to draw a more detailed scenario of how the system would be utilized. With this, developers and designers can assess both the appropriateness of the system and the feasibility of the given requirements. The process of storyboarding can be used in scenario and task modeling, which allows designers to create a rough visual profile of the interface.

• Scenario and Task Modeling

• Requirement Analysis

• User Analysis

• Interface Selection and Consolidation

Software interface components (e.g., search fields and widgets), interaction techniques (e.g., voice and facial recognition), and hardware specifications (e.g., sensors and display monitors) will be made in this design process. Note that the chosen individual interface components need to be consolidated into a practical package because not all interface components may be available on a working platform (e.g., desktop and smartphone). However, adjustments can be made for numerous reasons besides platform requirement, such as constraints in budget, time, personnel, etc.

• Interface Selection and Consolidation

• Requirement Analysis

• User Analysis

• Scenario and Task Modeling

The design configuration of a hardware interaction platform greatly depends on the characteristics of the application that requires a certain operating environment. Different interaction and subtasks may require various individual devices.

• Hardware Platforms

• Software Interface Components

These are the integrated parts of a system or an application interface. These components are the means to break the complexity of a software by providing an easy interaction to the user. Sometimes, software interface components are referred to as user interface components.

• Software Interface Components

• Hardware Platforms

(GUI), which are windows, icons, menus, and mouse/pointer-based interactions. These are sometimes referred to as WIMP (windows, icon, menu, and pointer). WIMP interfaces have significantly contributed to the propagation of computer technologies.

• WIMP

• False

These provide the working area of an application, which pertains to the user interface. Modern computer interfaces are designed around windows, or the visual output channels and abstractions for individual computational processes. For a single application, several subtasks might be needed simultaneously and be interfaced consequently through multiple windows or layers. It is also possible to launch overlapping windows in modern computers. For devices with small display size, like mobile phones, nonoverlapping windows are used instead. Nevertheless, flipping through different applications are possible

• Windows/Layers

• Icons

• Menu

• Direct Interaction Through Pointer

These allow activations of commands and tasks through selection. These can be organized as a one-dimensional list or a two-dimensional array of items. Selection of a menu item involves three (3) subtasks: activating the menu, scanning the items, and selecting an item. Menus can also be presented in various styles and mechanisms like the pull-down, pop-up, application bar, 1D toolbar, and tabs. See Table 2 for the list of menu styles and their proper usage.

• Menu

• Windows/Layers

• Icon

• Direct Interaction Through Pointer

GUI Components for User Input – In considering the interactive interface options of an application, it is essential to understand the following representative GUI components for soliciting input from a user in a conventional manner:

• Text box, Tool bar, forms, Dialog box, Combo box

• False