Search the practice set

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

23 results for “Requirements to Constraints”

Terminology · 10
term

Architectural Driver

The small subset of requirements and constraints that actually shape the structure of the system.

Architecture Fundamentals
term

Compliance Framework

A published set of control requirements an organisation is assessed against, which turns security posture into evidence somebody else will check.

Security Architecture
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

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

Non-Functional Requirement

A requirement about how well the system must behave rather than what it must do — latency, availability, throughput, security, cost.

Architecture Fundamentals
term

OLTP vs OLAP

Two workload shapes with opposite requirements — many small indexed transactions versus few large scans and aggregations — which is why they belong in different stores.

Data Warehousing
term

Pragmatism

Preferring the simplest architecture that satisfies the requirements, and treating additional structure as a cost that must be justified.

Meta-Skills
term

Quality Attribute Scenario

A structured, testable statement of a non-functional requirement: source, stimulus, environment, artefact, response, response measure.

Architecture Fundamentals
term

SQL vs NoSQL

A choice driven by access patterns, consistency requirements and query flexibility — not by data volume, which is the reason usually given.

Architecture Decision-Making
term

Solution Architecture

The design of a specific system that satisfies a specific business problem under a specific set of constraints.

Architecture Fundamentals