Adapted from Jeffery A.

Hoffers
Modern Database Management,
12th Edition
Lecture # 7
Database Development Process

Lecturer
Shermeen Adnan

1
 The Database Development Process
How do organizations start developing a
business?
Enterprise Data Modeling (EDM)
First step in DB development process
Specifies the scope and general contents of organizational
DB
Creates overall picture of an organizational data at high level
of abstraction
Entity-relationship diagram
Descriptions of entity types
Relationships between entities
Business rules
 The Database Development Process
EDM encompasses many databases
A particular database provides the data for one or
more Information Systems (IS).
In EDM
Current system is reviewed
The nature of business area to be supported is
analyzed
Data needed at a very high level of abstraction is
described
One or more DB development projects is planned
 The Database Development Process
How do we determine the type of data that is
required?
Who within the organization needs what
data?
Often this is done using matrixes. One type of
matrix matches business functions with the data
entity types they need; this is called a function-to-
data-entity matrix.
 Planning Matrixes
Show interrelationships between objects.
Location-to-Function
Unit-to-Function
Information System-to-Data Entity
Supporting Function-to-Data Entity
Information System-to-Objective
Example Business Funtion-to-data
entity matrix
Business Function-to-Data Entity
Planning Matrix
Information System-to-Objective
Planning Matrix
Approaches to Develop Database & IS
SDLC
Systems 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
 SDLC
Framework that describes the activity performed
at each stage of a software development project
Traditional methodology used to develop, maintain
and replace Information System
There are many variations of SDLC, 3 to 20 different
phases
The process appears to be circular
Conveys iterative nature of system
The steps can overlap or run parallel
Possible to backtrack
DB Development Activities During the
SDLC
 SDLC
Planning

Analysis

Logical Design

Physical Design

Implementation

Maintenance
 Systems Development Life Cycle
(Planning)
Purposepreliminary understanding
Planning Understand business situation and how IS
might help solve a problem or make an
Analysis opportunity possible
Deliverablerequest for study
Database activity
Enterprise modeling Logical Design
Analyze current data processing
Analyze the general business Physical Design
functions and their DB needs
Justify need for new data and DB in
Implementation
support of business
Early conceptual data modeling
Identify scope of DB requirements Maintenance
for proposed IS
Analyze overall data requirements
for business functions supported by
 Systems Development Life Cycle (Analysis)
Purposethorough requirements analysis and
structuring
To analyze the business situation thoroughly to
Planning
determine requirements, to structure those
requirements and to select among competing system
Analysis features
Deliverablefunctional system specifications
Logical Design
Database activitythorough and integrated
conceptual data modeling Physical Design
Develop preliminary conceptual Data Model,
including entities and relationships
Implementation
Compare preliminary Conceptual Data Model
(CDM) with Enterprise Data Model (EDM)
Develop detailed CDM, including all entities, Maintenance
relationships, attributes and business rules
Make CDM consistent with other models of IS
Populate repository with all conceptual DB specs
 Systems Development Life Cycle
(Logical Design)
Planning
Purpose To elicit and structure all
information requirements
Analysis
Deliverabledetailed design
specifications
Logical Design
Database activity logical database
design Physical Design
Analyze in detail the transactions, forms,
Implementation
displays and inquiries (DB views) required
by the business functions supported by the
Maintenance
DB
Integrate DB views into CDM
Identify data integrity and security
requirements and populate repository 15
 Systems Development Life Cycle
(Physical Design)
Planning Purpose To develop technology
and organizational specifications
Deliverableprogram/data
Analysis
structures, technology purchases,
organization redesigns
Logical Design
Database activity
physical database design Physical Design
Physical Design

Define database to DBMS

Implementation
Decide on physical data
organization
Maintenance
Design database processing
programs
16
 Systems Development Life Cycle
(Implementation)
PurposeTo write programs, build
Planning databases, test and install the new system
train users and finalize documentation
Analysis Deliverableoperational programs,
documentation, training materials
Logical Design

Physical Design
Database activity
database implementation Implementation
Implementation
Code and test DB processing programs
Complete DB documentation and
Maintenance
training materials
Install DB and convert data from prior
system
 Systems Development Life Cycle
(Maintenance)
Planning Purpose To monitor the operations
and usefulness of system and to repair
and enhance the system
Analysis
Deliverableperiodic audits

Logical Design

Physical Design

Database activity
database maintenance Implementation
Analyze DB and DB applications to ensure that
evolving information requirements are met Maintenance
Maintenance
Tune DB for improved performance
Fix errors in DB and DB applications
Recover DB when it is contaminated
 Database SDLC
SDLC Database Development
Activities
Identify Project
Enterprise
Initiate and Plan Modeling
Conceptual
Analyze Data Modeling
Logical
Logical Design DB Design
Physical DB
Physical Design Design/Creation
DB
Implementation Implementation
DB
Maintenance Maintenance
 Benefits of SDLC
Control large complex development projects
ensure team work
Avoid runaway projects
Avoids redundancy or duplication
Ease of maintenance
Easier to train and monitor development
Internal consistency and documentation make it
easier to modify later
Tolerates changes is MIS staffing
 Problems with SDLC
Information gap can be very costly
Designers want to freeze requirements, users
want to keep things open
Additional changes can cause severe delays
Initial user input may be difficult to get
Takes considerable time
All system details have to be specified up front