32 Best Practices & Methodology for Electronic Software Distribution & Operating System Provisioning
Identification of the ESD site processes required to build, test, and
distribute
ESD site processes required to build, test and distribute are identified is not a
work product, but a task outcome where all ESD site processes required to build,
test, and distribute are identified.
Determination of the request category
A requested ESD change may be specific to one function, such as packaging
new software, or may require the execution of several of the functions listed in
Table 2-1 on page 24 and Table 2-2 on page 24. During this step, the
determination of all functions, which must be performed in support of a given
ESD Change Request, is determined.
2.4.4 Develop backout and recovery plan
The purpose of the develop backout and recovery plan activity of the ESD
Change Request process is to develop and validate a backout and recovery plan
in case the ESD change fails. It also determines how the proposed change may
be reversed in case a back out from the change is required. It also tests and
validates the backout plan to ensure it is possible to use the backout and
recovery plan to back out of the proposed change in case the backout is required
in the future.
Tasks
The following tasks are performed during the develop backout and recovery plan
activity:
򐂰 Conducting backup and recovery assessment
This is performed by the Offering Architect, assisted by the Delivery Project
Manager and the Infrastructure Specialist.
The purpose of this task is to determine how the proposed change may be
reversed in case a backout from the change is required.
򐂰 Developing the backout plan
This is performed by the Offering Architect, assisted by the Delivery Project
Manager and the Infrastructure Specialist
The purpose of this task is to develop a backup plan to ensure that the
proposed change may be undone in case it negatively impacts the IT
environment, or if for any business or technical reason a backout from the
change is required. Established Backup and Recovery techniques may be
tailored and used for this purpose.
Chapter 2. Electronic Software Distribution Change Request process 33
򐂰 Validating the backout plan
This is performed by the Offering Architect, assisted by the Delivery Project
Manager and the Infrastructure Specialist.
The purpose of this task is to test and validate the backup plan to ensure that
it is in fact possible to use the backup plan to back out of the proposed
change in case the back out is required in the future.
Inputs and outputs
Input from any of the following external processes may be required during the
develop back out and recovery plan activity of the ESD Change Request
process:
򐂰 Change order
򐂰 IT management requirements
򐂰 Solution recovery strategy
Output from the develop back out and recovery plan activity of the ESD Change
Request process will produce:
򐂰 Collected data
򐂰 Identified request category
򐂰 Solution recovery strategy
򐂰 Validated backout plan
The following section is a description of the inputs to and outputs from the
develop back out and recovery plan activity that have not previously been
defined in any other section of this IBM Redbook.
Collected data
Collected data
is not a work product but a task outcome where all data required,
including backup media, backup interval, recovery requirements, recovery time
objective, recovery point objective, and so on, are collected.
Identified request category
A requested ESD change may be specific to one function, such as Prepare New
ESD package, or may require the execution of several of the functions listed in
Table 2-1 on page 24 and Table 2-2 on page 24. During this step, the
determination of all functions, which must be performed in support of a given
ESD Change Request, is performed.

Get Best Practices and Methodology for Electronic Software Distribution and Operating System Provisioning in an On Demand Business now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.