Implementation Plan Template

tukwilagleefulInternet and Web Development

Oct 31, 2013 (3 years and 7 months ago)

44 views




Ministry/Agency Name

Project Name

Project #:

Implementation Plan







Prepared by:

Author's Name

Prepared for:

[Company Name]

Date Submitted:

[Date]


Project Spo
nsor:

Project Sponsor's Name

Client Acceptor:

[if different than Sponsor]

Project Manager:

[Project Manager’s Name]


Document Number:

6450
-
20/Project Number /Implementation

Security Classification: Low

Version:

0.1


Last Updated:

October 31, 2013

Creation Date:

[Date]





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

Last revised:
2013
-
10
-
31


Page
2

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

Table of Contents

Table of Contents
................................
................................
................................
........

2

1.

Purpose

................................
................................
................................
...............

3

1.1.

Releases

................................
................................
................................
................................
......

3

2.

Database Server

................................
................................
................................
..

4

2.1.

Database Server Set
-
up
................................
................................
................................
............

4

2.2.

System Objects
................................
................................
................................
...........................

4

2.3.

Schema Objects

................................
................................
................................
.........................

4

2.4.

Ministry Objects

................................
................................
................................
..........................

5

2.5.

Loading Data

................................
................................
................................
...............................

5

2.6.

Clean
-
up

................................
................................
................................
................................
......

5

3.

Application Server

................................
................................
...............................

6

3.1.

Directory Structure and Files

................................
................................
................................
....

6

3.2.

Icons

................................
................................
................................
................................
.............

6

3.3.

Admin Shell Scripts

................................
................................
................................
....................

6

3.4.

Forms/Libraries/Menus and Reports
................................
................................
.......................

6

3.5.

Configuration

................................
................................
................................
...............................

7

4.

Client

................................
................................
................................
...................

8

5.

Handover

................................
................................
................................
.............

9

5.1.

Production Environment

................................
................................
................................
............

9

5.2.

Support
................................
................................
................................
................................
.........

9

5.3.

Communications

................................
................................
................................
.........................

9

5.4.

Training

................................
................................
................................
................................
........

9

5.5.

Documentation
................................
................................
................................
............................

9

5.6.

Security

................................
................................
................................
................................
......
10

Revi sion Log

................................
................................
................................
.............

11

Appendices

................................
................................
................................
...............

12

Approval

................................
................................
................................
...................

13


Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
3

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

1.

Purpose

This document references all the tasks necessary to implement an application at the Ministry. It
includes information required to:



Configure the database instance (including security, object creation and
converted data loads); and



Deploy the
application (including 9iAS specific).


1.1.

Releases


Release 1


Release 2



Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
4

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

2.

Data
base Server

2.1.

Database Server Set
-
up



2.2.

System Objects

Schemas/Users


Application Schema Creation


Schema

Objects Owned








Role and System Privileges


Manual Grants


Security



2.3.

Schema Objects

All Database Objects m
ust 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
u
ses 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 sy
nonyms associated with the
tables.

Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
5

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

Views and their Grants and Synonyms

Connect as schema owner and create all the views generated from the repository.

Stored Packages

To create the stored packages connect as Schema owner and run the following scripts:



@exa
mple_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

Loadi
ng Meta Data


Loading Converted Data


Reset Sequences


2.6.

Clean
-
up



Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
6

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

3.

Application Server

This section contain
s the directory structure and files for [Application Name] Release [Number]

3.1.

Directory Structure and Files


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 d
irectory:











3.2.

Icons

The icons are up and running. The following files have to be in the images directory:











3.3.

Admin Shell Scripts



3.4.

Forms/Libraries/Menus and Reports



Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
7

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

3.5.

Configuration

Oracle Application Server


Oracle Reports Server


Printer Setup


Unix Star
tup files



Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
8

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

4.

Client

Refer to the Technical Architecture document for desktop specifications. Standard Ministry
practice dictates that the application will be added to the START menu.


Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
9

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

5.

Handover


5.1.

Production Environment


Checkpoint

To be confirmed by

Data confirmed











5.2.

Support


Checkpoint

To be confirmed by

Data confirmed











5.3.

Communications


Checkpoint

To be confirmed by

Data c
onfirmed











5.4.

Training


Checkpoint

To be confirmed by

Data confirmed











5.5.

Documentation


Checkpoint

To be confirmed by

Data confirmed







Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
10

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

Checkpoint

To be confirmed by

Data confirmed





5.6.

Security


Checkpoint

To be confirmed by

Data confirmed












Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
11

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

Revision Log

Date

Version

Change Reference

Author

Reviewed by

[yyyy
-
mm
-
dd]

0.1































Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
12

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

Appendices

Enter content here.

Implementation Plan


Project Name

Last revised:
2013
-
10
-
31


Page
13

of
13

c:
\
program files
\
neevia.com
\
docconverterpro
\
temp
\
nvdc
\
2c45fd4b
-
f42b
-
4fd8
-
901f
-
a56903b209b0
\
tukwilagleeful_2545
796d
-
4ae2
-
4915
-
a69f
-
577114ec5c1d.doc

Security Classification: Low

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 project’s 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

Author's Name

[Title]

[Organization]










Accepted by

Signature

Date

[Client Acceptor’s
Name]

[Title]

[Organization]








Approved by

Signature

Date

[Client Approver’s Name]

[Title]

[Organization]







[Client Approver’s Name]

[Title]

[Organization]







[Project Manager’s Name]

[Title]

[Organization]







[IMG Approver’s Name]

[Tit
le]

[Organization]