Statement, in technical language that can be designed for and tested, of what a solution has to do (functional) or how well (non-functional). Each one comes from at least one business requirement or from a constraint.
In the Ultra Transcenders books
Each book explains Technical requirement in context, with comparison tables and the common traps.
Terms in this definition
- LEAST
Pass up to 254 expressions to this T-SQL function and it hands back whichever is smallest. Both Fabric Warehouse and SQL analytics endpoints support it.
- Business requirement
Owned by a stakeholder on the business side and phrased in business terms, it states something the solution must deliver for an objective to be achieved. Technical requirements later express it as measurable qualities or system behaviour.
- Constraint
Set by someone other than the architect, it fixes a limit the design cannot change, such as reusing existing hardware, a fixed budget or having just one data centre. Its effect is recorded and worked around, and any gap it leaves is logged as a risk.
Related terms
- Business objective
The top link in the chain that every business and technical requirement traces back to: a goal the organisation has, framed around things like regulatory exposure, time to market, revenue or cost, with no mention of how systems behave.
- Functional requirement
Describes a capability the system needs, for example a self-service catalogue, and is one kind of technical requirement. Qualities such as those in AMPRS belong instead to non-functional requirements, which cover how well that capability is delivered.