0% found this document useful (0 votes)
18 views33 pages

Lecture9 10 - The DB System Development Lifecycle

This document outlines the stages of the database system development lifecycle (DSDLC), emphasizing the importance of planning, design, and evaluation in creating effective database systems. It discusses the phases of database design, including conceptual, logical, and physical design, as well as criteria for selecting a Database Management System (DBMS). Additionally, it highlights the challenges faced in software development and the role of Computer-Aided Software Engineering (CASE) tools in improving the process.

Uploaded by

M Mahtab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views33 pages

Lecture9 10 - The DB System Development Lifecycle

This document outlines the stages of the database system development lifecycle (DSDLC), emphasizing the importance of planning, design, and evaluation in creating effective database systems. It discusses the phases of database design, including conceptual, logical, and physical design, as well as criteria for selecting a Database Management System (DBMS). Additionally, it highlights the challenges faced in software development and the role of Computer-Aided Software Engineering (CASE) tools in improving the process.

Uploaded by

M Mahtab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 33

CC-2141

Database Systems

Department of Computer Science


School of Systems & Technology - SST
Chapter Objectives

In this chapter you will learn:


The main stages of the database system development lifecycle (DSDLC).
The main phases of database design: conceptual, logical, and physical design.
The types of criteria used to evaluate a DBMS.
How to evaluate and select a DBMS.
The benefits of Computer-Aided Software Engineering (CASE) tools.

2
Software Crisis and Failure

 80–90% do not meet their performance goals;

 about 80% are delivered late and over budget;

 around 40% fail or are abandoned;

 under 40% fully address training and skills requirements;

 less than 25% properly integrate enterprise and technology objectives;

 just 10–20% meet all their success criteria.

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:

• identification of enterprise plans and goals with subsequent determination of information


systems needs;

• evaluation of current information systems to determine existing strengths and weaknesses;

• appraisal of IT opportunities that might yield competitive advantage.

8
1) Database Planning

 Define Mission Statement:

 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.

 A database system may have one or more user views.

 User View defines what is required of a database system from the perspective of:

• A Particular Job role (such as a Manager or a supervisor) or

• Enterprise application areas (such as marketing, sales etc)

 Identifying user views is an important aspect of developing a database system.

 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

 Identifying user views is an important aspect of developing a database system.

 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;

• the details of how data is to be used or generated;

• any additional requirements for the new database system.

 These requirements are described in documents collectively referred to as


requirements specifications.
13
Managing Requirements

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.

Mixed Approach: Integration of both the approaches

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

 Data modeling is the data design phase

 Building data model requires answering question about entities, relationships, and
attributes.

17
4) Database Design

 Three phases of database design: conceptual, logical, and physical design.

 Conceptual Design: Process of constructing a model of the data used , independent of


all physical consideration, Conceptual data model is built using the information in users
requirement specification

 Example: ER diagram

18
4) Database Design

Logical Design: Conceptual data model is independent of all physical consideration, a


logical model is derived knowing the underlined data model of the target DBMS

Example: Relational Data model

19
4) Database Design

 Physical Database Design: It specifies a description of the physical configuration of the


database, such a the tables, file organizations, indexes, security, datatypes, and other
parameters of data dictionary

 To describe how we intend to physically implement the logical database design

20
Data Modeling

 Data modeling is the process of


creating a visual representation
of the structure and relationships within a
database.

 It involves defining the data


elements and how they relate to
each other, as well as the rules and
constraints that govern the data's
behavior.

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.

 Two (2) aspects of application design:

 Transaction Design: An action, or series of actions, carried out by a single user or


application program, that accesses or changes the content of the database.

 User Interface Design: process of creating interfaces for software applications,


websites, and other digital products that are visually appealing, easy to use, and
intuitive for users.

24
User Interface Design
Guidelines

25
7) Prototyping

 Building a working model of a database system

 A prototype is a working model that does not normally have all the required
features or provide all the functionality of the final system.

 The main purpose of developing a prototype database system is to:

• allow users to use the prototype to identify the features of the system that work well or are
inadequate, and if possible

• to suggest improvements or even new features to the database system.

26
8) Implementation

 The physical realization of the database and application designs.

 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

 If testing is conducted successfully, it will uncover errors with the application


programs and possibly the database structure.

 Testing should also cover usability of the database system

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?

 Robustness: How tolerant is the system of user error?

 Recoverability: How good is the system at recovering from user errors?

 Adaptability: How closely is the system tied to a single model of work?

30
11) Operational Maintenance

 The process of monitoring and maintaining the database system following


installation.

 Monitoring the performance of the system.

 If the performance falls below an acceptable level, tuning or reorganization of the


database may be required.

 Maintaining and upgrading the database system (when required).

 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

You might also like