Sample from Managing Database: Four Critical Factors · 9.4 Appropriate DBMS Comparisions ......

Managing Database:Four Critical Factors

Whitemarsh Information Systems Corporation2008 Althea Lane

Bowie, Maryland 20716 Tele: 301-249-1142

Email: [email protected]: www.wiscorp.com

Managing Database: Four Critical Factors

Copyright 1998, Whitemarsh Information Systems CorporationProprietary Data, All Rights Reserved

ii

Table of Contents

1 Rationale for Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Non Database Processing Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 How the Environment Has Changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 The Promise of Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4 Database Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.5 Data Architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.6 Knowledge Worker Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.7 Interrelationship of Database & Knowledge Worker Framework . . . . . . . . . . . . . . . 261.8 Essential Database Viewpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2 Technology Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.1 First Generation of DBMS Technology: (1955-1970) . . . . . . . . . . . . . . . . . . . . . . . 292.2 Second Generation of DBMS–Relational DBMS (1970-1998) . . . . . . . . . . . . . . . . 362.3 Third Generation of DBMS (1998—) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.4 De Jure Database Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.5 Components of a DBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3 Staffing Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.1 Who Are the People . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.2 Database Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.3 Interrogation Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.4 Systems Control Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.5 Documentation and Standards Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833.6 DBMS Specialist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.7 Database Project Staff and Suggested Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

4 Database and Information Systems Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864.1 Information Technology Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874.2 Information Technology User Committee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.3 Information Technology Organization Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 The Project Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975.1 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985.2 Database Project Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105.3 Project Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125.4 Metabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116



iii

5.5 Project Planning, Management & Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185.6 Continuous Flow Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

6 Business Model Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206.1 Major Deliverables of Business Model Specification . . . . . . . . . . . . . . . . . . . . . . . 1216.2 Preliminary Analysis Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1226.3 Conceptual Specification Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1326.4 Prototype Creation & Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1646.5 Metabase Components Updated During Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . 1726.6 Business Model Specification Phase Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

7 Business Model Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1787.1 Major Milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1797.2 Binding Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1807.3 Metabase Support for Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1917.4 Implementation Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1937.4 Metabase Support for Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2147.6 Implementation Phase Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

8 Production & Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2228.1 Milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2238.2 Conversion & Deployment Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2248.3 Production & Administration Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2268.4 Metabase Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2398.5 Business Model Maintenance Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2408.6 Database Project Environment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

9 The DBMS Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2429.1 Dichotomy of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2439.2 Dichotomy of DBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2449.3 Selection Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2869.4 Appropriate DBMS Comparisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2879.5 Application Versus DBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

10 Key Factors Bearing on Database Success . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28910.1 Application Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29010.2 Management Expertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29110.3 Metabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292



iv

10.4 Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29910.5 Definable Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30010.6 Policy Coherence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30410.7 Key Factors Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

