Maximizing Testing ROI Prioritizing the uses of the system produces a weighted operational profile, or use profile. Many of the steps might seem straightforward enough in the context of the simple example presented here, but in a larger project, determining which use cases to stress and which to cover only briefly can be tricky. Indeed, building use profiles maximizes the return on investment of resources allocated to system testing, directing system testing in such a way that the reliability of the software increases the fastest. That is, test cases are selected so that those operations users depend on most are triggered most often. To illustrate the use profile technique, we'll model a simple banking system with which customers can directly access their accounts through automated teller machines.
Customers can add or remove money from their accounts or check their balances.
According to the UML notation, actors are stick figures and use cases are ovals. A dependency arrow shows the association of an actor to a specific use. The actors in the example system include a bank customer, a teller, a head teller and the electronic funds transfer system. The Use-Profile Process 1. Define complete set of actors.