Deployment Plans

1
Deployment Plans

• Produced by Precision Logic
• Patrick McQuay
• Joe Bretz
• Chris Renaud

2
Deployment Plan Presentation Agenda

• Definition
• Objectives
• Benefits
• Commercial Company Deployment plan
• Discussion on Issues affecting your Deployment
  Plan
• System Project Deployment Plan
• Example
• Departmental Deployment Plan
• Example
• Questions?

3
Definition

• The deployment plan is the documents that
  outline plans for deploying all or part of a
  completed application to its production
  environment.
• Note
• This is a living document that is developed
  incrementally and iteratively in parallel with
  other documents.

4
Objectives

• Delivering the final version of all deliverable
  work products to the customer organization.
• Deploying the
• Application to its production environments.
• Hardware components to their production
  environments.
• Databases to their hardware components.
• Deploying the remaining software components to
  their hardware components.
• Notifying the user organizations regarding the
  readiness of the application for use.

5
Benefits

• It decreases the risks associated with the
  deployment activity.
• Having an easy to follow plan, increases worker
  productivity during the deployment
• Increases confidence when deploying system

6
Commercial Company Deployment Plan

• Application Deployment
• Documentation Delivery
• Application Delivery
• Application Installation
• Application Tuning
• Data Component Deployment
• Documentation Delivery
• Data Component Delivery
• Data Component Installation
• Database Loading
• Database Tuning
• Hardware Component Deployment
• Documentation Delivery
• Hardware Component Delivery
• Hardware Component Installation
• Hardware Component Configuration
• Software Component Deployment
• Documentation Delivery

• Front Matter
• Title Page
• Name
• Version
• Customer Organization
• Development Organization
• Executive Overview
• Information Page
• Revision History
• Approval Signatures
• Location of Signed Original
• Distribution List
• Table of Contents
• Table of Figures
• Introduction
• Document Definition
• Document Objectives
• Intended Audience
• References

7
Discussion

• Broader issues?
• Clients range greatly in sophistication
• Consider your clients and their business
• What sort of installation files should be
  provided?
• Web apps database script, package for web files
• Stand-alone apps MSI, database/connection
  scripts
• Network apps MSI, database/connection scripts
• For a system project that can not be deployed by
  the student group right away, what sort of
  demonstration could be devised?
• gt?

8
The Your System Project guide should contain

• Step-by-step instructions on how to put the
  system into production
• It should include information on
• Minimum hardware requirements
• Type of operating system needed
• Servers and containers for theapplication and
  database
• Installing the database, including how to run any
  scripts
• How to install the application itself. This might
  include deploying to an ISP.

9
(No Transcript)
10
Deployment Guide for Departmental Use

• Deployment guide that would allow Facility to
  show off your projects at special events and to
  visiting dignitaries.
• Basically How to do a Quick and Dirty Local
  Install
• May be the same as your Clients Deployment Guide

11
(No Transcript)
12
Questions?
13
References

• Open Process Framework, by Donald Firesmith,
  http//www.donald-firesmith.com/Components/WorkPro
  ducts/DeploymentSet/DeploymentPlan/DeploymentPlan.
  html