Database Design Methodology

DatabaseDesign Methodology

Lesson 1:Introduction to Databases

Objectives

• List database types (e.g., flat file, relational), and identify their uses and architectures

• Describe the types of database management system (DBMS), and explain the benefits and limitations of each DBMS type

• Analyze and select appropriate database designs, and identify the solution that addresses the application needs

What Isa Database?

• File-based databases– Flat-file databases

• The evolution of databases

Relational Databasesand DBMSs

• Relational databases

• Structured Query Language

• Database administrator

• Advantages and disadvantages of DBMSs

• Choosing the correct database type

The Origins ofRelational Databases

• Codd first proposed the relational data model in 1970

• System R

• Development of SQL

• INGRES

• IBM UK Scientific Center

Summary

List database types (e.g., flat file, relational), and identify their uses and architectures

Describe the types of database management system (DBMS), and explain the benefits and limitations of each DBMS type

Analyze and select appropriate database designs, and identify the solution that addresses the application needs

Lesson 2:Relational

Database Fundamentals

Objectives• Define common database architectures

(e.g., single, multi-tier)• Describe the function of Structured Query

Language (SQL), including language subsets

• Describe the function of Data Definition Language (DDL)

• Describe the function of Data Manipulation Language (DML)

Objectives (cont’d)

• Describe the function of Data Control Language (DCL)

• Define essential database concepts and terms, including relation, relation name, table, row, column, value, relational algebra, data modeling, data relationship

• Explain the concepts of attribute, degree, tuple and cardinality


• Define entities, including strong entities, weak entities

• List characteristics of relations (e.g., column characteristics, row characteristics)

• Describe table types (e.g., base tables, virtual tables)

• Distinguish between primary and foreign keys, including null value, composite key

• Explain data models in relational databases


• Describe common database relationships (e.g., one to one, one to many, many to many) and identify the notation for such relationships (e.g., 1:n)

• Define relational integrity concepts, including domain constraints, entity and referential integrity views

• Explain the structure and purpose of a data dictionary

MultitierDatabase Architecture

• Two-tier client-server architecture– Fat client

• Three-tier client-server architecture– Thin client

• n-tier architecture

RelationalModel Terminology

• Relational data structure

• Rows (tuples)

• Columns (attributes)

• Domains

• Degrees

• Cardinality

• Normalization

Using Tablesto Represent Data

• Entities

• Characteristics of relations

• Types of tables

• Primary keys

• Foreign keys

Data Models

• Components– Structural information– Manipulative information– Integrity information

Entities andData Relationships

• Entity-relationship (ER) modeling

• Strong entities

• Weak entities

Relational Integrity

• Domain constraints

• Entity integrity

• Referential integrity

• Views

Database Languages

• Data Definition Language

• Data Manipulation Language

• Data Control Language

• Data dictionaries

SummaryDefine common database architectures

(e.g., single, multi-tier)Describe the function of Structured Query

Language (SQL), including language subsets

Describe the function of Data Definition Language (DDL)

Describe the function of Data Manipulation Language (DML)

Summary (cont’d)

Describe the function of Data Control Language (DCL)

Define essential database concepts and terms, including relation, relation name, table, row, column, value, relational algebra, data modeling, data relationship

Explain the concepts of attribute, degree, tuple and cardinality

Summary (cont’d)

Define entities, including strong entities, weak entities

List characteristics of relations (e.g., column characteristics, row characteristics)

Describe table types (e.g., base tables, virtual tables)

Distinguish between primary and foreign keys, including null value, composite key

Explain data models in relational databases

Summary (cont’d)

Describe common database relationships (e.g., one to one, one to many, many to many) and identify the notation for such relationships (e.g., 1:n)

Define relational integrity concepts, including domain constraints, entity and referential integrity views

Explain the structure and purpose of a data dictionary

Lesson 3:Database Planning

Objectives• Describe the elements of a database planning

strategy (e.g., defining the scope of a database application)

• List the necessary steps for creating a database requirements document, including conducting interviews, noting project constraints, identifying the precise duties of the database, creating a database design document


• Explain the importance of data modeling and entity relationship diagrams during the planning stage (e.g., define the concept of an entity-relationship [ER] diagram)

• Create a database prototype• Describe the purpose of database application

testing, including white-box testing, black-box testing


• List the criteria for selecting a database management system and an application interface

• Describe database design steps, including determining the proper steps in creating entities, applying normalization, selecting a database management system (DBMS)

