Pennsylvania Department of Public Welfare

sleeperhihatΔιαχείριση

7 Νοε 2013 (πριν από 3 χρόνια και 11 μήνες)

119 εμφανίσεις








Pennsylvania

Department of Public Welfare


Office of Information Systems





Enterprise Data Warehouse

Information Delivery Application

Guidelines for Remote Development


Version 1.0






July 27, 2004







Page
2

of
11

DPW Business and Technical Standards Document

Revised 07/27/04

sleeperhihat_41cf32d7
-
c4e0
-
434e
-
8d45
-
deaef750e0f6.docx


Table of Contents



Introduction

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

3

Purpose

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

3

Major Project Phases

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

5

Deliverable to

OIS

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

9

Document Change Log

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

11












Page
3

of
11

DPW Business and Technical Standards Document

Revised 07/27/04

sleeperhihat_41cf32d7
-
c4e0
-
434e
-
8d45
-
deaef750e0f6.docx



Enterprise Data Warehouse Information Delivery
Application Guidelines for Remote Development

Introduction

This document is intended to serve as an agreement between remote developers and OIS, Division of
Enterprise Knowledge Management (DEKM) regarding
responsibilities within the major phases of the
Enterprise Data Warehouse (EDW) Information Delivery application development lifecycle. It is aimed at
identifying resource requirements given Program Office needs, their future vision for the warehouse, and

meets the Division of Knowledge Management’s goal of balancing work assignments in order to serve
multiple program office development needs.


A responsibility matrix has been assigned to each task and lists which party is

a)

fully responsible for the task

b)

pr
imarily responsible for the task

c)

an input to completing the task

d)

reviewing a document/deliverable

e)

and lastly, whether an informational document or deliverable is completed at the completion of
that task.


This document should be periodically reviewed in o
rder to determine if the roles and responsibilities
matrices are accurate given changing project dynamics.


The Division of Enterprise Knowledge Management conducts a Knowledge Management Technical
meeting which takes place every Thursday from 2:30
-
3:00pm
in the Willow Oak Building. This meeting is
intended to identify and resolve all issues which relate to Knowledge Management projects


this
includes Geographic Information Systems (GIS), Enterprise Content Management (ECM), Information
Delivery, and the
Enterprise Data Warehouse (EDW).

Purpose

The purpose of this document is to

define roles and responsibilities for the process of developing, testing,
implementing and training new or existing applications for information delivery as well as conducting the
monthly refresh of EDW applications.





Page
4

of
11

DPW Business and Technical Standards Document

Revised 07/27/04

sleeperhihat_41cf32d7
-
c4e0
-
434e
-
8d45
-
deaef750e0f6.docx


Below is a diagram of the EDW System Landscape.


















Production

Database

MARS

Development

Database and
Cognos Web

SATURN

Quality Assurance, Test for
Production & Monthly Database
Update

Transport

Transport

JUPITER


Training and
Sandbox Database

Transport

MARS


Transport

Cognos Web

Production

NEPTUNE




Page
5

of
11

DPW Business and Technical Standards Document

Revised 07/27/04

sleeperhihat_41cf32d7
-
c4e0
-
434e
-
8d45
-
deaef750e0f6.docx


Major Project Phases

This section will outline the major tasks included within the following major EDW phases:
Monthly
Refresh, New Development, Testing, Maintenance/Error resolution, and Training/Implementation.
Please note that, for the most part, the tasks outlined below are intended to be completed in sequential
order. The following key has been used to desig
nate responsibility for each task:


X


Full Responsibility

P


Primary Responsibility

I


Input to Task

R


Documentation Review

N


No responsibility

Info


Informational Document Delivered

Tasks in

Bold

require a deliverable be submitted
to OIS


Monthly Refresh

The following major tasks will be performed during this phase:

Data Warehouse Activities

Ref

Task

OIS Tasks

Remote Tasks

A.1.1

Create correct extract files

I

X

A.1.2

Provide data for dimension table
updates which
pertain to the project

I

P

A.1.3

FTP extract files to data warehouse server

N

