chapter chapter 22:: the database development …is.cba.edu.kw/433/handouts/ch02.pdfdata (e.g....

Chapter Chapter 22::The Database Development The Database Development

ProcessProcessProcess Process

Modern Database ManagementModern Database Management99thth EditionEdition99 EditionEdition

Jeffrey A. Hoffer, Mary B. Prescott, Jeffrey A. Hoffer, Mary B. Prescott, Heikki Topi Heikki Topi

© © 2009 2009 Pearson Education, Inc. Pearson Education, Inc. Publishing as Prentice HallPublishing as Prentice Hall 11

ObjectivesObjectivesD fi iti f tD fi iti f tDefinition of termsDefinition of termsDescribe system development life cycleDescribe system development life cycleE plain p otot ping app oachE plain p otot ping app oachExplain prototyping approachExplain prototyping approachExplain agile software development approachExplain agile software development approachExplain roles of individualsExplain roles of individualsExplain roles of individualsExplain roles of individualsExplain threeExplain three--schema approachschema approachExplain role of packaged data modelsExplain role of packaged data modelsExplain role of packaged data modelsExplain role of packaged data modelsExplain threeExplain three--tiered architecturestiered architecturesExplain scope of database design projectsExplain scope of database design projectsExplain scope of database design projectsExplain scope of database design projectsDraw simple data modelsDraw simple data models

Chapter 2 © © 2009 2009 Pearson Education, Inc. Pearson Education, Inc. Publishing as Prentice HallPublishing as Prentice Hall 22

Enterprise Data ModelEnterprise Data Model

First step in database developmentFirst step in database developmentSpecifies scope and general contentSpecifies scope and general contentOverall picture of organizational data at high Overall picture of organizational data at high p g gp g glevel of abstractionlevel of abstractionEntityEntity--relationship diagramrelationship diagramEntityEntity relationship diagramrelationship diagramDescriptions of entity typesDescriptions of entity typesR l ti hi b t titiR l ti hi b t titiRelationships between entitiesRelationships between entitiesBusiness rulesBusiness rules


Figure 2-1 Segment from enterprise data model

Enterprise data model describes the high-glevel entities in an organization and the

l i hi brelationship between these entities


Information Systems ArchitectureInformation Systems Architecture(ISA)(ISA)(ISA)(ISA)

Conceptual blueprint for organization’s desired Conceptual blueprint for organization’s desired information systems structureinformation systems structureConsists of:Consists of:Consists of:Consists of:

Data (e.g. Enterprise Data ModelData (e.g. Enterprise Data Model––simplified ER simplified ER Diagram)Diagram)ag a )ag a )ProcessesProcesses––data flow diagrams, process decomposition, data flow diagrams, process decomposition, etc.etc.Data NetworkData Network topology diagram (like Figtopology diagram (like Fig 11 77))Data NetworkData Network––topology diagram (like Fig topology diagram (like Fig 11--77))PeoplePeople––people management using project people management using project management tools (Gantt charts, etc.)management tools (Gantt charts, etc.)g ( , )g ( , )Events and points in time (when processes are Events and points in time (when processes are performed)performed)Reasons for events and rules (e g decision tables)Reasons for events and rules (e g decision tables)


Reasons for events and rules (e.g., decision tables)Reasons for events and rules (e.g., decision tables)

Information EngineeringInformation EngineeringInformation EngineeringInformation EngineeringA dataA data--oriented methodology to create and oriented methodology to create and gygymaintain information systemsmaintain information systemsTopTop--down planningdown planning––a generic IS planning a generic IS planning

th d l f bt i i b dth d l f bt i i b dmethodology for obtaining a broad methodology for obtaining a broad understanding of the IS needed by the entire understanding of the IS needed by the entire organizationorganizationorganizationorganizationFour steps to TopFour steps to Top--Down planning:Down planning:

PlanningPlanningggAnalysisAnalysisDesignDesignImplementationImplementation


Identify Strategic PlanningIdentify Strategic PlanningIdentify Strategic Planning Identify Strategic Planning Factors (Table Factors (Table 22--22))(( ))

Organization goalsOrganization goals––what we hope to what we hope to accomplishaccomplishaccomplishaccomplishCritical success factorsCritical success factors––what MUST work what MUST work i d f t ii d f t iin order for us to survivein order for us to surviveProblem areasProblem areas––weaknesses we now haveweaknesses we now have


Identify Corporate Planning Identify Corporate Planning y p gy p gObjects (Table Objects (Table 22--33))

Organizational unitsOrganizational units––departmentsdepartmentsOrganizational unitsOrganizational units departmentsdepartmentsOrganizational locationsOrganizational locationsBusiness functionsBusiness functions––groups of business groups of business processesprocessesppEntity typesEntity types––the things we are trying to the things we are trying to model for the databasemodel for the databasemodel for the databasemodel for the databaseInformation systemsInformation systems––application programsapplication programs


