MSF for Agile Software Development Visual Studio 2005 Team System logo

Activity:

Develop Performance Model

Participating Roles

Responsible:

Architect

Consult:

Developer

Overview

Entry Criteria

  • The performance quality of service requirement has been divided into development tasks.

Sub-Activities

1

Review the Quality of Service Requirement

  • Identify the scenarios linked to the performance quality of service requirement.
  • Map the development tasks to the scenarios.

2

Identify Workload

  • From the quality of service requirements list, determine the workload for the application.

3

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.

4

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.

5

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.

6

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.

7

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.

Exit Criteria

Performance budgets have been attached to all development tasks for the quality of service requirement

Performance goals for the current iteration are met.

© 2006 Microsoft Corporation. All rights reserved.

Version 4.1.0