持续易用性工程(中文名)
noun, emerging term. The engineering practice of treating usability — whether people can find their way through shipped software — as a continuously measured and governed property: periodic measurement cycles against a held-constant task set, cross-version regression ledgers for discovered issues, human adjudication of severity and acceptance, and release gates that consume usability readings. Organized as an institutional function — a named role, a budget line, an owned ledger — in the way Site Reliability Engineering organizes reliability.
Inherited, with deliberate modification, from Usability Engineering (Tyldesley 1988; Nielsen 1993). The ancestor's quantitative core — usability as a measurable engineering quantity, tested after construction — is retained in full. What is modified is its unconditional front-loading of quantitative targets: the practice front-loads only what is mechanically derivable (semantic floors: required information × required decisions), and derives tolerance bands from accumulated measurement history instead.
From Site Reliability Engineering it takes the institutional form, not the domain: formation by having software engineers design the verification function; a named role and budget line rather than a project ritual; regression ledgers and gate policy rather than one-off studies. In one line — the ancestor said “set quantitative goals, build, then test”; this practice says “measure first, then quantify; derive first, then prescribe; run continuously so that quantification and prescription regenerate each cycle.”
The term names the engineering-gate layer of mainstream software practice. The vacancy it fills is claimed narrowly: in mainstream software the mechanism layer is mature (CI release gates, metrics, and analytics are abundant), while task-usability metric families appear in no release-gate condition. This is not a claim that the industry lacks usability governance. Adjacent and vertical occupants are recorded, not denied:
Mainstream software demonstrably accommodates governance disciplines with institutional slots — accessibility engineering is the worked example — which is what makes this slot shape credible. The term is not a software development methodology (not a member of the *-DD family), and not a subtype of software testing: its measuring object is whether people find their way, not whether the machine is correct.
This page is a terminology placeholder and genealogy record, first published . The term is in early use by its initial practitioner; the definition above is a working definition and may evolve (see changelog). External adoption is the test that matters for any engineering discipline, and has not yet occurred. Source, edit history, and issue tracker: github.com/continuous-usability-engineering.
sha256:35f0404e4a1f78d5d202916656ac6224e8f4cddc53d32e4c5b00f901a941aa12