Database Design Life Cycle

• Create a database strategy• Define database

application scope• Create a database

requirements document• Design the database• Select a DBMS• Design the database

application

• Create database prototypes

• Test the database application

• Implement the database application

• Convert legacy data

• Maintain the database

DatabaseRequirements Document

• Conducting interviews

• Requirements document information

Selecting a DBMS

• Selection criteria– Data definition functionality– Physical criteria– Access criteria– Transactions– Utilities– Development tools– Miscellaneous features

Selecting anApplication Interface

GUI considerations– Descriptive page titles– Clear instructions– Consistent grouping of

input fields– Logically labeled fields– Consistent color use– Properly sized data

entry fields

– Logical cursor movement

– Error messages

– Clearly indicated optional fields

– Completion message

SummaryDescribe the elements of a database

planning strategy (e.g., defining the scope of a database application)

List the necessary steps for creating a database requirements document, including conducting interviews, noting project constraints, identifying the precise duties of the database, creating a database design document

Summary (cont’d)

Explain the importance of data modeling and entity relationship diagrams during the planning stage (e.g., define the concept of an entity-relationship [ER] diagram)

Create a database prototypeDescribe the purpose of database

application testing, including white-box testing, black-box testing

Summary (cont’d)

List the criteria for selecting a database management system and an application interface

Describe database design steps, including determining the proper steps in creating entities, applying normalization, selecting a database management system (DBMS)

Lesson 4:Overview of DatabaseDesign Methodology

Objectives

• List the steps of the conceptual design phase (e.g., identifying entities, attribute domains, relationships)

• Describe how to identify entities

• List ways to identify attributes and attribute domains for entities


• List ways to identify candidate and primary keys for entities

• Identify and determine data relationships

• Create an entity-relationship (ER) diagram

• Analyze an entity-relationship (ER) diagram or model to determine relation types


• Define and describe domains• Explain the results of poor database design,

and describe insertion, deletion and update anomalies in databases


Effects ofPoor Database Design

• Insertion anomalies

• Deletion anomalies

• Update anomalies

DatabaseDesign Phases

• Conceptual phase

• Logical phase

• Physical phase

ConceptualDatabase Design

• Identifying entities• Identifying attributes and attribute domains for

entities• Identifying relationships• Identifying candidate and primary keys for entities• Creating an entity-relationship (ER) diagram• Reviewing the ER model by the user and design

team

Entity-Relationship Models

• Creating ER models

• Defining domains

• Common SQL data types

• Determining data relationships– Recursive relationships

Summary

List the steps of the conceptual design phase (e.g., identifying entities, attribute domains, relationships)

Describe how to identify entitiesList ways to identify attributes and attribute

domains for entities

Summary (cont’d)

List ways to identify candidate and primary keys for entities

Identify and determine data relationshipsCreate an entity-relationship (ER) diagramAnalyze an entity-relationship (ER)

diagram or model to determine relation types

Summary (cont’d)

Define and describe domainsExplain the results of poor database design,

and describe insertion, deletion and update anomalies in databases


Lesson 5:Normalization

Objectives

• Distinguish between specific normal forms, including first normal form (1NF), second normal form (2NF), third normal form (3NF), Boyce-Codd normal form (BCNF)

• Describe the normalization process

• Define and explain determinant, decomposition and functional dependency

What Is Normalization?

• Normal forms

• First normal form– First normal form anomalies

• Second normal form– Second normal form anomalies

• Third normal form

• Boyce-Codd normal form

Related Concepts

• Decomposition

• Atomic value

• Partial functional dependency

• Transitive dependency

• Denormalization

Summary

Distinguish between specific normal forms, including first normal form (1NF), second normal form (2NF), third normal form (3NF), Boyce-Codd normal form (BCNF)

Describe the normalization processDefine and explain determinant,

decomposition and functional dependency

Summary (cont’d)


Lesson 6:Logical Database Design

Objectives

• Explain the structure and purpose of a data dictionary

• Identify logical database design issues

• List the steps of the logical database design phase (e.g., creating a raw data model; identifying and documenting entities, attributes, relationships, domains, and candidate and primary keys)


• Identify the cardinality of data relationships

• Identify and resolve inexpedient data relationships

• Create an integrated logical data model from a conceptual data model

• Use Data Definition Language (DDL)


• Validate a logical data model against user operations and system requirements

• Define integrity constraints (e.g., necessary data, domain constraints, entity integrity, referential integrity)

