<PROJECT NAME> REQUIREMENTS MANAGEMENT PLAN

Version <1.0> <mm/dd/yyyy>

[Insert appropriate Disclaimer(s): E.g.: For Internal CDC Use Only, Sensitive B t Unclassi!ie"#

<Project Name>

VERSION HISTORY
[Provide information on how the development and distribution of the Requirements Management Plan, up to the final point of approval, was controlled and tracked. se the table below to provide the version number, the author implementin! the version, the date of the version, the name of the person approvin! the version, the date that particular version was approved, and a brief description of the reason for creatin! the revised version."
Version # 1.0 Implemented B <#uthor name> Re!ision "#te <mm/dd/yy> Appro!ed B <name> Appro!#l "#te <mm/dd/yy> Re#son Initial Requirements Management Plan draft

UP Templ#te Version$ 11/30/06

Page 2 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Note to the Author

['his document is a template of a (e)uirements *ana!ement Plan 'emplate document for a pro+ect. 'he template includes instructions to the author, boilerplate te,t, and fields that should be replaced with the values specific to the pro+ect. -lue italici.ed te,t enclosed in s)uare brackets %[te,t"& provides instructions to the document author, or describes the intent, assumptions and conte,t for content included in this document. -lue italici.ed te,t enclosed in an!le brackets %<te,t>& indicates a field that should be replaced with information specific to a particular pro+ect. 'e,t and tables in black are provided as boilerplate e,amples of wordin! and formats that may be used or modified as appropriate to a specific pro+ect. 'hese are offered only as su!!estions to assist in developin! pro+ect documents/ they are not mandatory formats.

0hen usin! this template for your pro+ect document, it is recommended that you follow these steps1 $. (eplace all te,t enclosed in an!le brackets %i.e., <Pro+ect 2ame>& with the correct field values. 'hese an!le brackets appear in both the body of the document and in headers and footers. 'o customi.e fields in *icrosoft 0ord %which display a !ray back!round when selected&1 a. 3elect 4ile>Properties>3ummary and fill in the 'itle field with the 5ocument 2ame and the 3ub+ect field with the Pro+ect 2ame. b. 3elect 4ile>Properties>6ustom and fill in the 7ast *odified, 3tatus, and 8ersion fields with the appropriate information for this document. c. #fter you click 9: to close the dialo! bo,, update the fields throu!hout the document with these values by selectin! ;dit>3elect #ll %or 6trl<#& and pressin! 4=. 9r you can update an individual field by clickin! on it and pressin! 4=. 'his must be done separately for >eaders and 4ooters. ?. *odify boilerplate te,t as appropriate to the specific pro+ect. @. 'o add any new sections to the document, ensure that the appropriate header and body te,t styles are maintained. 3tyles used for the 3ection >eadin!s are >eadin! 1, >eadin! ? and >eadin! @. 3tyle used for boilerplate te,t is -ody 'e,t. A. 'o update the 'able of 6ontents, ri!ht<click and select B pdate fieldC and choose the option< B pdate entire tableC D. -efore submission of the first draft of this document, delete this B2otes to the #uthorC pa!e and all instructions to the author, which appear throu!hout the document as blue italici.ed te,t enclosed in s)uare brackets."
Page 3 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

TABLE O% &ONTENTS
1 INTRODUCTION......................................................................................................................5 1.1 Purpose of The Requirements Management Plan..............................................................5 2 REQUIREMENTS MANAGEMENT OVERVIEW...............................................................5 2.1 Organization, Responsibilities, and Interfa es...................................................................5 2.2 Tools, !n"ironment, and Infrastru ture..............................................................................5 3 REQUIREMENTS MANAGEMENT......................................................................................5 #.1 $ssumptions%&onstraints....................................................................................................5 #.2 Requirements 'efinition....................................................................................................5 #.# Requirements Tra eabilit(..................................................................................................5 #.) *or+flo,s and $ ti"ities...................................................................................................5 #.5 &hange Management..........................................................................................................REQUIREMENTS MANAGEMENT PLAN APPROVAL.....................................................7 APPENDIX A: REFERENCES...................................................................................................8 APPENDIX B: KE TERMS......................................................................................................! APPENDIX C: REQUIREMENTS DEFINITION TEMPLATE..........................................1" APPENDIX D: REQUIREMENTS TRACEABILIT TEMPLATE...................................11

Page 4 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

' INTRO"U&TION
1.1 PURPOSE O% THE REQUIREMENTS MANAGEMENT PLAN [Provide the purpose of the (e)uirements *ana!ement Plan. 'his document should be tailored to fit a particular pro+ectEs needs." The Requirements Management lan is used to do!ument the ne!essar" information required to effe!ti#el" manage ro$e!t requirements from definition% through tra!ea&ilit"% to deli#er". The Requirements Management Plan is !reated during the Planning Phase of the ro$e!t. Its intended audien!e is the ro$e!t manager% ro$e!t team% ro$e!t s onsor and an" senior leaders 'hose su ort is needed to !arr" out the lan.

( REQUIREMENTS MANAGEMENT OVERVIE)

2.1 ORGANI*ATION+ RESPONSIBILITIES+ AN" INTER%A&ES [5escribe here who is !oin! to be responsible for performin! the various activities described in the re)uirements workflows defined later in this document." TOOLS+ ENVIRONMENT+ AN" IN%RASTRU&TURE [5escribe the computin! environment and software tools to be used in fulfillin! the (e)uirements *ana!ement functions throu!hout the pro+ect or product lifecycle. 5escribe the tools and procedures that will be used to control the versionin! of the (e)uirements items !enerated throu!hout the pro+ect or product lifecycle."

2.2

, REQUIREMENTS MANAGEMENT
3.1 ASSUMPTIONS-&ONSTRAINTS [5efine any assumptions and/or constraints taken into account when definin! re)uirement for this section of this document." REQUIREMENTS "E%INITION [5escribe the approach and tools that the pro+ect will use to define the specifications of the pro+ect re)uirements. ;,plicitly describin! pro+ect re)uirements promotes the correct and efficient development and delivery of that re)uirement. #ppendi, 6 is for a (e)uirements 5efinition 7o! that the pro+ect team can adapt and populate for this purpose. % se the 656 P (e)uirements 5efinition Practices Fuide as reference to complete this section.&" REQUIREMENTS TRA&EABILITY [5escribe the approach and tools that the pro+ect will use to trace the pro+ect re)uirements throu!hout the systems life cycle. 'he approach that is followed should enable the pro+ect team to ensure that the pro+ect delivers the pro+ect re)uirements e,actly as specified and that they fulfill the pro+ect re)uirements. #ppendi, 5 is for a (e)uirements 'raceability *atri, that the pro+ect team can adapt and populate for this purpose. % se the 656 P (e)uirements 'raceability Practices Fuide as reference to complete this section.&" )OR.%LO)S AN" A&TIVITIES [5escribe the workflows and activities that apply to mana!in! re)uirements.
Page ( of 11 [$nsert appropriate disclaimer%s&"

3.2

3.3

3.#

<Project Name>

5escribe review activities, includin! review ob+ectives, responsibilities, timin!, and procedures." 3.5 &HANGE MANAGEMENT [5escribe the process by which problems and chan!es are submitted, reviewed, and resolved. 'his should include the process for ne!otiatin! re)uirements chan!es with customers, and any contractual processes, activities, and constraints. 5escribe the membership of the 6han!e 6ontrol -oard %66-& and procedures for processin! chan!e re)uests and approvals to be followed by the 66-."

Page 6 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Re/0irements M#n#1ement Pl#n Appro!#l

The undersigned a!)no'ledge the" ha#e re#ie'ed the <Pro+ect 2ame> Re/0irements M#n#1ement Pl#n and agree 'ith the a roa!h it resents. *hanges to this Requirements Management Plan 'ill &e !oordinated 'ith and a ro#ed &" the undersigned or their designated re resentati#es. [7ist the individuals whose si!natures are re)uired. ;,amples of such individuals are Pro+ect 3ponsor, -usiness 3teward, 'echnical 3teward and Pro+ect *ana!er. #dd additional si!nature lines as necessary." +ignature, Print .ame, Title, Role, +ignature, Print .ame, Title, Role, +ignature, Print .ame, Title, Role, -ate, -ate, -ate,

Page / of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Appendi2 A$ Re3eren4es
[$nsert the name, version number, description, and physical location of any documents referenced in this document. #dd rows to the table as necessary." The follo'ing ta&le summari0es the do!uments referen!ed in this do!ument. "o40ment "es4ription Lo4#tion N#me #nd Version <5ocument [Provide description of the < (7 or 2etwork path where 2ame and document" document is located> 8ersion 2umber>

Page 1 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Appendi2 B$ .e Terms
[$nsert terms and definitions used in this document. #dd rows to the table as necessary. 4ollow the link below to for definitions of pro+ect mana!ement terms and acronyms used in this and other documents. http1//www?.cdc.!ov/cdcup/library/other/help.htm The follo'ing ta&le ro#ides definitions for terms rele#ant to this do!ument. Term [$nsert 'erm" [$nsert 'erm" [$nsert 'erm" "e3inition [Provide definition of the term used in this document." [Provide definition of the term used in this document." [Provide definition of the term used in this document."

Page 2 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Appendi2 &$ Re/0irements "e3inition Templ#te

[8isit the 656 P website for the most updated version of the 656 (e)uirements 5efinition 'emplate. http: !!!"c#c"go$ c#cup " P

Page 10 of 11 [$nsert appropriate disclaimer%s&"

<Project Name>

Appendi2 "$ Re/0irements Tr#4e#5ilit Templ#te

[8isit the 656 P website for the most updated version of the 656 (e)uirements 'raceability 'emplate. http: !!!"c#c"go$ c#cup " P

Page 11 of 11 [$nsert appropriate disclaimer%s&"