Directions for using
template:
Read the Guidance
(Arial blue font in brackets) to understand the
information that should be placed in each section of this template. Then delete
the Guidance and replace the placeholder within <<Begin text here>>
with your response. There may be additional Guidance in the Appendix of some
documents, which should also be deleted once it has been used.
Some templates have four levels of headings. They are not indented, but can be differentiated by font type and size:
You may elect to indent sections for readability.
|
Author |
|
|
Author Position |
|
|
Date |
|
Ó 2002 Microsoft Corporation. All rights reserved.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Microsoft
and Visual Basic are either registered trademarks or trademarks of Microsoft in
the
Change Record
|
Date |
Author |
Version |
Change Reference |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Version Approved |
Position |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Distribution
|
Name |
Position |
|
|
|
|
|
|
|
|
|
|
|
|
Document Properties
|
Item |
Details |
|
Document Title |
Performance Plan |
|
Author |
|
|
Creation Date |
|
|
Last Updated |
|
[Introduction to the
Template
Description:
The Performance Plan describes the solution’s performance requirements, what
elements of the solution will be developed to measure performance, and how
solution performance will be measured to ensure the requirements are
continuously met.
Justification:
A solution that does not meet the performance expectations of its stakeholders
is not a solution; therefore, the project must develop plans to address
performance requirements and to develop a solution monitoring process that
ensures the delivery of performance.
{Team
Role Primary: Development is responsible for the content of the
Performance Plan. Program Management ensures that the plan meets quality
expectations and is incorporated into the Master Project Plan and aligned with
the Operations Plan.
Team
Role Secondary:
All other roles are responsible for reviewing the plan to ensure that it is
executable and addresses the performance expectations relating to their
functional areas of the solution.}]
[Description:
Provide an overall summary of the contents of this
document.]
Justification:
Some
readers may need to know only the highlights of the plan, and summarizing
creates that user view. It also enables the full reader to know the essence of
the document before they examine the details.]
<<Begin text here>>
[Description:
The Objectives section defines the primary drivers that determine performance
requirements and the key objectives of the overall performance
approach.
Justification:
Identifying
the drivers and performance objectives signals to the customer that Microsoft
has carefully considered the situation and created an appropriate
approach.]
<<Begin text here>>
[Description:
The Performance Requirements section describes the solution’s performance
requirements explicitly defined by its solution users and other stakeholders.
Justification:
Clearly defined requirements support the development of a solution that delivers
within performance expectations.]
[Description: The Solution and Component Metrics
section describes for the overall solution, its critical components, the
sequences of those components, and the metrics that identify acceptable
performance. These metrics should be established at both the solution and
component level.]
<<Begin text here>>
[Description:
The Load section describes the procedures, methods, and tools to be used to
measure the load imposed on solution components. You may reference the Load
Matrix from the Capacity Plan or summarize it to provide an overall
understanding of load requirements.]
<<Begin text here>>
[Description:
The Response Time section defines the response times required for a solution to
respond to a user request for service. These requirements should define response
times for individual transactions and for complete user
scenarios.]
[Description:
The End-to-End Response Time section identifies all possible end-to-end
sequences through the solution and the maximum expected durations of those
sequences.]
<<Begin text here>>
[Description:
The Detailed Response Time section defines the incremental response time
requirements within the end-to-end sequences.]
<<Begin text here>>
[Description: The Performance Environment section
describes the entire performance measurement and analysis infrastructure
including processes, methods, tools, and resources, and the way these items
operate together to form a measurement infrastructure. Include graphical
illustrations of the infrastructure and its relationships to the solution. For
example, show how the measurement infrastructure gathers and records performance
measurements for solution components.
Justification:
This
information, described as a set of integrated elements, is the “performance
solution” aspect of the overall solution. Effective performance management
occurs when individual performance processes are integrated into a
system.]
[Description:
The
Infrastructure section describes the hardware and software components that will
support the performance measurement and analysis processes.]
<<Begin text here>>
[Description:
The
Tools section describes the
tools that will be built into the solution and/or applied to the solution and
its components to gather, record, analyze, and report solution and solution
component performance.]
<<Begin text here>>
[Description:
The Methodology section describes the methods that will be used to measure
solution and component performance and to analyze and report findings. This
information may be presented at multiple levels of
detail.]
<<Begin text here>>
[Description:
The
Performance Testing Steps section lists and describes the steps
for each performance measurement procedure.]
<<Begin text here>>
[Description:
The
Staff Resource Requirements section describes the personnel that will be
required to measure solution and component performance and to analyze and report
findings. It may include identification of specific groups or individuals who
will be assigned to performance management processes.]
<<Begin text here>>
[Description:
The Performance Tools section describes any performance tools used or considered
such as AppCenter Test or LoadRunner.]
<<Begin text here>>