UX Reference · Topic
Design systems and implementation
Design systems connect reusable design decisions with implementation and maintenance. These entries cover components, specifications, consistency and delivery practices.
33 entries
Acceptance CriteriaAcceptance criteria are agreed conditions used to determine whether a requirement, user story, feature, or service change has been…Also: Acceptance conditions, definition of acceptance, story criteria
Accessibility RegressionAccessibility regression is the reintroduction or creation of accessibility barriers after a design, content, code, component, or release…Also: A11y regression, accessibility defect regression, accessibility quality regression
ComponentA component is a reusable element with a defined purpose, structure, behavior, and implementation rules within an interface, design…Also: UI component, interface component, reusable component
Component DocumentationComponent documentation is the structured guidance that explains how a reusable interface component should be used, configured…Also: Component guidance, component usage documentation, component specs
Component GovernanceComponent governance is the process of controlling how reusable interface components are proposed, approved, documented, implemented…Also: Component lifecycle governance, component stewardship, component management
Component VariantA component variant is an approved version, state, size, style, or behavior of a reusable interface component that serves a specific use…Also: Variant, component state, component variation
Decision LogA decision log is a structured record of important decisions, including the decision made, context, evidence, alternatives, rationale…Also: Decision register, decision record, decision history
Design HandoffDesign handoff is the process of transferring design intent, specifications, assets, content, behavior, constraints, and contextual…Also: Designer-developer handoff, design-to-development handoff, UX handoff
Design Quality AssuranceDesign quality assurance is the structured review of whether implemented design, content, interaction, accessibility, and component…Also: Design QA, UX QA, design review QA
Design RationaleDesign rationale is the documented reasoning behind a design decision, including the problem, evidence, alternatives, trade-offs…Also: Design reasoning, rationale documentation, decision rationale
Design ReviewA design review is a structured evaluation of a design artifact, interface, flow, or concept before or during implementation to identify…Also: Expert design review, UX design critique, interface review
Design SpecificationA design specification is a documented description of how a design should be built, including layout, content, components, states…Also: Design spec, UI specification, design documentation
Design SystemA design system is a governed set of reusable interface components, interaction patterns, visual rules, content conventions, accessibility…Also: UI system, interface system, component system
Design System GovernanceDesign system governance is the set of roles, rules, processes, and decision structures used to maintain, evolve, approve, document, and…Also: Design-system management, design-system operating model, design-system stewardship
Design TokenA design token is a named, reusable value that represents a design decision, such as color, spacing, typography, border radius, elevation…Also: Token, design variable, semantic token
Front-End Implementation QualityFront-end implementation quality is the degree to which the coded user interface is usable, accessible, reliable, maintainable…Also: Coded UI quality, front-end quality, UI implementation quality
Functional RequirementA functional requirement describes what a system, product, service, or component must do to support a user, business, or operational need.Also: System function, feature requirement, behavioural requirement
Implementation FidelityImplementation fidelity is the extent to which the built product or interface accurately reflects the approved design intent, including…Also: Design-to-code fidelity, design implementation accuracy, implementation accuracy
Implementation ReviewImplementation review is the structured evaluation of a built interface against approved design, content, component, accessibility…Also: Front-end review, design-to-code review, implementation QA
Implementation RiskImplementation risk is the possibility that a product, service, system, or change effort will fail, underperform, create harm, or produce…Also: Delivery risk, rollout risk, implementation failure risk
Interaction ConsistencyInteraction consistency is the extent to which similar interface elements, actions, states, and workflows behave in predictable and…Also: Behavioral consistency, interface behavior consistency, interaction behavior consistency
Interaction SpecificationAn interaction specification is a documented description of how an interface or component should behave, including states, triggers…Also: Interaction spec, behavior specification, UI behavior specification
Non-Functional RequirementA non-functional requirement describes a quality, constraint, or condition that a system, product, or service must satisfy, such as…Also: NFR, quality requirement, quality attribute
PatternA pattern is a reusable solution structure for a recurring problem within a defined context, including the problem, when it appears, the…Also: Design pattern, interaction pattern, UI pattern
Pattern LibraryA pattern library is an organized collection of reusable design patterns, guidance, examples, and usage rules that help teams solve…Also: Design pattern library, UX pattern library, interface pattern library
Release ReadinessRelease readiness is the assessment of whether a product, feature, service change, or digital journey is ready to be launched or released…Also: Launch readiness, go-live readiness, release review
Responsive DesignResponsive design is an approach in which digital interfaces adapt to different screen sizes, devices, input methods, and viewing…Also: Responsive web design, adaptive layout, multi-device design
Use CaseA use case is a structured description of how an actor interacts with a system, service, or process to achieve a goal under specific…Also: Actor-goal scenario, system interaction scenario, usage scenario
User RequirementA user requirement is a statement of what a system, product, service, or interaction must support so that users can meet identified needs…Also: User-centered requirement, user requirement statement, user-facing requirement
User StoryA user story is a short delivery-focused statement that describes a user, what they need to do, and why that value matters.Also: Agile story, product story, service story
UX DebtUX debt is the accumulated cost of unresolved user experience problems, design inconsistencies, accessibility gaps, content issues, or…Also: User experience debt, design debt, usability debt
Visual ConsistencyVisual consistency is the extent to which visual design elements such as typography, color, spacing, layout, iconography, elevation, and…Also: Visual coherence, visual uniformity, interface visual consistency
WireframeA wireframe is a simplified representation of an interface that shows structure, content areas, navigation, controls, and functional…Also: Low-fidelity layout, structural screen sketch, interface wireframe