You are on page 1of 11

<<Project Name>>

Traceability Audit
Customer Name
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 tet here!! with "our response. There ma" be
additional Guidance in the Appendi of some documents# which should also be
deleted once it has been used.
$ome templates ha%e four le%els of headings. The" are not indented# but can be
differentiated b" font t"pe and si&e:
'eading ( ) Arial Bold (* font
'eading + ) Arial Bold ,talic (- font
'eading . ) Arial Bold (. font
'eading . ) Arial Bold ,talic (+ font
/ou ma" elect to indent sections for readabilit".
Author
Author 0osition
1ate
2ersion: (.3
3453+5+3(-
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 accurac of an
information presented after the date of publication.
This document is for informational purposes onl. MICROSOFT MAKES NO ARRANTIES! E"PRESS OR
IMP#IE$! IN T%IS $OC&MENT'
Microsoft and !isual Basic are either registered trademarks or trademarks of Microsoft in the "nited #tates and$or
other countries.
3453+5+3(-

Revision & Sign-off Sheet
6hange Record
1ate Author 2ersion 6hange Reference
Re%iewers
7ame 2ersion Appro%ed 0osition 1ate
1istribution
7ame 0osition
1ocument 0roperties
,tem 1etails
1ocument Title Traceabilit" Audit
Author
6reation 1ate
8ast 9pdated
3453+5+3(-

Table of Contents
$ummar"..........................................................................................................................
Audit $cope and 1imensions..........................................................................................
:unctional $pecification Audit........................................................................................
Re;uirements Anal"sis Audit......................................................................................
Business Re;uirements............................................................................................
$"stem Re;uirements..............................................................................................
9ser Re;uirements.................................................................................................-
<perations Re;uirements.......................................................................................-
6onceptual 1esign Audit............................................................................................-
8ogical 1esign Audit..................................................................................................-
0h"sical 1esign Audit................................................................................................=
>aster 0ro?ect 0lan Audit...............................................................................................=
1e%elopment 0lan Audit.............................................................................................=
Test 0lan Audit...........................................................................................................=
6ommunication 0lan Audit........................................................................................=
>icrosoft $upport 0lan Audit.....................................................................................*
<perations 0lan Audit.................................................................................................*
$ecurit"...................................................................................................................*
A%ailabilit".............................................................................................................*
6apacit"..................................................................................................................*
>onitoring..............................................................................................................*
0erformance............................................................................................................*
$upport...................................................................................................................@
Backup and Reco%er".............................................................................................@
AndB9ser $upport 0lan Audit.....................................................................................@
1eplo"ment 0lan Audit..............................................................................................@
Training 0lan Audit....................................................................................................@
0urchasing and :acilities 0lan Audit..........................................................................@
>igration 0lan Audit..................................................................................................4
0ilot 0lan Audit..........................................................................................................4
Budget 0lan Audit.......................................................................................................4
Tools 0lan Audit.........................................................................................................4
3453+5+3(-
%I(troductio( to t)e Tem*late
$escri*tio(+ The Traceabilit Audit documents the processes of &' comparing
specifications to what was actuall developed and plans to actual events, 2'
identifing if and where change control process broke down, and (' determining the
cause of all variations and deviations. The comparison process focuses on
)unctional #pecification and the Master *ro+ect *lan 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
)unctional #pecification, or scope$schedule$budget changes in the Master *ro+ect
*lan. The comparison process will also discover if those documents were maintained
through the change control procedure. -f not, the must be updated and change
re.uests made.
,usti-icatio(+ A pro+ect must satisf the criteria upon which it was established during
the envisioning and planning phases. -ts documentation represents the discipline and
commitment of a team dedicated to delivering .ualit. The traceabilit audit process
confirms .ualit documentation or remediates e/isting documentation to e/pected
standards. -n addition, the development phase must be assessed to ensure that what
was committed to during earl phases has been actuall built. The traceabilit audit
will also confirm or remediate this.
The result of a traceabilit audit, regardless of its intermediate findings, is a pro+ect
with current and accurate documentation and development results aligned with the
)unctional #pecification.
0Team Role Primary+ Pro.ram Ma(a.eme(t 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 ever portion of the deliver has been
tested and reported in accordance to plan. $e/elo*me(t is responsible for managing
the action items for an remaining deliver activities to ensure the return audit results
are acceptable.
Team Role Seco(dary+ Product Ma(a.eme(t will review audit results in order to
discuss the status of the build to e/ternal stakeholders. Release Ma(a.eme(t will
review audit results to ensure that support, operational, securit and deploment
concerns have been audited and passed successfull. &ser E0*erie(ce will review
audit results in order to confirm that user e/perience re.uirements have been met.12
3453+5+3(- (

Summary
%$escri*tio(+ *rovide an overall summar of the contents of this document.
,usti-icatio(+ #ome pro+ect participants ma need to know onl the highlights of the
audit, and summari3ing creates that user view. -t also enables the full reader to know
the essence of the document before the e/amine the details.2
<<Begin tet here!!
Audit Sco*e a(d $ime(sio(s
%$escri*tio(+ The Audit #cope and 4imensions section defines the scope of the
audit and the documents and pro+ect activities currentl under review. This section
should also include a description of the audit approach 5audit model', evaluation
criteria, and the .ualifications of the audit team.
,usti-icatio(+ This information provides conte/t for the remaining document and
establishes authorit and audit parameters.2
<<Begin tet here!!
Fu(ctio(al S*eci-icatio( Audit
%$escri*tio(+ The )unctional #pecification Audit section describes the results of
auditing the set of documents that together are called the )unctional #pecification.2
Requirements Analysis Audit
%$escri*tio(+ The 6e.uirements Analsis Audit section describes the results of
auditing the four tpes of re.uirements documents.2
1usi(ess Re2uireme(ts
%$escri*tio(+ The Business 6e.uirements section describes the results of the audit
of the business re.uirements document. This information should include the date of
the audit, the version of the sub+ect re.uirements document, and the list of variations
found between the developed solution and the contents of the re.uirements
document. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
System Re2uireme(ts
%$escri*tio(+ The #stem 6e.uirements section describes the results of the audit of
the sstem re.uirements document. This information should include the date of the
audit, the version of the sub+ect re.uirements document, and the list of variations
found between the developed solution and the contents of the re.uirements
3453+5+3(- +

document. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
&ser Re2uireme(ts
%$escri*tio(+ The "ser 6e.uirements section describes the results of the audit of
the user re.uirements document. This information should include the date of the
audit, the version of the sub+ect re.uirements document, and the list of variations
found between the developed solution and the contents of the re.uirements
document. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
O*eratio(s Re2uireme(ts
%$escri*tio(+ The 7perations 6e.uirements section describes the results of the
audit of the business re.uirements document. This information should include the
date of the audit, the version of the sub+ect re.uirements document, and the list of
variations found between the developed solution and the contents of the
re.uirements document. )or each variation, describe its character. )or each
variation, or set of similar variations, describe its cause.2
<<Begin tet here!!
Conceptual Design Audit
%$escri*tio(+ The Conceptual 4esign 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 sub+ect design document, and the list of variations found
between the developed solution and the contents of the design document. )or each
variation, describe its character. )or each variation, or set of similar variations,
describe its cause.
This section ma also contain the results of a traceabilit audit between the
conceptual design and the previous re.uirements documents.2
<<Begin tet here!!
Logical Design Audit
%$escri*tio(+ The 8ogical 4esign 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 sub+ect design document, and the list of variations found between the
developed solution and the contents of the design document. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.
This section ma also contain the results of a traceabilit audit between the logical
design and the previous re.uirements documents.2
3453+5+3(- .

<<Begin tet here!!
hysical Design Audit
%$escri*tio(+ The *hsical 4esign Audit section describes the results of the audit of
the phsical design document. This information should include the date of the audit,
the version of the sub+ect design document, and the list of variations found between
the developed solution and the contents of the design document. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.
This section ma also contain the results of a traceabilit audit between the phsical
design and the previous re.uirements documents.2
<<Begin tet here!!
Master Project Pla( Audit
%$escri*tio(+ The Master *ro+ect *lan Audit section describes the results of auditing
the set of documents that together are called the Master *ro+ect *lan.2
Development lan Audit
%$escri*tio(+ The 4evelopment *lan 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 sub+ect plan, and the list of variations found between the actual
development activities and resulting developed solution and the activities defined in
the plan. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
Test lan Audit
%$escri*tio(+ The Test *lan 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 sub+ect
plan, and the list of variations found between the actual test activities and resulting
developed solution and the activities defined in the plan. )or each variation, describe
its character. )or each variation, or set of similar variations, describe its cause.2
<<Begin tet here!!
Communication lan Audit
%$escri*tio(+ The Communication *lan 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 sub+ect plan, and the list of variations found between the
actual communication activities and those defined in the plan. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.2
3453+5+3(- -

<<Begin tet here!!
!icrosoft Support lan Audit
%$escri*tio(+ The Microsoft #upport *lan 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 sub+ect plan, and the list of variations found between the
actual support activities and resulting developed solution and the activities defined in
the plan. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
"perations lan Audit
%$escri*tio(+ The 7perations *lan 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 sub+ect plan, and the list of variations found between the actual operations
implementation activities and resulting developed solution and the activities defined
in the plan. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.
This section also contains sub9sections for each of the plans that together comprise
the operations plan. :ach of these sections should also contain the above9stated
information.2
<<Begin tet here!!
Security
<<Begin tet here!!
A/ailability
<<Begin tet here!!
Ca*acity
<<Begin tet here!!
Mo(itori(.
<<Begin tet here!!
Per-orma(ce
<<Begin tet here!!
3453+5+3(- =

Su**ort
<<Begin tet here!!
1ac3u* a(d Reco/ery
<<Begin tet here!!
#nd-$ser Support lan Audit
%$escri*tio(+ The :nd9"ser #upport *lan Audit section describes the results of the
audit of the end9user support plan. This information should include the date of the
audit, the version of the sub+ect plan, and the list of variations found between the
actual support activities and resulting developed solution and the activities defined in
the plan. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
Deployment lan Audit
%$escri*tio(+ The 4eploment *lan Audit section describes the results of the audit of
the deploment plan. This information should include the date of the audit, the
version of the sub+ect plan, and the list of variations found between the actual
deploment activities and resulting developed solution and the activities defined in
the plan. )or each variation, describe its character. )or each variation, or set of
similar variations, describe its cause.2
<<Begin tet here!!
Training lan Audit
%$escri*tio(+ The Training *lan 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
sub+ect plan, and the list of variations found between the actual training activities and
resulting developed solution and the activities defined in the plan. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.2
<<Begin tet here!!
urchasing and %acilities lan Audit
%$escri*tio(+ The *urchasing and )acilities *lan 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 sub+ect plan, and the list of variations found
between &' the actual purchasing activities and 2' the preparation of the facilities and
the resulting developed solution, and the activities defined in the plan. )or each
variation, describe its character. )or each variation, or set of similar variations,
describe its cause.2
<<Begin tet here!!
3453+5+3(- *

!igration lan Audit
%$escri*tio(+ The Migration *lan 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 sub+ect plan, and the list of variations found between the actual migration
activities and resulting developed solution and the activities defined in the plan. )or
each variation, describe its character. )or each variation, or set of similar variations,
describe its cause.2
<<Begin tet here!!
ilot lan Audit
%$escri*tio(+ The *ilot *lan 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
sub+ect plan, and the list of variations found between the actual pilot activities and
resulting developed solution and the activities defined in the plan. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.2
<<Begin tet here!!
&udget lan Audit
%$escri*tio(+ The Budget *lan 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
sub+ect plan, and the list of variations found between the actual budget and resulting
developed solution and the estimated budget defined in the plan. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.2
<<Begin tet here!!
Tools lan Audit
%$escri*tio(+ The Tools *lan 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
sub+ect plan, and the list of variations found between the actual tools used and
resulting developed solution and the tools defined in the plan. )or each variation,
describe its character. )or each variation, or set of similar variations, describe its
cause.2
<<Begin tet here!!
3453+5+3(- @