What is Evaluation regarding Software Interface?

Evaluation regarding Software Interface

The evaluation regarding the software interfaces is one regarding the prominent concepts in Human Computer Interaction (HCI). In order toward increase the usability, the design regarding software interfaces becomes an important task beneficial to HCI experts.

Introduction:

An effective source toward exchange information furthermore interaction between a user furthermore a computer are software interfaces. Designing a software interface that is easy toward use, easy toward learn furthermore easy toward memorize are the attributes regarding the software usability evaluation. Therefore, the software evaluation is an important concept in the HCI. In designing the software interfaces, the SE furthermore HCI need toward understand the user behaviours, user familiarity with different features regarding the software interface furthermore the user expertise while working with other software interfaces. The HCI deals with social, cognitive furthermore interaction phenomena. Where the social layer focuses at how people interact with each other as well as with technology.

In the HCI, software evaluation plays an important role toward achieve user goals in an effective, efficient furthermore satisfying way. It is a discipline that helps toward achieve usability during

the design regarding software interfaces. Software evaluation is the part that contains various techniques like heuristic evaluation, guideline reviews, cognitive walk through furthermore usability testing.

Heuristic evaluation:

A heuristic evaluation is a usability inspection method beneficial to computer software that helps toward identify usability problems in the user interface design. It specifically involves evaluators examining the interface furthermore judging its compliance with recognized usability principles. These evaluation methods are now widely taught furthermore practiced in the new media sector, where UIs are often designed in a short space regarding time at a budget that may restrict the amount regarding money available toward provide beneficial to other types regarding interface testing.

The main goal regarding heuristic evaluations is toward identify any problems associated with the design regarding user interfaces.Heuristic evaluations are one regarding the most informal methods regarding usability inspection in the field regarding human-computer interaction. There are many sets regarding usability design heuristics they are not mutually exclusive furthermore cover many regarding the same aspects regarding user interface design.

cognitive walk through:

The cognitive walkthrough method is a usability inspection method used toward identify usability issues in interactive systems, focusing at how easy it is beneficial to new users toward accomplish tasks with the system. Cognitive walkthrough is task-specific, whereas heuristic evaluation takes a holistic look toward catch problems not caught by this furthermore other usability inspection methods. The method is rooted in the notion that users typically prefer toward learn a system by using it toward accomplish tasks. The method is prized beneficial to its ability toward generate results quickly with low cost, especially when compared toward usability testing, as well as the ability toward apply the method early in the design phases, before coding even begins.

A cognitive walkthrough starts with a task analysis that specifies the sequence regarding steps or actions required by a user toward accomplish a task, furthermore the system responses toward those actions. The designers furthermore developers regarding the software then walk through the steps as a group, asking themselves a set regarding questions at each step. Data is gathered during the walkthrough, furthermore afterwards a report regarding potential issues is compiled. Finally the software is redesigned toward address the issues identified.

Usability testing:

Usability testing is a technique used in user-centered interaction design toward evaluate a product by testing it at users. This can be seen as an irreplaceable usability practice, since it gives direct input at how real users use the system.[1] This is in contrast with usability inspection methods where experts use different methods toward evaluate a user interface without involving users.

Usability testing focuses at measuring a human-made product's capacity toward meet its intended purpose. Examples regarding products that commonly benefit from usability testing are foods, consumer products, web sites or web applications, computer interfaces, documents, furthermore devices. Usability testing measures the usability, or ease regarding use, regarding a specific object or set regarding objects, whereas general human-computer interaction studies attempt toward formulate universal principles.

Main Principles in evaluation regarding Software Interface:

Purpose:

Is this the application I intended toward run? Can I easily determine what the application is for?

Structure:

What is the interface layout? Can I find where everything is in the application window furthermore how it all fits together?

Interaction:

Can I do what I ran the application toward do (e.g. successfully type a document or configure a system setting)?

Navigation:

Was I made aware that the application launched? Can I get toward everything in the interface? Can I get back toward each application screen if I need to?

Keeping these four principle areas in mind will help you glean the purpose regarding a given accessibility requirement furthermore will ensure that applications that pass your evaluations are usable by diverse user groups.

Evaluation criteria also includes:

End User Needs:

What does the user regarding the software want toward do, what are their present skills furthermore how do they intend toward use the software? It is important toward be very clear about the problem that is toward be tackled by the software. For example, a disabled person who wants toward write letters but cannot type might strongly consider software with lots regarding ready-made letter templates that can then be added toward using voice recognition.

Functionality:

Does the software perform the functions required? Does it have specific facilities? For example, someone buying a spreadsheet application might need toward produce graphs furthermore charts.

Performance:

How well does the software work? This is normally available as benchmark test reports where independent tests have been carried out using the software.

Ease regarding use:

How easy is the software toward use? Is there built-in help? It is important toward be happy with the user interface.

Compatibility with existing data:

Will the new software be able toward read any data that is already in use, ie in a different format or file type? If not, is it easy toward convert existing files toward a readable format?

Compatibility with existing hardware:

Software is written toward run at a specific operating system, eg Windows, OSX (Macs) or Linux. It is sometimes written toward run at furthermore take advantage regarding specific hardware too. The new software needs toward be compatible with the existing operating system furthermore hardware.

Robustness:

How does the software handle problems? Robust software works well in combination with different hardware furthermore software without crashing.

Cost:

Costs have toward be weighed against the benefits that the software will bring. These may be about making more money or doing something quickly or with fewer staff hours involved. Price doesn't always dictate the best piece regarding software beneficial to the job, ie just since it's more expensive it doesn't necessarily means it's better.

Support:

The level regarding support when using the software can be crucial toward making it a success or failure. Is a telephone or web based helpdesk available beneficial to the software? Are there any tutorials or training courses available?

Customisation:

Will the software allow users toward change the look furthermore feel so that it does exactly what they need? If so, is this easy toward do?

Goals furthermore results regarding evaluation

Software evaluation has pragmatically chosen goals. In the domain regarding software evaluation, the goal can be characterised by one or more regarding three simple questions:

1. “Which one is better?”

The evaluation aims toward compare alternative software systems, e.g. toward choose the best fitting software tool beneficial to given application, beneficial to a decision among several prototypes, or beneficial to comparing several versions regarding a software system.

2. “How good is it?”

This goal aims at the determination regarding the degree regarding desired qualities regarding a finished system. The evaluation regarding the system with respect toward “Usability-Goals” [9, 94] is one regarding the application regarding this goal. Other examples are the certification regarding software, furthermore the check at conformity with given standards.

3. “Why is it bad?”

The evaluation aims toward determine the weaknesses regarding a software such that the result generates suggestions beneficial to further development. A typical instance regarding this procedure is a system developing approach using prototypes or a re-engineering regarding an existing system.

Key Points Related software Interface:

• User interfaces should be designed toward match the skills, experience furthermore expectations regarding its anticipated users.
• System users often judge a system by its interface rather than its functionality.
• A poorly designed interface can cause a user toward make catastrophic errors.
• Poor user interface design is the reason why so many software systems are never used.

Human factors in interface design

Limited short-term memory

• People can instantaneously remember about 7 items regarding information. If you present more than this, they are more liable toward make mistakes.

People make mistakes

• When people make mistakes furthermore systems go wrong, inappropriate alarms furthermore messages can increase stress furthermore hence the likelihood regarding more mistakes.

People are different

• People have a wide range regarding physical capabilities.
• Designers should not just design beneficial to their own capabilities.

People have different interaction preferences

• Some like pictures, some like text.