Web of System Performance (WOSP) analysis

Description

Specify and evaluate a design against eight paired performance requirements (functionality, usability, security, extendibility, reliability, flexibility, connectivity, privacy), weighted by environment, and resolve the tensions between pairs.

Whitworth argues that treating non-functional requirements as second class creates a 'requirements mess'. Any system has four constituents (boundary, structure, effector, receptor), each designed to seize opportunities or reduce risks, giving eight requirements in four pairs: security and extendibility, reliability and flexibility, functionality and usability, privacy and connectivity. They are restated at hardware, software, HCI and community levels; the social version reads productivity, synergy, freedom, order, ownership, openness, transparency and privacy. On a radar web, area is overall performance, shape reflects how the environment weights each requirement, and lines across the web are tensions that tighten as systems mature (the 'version 2 paradox'). Innovation means resolving tensions, as Palm's Graffiti resolved portability against usability that defeated the Apple Newton. Each requirement maps to its own specialist analysis and test, such as usability testing, penetration testing or legitimacy analysis.

Attributes

Loss type
Latent
Effort
Days

Steps

  1. Identify the system level being designed (hardware, software, HCI or community) and translate project terms into the eight requirements using a synonyms table.
  2. State concrete requirements for each of the eight criteria (for a community, use the social set: productivity, synergy, freedom, order, ownership, openness, transparency, privacy).
  3. Weight each requirement for the expected environment, raising security in threat-heavy settings and extendibility in opportunity-rich ones.
  4. Assess performance on each requirement with its matching specialist analysis or test, gathering evidence such as screenshots and test results.
  5. Draw the radar web and compare its shape with the environment's weighting.
  6. Identify tensions where two requirements act on the same part (for example transparency against privacy) and look for designs that satisfy both rather than trading one off.
  7. Summarise strengths, gaps and proposed resolutions, avoiding gains in one corner at the cost of overall area.

Sources

  • HCI Encyclopedia (Soegaard & Dam, 2014)
  • The Social Design (Whitworth & Ahmad, 2014)

Also known as

  • WOSP
  • Web of system performance
  • Eight general system requirements
  • General system requirements web
  • Eight-criterion performance web
  • Social web of performance audit
  • Web of social performance
  • Eight community requirements audit

Categories

  • Strategy & Collaboration
  • Systems & Complexity