Académique Documents
Professionnel Documents
Culture Documents
Project Name
Project #:
Implementation Plan
Prepared by:
Prepared for:
Date Submitted:
Author's Name
[Company Name]
[Date]
Project Sponsor:
Client Acceptor:
Project Manager:
About this template: This template uses built in styles to assist the author in preparing
the layout of the document. For assistance with styles, please contact the Project Support
Office:
Implementation Plan
Project Name
Table of Contents
Table of Contents................................................................................................................ 2
1.
Purpose........................................................................................................................ 3
1.1. Releases.........................................................................................................................3
2.
Database Server.......................................................................................................... 4
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
3.
Application Server...................................................................................................... 6
3.1.
3.2.
3.3.
3.4.
3.5.
4.
Client............................................................................................................................ 8
5.
Handover..................................................................................................................... 9
5.1.
5.2.
5.3.
5.4.
5.5.
5.6.
Production Environment.................................................................................................9
Support...........................................................................................................................9
Communications.............................................................................................................9
Training........................................................................................................................... 9
Documentation................................................................................................................9
Security......................................................................................................................... 10
Revision Log..................................................................................................................... 11
Appendices....................................................................................................................... 12
Approval............................................................................................................................ 13
Page 2 of 13
Security Classification: Low
Implementation Plan
1.
Project Name
Purpose
This document references all the tasks necessary to implement an application at the Ministry. It
includes information required to:
1.1.
Releases
Release 1
Release 2
Page 3 of 13
Security Classification: Low
Implementation Plan
2.
Database Server
2.1.
2.2.
System Objects
Project Name
Schemas/Users
Schema
Objects Owned
Manual Grants
Security
2.3.
Schema Objects
All Database Objects must be generated out of Oracle Designer/2000. Make sure the newest
version of the repository is loaded and available. The objects must be generated for each
individual schema owner. I.e. generate all of the objects and associated grants for the required
uses in turn.
Tables and their Constraints, Sequences, Indexes, Triggers, Grants and Synonyms
Connect as schema owner and create all the tables generated from the repository. This will also
create the constraints, sequences, indexes, triggers, grants and synonyms associated with the
tables.
Page 4 of 13
Security Classification: Low
Implementation Plan
Project Name
@example_script1.sps
@example_script2.spb
Ensure that all packages are valid by checking in USER_OBJECTS for those objects with status
of INVALID. If any are invalid, execute ALTER <object name> COMPILE;
2.4.
Ministry Objects
Stored Packages
2.5.
Loading Data
Reset Sequences
2.6.
Clean-up
Page 5 of 13
Security Classification: Low
Implementation Plan
3.
Project Name
Application Server
This section contains the directory structure and files for [Application Name] Release [Number]
3.1.
HTML
The following files have to be in the HTML directory:
img
The following images are used by the html pages and should be saved in the image directory:
3.2.
Icons
The icons are up and running. The following files have to be in the images directory:
3.3.
3.4.
Page 6 of 13
Security Classification: Low
Implementation Plan
3.5.
Project Name
Configuration
Printer Setup
Page 7 of 13
Security Classification: Low
Implementation Plan
4.
Project Name
Client
Refer to the Technical Architecture document for desktop specifications. Standard Ministry
practice dictates that the application will be added to the START menu.
Page 8 of 13
Security Classification: Low
Implementation Plan
5.
Handover
5.1.
Production Environment
Checkpoint
5.2.
To be confirmed by
Data confirmed
To be confirmed by
Data confirmed
To be confirmed by
Data confirmed
To be confirmed by
Data confirmed
Training
Checkpoint
5.5.
Data confirmed
Communications
Checkpoint
5.4.
To be confirmed by
Support
Checkpoint
5.3.
Project Name
Documentation
Checkpoint
Page 9 of 13
Security Classification: Low
Implementation Plan
Checkpoint
5.6.
Project Name
To be confirmed by
Data confirmed
To be confirmed by
Data confirmed
Security
Checkpoint
Page 10 of 13
Security Classification: Low
Implementation Plan
Project Name
Revision Log
Date
[yyyy-mm-dd]
Version
0.1
Change Reference
Author
Reviewed by
Page 11 of 13
Security Classification: Low
Implementation Plan
Project Name
Appendices
Enter content here.
Page 12 of 13
Security Classification: Low
Implementation Plan
Project Name
Approval
This document has been approved as the official Implementation Plan for the Project Name
project.
Following approval of this document, changes will be governed by the projects change
management process, including impact analysis, appropriate reviews and approvals, under the
general control of the Master Project Plan and according to Project Support Office policy.
Prepared by
Signature
Date
Signature
Date
Signature
Date
Author's Name
[Title]
[Organization]
Accepted by
[Client Acceptors Name]
[Title]
[Organization]
Approved by
[Client Approvers Name]
[Title]
[Organization]
[Client Approvers Name]
[Title]
[Organization]
[Project Managers Name]
[Title]
[Organization]
[IMG Approvers Name]
[Title]
[Organization]
Page 13 of 13
Security Classification: Low