Chapter 2: The Database Development Process

Modern Database Management 7th Edition

Chapter 2

In this lecture you will learn:

General steps to be followed in the analysis, design, implementation and administration of databases. Systems development life cycle Other approaches to database and application development Differences between external, conceptual and internal schemas Three-tier architecture

Chapter 2
2

Enterprise Data Modeling

Chapter 2

Range and general contents of organizations database Database development begins with enterprise data modeling The first step in database development by which the scope and general contents of organizational databases are specified. This step occurs during information systems planning for an organization Its purpose is to create an overall picture or explanation of organizational data, not the design for a particular database.
3

Information Systems Architecture (ISA)

Enterprise Data Model is the overall blueprint for organizations information systems Developed by IS planners Consists of:

Data (Enterprise Data Model simplified ER Diagram) Processes data flow diagrams, process decomposition, etc. Network transport data around the org - topology diagram People people management using project management tools (Gantt charts, etc.) Events and Points in Time (when processes are performed) Chapter 2 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

Chapter 2

Top-Down Planning Approach

specific IS are deduced from a broad understanding of information needs rather than from consolidating many specific information requests. This offers the advantage of a broad perspective- a way to look at integration of individual system components, an understanding of the relationship of IS to business objectives and an understanding of the impact of IS across the whole organization

Chapter 2
6

Four steps in Information Engineering:

Planning
Results in an Information Systems Architecture

Analysis
Results in functional specificationsi.e. what we want

Design
Results in design specificationsi.e. how well do it

Implementation
Results in final operational system

Chapter 2

Information Systems Planning

IT Planning to meet Corporate strategy

Strategy development

Its goal is to align information technology with the business strategies of the organization. Such an alignment is important in order to achieve the maximum benefits from investments in information systems and technologies.
Chapter 2

Three Steps in IS Planning

1. Identify strategic planning factors 2. Identify corporate planning objects 3. Develop enterprise model The purpose of identifying these factors is to develop the planning context and to link information system plans to the strategic business plans.
Chapter 2
10

Identify Strategic Planning Factors

Organization goals what we hope to accomplish Critical success factors what MUST work in order for us to survive Problem areas weaknesses we now have

Chapter 2

11

Example:
Planning Factor Goals Examples: Maintain 10% per year growth rate Maintain 15% before-tax return on investment Avoid employee layoffs Be a responsible corporate citizen

Critical Success Factors

High quality products On-time deliveries of finished products High productivity of employees

Problems Areas

Inaccurate sales forecasts Increasing competition Stockouts of finish product

Chapter 2

12

Identify Corporate Planning Objects

Organizational units- the various departments of the organization Organizational locations- the places where business operations occur Business functions related groups of business processes that support the mission of the organization-these might become the users Entity types major categories of data about people, places, things managed by the organization-the things we are trying to model Information (application) systems- the application software and supporting procedures for handling sets of data.
13

Chapter 2

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

Chapter 2

14

Enterprise Data Model

First step in database development Specifies scope and general content of organizational databases are specified. Overall picture of organizational data, not specific design This step occurs during information systems planning for an organization Its purpose is to create an overall picture or explanation of organizational data, not the design for a particular database. Entity-relationship diagram Descriptions of entity types Relationships between entities Business rules
15

Chapter 2

Figure 2-1 Segment from enterprise data model (Pine Valley Furniture Company) [simplified E-R diagram, repeat of figure 1.3] Enterprise data model describes the entities in an organization and the relationship between these entities

16

Figure 2.2 -- Example of process decomposition of an order fulfillment function (Pine Valley Furniture)

Decomposition -- breaking large tasks into smaller tasks in a hierarchical structure chart

17

Planning Matrixes

Function-to-data entity Location-to-function this indicates which business functions are being performed at which business locations Unit-to-function- identifies which business functions are performed by or are the responsibility of which business units. IS-to-data entity- explains how each information system interacts which each data entity(e.g. whether each system creates, retrieves, updates or deletes data in each entity). Supporting function-to-data entity which data are captured, used, updated, deleted within each function IS-to-business objective-shows each information systems support each business objectives

Chapter 2

18

Example business function-to-data entity matrix (fig. 2.3)

Data Entity Types Business Function (users) Customer Product Raw Material Order Work Center Work Order Invoice Equipment Employee

Business Planning Product Development Materials Management Order Fulfillment Order Shipment Sales Summarization Production Operations Finance and Accounting
Chapter 2

X X X X

X X X X X X X X

X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
19

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

Chapter 2

20

Systems Development Life Cycle

Project Identification and Selection Project Initiation and Planning

Database Development Process

Enterprise modeling

Conceptual data modeling

Analysis
Logical Design Physical Design Implementation Maintenance Chapter 2
21

Logical database design Physical database design and definition Database implementation Database maintenance

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning Analysis

Logical Design Physical Design Implementation Maintenance

Chapter 2

22

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose --preliminary understanding Deliverable request for project

Logical Design Physical Design

Database activity enterprise modeling

Implementation Maintenance

Chapter 2

23

Enterprise Data Modeling

Analyze current data processing Analyze the general business functions and their database needs Justify need for new data and databases in support of business

Chapter 2

24

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning

Purpose state business situation and solution Deliverable request for analysis

Analysis

Logical Design Physical Design

Database activity conceptual data modeling

Implementation Maintenance

Chapter 2

25

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning

Purpose thorough analysis Deliverable functional system specifications

Analysis

Logical Design Physical Design

Database activity conceptual data modeling

Implementation Maintenance

