|
|
|
|
|
|
|
|
|
Enterprise MSF Agile (with CobiT) > Wiki Pages > Activity - Develop Performance Model (Create a Quality of Service Requirement)
|
Activity - Develop Performance Model (Create a Quality of Service Requirement)
|
|
|
|
|
|
Activity Information Develop Performance Model
DescriptionPerformance modeling is a process to help identify and address potential performance issues in the application. A performance model is developed from a quality of service requirement, which is then broken into development tasks. Each development task is assigned a performance budget for implementation. StepsReview the Quality of Service Requirement: Identify the scenarios linked to the performance quality of service requirement. Map the development tasks to the scenarios.
Identify Workload: From the quality of service requirements list, determine the workload for the application. Identify Performance Objectives: Using the workload estimates and the quality of service requirements list, identify the performance objectives for each of the key scenarios. These include objectives such as response time, throughput, and resource use. Identify Performance Budget: Identify the performance related resources budgeted to meet the performance objectives. Some examples of performance related resources are execution time and network bandwidth.
Determine the maximum allowable allocation of each resource. Allocate Budget: Spread the budgeted resources across the processing steps for each scenario.
When unsure of how to allocate the budget, make best guesses or divide the resources evenly among the steps. Budgeting is refined as the actual values for the tasks are validated.
Describe the allocation in the appropriate development task work item. Use the description field to concretely describe the budget. Evaluate Budget: Find budget allocations that pose a risk to meeting performance objectives.
Consider tradeoffs that help meet performance objectives such as design and deployment alternatives.
Reevaluate quality of service requirements if necessary. Validate the Model: Identify the scenarios that do not meet budget allocations.
Measure the performance of the scenarios. Use prototyping in early iterations if production code is not available.
Repeat the budgeting, evaluation, and validation steps as necessary using data acquired during validation.
Inputs and Outputs| WorkProduct | Input | Output | Allowable States |
|---|
| Task | /Wiki%20Pages/images/Input.gif) | /Wiki%20Pages/images/Output.gif) | Active |
|
Last modified at 1/17/2008 11:18 PM by Administrator
|
|
|
|
 |
 |
 |
 |
|