Quiz
UML for Precise Solution Specification
Understanding how UML diagrams alone are insufficient for a fully precise, unambiguous solution specification.
A team uses UML class diagrams to specify a banking solution, but reviewers reject the model because business rules like 'an account balance may never drop below its overdraft limit' cannot be enforced by the diagram's graphical notation alone. What is the correct UML-based technique to make such invariants and pre/postconditions part of the formal specification?