Database System Development Lifecycle

From Chapter 10, Database Systems by Connolly and Begg (5th edn, 2010)

Pearson Education 2009

Objectives
Main

components of an information system.

Main

stages of database system development lifecycle. phases of database design: conceptual, logical, and physical design.

Main

Pearson Education 2009

2 2

Information System (IS)

Resources

that enable collection, management, control, and dissemination of information throughout an organization. is fundamental component of an IS, and its development/usage should be viewed from perspective of the wider requirements of the organization.

Database

Pearson Education 2009

Database System Development Lifecycle

Database

planning

System

definition
collection and analysis

Requirements

Database
DBMS

design

selection (optional)

Pearson Education 2009

Database System Development Lifecycle

Application Prototyping

design (optional)

Implementation Data

conversion and loading maintenance

Testing Operational

Pearson Education 2009

Stages of the Database System Development Lifecycle

Pearson Education 2009

Database Planning
Management

activities that allow stages of database system development lifecycle to be realized as efficiently and effectively as possible. be integrated with overall IS strategy of the organization.

Must

Pearson Education 2009

Database Planning Mission Statement

Mission

statement for the database project defines major aims of database application. driving database project normally define the mission statement.

Those

Mission

statement helps clarify purpose of the database project and provides clearer path towards the efficient and effective creation of required database system.

Pearson Education 2009

Database Planning Mission Objectives

Once

mission statement is defined, mission objectives are defined. objective should identify a particular task that the database must support.

Each

May

be accompanied by some additional information that specifies the work to be done, the resources with which to do it, and the money to pay for it all.

Pearson Education 2009

Database Planning

Database planning should also include development of standards that govern:

how data will be collected, how the format should be specified, what necessary documentation will be needed, how design and implementation should proceed.

Pearson Education 2009

10

System Definition
Describes

scope and boundaries of database system and the major user views. view defines what is required of a database system from perspective of: a particular job role (such as Manager or Supervisor) or enterprise application area (such as marketing, personnel, or stock control).
Pearson Education 2009

User

11

System Definition
Database

application may have one or more user views. user views helps ensure that no major users of the database are forgotten when developing requirements for new system. views also help in development of complex database system allowing requirements to be broken down into manageable pieces.
Pearson Education 2009

Identifying

User

12

Representation of a Database System with Multiple User Views

13
Pearson Education 2009

Requirements Collection and Analysis

Process

of collecting and analyzing information about the part of organization to be supported by the database system, and using this information to identify users requirements of new system.

Pearson Education 2009

14

Requirements Collection and Analysis

Information

including: a description of data used or generated; details of how data is to be used/generated; any additional requirements for new database system.

is gathered for each major user view

Information

is analyzed to identify requirements to be included in new database system. Described in the requirements specification.
Pearson Education 2009

15

Requirements Collection and Analysis

Another

important activity is deciding how to manage the requirements for a database system with multiple user views. Three main approaches: centralized approach; view integration approach; combination of both approaches.

Pearson Education 2009

16

Requirements Collection and Analysis

Centralized

approach Requirements for each user view are merged into a single set of requirements. A data model is created representing all user views during the database design stage.

Pearson Education 2009

17

Centralized Approach to Managing Multiple User Views

Pearson Education 2009

18

Requirements Collection and Analysis

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.

Pearson Education 2009

19

Requirements Collection and Analysis

Data

model representing single user view (or a subset of all user views) is called a local data model.

Each

model includes diagrams and documentation describing requirements for one or more but not all user views of database.

Pearson Education 2009

20

Requirements Collection and Analysis

Local

data models are then merged at a later stage during database design to produce a global data model, which represents all user views for the database.

Pearson Education 2009

21

View Integration Approach to Managing Multiple User Views

Pearson Education 2009

22

Database Design
Process

of creating a design for a database that will support the enterprises mission statement and mission objectives for the required database system.

Pearson Education 2009

23

Database Design
Main approaches include: Top-down or Entity-Relationship Modelling Bottom-up or Normalisation Top-down approach Starts with high-level entities and relationships with successive refinement to identify more detailed data model. Suitable for complex databases. Bottom-up approach Starts with a finite set of attributes and follows a set of rules to group attributes into relations that represent entities and relationships. Suitable for small number of attributes.
Pearson Education 2009

24

Database Design
Main

purposes of data modeling include: to assist in understanding the meaning (semantics) of the data; to facilitate communication about the information requirements.

Building

data model requires answering questions about entities, relationships, and attributes.
25

Pearson Education 2009

Database Design

A data model ensures we understand: - each users perspective of the data; - nature of the data itself, independent of its physical representations; - use of data across user views.

Pearson Education 2009

26

Criteria to Produce an Optimal Data Model

Pearson Education 2009

27

Database Design

Three phases of database design: Conceptual database design Logical database design Physical database design.

Pearson Education 2009

28

Conceptual Database Design

Process of constructing a model of the data used in an enterprise, independent of all physical considerations. Data model is built using the information in users requirements specification. Conceptual data model is source of information for logical design phase.

Pearson Education 2009

29

Logical Database Design

Process

of constructing a model of the data used in an enterprise based on a specific data model (e.g. relational), but independent of a particular DBMS and other physical considerations. data model is refined and mapped on to a logical data model.

Conceptual

Pearson Education 2009

30

Physical Database Design

Process

of producing a description of the database implementation on secondary storage. base relations, file organizations, and indexes used to achieve efficient access to data. Also describes any associated integrity constraints and security measures. to a specific DBMS.

Describes

Tailored

Pearson Education 2009

31

Three-Level ANSI-SPARC Architecture and Phases of Database Design

Pearson Education 2009

32

DBMS Selection
Selection

of an appropriate DBMS to support the database system. Undertaken at any time prior to logical design provided sufficient information is available regarding system requirements. Main steps to selecting a DBMS:
define Terms of Reference of study; shortlist two or three products; evaluate products; recommend selection and produce report.
Pearson Education 2009

33

DBMS Evaluation Features

Pearson Education 2009

34

DBMS Evaluation Features

Pearson Education 2009

35

Example - Evaluation of DBMS Product

Pearson Education 2009

36