General Definitions
Requirement is a widely used technical term, in context with product and process development wikipedia delivers the following definition:
In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder. Requirements can come with different levels of specificity; for example, a requirement specification or requirement “spec” (often imprecisely referred to as “the” spec/specs, but there are actually different sorts of specifications) refers to an explicit, highly objective/clear (and often quantitative) requirement (or sometimes, set of requirements) to be satisfied by a material, design, product, or service.[1]
The International Usability and UX Qualification Board (UXQB) uses a definition that is focused on interactive systems:
A condition or capability that must be met or possessed by an interactive system to satisfy an agreement, standard, specification or other formally imposed documents.
Notes:
1. A requirement should have a determinable condition that makes it possible to validate it.
2. This glossary defines the following types of requirements:
3. This glossary further distinguishes between
(CPUX-UR – Curriculum (Version 1.3, June 2016))
« Back to Glossary Index