How to Gather Requirements for a New Computer System

Human-computer Interaction takes certain steps to ensure news systems will integrate appropriately with the host and users. To do this, it is necessary to work with end users to determine appropriate requirements. In one example, we may decide to create a new e-mail system for a university. Some of the key process steps and actions are outlined below.

Because the implementation of a new e-mail system will affect a large group of users, some users will be directly involved in the design process, while others will simply receive training and instructions for system use. The group directly involved will be involved in data-gathering techniques like interviews and questionnaires in addition to actually testing the new system. The feedback on the usability and functionality of the e-mail system will determine if it is ready for implementation. These users may also be used in an effort to train or help with questions on learning the new system for all users.

As mentioned above, preparation for implementation involves certain steps pertaining to the sample user group as well as the whole.

Action: Select appropriate sample user group for data gathering and feedback.

Objective: The objective is to select those users with certain attributes that will accurately represent the users as a whole for his new e-mail system. Users may be selected for frequency of use of e-mail, previous experience, age, education or other characteristics. Selecting the appropriate users will lead to efficient design because the feedback will represent the users' needs.

Action: Produce prototype of functioning e-mail system and allow users to test functionality and usability.

Objective: Here the sample group of users gets their first interaction/look at what the new system will be like. It is important to allow for this hands-on approach before full implementation because it provides final feedback. Users can comment on how accurately the system meets their needs and prior recommendations.

Action: Train specific users on use of the system.

Objective: While it is not feasible to train an entire user group on how to use the new system, it is often beneficial to select certain individuals who will serve to help train the remaining whole. In the case of a "learn on your own" product, these trainers are not necessary. If successful, transition to the new system will go smoothly.

Action: Create training manuals, instructions and any other necessary material to help users learn the new system.

Objective: With any new system, learnability is a key concept. Users must be able to quickly understand and interact with the new system. A successful set of instructions will have the user familiar with a new system in limited time and use.