Roberto PolilloDISCO, University of Milano Bicocca

Quality in Web Engineering Workshop 2011Paphos, Cyprus, 21 June 2011

Quality Models for Web [2.0] Sites:a Methodological Approach and a Proposal

Quality models (QM)

"A QM is a defined set of characteristics, and of relationships between them, which provides a framework for specifying quality requirements and evaluating quality"

ISO/IEC 25000:2005

Requirements

Design Development

Operations

ISO/IEC 25010 Product Quality Model

Web sites are different animals Unstructured information content

prevail on structured data user navigation, not data management and computation

Main purpose is communication, not computing

Continuous evolution (perpetual ß) Quality may depend on user actions

(Web 2.0)

ISO/IEC 25010 Product Quality Model

"Any system stakeholder with an active role in creating or maintaining some quality attribute of the system"

In Web sites theyare many and diverse

Community manager

End user

Web

2.0

site

s Web designer

Visual designer Function

designer

Platform

developer

Content editor

Web master

Data centermanager

Site owner

Web site

quality

Usabilityprofessional

Site developer

Quality Actors

Map quality characteristcs to quality actors in the simplest possible way ("organization mapping")

Quality model [Sub-]characteristics

InvolvedactorsC1

C2C3C4C5….

A1A2A3A4A1,A3

Quality model [Sub-]characteristics

Involvedactors

C1C2C3C4C5….

A1,A2,A3A3,A4A2,A3A1,A2,A4A1,A2,A4

Good mapping Bad mapping

QM for Web sites: the most important goal

Requirements for Web sites QM An "organization mapping" as simple as

possible Tailorable to the class of sites under

consideration Subsettable according to purpose Scalable wrt site complexity Universally usable and accessible

Really a QM family

Serv

er

& n

etw

ork

pla

tform

Sit

e

pla

tform

Sit

e

ContentInformati

on architect

ure & navigatio

n

Web designer

A1

Graphics &

branding

Visualdesigner

A2

Company

generated

ContenteditorA5

Software

functions

Functiondesigner

A3

Softwaredeveloper

A4

Building the QM

User

Community managerA6

Usergenerat

ed

Usabilityprof

A7

ArchitectureA1

CommunicationA2

Functionality A3

Software codeA4

Content A5

CommunityA6 Usability,

Accessibility A7, all

Webmaster

A8

Data Centermngmt

A9

PlatformA8, A9

QM: characteristics

Names are chosen to be understandable by anybody

Information architectureNavigation

Brand identityVisual designTypographyMultimedia usage

Categorization/labellingConformity to style guideInformation/data qualityContent timelinessContent localization

Functional adequacyFunctional correctnessSecurity / privacy

User relationsCommunity management

FindabilityBand requirementsClient independenceUsers ability requirements Effectiveness

EfficiencyUser satisfaction

Architecture

Communication

Functionality

Content

Community

Accessibility

Usability

Software code

Platform Platform adequacySite availabilitySite performancesAccess monitoring

CHARACTERISTICS

SUB-CHARACTERISTICS

Exte

rnal qu

alit

y

& q

ualit

y in

use

Inte

rna

l qualit

y

Reliability

Compliance to standardsMaintainability

Relationship with ISO QM

Conclusions

ISO QM not fit for Web sites/applications Starting from quality actors / Web site

logical components seems more practical

In Web 2.0, users are essential quality actors

The proposed QM can be specialized for different purposes, keeping the top layer stable ("family of QM")

Thank you!