Constraints and Assumptions
What you'll learn: How to identify and document the fixed limitations and working beliefs that guide your software solution.
What Are Constraints and Assumptions?
When building software, you're never starting with a blank slate and total freedom. Constraints are the hard boundaries you must work within—things you cannot change. Assumptions are beliefs you're taking as true—things you expect to be the case, but haven't fully verified yet.
Think of constraints like building a house on a hillside: the slope is fixed, and you must design around it. Assumptions are like expecting the weather to stay dry during construction—probably true, but worth documenting in case it's not.
Types of Constraints
Technical: Must use Java 11, database can handle max 1000 requests/second, system must run on Linux servers.
Business: Budget is $50,000, launch date is March 1st, only three developers available.
Environmental: Users have slow internet connections, system must work offline, data cannot leave the EU.
Why Document Them?
Recording constraints and assumptions prevents surprises. If you assume users have modern browsers but many don't, your solution breaks. If you ignore the constraint that your backend must integrate with a legacy system, you'll design something impossible to deploy.
These documents also protect you: when stakeholders later ask "Why didn't you build X?", you can point to the constraint that prevented it.
Example
Constraint: Authentication must use the company's existing Active Directory system.
Assumption: Users will access the application during business hours, not 24/7.
Key Takeaway: Constraints are unchangeable boundaries; assumptions are working beliefs that need validation. Document both clearly to avoid costly surprises and guide realistic solution design.