UML provides great artifacts that aid traceability from start to finish; however, they don't directly clarify the distributed or throughput requirements of the application. Although component and deployment diagrams can model the notion of “location,” applications need a set of views that deal specifically with network and database loading and distribution. The good news is that the input to this effort comes directly from the use-cases, class diagram, and sequence diagrams; thus the project still weaves in traceability. These non-UML diagrams I call usage matrices. There are three types:
The event/frequency matrix applies volumetric ...