Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
122 views

Chapter 2 Database Development Process

Enterprise data model describes the highlevel entities in an organization and the relationship between these entities. Information Systems Architecture (ISA) IS a blueprint for organization's desired information systems structure. Top-down planning IS a generic IS planning methodology for obtaining a broad understanding of the IS needed by the entire organization.

Uploaded by

Lei Ann Fernandez
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
122 views

Chapter 2 Database Development Process

Enterprise data model describes the highlevel entities in an organization and the relationship between these entities. Information Systems Architecture (ISA) IS a blueprint for organization's desired information systems structure. Top-down planning IS a generic IS planning methodology for obtaining a broad understanding of the IS needed by the entire organization.

Uploaded by

Lei Ann Fernandez
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 26

Chapter 2: The Database Development Process

Modern Database Management 9th Edition


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

2009 Pearson Education,1Inc. Publishing as Prentice Hall

Enterprise Data Model


First step in database development Specifies scope and general content Overall picture of organizational data at high level of abstraction Entity-relationship diagram Descriptions of entity types Relationships between entities Business rules

Figure 2-1 Segment from enterprise data model

Enterprise data model describes the highlevel entities in an organization and the relationship between these entities

Information Systems Architecture (ISA)


Conceptual blueprint for organizations desired information systems structure Consists of:
Data (e.g. Enterprise Data Modelsimplified ER Diagram) Processesdata flow diagrams, process decomposition, etc. Data Networktopology diagram (like Fig 1-7) Peoplepeople management using project management tools (Gantt charts, etc.) Events and points in time (when processes are performed) Reasons for events and rules (e.g., decision tables)

Information Engineering
A data-oriented methodology to create and maintain information systems Top-down planninga generic IS planning methodology for obtaining a broad understanding of the IS needed by the entire organization Four steps to Top-Down planning:
Planning Analysis Design Implementation

Identify Strategic Planning Factors (Table 2-2)


Organization goalswhat we hope to accomplish Critical success factorswhat MUST work in order for us to survive Problem areasweaknesses we now have

Identify Corporate Planning Objects (Table 2-3)


Organizational unitsdepartments Organizational locations Business functionsgroups of business processes Entity typesthe things we are trying to model for the database Information systemsapplication programs
8

Develop Enterprise Model


Functional decomposition
Iterative process breaking system description into finer and finer detail

Enterprise data model Planning matrixes


Describe interrelationships between planning objects

Planning Matrixes
Describe relationships between planning objects in the organization Types of matrixes:
Location-to-function Unit-to-function IS-to-data entity Supporting function-to-data entity IS-to-business objective

10

Example Business Function-to-Data Entity Matrix (Fig. 2-3)

11

Two Approaches to Database and IS Development


SDLC
System Development Life Cycle Detailed, well-planned development process Time-consuming, but comprehensive Long development cycle

Prototyping

Rapid application development (RAD) Cursory attempt at conceptual data modeling Define database during development of initial prototype Repeat implementation and maintenance activities with new prototype versions

12

Systems Development Life Cycle (see also Figures 2.4, 2.5)


Planning Analysis Logical Design Physical Design Implementation Maintenance

13

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Planning Analysis Logical Design Physical Design

Purposepreliminary understanding Deliverablerequest for study

Database activity enterprise modeling and early conceptual data modeling

Implementation Maintenance

14

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning

Purposethorough requirements analysis and structuring Deliverablefunctional system specifications Analysis Analysis
Logical Design Physical Design

Database activitythorough and integrated conceptual data modeling

Implementation Maintenance

15

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Analysis Logical Design Logical Design Physical Design

Purposeinformation requirements elicitation and structure Deliverabledetailed design specifications

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

Implementation Maintenance

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Analysis Logical Design

Purposedevelop technology and organizational specifications Deliverableprogram/data structures, technology purchases, organization redesigns

Physical Design Physical Design Database activity physical database design (define database to DBMS, physical data organization, database processing programs)
17

Implementation Maintenance

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Analysis Logical Design Physical Design

Purposeprogramming, testing, training, installation, documenting Deliverableoperational programs, documentation, training materials

Database activity database implementation, including coded programs, documentation, installation and conversion
18

Implementation Implementation Maintenance

Systems Development Life Cycle (see also Figures 2.4, 2.5) (cont.)
Planning Analysis Logical Design Physical Design

Purposemonitor, repair, enhance Deliverableperiodic audits

Database activity database maintenance, performance analysis and tuning, error corrections
19

Implementation Maintenance Maintenance

CASE
Computer-Aided Software Engineering (CASE) software tools providing automated support for systems development Three database features:
Data modelingdrawing entity-relationship diagrams Code generationSQL code for table creation Repositoriesknowledge base of enterprise information

20

Packaged Data Models


Model components that can be purchased, customized, and assembled into full-scale data models Advantages
Reduced development time Higher model quality and reliability

Two types:
Universal data models Industry-specific data models

21

Managing Projects
Projecta planned undertaking of related activities to reach an objective that has a beginning and an end Involves use of review points for:
Validation of satisfactory progress Step back from detail to overall view Renew commitment of stakeholders

Incremental commitmentreview of systems development project after each development phase with rejustification after each phase

22

Managing Projects: People Involved



23

Business analysts Systems analysts Database analysts and data modelers Users Programmers Database architects Data administrators Project managers Other technical experts

Database Schema
External Schema
User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users

Conceptual Schema
E-R modelscovered in Chapters 3 and 4

Internal Schema
Logical structurescovered in Chapter 5 Physical structurescovered in Chapter 6

24

Figure 2-7 Three-schema architecture


Different people have different views of the databasethese are the external schema

The internal schema is the underlying design and implementation

25

26

You might also like