<Company Name>

IT Operations
Data Lifecycle Management Plan

Version <1.0>

[Note: The following template is provided for use with the IBM Tivoli Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the
author and should be deleted before publishing the document. A paragraph entered following this style
will automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for
this document. After closing the dialog, automatic fields may be updated throughout the document by
selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must
be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and
the field contents. See Word help for more information on working with fields.]
IT Operations Version: <1.0>
Data Lifecycle Management Plan Date: <dd/mmm/yy>
<document identifier>

Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>

Confidential <Company Name>, 2018 Page 2

IT Operations Version: <1.0>
Data Lifecycle Management Plan Date: <dd/mmm/yy>
<document identifier>

Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms, and Abbreviations 3
1.4 References 3
1.5 Overview 3

2. Data Lifecycle Model 3

3. Media 3

4. Backup Plan 3

5. Data Security 3

6. Supporting Information 3

Confidential <Company Name>, 2018 Page 3

IT Operations Version: <1.0>
Data Lifecycle Management Plan Date: <dd/mmm/yy>
<document identifier>

Document Title
1. Introduction
[The introduction of the Document_Title (DT) provides an overview of the entire DT. It includes the
purpose, scope, definitions, acronyms, abbreviations, references, and overview of the DT.]
[Note: The DT document captures the complete software requirements for the system, or a portion of the
system. Following is a typical DT outline for a project using only traditional, natural-language style
requirements—with no use-case modeling. It captures all requirements in a single document. For a
template of an DT using use-case modeling, see rup_DTuc.dot.]
[Many different arrangements of an DT are possible. Refer to [IEEE830-1998] for further elaboration of
these explanations, as well as other options for DT organization.]
1.1 Purpose
[Specify the purpose of this DT. The DT fully describes the external behavior of the application or
subsystem identified. It also describes nonfunctional requirements, design constraints, and other factors
necessary to provide a complete and comprehensive description of the requirements for the software.]
1.2 Scope
[A brief description of the scope of the document. Identify what it includes and what it excludes.]
1.3 Definitions, Acronyms, and Abbreviations
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly
interpret the DT. This information may be provided by reference to the project’s Glossary.]
1.4 References
[This subsection provides a complete list of all documents referenced elsewhere in the DT. Identify each
document by title, report number if applicable, date, and publishing organization. Specify the sources
from which the references can be obtained. This information may be provided by reference to an appendix
or to another document.]
1.5 Overview
[This subsection describes what the rest of the DT contains and explains how the document is organized.]
2. Data Lifecycle Model
[Describe the overall model of how data transitions from active use through various stages to eventual
disposal.]
3. Media
[Identify the types of media to be used at various stages in the data lifecycle.]
4. Backup Plan
[Describe the overall plan for backing up data and providing restoration.]
5. Data Security
[Describe how data security classification is determined during lifecycle transitions.]

6. Supporting Information
[The supporting information makes the DT easier to use. It includes:

Confidential <Company Name>, 2018 Page 4

IT Operations Version: <1.0>
Data Lifecycle Management Plan Date: <dd/mmm/yy>
<document identifier>

 Table of contents
 Index
 Appendices
These may include use-case storyboards or user-interface prototypes. When appendices are included, the
DT should explicitly state whether or not the appendices are to be considered part of the requirements.]

Confidential <Company Name>, 2018 Page 5