Lecture9 10 - The DB System Development Lifecycle
Lecture9 10 - The DB System Development Lifecycle
Database Systems
2
Software Crisis and Failure
3
Major Reasons of Failure & Solution
4
The Information Systems
Development Lifecycle
(SDLC)
5
6
DSDL – Detailed Stages and Activities
7
1) Database Planning
The management activities that allow the stages of the database system development lifecycle
to be realized as efficiently and effectively as possible.
Database planning must be integrated with the overall IS strategy of the organization.
There are three main issues involved in formulating an IS strategy, which are:
8
1) Database Planning
Mission Statement defines major aims of the database application and helps clarify its purpose
Example: The Purpose of a Hotel database system is to maintain the data that is used to
support hotel room rentals
Mission Objective:
After mission statement mission Objectives are defined which should identify a particular task
that the database must support.
Example: To maintain (insert, update, delete) data on hotel rooms, guests and
bookings.
9
2) System Definition
Describes the scope and boundaries of the database system and the major user views.
User View defines what is required of a database system from the perspective of:
It is important that we include within our system boundaries not only the current users and application
areas, but also future users and applications.
A user view defines what is required of a database system in terms of the data to be held and the
transactions to be performed on the data.
10
2) System Definition
It is important that we include within our system boundaries not only the current
users and application areas, but also future users and applications.
A user view defines what is required of a database system in terms of the data to
be held and the transactions to be performed on the data.
11
Representation of the database with multiple user
views
12
3) Requirements Collection and Analysis
This stage involves the collection and analysis of information about the part of
the enterprise to be served by the database.
There are many techniques for gathering this information, called fact-finding
techniques. Information is gathered for each major user view (that is, job role or
enterprise application area), including:
• a description of the data used or generated;
There are three main approaches to managing the requirements of a database system
with multiple user views:
Centralized Approach: Requirements for each user view are merged into a single set of
requirements for the new database system. A data model representing all user views is
created during the database design stage.
View Integration Approach: Requirements for each user view remain as separate lists.
Data models representing each user view are created and then merged later during the
database design stage.
14
a) Centralized approach
15
b) View Integration
Approach
16
4) Database Design
Creating a Design for a database that will support the mission statement and
mission objectives
Building data model requires answering question about entities, relationships, and
attributes.
17
4) Database Design
Example: ER diagram
18
4) Database Design
19
4) Database Design
20
Data Modeling
21
Phases of Database Design
Three (3) main phases: conceptual, logical, and physical design.
Conceptual Data Model: This represents high-level concepts and relationships between
them. It's often used in the early stages of a project to capture the essential business
requirements.
Logical Data Model: This defines the structure of the data elements and their
relationships, without consideration for specific database implementations. It's more detailed
than a conceptual model and focuses on entities, attributes, and relationships.
Physical Data Model: This describes how data is stored in a specific database
management system (DBMS). It includes details such as tables, columns, indexes, and
constraints.
22
5) DBMS Selection
23
6) Application Design
The design of the user interface and the application programs that use and
process the database.
24
User Interface Design
Guidelines
25
7) Prototyping
A prototype is a working model that does not normally have all the required
features or provide all the functionality of the final system.
• allow users to use the prototype to identify the features of the system that work well or are
inadequate, and if possible
26
8) Implementation
The database implementation is achieved using the DDL of the selected DBMS
The DDL statements are used to create the database structures and empty
database files
Security and integrity controls for the system are also implemented
The application programs are implemented using the preferred third- or fourth
generation language
27
9) Data Conversion and Loading
Transferring any existing data into the new database and converting any existing
applications to run on the new database.
This stage is required only when a new database system is replacing an old system.
Nowadays, it is common for a DBMS to have a utility that loads existing files into the
new database.
The utility usually requires the specification of the source file and the target
database, and then automatically converts the data to the required format of the new
database files.
28
10) Testing
The process of running the database system with the intent of finding errors.
This is achieved using carefully planned test strategies and realistic data
29
Database Evaluation Criteria
Learnability: How long does it take a new user to become productive with the
system?
Performance: How well does the system response match the user’s work practice?
30
11) Operational Maintenance
New requirements are incorporated into the database system through the
preceding stages of the lifecycle.
31
CASE (Computer Aided Software Engineering) Tools
32
Thankyou
Any Queries?
33