• Create corporate and enterprise data models based on user views of data


• Validate the enterprise data model


LogicalDatabase Design

• Logical data models– One-to-one– One-to-many– Many-to-many

Creating aLogical Data Model

Data model refinement

Logical data model creation

Normalization

Logical data model creation

Data model refinement

Normalization

Using a DatabaseDefinition Language

• Data dictionaries

• Validating the logical data model

DefiningIntegrity Constraints

• Necessary data

• Domain constraints

• Entity integrity

• Referential integrity

• Enterprise constraints

Creating anEnterprise Data Model

• User views

• Normalization

• Validating data operations

Summary

Explain the structure and purpose of a data dictionary

Identify logical database design issuesList the steps of the logical database design

phase (e.g., creating a raw data model; identifying and documenting entities, attributes, relationships, domains, and candidate and primary keys)

Summary (cont’d)

Identify the cardinality of data relationshipsIdentify and resolve inexpedient data

relationshipsCreate an integrated logical data model

from a conceptual data modelUse Data Definition Language (DDL)

Summary (cont’d)

Validate a logical data model against user operations and system requirements

Define integrity constraints (e.g., necessary data, domain constraints, entity integrity, referential integrity)

Create corporate and enterprise data models based on user views of data

Summary (cont’d)

Validate the enterprise data modelDescribe database design steps, including

determining the proper steps in creating entities, applying normalization, selecting a database management system (DBMS)

Lesson 7:Physical Database Design

Objectives

• List the elements of physical database design

• Determine physical database design issues

• Describe how to create base relations for a target database management system (DBMS) using Data Definition Language (DDL)


• Identify and create enterprise constraints for a target DBMS

• Define secondary indexes and determine when to use them

• Create a base relation

• Identify referential constraints


• Explain denormalization and describe when it is necessary

• Create user views (e.g., the CREATE VIEW SQL statement)

• Design database access rules


• Use appropriate commands to create, insert and retrieve data from a database table, including the SELECT, CREATE TABLE and CREATE VIEW statements

PhysicalDatabase Design

• Creating base relations for a target DBMS

• Data Definition Language

CreatingEnterprise Constraints

• Determining referential constraints

UsingSecondary Indexes

• A secondary index is a mechanism that creates an additional key for a relation

Denormalization

• The process of reuniting relations that were split during the normalization process to improve performance

CreatingUser Views

• Determine the appropriate data to be included with each particular view

DesigningDatabase Access Rules

• Identifiers

• Privileges– SELECT– UPDATE– DELETE

Summary

List the elements of physical database design

Determine physical database design issuesDescribe how to create base relations for a

target database management system (DBMS) using Data Definition Language (DDL)

Summary (cont’d)

Identify and create enterprise constraints for a target DBMS

Define secondary indexes and determine when to use them

Create a base relationIdentify referential constraints

Summary (cont’d)

Explain denormalization and describe when it is necessary

Create user views (e.g., the CREATE VIEW SQL statement)

Design database access rules

Summary (cont’d)

Use appropriate commands to create, insert and retrieve data from a database table, including the SELECT, CREATE TABLE and CREATE VIEW statements

Lesson 8:Structured Query Language

Objectives• Perform data manipulation• Describe basic SQL syntax• List data types used in SQL, including

SMALLINT, DECIMAL (p, q), CHAR(n) and TIMESTAMP

• Define the term schema in relation to databases

• Create a schema using the CREATE SCHEMA statement


• Drop schemas from a database using the DROP SCHEMA statement

• Use appropriate commands to create, insert and retrieve data from a database table, including using the SELECT, CREATE TABLE and CREATE VIEW statements

• Use the INSERT command appropriately


• Use appropriate UPDATE and DELETE statements to update or delete information from a database, including working with tuples

• Use the DISTINCT keyword

• Compose predicates and other statements using the WHERE clause


• Identify the use and structure of Boolean operators

• Describe SQL special operators and ORDER BY clauses (e.g., the IN, BETWEEN and LIKE operators)

• Deploy the ORDER BY clause to order output by column or group of columns


• Retrieve data from relations using the SELECT statement

• Create statements using the GRANT keyword to control user access to relations

• Use the REVOKE keyword to limit access

SQL Basics

• Subsets of SQL

• SQL features

• Data types

DataDefinition Language

• Creating a schema

• Altering and dropping relations and views

DataManipulation Language