Chapter 2

26

Conceptual Data Modeling

Identify scope of database requirements for proposed information system Analyze overall data requirements for business functional supported by database Develop preliminary conceptual data model including entities and relationships Compare preliminary conceptual data model with enterprise data model Develop detailed conceptual data model, including entities, relationships, attributes and business rules Make conceptual data model consistent with other models of information system Populate repository with all conceptual database applications

Chapter 2

27

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning

Purpose information requirements structure Deliverable detailed design specifications

Analysis

Logical Design Physical Design

Database activity logical database design

Implementation Maintenance

Chapter 2

28

Logical Database Design

Analyze in detail the transactions, forms, displays and inquiries (database views) required by the business functions supported by the database Integrate database views into conceptual data model Identify data integrity and security requirements and populate repository

Chapter 2
29

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose develop technology specs Deliverable program/data structures, technology purchases, organization redesigns

Logical Design Physical Design

Database activity physical database design

Implementation Maintenance

Chapter 2

30

Physical Database Design

Define database to DBMS (often generated from repository) Decide a physical organization of data Design database processing programs

Chapter 2

31

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose programming, testing, training, installation, documenting Deliverable operational programs, documentation, training materials

Logical Design Physical Design

Database activity database implementation

Implementation Maintenance

Chapter 2

32

Database Implementation
Code and test database processing programs Complete database documentation and training materials Install databases and convert data from prior systems

Chapter 2

33

Systems Development Life Cycle (figures 2.4, 2.5)

Project Identification and Selection Project Initiation and Planning Analysis

Purpose monitor, repair, enhance Deliverable periodic audits

Logical Design Physical Design

Database activity database maintenance

Implementation Maintenance

Chapter 2

34

Database Maintenance
Analyze database and database applications to ensure that evolving information requirements are met Tune database for improved performance Fix errors in database and database applications and recover database when it is contaminated.

Chapter 2
35

Alternative IS Development Approaches

Organizations nowadays use Rapid Application Development (RAD) which follows an iterative process of rapidly repeating analysis, design and implementation steps until the developer converge on the system the user wants. These RAD methods work best when most of the database needed already exists. One of the most popular RAD methods is prototyping.

Chapter 2
36

Prototyping

An iterative process of systems development in which requirements are converted to a working system that is continually revised through close work between analysts and users.

Chapter 2

37

Figure 2-6 The prototyping methodology and database development process

38

Figure 2-6 The prototyping methodology and database development process

39

Figure 2-6 The prototyping methodology and database development process

40

Figure 2-6 The prototyping methodology and database development process

41

Figure 2-6 The prototyping methodology and database development process

42

Managing Projects: People Involved

Database is developed as part of a project Project is a planned undertaking of related activities to reach an objective that has a beginning and an end. It begins with Project Initiation and Planning phase and ends up with the last step of implementation phase. Systems analysts- person that analyze the business situation and identify the need for information and information services to meet the problems or opportunities of the business Database analysts- concentrates on determining the requirements and design for the database component of the information systems Users- provide assessment of their information needs and monitor that the developed system meets their needs. Programmers design and write computer programs that have embedded in them commands to maintain and access data in the database. Database/data administrators have responsibility for existing and future databases and ensure consistency and integrity across databases, and its experts on database technology, provide consulting and training to other project team members. Chapter 2 Systems programmers, network administrators, testers, technical 43

Figure 2-7a Gantt Chart

Shows time estimates of tasks - This is a graphical diagram for depicting project plans

44

Figure 2-7b PERT chart

Shows dependencies between tasks

45

Database Schema
Schema is a structure that contains description of objects created by a user. Physical Schema (Physical structures) - Specification for how data from a logical schema are stored in a computers secondary memory by a database management system. Conceptual Schema (ER models)- A detailed technology independent specification of the overall structure of the database External Schema (User Views, Subsets of Conceptual Schema)- A logical description of some portion of database that is required by a user to perform some task. Can be determined from business-function/data entity matrices) DBA determines schema for different users This is part of people-management in databases Chapter 2

46

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

Chapter 2

47

Figure 2-8 Three-schema database architecture

External schema

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

Internal schema

48

Three-tier architecture:

A client/server configuration that includes three layers; a client layer and two server layers.

Chapter 2

49

Client/Server Architecture:

A local area network-based environment in which database software on a server (called database software or database engine) performs database commands sent to it from client workstations an application programs on each client concentrate on user interface functions.
50

Chapter 2

Reasons for using Client/Server Architecture:

It allows for simultaneous processing in multiple processors for the same application, thus improving application response time and data processing speed; It is possible to take advantage of the best processing features of each computer platform; You can mix client technologies and yet share common data; in addition, you can change technologies at any tier with limited impact on the system modules of other tiers; Processing can be performed close to the source of processed data, thereby improving response times and reducing network traffic. It allows for and encourages the acceptance of open system standards.

Chapter 2

51

Figure 2-10 Three-tiered client/server database architecture

52

Client tier a desktop or laptop computer; which concentrates on managing the user-system interface and localized data-also called the presentation tier Application/Web server tier processes HTTP protocol, scripting tasks, performs calculations, and provides access to data-also called the process services tier. Enterprise server (minicomputer or mainframe)performs sophisticated calculations and manages the merging of data from multiple sources across the organization also called the data services tier.

Chapter 2

53

Pine Valley Furniture

Preliminary data model (figure 2-11)

Chapter 2

54

Pine Valley Furniture

MS Access data model prototype (figure 2-14)

Chapter 2

55