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 |
|
Version: 1.0
Ó 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 |
Traceability Audit |
|
Author |
|
|
Creation Date |
|
|
Last Updated |
|
Functional Specification Audit
Purchasing and Facilities Plan Audit
[Introduction to the Template
Description:
The Traceability Audit documents the processes of 1) comparing specifications to
what was actually developed and plans to actual events, 2) identifying if and
where change control process broke down, and 3) determining the cause of all
variations and deviations. The comparison process focuses on Functional
Specification and the Master Project Plan and looks at what occurred in the
development phase and how that was different than planned. These differences
could take the form of feature reduction, elimination, creation; modifications
in the Functional Specification; or scope/schedule/budget changes in the Master
Project Plan. The comparison process will also discover if those documents were
maintained through the change control procedure. If not, they must be updated
and change requests made.
Justification:
A
project
must
satisfy the criteria upon which it was established during the envisioning and
planning phases. Its documentation represents the discipline and commitment of a
team dedicated to delivering quality. The traceability audit process confirms
quality documentation or remediates existing documentation to expected
standards. In addition, the development phase must be assessed to ensure that
what was committed to during early phases has been actually built. The
traceability audit will also confirm or remediate this.
The
result of a traceability audit, regardless of its intermediate findings, is a
project with current and accurate documentation and development results aligned
with the Functional Specification.
{Team
Role Primary: Program Management
is responsible for ensuring that the audit is performed and the documentation is
completed. Test is responsible for validating that all
testing is completed and every portion of the delivery has been tested and
reported in accordance to plan. Development is responsible for managing
the action items for any remaining delivery activities to ensure the return
audit results are acceptable.
Team
Role Secondary:
Product Management will review audit
results in order to discuss the status of the build to external stakeholders. Release Management will review audit
results to ensure that support, operational, security and deployment concerns
have been audited and passed successfully. User Experience will review audit
results in order to confirm that user experience requirements have been
met.}]
[Description: Provide an overall summary
of the contents of this document.
Justification:
Some
project participants may need to know only the highlights of the audit, 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 Audit Scope and
Dimensions section defines the scope of the audit and the documents and project
activities currently under review. This section should also include a
description of the audit approach (audit model), evaluation criteria, and the
qualifications of the audit team.
Justification:
This
information provides context for the remaining document and establishes
authority and audit parameters.]
<<Begin
text here>>
[Description: The Functional
Specification Audit section describes the results of auditing the set of
documents that together are called the Functional
Specification.]
[Description: The Requirements Analysis
Audit section describes the results of auditing the four types of requirements
documents.]
[Description: The Business Requirements
section describes the results of the audit of the business requirements
document. This information should include the date of the audit, the version of
the subject requirements document, and the list of variations found between the
developed solution and the contents of the requirements document. For each
variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The System Requirements
section describes the results of the audit of the system requirements document.
This information should include the date of the audit, the version of the
subject requirements document, and the list of variations found between the
developed solution and the contents of the requirements document. For each
variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin
text here>>
[Description: The User Requirements
section describes the results of the audit of the user requirements document.
This information should include the date of the audit, the version of the
subject requirements document, and the list of variations found between the
developed solution and the contents of the requirements document. For each
variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin
text here>>
[Description: The Operations
Requirements section describes the results of the audit of the business
requirements document. This information should include the date of the audit,
the version of the subject requirements document, and the list of variations
found between the developed solution and the contents of the requirements
document. For each variation, describe its character. For each variation, or set
of similar variations, describe its cause.]
<<Begin text here>>
[Description: The Conceptual Design
Audit section describes the results of the audit of the conceptual design
document. This information should include the date of the audit, the version of
the subject design document, and the list of variations found between the
developed solution and the contents of the design document. For each variation,
describe its character. For each variation, or set of similar variations,
describe its cause.
This
section may also contain the results of a traceability audit between the
conceptual design and the previous requirements
documents.]
<<Begin text here>>
[Description: The Logical Design Audit
section describes the results of the audit of the logical design document. This
information should include the date of the audit, the version of the subject
design document, and the list of variations found between the developed solution
and the contents of the design document. For each variation, describe its
character. For each variation, or set of similar variations, describe its cause.
This
section may also contain the results of a traceability audit between the logical
design and the previous requirements documents.]
<<Begin text here>>
[Description: The Physical Design Audit
section describes the results of the audit of the physical design document. This
information should include the date of the audit, the version of the subject
design document, and the list of variations found between the developed solution
and the contents of the design document. For each variation, describe its
character. For each variation, or set of similar variations, describe its cause.
This
section may also contain the results of a traceability audit between the
physical design and the previous requirements documents.]
<<Begin text here>>
[Description: The Master Project Plan
Audit section describes the results of auditing the set of documents that
together are called the Master Project Plan.]
[Description: The Development Plan Audit
section describes the results of the audit of the development plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual development activities
and resulting developed solution and the activities defined in the plan. For
each variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The Test Plan Audit
section describes the results of the audit of the test plan. This information
should include the date of the audit, the version of the subject plan, and the
list of variations found between the actual test activities and resulting
developed solution and the activities defined in the plan. For each variation,
describe its character. For each variation, or set of similar variations,
describe its cause.]
<<Begin text here>>
[Description: The Communication Plan
Audit section describes the results of the audit of the communication plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual communication
activities and those defined in the plan. For each variation, describe its
character. For each variation, or set of similar variations, describe its
cause.]
<<Begin text here>>
[Description: The Microsoft Support Plan
Audit section describes the results of the audit of the Microsoft support plan.
This information should include the date of the audit, the version of the
subject plan, and the list of variations found between the actual support
activities and resulting developed solution and the activities defined in the
plan. For each variation, describe its character. For each variation, or set of
similar variations, describe its cause.]
<<Begin text here>>
[Description: The Operations Plan Audit
section describes the results of the audit of the operations plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual operations
implementation activities and resulting developed solution and the activities
defined in the plan. For each variation, describe its character. For each
variation, or set of similar variations, describe its cause.
This
section also contains sub-sections for each of the plans that together comprise
the operations plan. Each of these sections should also contain the above-stated
information.]
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
<<Begin text here>>
[Description: The End-User Support Plan
Audit section describes the results of the audit of the end-user support plan.
This information should include the date of the audit, the version of the
subject plan, and the list of variations found between the actual support
activities and resulting developed solution and the activities defined in the
plan. For each variation, describe its character. For each variation, or set of
similar variations, describe its cause.]
<<Begin text here>>
[Description: The Deployment Plan Audit
section describes the results of the audit of the deployment plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual deployment activities
and resulting developed solution and the activities defined in the plan. For
each variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The Training Plan Audit
section describes the results of the audit of the training plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual training activities
and resulting developed solution and the activities defined in the plan. For
each variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The Purchasing and
Facilities Plan Audit section describes the results of the audit of the
purchasing and facilities plan. This information should include the date of the
audit, the version of the subject plan, and the list of variations found between
1) the actual purchasing activities and 2) the preparation of the facilities and
the resulting developed solution, and the activities defined in the plan. For
each variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The Migration Plan Audit
section describes the results of the audit of the migration plan. This
information should include the date of the audit, the version of the subject
plan, and the list of variations found between the actual migration activities
and resulting developed solution and the activities defined in the plan. For
each variation, describe its character. For each variation, or set of similar
variations, describe its cause.]
<<Begin text here>>
[Description: The Pilot Plan Audit
section describes the results of the audit of the pilot plan. This information
should include the date of the audit, the version of the subject plan, and the
list of variations found between the actual pilot activities and resulting
developed solution and the activities defined in the plan. For each variation,
describe its character. For each variation, or set of similar variations,
describe its cause.]
<<Begin text here>>
[Description: The Budget Plan Audit
section describes the results of the audit of the budget plan. This information
should include the date of the audit, the version of the subject plan, and the
list of variations found between the actual budget and resulting developed
solution and the estimated budget defined in the plan. For each variation,
describe its character. For each variation, or set of similar variations,
describe its cause.]
<<Begin text here>>
[Description: The Tools Plan Audit
section describes the results of the audit of the tools plan. This information
should include the date of the audit, the version of the subject plan, and the
list of variations found between the actual tools used and resulting developed
solution and the tools defined in the plan. For each variation, describe its
character. For each variation, or set of similar variations, describe its
cause.]
<<Begin text here>>