Typical Versus Worst Case
abstract
System design must address the typical needs and expectations of the user as well as the worst case use conditions.
A continuous tension exists between the day to day requirements for a new product and the requirements in exceptional cases.
The System Architect must understand both requirements and be able to discuss them in terms of value in order to make a balanced product.
This article gives some handles to tackle this problem.
status:
preliminary draft
download statistics: |
Slides: 937 downloads |
| Paper: 1108 downloads |