Develop Enterprise ModelDevelop Enterprise Model

Functional decompositionFunctional decompositionIterative process breaking system description Iterative process breaking system description into finer and finer detailinto finer and finer detail

Enterprise data model Enterprise data model

Planning matrixes Planning matrixes Describe interrelationshipsDescribe interrelationshipsDescribe interrelationships Describe interrelationships between planning objectsbetween planning objects


Planning MatrixesPlanning MatrixesD ib l i hi b l iD ib l i hi b l iDescribe relationships between planning Describe relationships between planning objects in the organizationobjects in the organizationTypes of matrixes:Types of matrixes:

LocationLocation--toto--functionfunctionLocationLocation toto functionfunctionUnitUnit--toto--functionfunctionISIS--toto--data entitydata entityISIS--toto--data entitydata entitySupporting functionSupporting function--toto--data entitydata entityISIS toto business objectivebusiness objectiveISIS--toto--business objectivebusiness objective


Example Business FunctionExample Business Function--toto--Data Entity Matrix (FigData Entity Matrix (Fig 22 33))Data Entity Matrix (Fig. Data Entity Matrix (Fig. 22--33))


Two Approaches to Database Two Approaches to Database and IS Developmentand IS Development

SDLCSDLCSDLCSDLCSystem Development Life CycleSystem Development Life CycleDetailed wellDetailed well--planned development processplanned development processDetailed, wellDetailed, well planned development processplanned development processTimeTime--consuming, but comprehensiveconsuming, but comprehensiveLong development cycleLong development cycleo g d op yo g d op y

PrototypingPrototypingRapid application development (RAD)Rapid application development (RAD)Rapid application development (RAD)Rapid application development (RAD)Cursory attempt at conceptual data modelingCursory attempt at conceptual data modelingDefine database during development of initial Define database during development of initial g pg pprototypeprototypeRepeat implementation and maintenance activities Repeat implementation and maintenance activities with new prototype versionswith new prototype versions


with new prototype versionswith new prototype versions

Systems Development Life CycleSystems Development Life Cycle(see also Figures (see also Figures 22..44, , 22..55) )

Planning

A l iAnalysis

Logical Design

Physical Design

Logical Design

Implementation

Maintenance


Systems Development Life CycleSystems Development Life Cycle(see also Figures (see also Figures 22..44, , 22..55) (cont.)) (cont.)

Planning

A l i

Planning Purpose––preliminary understandingDeliverable––request for study

Analysis

Logical Design

Physical Design

Logical Design

ImplementationDatabase activity––enterprise modeling and

Maintenance

enterprise modeling and early conceptual data modeling


Systems Development Life CycleSystems Development Life Cycle(see also Figures (see also Figures 22..44, , 22..55) (cont.) ) (cont.)

Purpose thorough requirements analysis andPlanning

A l iA l i

Purpose–thorough requirements analysis and structuringDeliverable–functional system specifications

Analysis

Logical Design

Analysis

Physical Design

Logical Design

ImplementationDatabase activity–thorough and integrated conceptual

Maintenance

and integrated conceptual data modeling



Purpose–information requirements elicitationPlanning

A l i

Purpose information requirements elicitation and structureDeliverable–detailed design specifications

Analysis

Logical DesignLogical Design

Physical Design

Logical DesignLogical Design

ImplementationDatabase activity–logical database design

Maintenance

logical database design (transactions, forms, displays, views, data integrity and security)


integrity and security)


Purpose develop technology andPlanning

A l i

Purpose–develop technology and organizational specificationsDeliverable–program/data t t t h l hAnalysis

Logical Design

structures, technology purchases, organization redesigns

Physical Design

Logical Design

Physical Design

ImplementationDatabase activity–physical database design (define

Maintenance

physical database design (define database to DBMS, physical data organization, database processing programs)


processing programs)


Purpose–programming, testing, training,Planning

A l i

Purpose programming, testing, training, installation, documentingDeliverable–operational programs, documentation training materialsAnalysis

Logical Design

documentation, training materials

Physical Design

Logical Design

ImplementationImplementationDatabase activity–database implementation,

Maintenanceincluding coded programs, documentation, installation and conversion



Planning

A l i

Purpose–monitor, repair, enhanceDeliverable–periodic audits

Analysis

Logical Design

Physical Design

Logical Design

ImplementationDatabase activity–database maintenance,

MaintenanceMaintenanceperformance analysis and tuning, error corrections


Prototyping Database MethodologyPrototyping Database Methodology(Figure(Figure 22 66))(Figure (Figure 22..66) )


