Académique Documents
Professionnel Documents
Culture Documents
deployment plan?
Outputs
include
is where the release milestone occurs once the team addresses all outstanding issues and ships the product or places it in service
Part
of Project Closure
Construct Verify
software components
and test data users and document the system the system
Convert Train
Install
The
of the work steps for complete deployment, and who does them
The
Creating a deployment plan is essential to creating and installing a configuration management environment. The deployment plan outlines the scope, approach and execution planned for the deployment of the project
deliverables.
The
deployed.
The
Deployment goals and critical success factors Roles and responsibilities of the parties involved in the deployment of the project deliverables
Contingency information
Training plan
Release
Production
Plan
Plan
Describe the activities for a phased implementation or rollout. Track the dates for the release of various function, and/or track the formal review points in the testing cycle of your product. Your release plan may also include the following activities, as appropriate:
Preparation of the environment
Conversion information
Create a Product Implementation Task List. Describe what preparation is required for this new tool or application to operate. Specify any features that need modification to adapt to the new product. Identify the steps necessary to assist the user in preparing for this new product. Deliverables: Production Readiness Checklist
Develop a plan to communicate with all interested parties of this project (stakeholders, sponsors, users, developers)
This planning ensures that everyone who need to be informed about projects activities and results
Use
a tool to record:
owners
Project decisions and reasons
Deliverable:
Issue/Action-Decision Log
Template
Plan
wrong.
Develop
Outline
the approach, activities, and tasks necessary at each point in the deployment.
Deliverable:
the system will replace an existing system, compatibility, conversion, and migration issues must be addressed. Specifically:
Data from an existing system must be carried forward (and possibly converted in format) for the new system. Existing user interfaces (screen formats, commands, etc) must be supported in the new system. All existing application programming interfaces (APIs) must be maintained
Migration from the existing system to the new one must not disrupt end user service for more than a pre-determined amount of time (varies depending on the business). The new system must be capable of operating in parallel with the old system during the migration period. There must be a capability to fall back to the old system, if needed, during the first two weeks of operation. Old archive data may need to be processed on the new system. If it is cryptographically protected, then the encryption keys will need special consideration when migrating
a system into a production environment requires planning and preparation. Technical factors to be considered include :
Users of the system may need to be trained. The production support environment must be prepared and production support staff must be trained and ready to support the system. Production support procedures, including backup, recovery, and problem resolution must be established
systems can never be shut down (example : network and telephony switches) These systems may require new versions of the system to be deployed while the previous version is still running. Upgrading a high-availability system usually requires special architectural considerations
systems must be deployed incrementally, in parts, due to timing or availability issues. the system cannot be deployed all at once, the order in which components must be installed, and the nodes on which they are installed, must be determined.
If
include:
an application is deployed over a period of time, issues which need to be resolved include:
The software must be able to run in a partial configuration Different versions of the software must be capable of coexisting It must be possible to revert back to a prior version of the system in the event that problems with the new system are detected
each category of user, including administration, operators, and end users, identify:
What types of IT systems they use at the present. If this system will bring the first use of IT to any users, either within or external to the organization, flag this as a special requirement that will merit special attention. What new functions will be brought to them by this system. In broad terms, what their training needs will be.
The
The
The
following figure depicts the steps in the planning, design, and implementation of system solution.
The
Logical Design Logical architecture Deployment scenario Deployment Design Deployment architecture Implementation specifications Implementation plans
Deployment Implementation Hardware setup Installation, upgrade, and migration Configuration and customization Development and integration Prototypes and pilots Production rollout
Three
primary issues to consider that come into play before or after the Deployment Phase of a system development project are listed below :