Constraint

Intro

A constraint is an external factor that limits how an organization can achieve its goals. It matters because constraints shape feasible architectures and delivery plans.

Key points:

• Sets boundaries such as budget, regulation, or dependencies.
• Improves realism in planning and design.
• Common use cases: regulatory caps (Data), compatibility limits (Tech), service level targets (Apps), policy rules (BPM).
• Pitfall: ignoring constraints until late, causing rework.

Examples:

• Data residency laws restricting cloud regions.
• Legacy interface protocols limiting integration options.
• Fixed go‑live dates driven by contract obligations.

In practice:

Document constraints alongside requirements and validate designs against them at each stage.

Related terms: requirement; assumption; risk

FAQs:

Q: Are constraints always external?
A: Typically yes; internal policies can act as constraints too.

Q: Can constraints change?
A: Yes; monitor and update designs as constraints evolve.

‍