Search the practice set

126 questions, 454 terms and 400 topics in 20 areas.

16 results for “Constraint Thinking”

Terminology · 10
term

Constraint Thinking

Designing for the budget, timeline, skills, regulations and existing estate that actually exist, rather than for the ones a textbook assumes.

Meta-Skills
term

Failure Thinking

Making "what happens when this fails?" a standing question applied to every component and every dependency in a design.

Meta-Skills
term

Foreign Key Constraint

A database-enforced rule that a referencing value must exist in the referenced table — referential integrity that no application bug can violate.

Relational Modelling
term

Product Thinking

Treating what you build as something with users, a value proposition and a lifecycle, rather than as a project that completes.

Business Architecture
term

Regulatory Constraint

A legal requirement that removes design options — and one that must be established early, because it is not negotiable and is expensive to retrofit.

Business Architecture
term

Systems Thinking

Reasoning about a system in terms of the interactions and feedback loops between its parts, rather than the parts individually.

Meta-Skills
term

Blue-Green Database Schema

The constraint that makes fast rollback actually work — both application versions must be able to run against one schema at the same time.

Release Strategies
term

Capital One's Data Centre Exit

A major US bank closed all eight of its data centres and moved fully to public cloud, treating governance automation as the enabling technology rather than a constraint.

Enterprise Architecture
term

Cognitive Load

The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.

Software Architecture
term

Time to Market

How long it takes to get a capability in front of customers — often the constraint that dominates every other architectural quality.

Business Architecture