• Inserting values into relations• Deleting records from relations• Updating values in relations• Retrieving data from relations• Aliases• SQL special operators and ORDER BY

clauses

DataControl Language

• Granting privileges

• Revoking privileges

SummaryPerform data manipulationDescribe basic SQL syntaxList data types used in SQL, including

SMALLINT, DECIMAL (p, q), CHAR9n) and TIMESTAMP

Define the term schema in relation to databases

Create a schema using the CREATE SCHEMA statement

Summary (cont’d)

Drop schemas from a database using the DROP SCHEMA statement

Use appropriate commands to create, insert and retrieve data from a database table, including using the SELECT, CREATE TABLE and CREATE VIEW statements

Use the INSERT command appropriately

Summary (cont’d)

Use appropriate UPDATE and DELETE statements to update or delete information from a database, including working with tuples

Use the DISTINCT keywordCompose predicates and other statements

using the WHERE clause

Summary (cont’d)

Identify the use and structure of Boolean operators

Describe SQL special operators and ORDER BY clauses (e.g., the IN, BETWEEN and LIKE operators)

Deploy the ORDER BY clause to order output by column or group of columns

Summary (cont’d)

Retrieve data from relations using the SELECT statement

Create statements using the GRANT keyword to control user access to relations

Use the REVOKE keyword to limit access

Lesson 9:Relational Algebra

Objectives

• Describe a selection operation

• Create a projection operation

• Explain and use a Cartesian product operation

• Create unions

• Define a set difference operation


• Describe an intersection operation

• Create a theta-join

• Use a natural join

• Create an equi-join

• Create an outer join

DefiningRelational Algebra

• Selection

• Projection

• Cartesian product

• Union

• Difference

• Intersection

• Joins

Summary

Describe a selection operationCreate a projection operationExplain and use a Cartesian product

operationCreate unionsDefine a set difference operation

Summary (cont’d)

Describe an intersection operationCreate a theta-joinUse a natural joinCreate an equi-joinCreate an outer join

Lesson 10:Transactions andDatabase Security

Objectives

• Define the concept of a transaction, including use of the INSERT, DELETE and UPDATE operations

• Identify the two results of a transaction (commit and rollback)

• Describe the four desirable "ACID" properties (atomicity, consistency, isolation, durability)


• Define serializability in relation to a DBMS• List concurrency control methods, including

locking and timestamps• Describe the steps involved in optimistic

concurrency control (e.g., reading, validation, writing), including knowing when and when not to use optimistic concurrency control


• Identify issues that can occur if concurrency control is not enacted property (e.g., dirty reads, lost and uncommitted updates, unrepeatable query results)

• Identify issues and determine the scope of database security (e.g., theft, privacy, integrity control, availability)


• List typical security threats to databases

• Describe database countermeasure and protection techniques (e.g., encryption, ways to create views)

Transactions

• Commit

• Rollback

• ACID properties– Atomicity– Consistency– Isolation– Durability

Concurrency Control

• Lost updates• Uncommitted updates• Unrepeatable query results• Serializability• Concurrency control methods

– Locking– Timestamps

• Optimistic concurrency control

DatabaseSecurity

• The scope of database security

• Types of security threats

• Types of protection techniques

Summary

Define the concept of a transaction, including use of the INSERT, DELETE and UPDATE operations

Identify the two results of a transaction (commit and rollback)

Describe the four desirable "ACID" properties (atomicity, consistency, isolation, durability)

Summary (cont’d)

Define serializability in relation to a DBMSList concurrency control methods, including

locking and timestampsDescribe the steps involved in optimistic

concurrency control (e.g., reading, validation, writing), including knowing when and when not to use optimistic concurrency control

Summary (cont’d)

Identify issues that can occur if concurrency control is not enacted property (e.g., dirty reads, lost and uncommitted updates, unrepeatable query results)

Identify issues and determine the scope of database security (e.g., theft, privacy, integrity control, availability)

Summary (cont’d)

List typical security threats to databasesDescribe database countermeasure and

protection techniques (e.g., encryption, ways to create views)


Introduction to DatabasesRelational Database FundamentalsDatabase PlanningOverview of Database Design MethodologyNormalization


Logical Database DesignPhysical Database DesignStructured Query LanguageRelational AlgebraTransactions and Database Security

Database Design Methodology

• For information about the CIW Database Specialist exam and certification, visit www.CIW-certified.com

Database Design Methodology

Documents

Transcript of Database Design Methodology