X

A.1.4

Notify DEKM when new codes are added for Lookup
tables

P

I

A.1.5a

Update dimension tables in Dev if new codes are
found

I

P

A.1.5b

Update dimension
tables in TFP & DEV if new codes
are found

X

I

A.1.6

Load base tables in TFP

P

I

A.1.7

Run script to obtain record counts and run times

P

I

A.1.8

Validate data in the base tables

I

P

A.1.9

Load any report tables in TFP

P

I

A.1.10

Validate data in
the report tables

I

P

A.1.11

Run script to obtain record counts and run times

P

I

A.1.12

Move data (base tables, report tables, and
dimension table changes) from TFP to production

P

I

A.1.13

Run the validation script

P

I

Information Delivery
Activities

Ref

Task

OIS Tasks

Remote Tasks

A.2.1

Update model fields with new date range

I

P

A.2.2

Update dimensions to accommodate new codes

P

I

A.2.3

Build cubes

P

I

A.2.4

Validate contents of each cube

I

P

A.2.5

Move cubes to production

P

I




Page
7

of
11


DPW Business and Technical Standards

Revised
07/27/04

EDW Procedures for Remote Development
.do
c

Requirements and Design


New or Revisions to Production

The following major tasks will be performed during this phase:

Ref

Task

OIS Tasks

Remote Tasks

B.1.1

Initial requirements gathering/source identification

I

X

B.1.2

Requirements gathering and design

meetings

I

X

B.1.3

Identify Data fields and where reports will be from
(DW or operational)

I

P

B.1.4

Develop Functional Requirements deliverable

R

X

B.1.5

Develop GSD General System Design

(may combine
with DSD for a revision or small project)

N

X

B.1.6

Impact analysis of new requirements on existing logic

I

P

B.1.7

Signoff for GSD

R

X

B.2.1

New logic design and testing plan

I

X

B.2.2

Impact analysis of new logic on existing ETL
applications

P

I

B.2.3

Develop DSD Detailed System Design

R

X

B.2.3a

Develop New Logic Design for Transformation
Specification Deliverable

I/R

P

B.2.3b

Develop New Logic Design for Test Plan
Deliverable

I/R

P

B.2.3c

Develop New Logic Design for Metadata
Documents Deliverable

I/R

P

B.2.3d

Develop Initial
Communications Plan

R

X

B.2.4

Signoff for Requirements and DSD

R

X





Page
8

of
11


DPW Business and Technical Standards

Revised
07/27/04

EDW Procedures for Remote Development
.do
c

Information Delivery Component Development

The following major tasks will be performed during this phase:

Ref

Task

OIS Tasks

Remote Tasks

C.3.1

Create HNET compliant logical/physical data models
[ER diagram and design deliverable]
(If separate database
structures are necessary for reporting apps)

I

P

C.3.2

Submit Data Dictionary Add Form to DEKM liaison

I

P

C.3.3

Submit Database Request for
Services to DEKM
liaison

I

P

C.3.4

Implement physical model in development database
environment

P

I

D.5.1

New ID component design and development

N

X

D.5.2

Impromptu catalog design, development, and
integration into enterprise catalog

R

P

D.5.3

Validation of new ID component design

I

X

D.5.4

Determine and Complete
Security/Capacity/Refresh Strategies Document

R

X

D.5.5

Complete Test Package

I

X

D.5.6

ETL/ID Component Signoff from Program Office

R

X

D.5.7

Create Help Doc and Technical
Specification for
each application

R

X

D.5.8

Update metadata and operational documentation

R

X

D.5.9

Submit new capacity plan or incorporate into
existing project capacity plan

I

X


Training and Implementation

The following major tasks will be performed

during this phase:

Ref

Task

OIS Tasks

Remote Tasks

E.1.1

Implement Metadata

P

I

E.1.2

Provide
Upfront Entry Names including Folder
and Application Descriptions

I

P

E.1.2

Implement new ETL and ID components

P

I

E.1.3

Establish Update Schedule and
Dependencies with
ETL and app generation staff

I

P

E.1.4

