Optimizing Website Content to Improve Correctness of the Website Design

Related Work

As we know, the quality assurance was and is one of the challenging processes in software engineering as well as for the web engineering, as a new discipline. Although there exists many design guidelines, and metrics for the evaluation of web sites and applications, most of them lack a well-defined specification framework and even worse a strategy for consultation and reuse. Some initial efforts have been recently made to classify metrics for some entity type as for example metrics for software products. Particularly, in last few years a set of web site metrics were defined and specified based on the data collection point of view. The quality model must be able to assess the quality of each and every aspect of the website and it should cover the process of all web engineering activities. A set of guidelines are evolved to build a qualitative model of a website. Dreyfus P (1998) stated that guideline consists of a design and evaluation principle to be observed to get and to guarantee a usable user interface. Guidelines can be found in many different formats with contents varying both in quality and level of detail, ranging from ill-structured common sense statements to formalized rules ready for automatic guidelines checking. Certain rules are validated by experimental results provided by user tests, experiments in laboratory or other techniques. Guidelines can be classified as shown in figure 1 by type ranging from the most general to the most specific: principles, guidelines and recommendations.

Figure 1.

Principles, guidelines, and recommendations for quality website design

Principles are general objectives guiding conceptual User Interface (UI) decisions. They reflect the knowledge around human perception, learning and behavior and are generally expressed in generic terms like “Use images and metaphors consistent with real world” so that they can be applied for a wide range of cases. Guidelines are based on principles specific to a particular design domain. For example, a web design rule can stipulate to “use a consistent look and a visual language inside the site”. Some guidelines have to be interpreted more and altered to reflect the needs of a particular organization or a design case. Recommendations determine conceptual decisions specific to a particular domain of application and should reflect the needs and the terminology of a given organization. They are unambiguous statements so that no place for interpretation is left. Recommendations include ergonomic algorithms, user interface patterns and design rules. Design rules are functional and operational requirements specifying the design of a particular interface, e.g. “Every web page needs an informative title”.