Developing a usage model - page three
A little over a year ago I met with another tester in town to provide advice on performance testing. I recently found the notes from the meeting in an old notebook. In the five pages of handwritten notes, I documented my understanding of the problem and how I would approach the project. Take these notes for what they are - sketches over the course of an hour or two as I asked questions and clarified the project. However, I thought they would be interesting to share.
The third page was an attempt to document the initial usage model.
The notation is the UCML, which stands for User Communty Modeling Language. You'll see four types of users: clients (aka "users"), administrators, customers (of the clients), and system tasks. From there I attempted to capture tasks of interest and some rough percentages for each task across the user population.
The third page was an attempt to document the initial usage model.
The notation is the UCML, which stands for User Communty Modeling Language. You'll see four types of users: clients (aka "users"), administrators, customers (of the clients), and system tasks. From there I attempted to capture tasks of interest and some rough percentages for each task across the user population.