Step 2. Make a Reproducible Assessment Script (ie: a RAS)
Choose the application areas that the most end-users use most of the time. In many commercial applications 10% of the application is often used 90% of the time by 90% of the users. Always assess the 10% that is used most first, which is what most people are most likely to complain about.
Choose the application area which the most business benefit will be gained from any improvements. This probably means using the 90/10 rule again, but even within that, improving just one area like Order Entry might be 95% of the overall business benefit gain.
Create a RAS that involves 30 or more interactions with the web server.
In the RAS record exactly how many server interactions are performed.
Rather than just cruising around randomly in the application, make the RAS work as end-users would work, completing typical actions, especially where cyclical activities are repeatedly performed.
Write the RAS down as a table of scripted steps so that it can be easily repeated. This also allows other people to be delegated to complete the test cycles for you.
Include a ‘Perceived Elapsed Response Time’ (PERT) column in which the perceived response time of each step can be recorded by using a stopwatch.
Producing and keeping a RAS for each test you perform is useful as it documents any gradual improvements you make. It also provides, in a very subjective and emotive area, something objective that can be used as the basis for discussions with management, end-users, etc.