Provide validation scripts for PROD

I

P

E.1.5

Implement Web Pages

X

N

E.1.6

Develop Flash or other announcements detailing new
functionality

X

N

E.2.1

Update training manuals and course curricula

P

I

E.2.2

Develop on
-
line courses

P

I

E.2.3

Conduct new user and refresher training

P

I

E.3.1

Communicate with users to increase use and visibility
of the warehouse

I

P




Page
9

of
11


DPW Business and Technical Standards

Revised
07/27/04

EDW Procedures for Remote Development
.do
c

Deliverable to OIS

The following deliverables will be given to OIS during the
phases identified above.


Deliverable/Ref

Description

Phase

Functional Requirements
Document / B.1.4

Document outlining the
business questions that need
to be supported by the
system, their level of criticality
and their level of effort.

Requirements &
Design

General Systems Design /
B.1.5

This document provides a
high level systems design.
For small projects, this may
be combined into the DSD.

Requirements & Design

Detailed Systems Design /
B.2.3

This document provides a
detailed plan of how the
system being designed will
meet the requirements
outlined in the requirements
documents. For information
delivery, document should
outline reports to be created
and what data will be needed
for each report and highlight
the measures, dimensions
and detail
s for each report.

Requirements & Design

Test Plan / B.2.3b

Document outlining how the
report or cube will be tested,
what the specific test scripts
will be and who will be
involved in the testing.

Requirements & Design

Metadata Document / B.2.3c
& D.5.8

The current standard for
metadata submission is
comprised of updating an
Access DB for tables and
separate MS Word documents
for Cubes, Reports, and
Maps. This provides the
information necessary to
update the metadata
repository.

Requirements & Design

Tra
ining/Implementation

Communications Plan /
B.2.3d

This document provides
detailed information on the
means of communication
that will be used to notify
Requirements & Design




Page
10

of
11


DPW Business and Technical Standards

Revised
07/27/04

EDW Procedures for Remote Development
.do
c

Deliverable/Ref

Description

Phase

the users of the
applications of their
existence and use.

Request for Database
S
ervices (this includes ER
Diagram, DB Change Request
Form, Data Dictionary Form) /
C.3.2 & C.3.3

Document submitted to DEKM
(OIS) for the purpose of
defining additions or changes
to the structure of the data
warehouse. This includes
capacity estimates.
N
ote: The
document should provide
sufficient detail regarding why
the change is needed.
A
DEKM Analyst will then
submit this form to Data
Administration.

Development

Impromptu Catalog Request /

D.5.2

Form to provide information
needed to either request
OIS
develop or maintain an
Impromptu catalog or
document the catalog created
by the remote development
team.

Development

&
Training/Implementation

Security and Data
Retention/Capacity / D.5.4

This document specifies any
restrictions to accessing the
proje
ct applications and
provides information of the
amount of data to be storage
and its refresh strategy.

Development

DW Test Package / D.5.5

This document demonstrates
through applicable
parameters, conditions,
outputs, etc. why the
development team feels t
he
application(s) are functioning
properly.

Development

Help Doc and Technical
Specification / D.5.7

This document has a two fold
purpose: (1) Provide basic
information for users of the
application, and (2) provide
technical details needed for
maintenance

of the
application by a developer.

Development

Operational Documentation /
D.5.8

This document contains
information on how to
maintain the new table,
Training/Implementation




Page
11

of
11


DPW Business and Technical Standards

Revised
07/27/04

EDW Procedures for Remote Development
.do
c

Deliverable/Ref

Description

Phase

mapping, cube, etc. This
includes, but is not limited to
ER Diagrams, ETL Flow
Diagrams, Full and Month
ly
Update/Refresh Strategies for
both the ETL process as well
as the ID process.

KM Signoff Form / B.2.4 &
D.5.6

Form on which users indicate
their acceptance of the
product listed on the form. A
form should be provided for
each
signoff task.

Various




Document Change Log


Change
Date

Version

CR #

Change Description

Author and
Organization

07/27/2004

1.0


Larry Leitzel

BTE