Prototyping Database MethodologyPrototyping Database Methodology(Figure(Figure 22 66)) (cont )(cont )(Figure (Figure 22..66) ) (cont.)(cont.)


Prototyping Database MethodologyPrototyping Database Methodology(Figure(Figure 22 66)) (cont )(cont )(Figure (Figure 22..66)) (cont.)(cont.)


Prototyping Database MethodologyPrototyping Database Methodology(Figure(Figure 22 66)) (cont )(cont )(Figure (Figure 22..66) ) (cont.)(cont.)


CASECASEComputerComputer Aided Software EngineeringAided Software EngineeringComputerComputer--Aided Software Engineering Aided Software Engineering (CASE)(CASE)––software tools providing automated software tools providing automated

f d lf d lsupport for systems developmentsupport for systems developmentThree database features:Three database features:Three database features:Three database features:

Data modelingData modeling––drawing entitydrawing entity--relationship relationship diagramsdiagramsdiagramsdiagramsCode generationCode generation––SQL code for table creationSQL code for table creationRepositoriesRepositories––knowledge base of enterprise knowledge base of enterprise informationinformation


Packaged Data ModelsPackaged Data Models

Model components that can be purchased, Model components that can be purchased, customized and assembled into fullcustomized and assembled into full scale datascale datacustomized, and assembled into fullcustomized, and assembled into full--scale data scale data modelsmodelsAdvantagesAdvantagesAdvantagesAdvantages

Reduced development timeReduced development timeHigher model quality and reliabilityHigher model quality and reliabilityHigher model quality and reliabilityHigher model quality and reliability

Two types:Two types:Universal data modelsUniversal data modelsUniversal data modelsUniversal data modelsIndustryIndustry--specific data modelsspecific data models


M i P j tM i P j tManaging ProjectsManaging ProjectsP j tP j t l d d t ki f l t dl d d t ki f l t dProjectProject––a planned undertaking of related a planned undertaking of related activities to reach an objective that has a activities to reach an objective that has a beginning and an endbeginning and an endbeginning and an endbeginning and an endInvolves use of review points for:Involves use of review points for:

V lid ti f ti f tV lid ti f ti f tValidation of satisfactory progressValidation of satisfactory progressStep back from detail to overall viewStep back from detail to overall viewR it t f t k h ldR it t f t k h ldRenew commitment of stakeholdersRenew commitment of stakeholders

Incremental commitmentIncremental commitment––review of review of t d l t j t ft ht d l t j t ft hsystems development project after each systems development project after each

development phase with rejustification development phase with rejustification after each phaseafter each phase


after each phaseafter each phase

Managing Projects: People InvolvedManaging Projects: People InvolvedManaging Projects: People InvolvedManaging Projects: People InvolvedBusiness analystsBusiness analystsyySystems analystsSystems analystsDatabase analysts and data modelersDatabase analysts and data modelersDatabase analysts and data modelersDatabase analysts and data modelersUsersUsersProgrammersProgrammersDatabase architectsDatabase architectsData administratorsData administratorsProject managersProject managersProject managersProject managersOther technical expertsOther technical experts


Database SchemaDatabase SchemaDatabase SchemaDatabase SchemaExternal SchemaExternal SchemaExternal SchemaExternal Schema

User ViewsUser ViewsSubsets of Conceptual SchemaSubsets of Conceptual SchemaSubsets of Conceptual SchemaSubsets of Conceptual SchemaCan be determined from businessCan be determined from business--function/data function/data entity matricesentity matricese t ty at cese t ty at cesDBA determines schema for different usersDBA determines schema for different users

Conceptual SchemaConceptual SchemaConceptual SchemaConceptual SchemaEE--R modelsR models––covered in Chapters covered in Chapters 3 3 and and 44

Internal SchemaInternal SchemaInternal Schema Internal Schema Logical structuresLogical structures––covered in Chapter covered in Chapter 55Physical structuresPhysical structures––covered in Chapter covered in Chapter 66


yy pp

Figure 2-7 Three-schema architecture

Different people have differenthave different views of the database…these are the externalare the external schema

The internal schema is theschema is the underlying design and i l iimplementation


Pine Valley FurniturePine Valley FurniturePine Valley FurniturePine Valley Furniture

Segment of project data model (Figure 2-11)


Figure 2-12 Four relations (Pine Valley Furniture)


Figure 2-12 Four relations (Pine Valley Furniture) (cont.)


All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means electronicretrieval system, or transmitted, in any form or by any means, electronic,

mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher. Printed in the United States of America.

Copyright © Copyright © 2009 2009 Pearson Education, Inc. Pearson Education, Inc. Publishing as Prentice HallPublishing as Prentice Hall


chapter chapter 22:: the database development …is.cba.edu.kw/433/handouts/ch02.pdfdata (e.g....

Documents