11 Review and Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30611.1 Rationale for Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30711.2 Technology Viewpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30811.3 Information Technology Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30911.4 the Database Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31011.5 the Database Project (Cont.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31111.6 Selecting the Right DBMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31511.7 Controlling Database Risk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31611.8 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317



1

1 Rationale for Database

M Non-Database Environment

M How the Environment Has Changed

M The Promise of Database

M What Constitutes Database



2

1.1 Non Database Processing Environment

M Large Sequential Files

M Founded on Report Requirements

M Design Strategy



3

Result

M Collect Only What You Report.

M Store Only in Pre-report Format.

M Extract Specific Data from

M Natural Contexts into Processing Efficient Storage.



4

Everyone Goes Berserk When a Change Happens Because............

M All File Formats Have to Be Changed

M All Report Programs Have to Be Changed

M All Input Programs Have to Be Changed

M All Translation Programs Have to Be Changed

In Short, Everything Has to Be Changed, And So, .................



5

We Invented, Crafty Sex Codes

Crafty Sex Codes

CodeAge Sex Handicapped

Status

0-5 6-25 26 & up Male Female Yes No

1 U U U

2 U U U

3 U U U

4 U U U

5 U U U

6 U U U

7 U U U

8 U U U

9 U U U U

0 U U U U



6

But That Was No Problem Because

M We documented very well

M We never changed jobs

M We alone owned the entire system



7

1.2 How the Environment Has Changed

Ownership Abstraction

Which Results in



8

Common Access



9

But That Requires

M Public rules/policies

M Public programs

M Natural data contexts

M Single purpose data



10

The Effects of Centralization and Decentralization of Semantics and Data

Questions Regarding Data DistributionEffects

Semantic Control

Centralized Decentralized

Data Storage Control

Cen

tral

ized

Dec

entr

aliz

ed

Cen

tral

ized

Dec

entr

aliz

ed

Is data able to be shared among sites? Yes Yes No No

Is concurrent processing of the samedata possible?

Yes Maybe No No

Are common or corporate reportspossible?

Yes Yes No No

Can there be an overbearing "bigbrother" feeling?

Yes Maybe No No

Is there local control and ownership? No Maybe Yes Yes

Does there need to be common datastandards & policies?

Yes Yes No No

Can local data requirements besatisfied?

Maybe Yes Maybe Yes



11

The Effects of Centralization and Decentralization of Process Developmentand Execution

Questions Regarding SystemDistribution Effects

Development Control


Execution Location

Cen

tral

ized

Dec

entr

aliz

ed

Cen

tral

ized

Dec

entr

aliz

ed

Is the same program able to be sharedamong sites?

Yes Yes No No

Is concurrent processing of the samedata possible?

Yes Maybe No No

Are common or corporate reportsguaranteed?

Yes Maybe No No


Yes Maybe No No


Does there need to be commonprocessing standards & practices?

Yes Yes No No

Can local processing requirements besatisfied?

Maybe Yes Maybe Yes



12

The Effects of Centralization and Decentralization of Database Objects

Questions Regarding Database ObjectDistribution Effects

Semantic Control


Development Control

Cen

tral

ized

Dec

entr

aliz

ed

Cen

tral

ized

Dec

entr

aliz

ed

Are database objects able to be sharedamong sites?

Yes Yes No No

Is concurrent processing of the samedatabase object instance possible?

Yes Maybe No No

Are common or corporate reportspossible?

Yes Yes No No


Yes Maybe No No


Does there need to be common datastandards & policies?

Yes Yes No No

Can local data requirements besatisfied?

Maybe Yes Maybe Yes



13

Comparing Attributes In the Non Database and Database Approaches

Approach Comparison

Characteristic Non Database Processing Database Processing

Ownership Programmer Corporation

File Stand-alone, transient storageand high performancestructure design

Permanent storage; smallpart of a naturallyorganized structure

Input Only critical data to servereport needs; one datacollection per report

Capture data andcontexts; preserveenvironment and history;one data collection perdatabase

Output Multiple reports via singlepass of data file

Transient reportrequirements that changeoften

Program File division and proceduredivision with program basedsemantics to process multi-meaning data fields

Cobol only for updatesand complex reports; adhoc language; allsemantics within thedatabase

Data field Small as possible; pack asmany values and meanings aspossible

Single meaning; welldefined with strict rules



14

Change of Focus

And That Enables...



15

1.3 The Promise of Database

M Database centered analysis & design

M Database designs built on natural reflections of business functionfundamentals

M Long term stability in data emphasis on "canned" tools to accomplishtransient work

M Corporate ownership

M Common processing



16

1.4 Database Classes

Database Class Characteristics

Original data capture Captured at source, Application specific.Vendor’s package if possible. Ex: OrderProcessing

Transaction data stagingarea

Business transaction data that is transformed tocommon format. Application specific. Custom,but simple applications. Ex: MPS

Subject area databases Integrated business data that is broad andcomprehensive. Subject area coverage. Custom,but simple. Ex: In-Market Reporting

Data warehouses End-user business data that meets specific needsdesign. Application specific. Vendor package ifpossible. Ex: Improved Sales Reporting

Reference data Reference data is that set of data that is commonlyemployed across the other different databaseclasses. Examples of reference data include sets ofdata include: Gender codes and names, Statecodes and names, and units of measure andnames.



17



18

1.5 Data Architectures

Given fundamental business data for typical enterprise....



19

Business Unit Data Architecture



20

Country-wide Data Architectures



21

World-wide Data Architecture



22

1.6 Knowledge Worker Framework

Whitemarsh Knowledge Worker Framework

Levels Mission

Man-Machine Interface

Machine Interface Man

DatabaseObject

BusinessInformationSystem

BusinessEvent

BusinessFunction Organization

Scope List ofbusinessmissions

List of majorbusinessresources

List ofbusinessinformationSystems

List ofinterfaceevents

List of majorbusinessscenarios

List oforganizations

Business Missionhierarchies

Resource lifecycles

Informationsequencingandhierarchies

Eventsequencingandhierarchies

Businessscenariosequencingandhierarchies

Organizationcharts, jobsand descriptions

System Policy hierarchies

Databaseobject models

Informationsystemdesigns

Invocationprotocols,input andoutput data,and messages

Best practices,qualitymeasures andaccomplishmentassessments

Job roles, responsibilities, and activityschedules

Tech-nology

Policyexecutionenforcement

Logical DBMSschemas

Informationsystemsapplication designs

Presentationlayerinformationsysteminstigators

Activity sequences toaccomplishbusinessscenarios

Procedure manuals, tasklists, qualitymeasures andassessments

Deploy-ment

Installed businesspolicy andprocedures

PhysicalDBMSschemas

Implementedinformationsystems

Client & serverwindowsand/or batchexecutionmechanisms

Office policies andprocedures toaccomplish activities

Dailyschedules,shift andpersonnelassignments

Oper-ations

Operating business

DBMS views Operatinginformationsystems

Start, stop,and messages

Detailedprocedure basedinstructions

Daily activityexecutions, andassessments



23

Information Technology Cells


Levels Mission



DatabaseObject


BusinessEvent




List of businessinformationSystems

List of interfaceevents




Resource lifecycles

Informationsequencing andhierarchies

Eventsequencing andhierarchies

Businessscenariosequencing andhierarchies

Organizationcharts, jobs and descriptions


Database objectmodels

Informationsystem designs

Invocationprotocols, inputand output data,and messages



Tech-nology


Logical DBMSschemas


Presentationlayer informationsysteminstigators



Deploy-ment


Physical DBMSschemas


Client & serverwindows and/orbatch executionmechanisms

Office policies and proceduresto accomplish activities

Daily schedules,shift andpersonnelassignments

Oper-ations

Operating business


Start, stop, andmessages





24

Information Technology Environment Cells


Levels Mission



DatabaseObject


BusinessEvent




List of businessinformationSystems

List of interfaceevents




Resource lifecycles

Informationsequencing andhierarchies

Eventsequencing andhierarchies

Businessscenariosequencing andhierarchies

Organizationcharts, jobs and descriptions


Database objectmodels

Informationsystem designs

Invocationprotocols, inputand output data,and messages



Tech-nology


Logical DBMSschemas


Presentationlayer informationsysteminstigators



Deploy-ment


Physical DBMSschemas


Client & serverwindows and/orbatch executionmechanisms

Office policies and proceduresto accomplish activities

Daily schedules,shift andpersonnelassignments

Oper-ations

Operating business


Start, stop, andmessages





25

Allocation of the U. S. Government’s Sources of Critical Errors inInformation Technology Projects


Levels Mission



DatabaseObject

BusinessInformation

SystemBusiness

EventBusinessFunction Organization

Scope 13 5 6 1 8 10

Business 12 6 6 1 15 14

System 8 6 5 0 28 18

Technol-ogy

3 0 0 0 18 14

Deploy-ment

1 0 0 0 12 11

Opera-tions

1 0 0 0 8 8



26

1.7 Interrelationship of Database & Knowledge Worker Framework



27

1.8 Essential Database Viewpoints

ManagingDatabaseViewpoint

Interrelationships Among Database Viewpoints

Logical Physical InterrogationSystemControl

Technology

(2)

Data model Databasecreation andmaintenance

Data selectionand reporting

Audit trails,protection andevolution etc.

Staffing(3)

Databasespecialist

DBMSspecialist

Interrogationspecialist

Systemcontrolspecialist

Project(4-8)

Conceptual specification phase

Implementation phase

Production and administration phase

DBMS(9)

Schemaand sub-schema

Accessmethods, dataloading,update, andmaintenance

Query, hostlanguage,report writers

Utilities,languages andtechniques

Sample from Managing Database: Four Critical Factors · 9.4 Appropriate DBMS Comparisions ......

Documents

Transcript of Sample from Managing Database: Four Critical Factors · 9.4 Appropriate DBMS Comparisions ......