128 CHAPTER 5 PERFORMANCE THROUGH THE APPLICATION (Web design course)
128 CHAPTER 5 PERFORMANCE THROUGH THE APPLICATION DEVELOPMENT LIFE CYCLE An important aspect of defining intelligent SLAs is tracking them. The best way to do this is to integrate them into your application use cases. A use case is built from a general thought, such as The application must provide search functionality for its patient medical records, but then the use case is divided into scenarios. Each scenario defines a path that the use case may follow given varying user actions. For example, what does the application do when the patient exists? What does it do when the patient does not exist? What if the search criterion returns more than one patient record? Each of these business processes needs to be explicitly called out in the use case, and each needs to have an SLA associated with it. The following exercise demonstrates the format that a proper use case containing intelligent SLAs should follow. USE CASE: PATIENT HISTORY SEARCH FUNCTIONALITY Use Case The Patient Management System must provide functionality to search for specific patient medical history information. Scenarios Scenario 1: The Patient Management System returns one distinct record. Scenario 2: The Patient Management System returns more than one match. Scenario 3: The Patient Management System does not find any users meeting the specified criteria. Preconditions The user has successfully logged in to the application. Triggers The user enters search criteria and submits data using the Web interface. Descriptions Scenario 1: 1. The Patient Management 2. . . . Scenario 2: 3. . . . Postconditions The Patient Management System displays the results to the user. SLAs Scenario 1: The Patient Management System will return a specific patient matching the specified criteria in less than three seconds for 95 percent of requests. The response time will at no point stray more than two standard deviations from the mean. Scenario 2: The Patient Management System will return a collection of patients matching the specified criteria in less than five seconds for 95 percent of requests. The response time will at no point stray more than two standard deviations from the mean. Scenario 3: When the Patient Management System cannot find a user matching the specified criteria, it will inform the user in less than two seconds for 95 percent of requests. The response time will at no point stray more than two standard deviations from the mean.
Note: If you are looking for best quality webspace to host and run your tomcat application check Vision virtual web hosting services