The Database Environment and Development Process: Modern Database Management 10 Edition
The Database Environment and Development Process: Modern Database Management 10 Edition
Objectives
Define terms Name limitations of conventional file processing Explain advantages of databases Identify costs and risks of databases List components of database environment Identify categories of database applications Describe database system development life cycle Explain prototyping and agile development approaches Explain roles of individuals Explain the three-schema architecture for databases
2
Definitions
Database: organized collection of logically related data Data: stored representations of meaningful objects and events
Information: data processed to increase knowledge in the person using the data Metadata: data that describes the properties and context of user data
3
Graphical displays turn data into useful information that managers can use for decision making and interpretation
Chapter 1 2011 Pearson Education, Inc. Publishing as Prentice Hall
5
Descriptions of the properties or characteristics of the data, including data types, field sizes, allowable values, and data context
Chapter 1 2011 Pearson Education, Inc. Publishing as Prentice Hall
6
Program-Data Dependence
All programs maintain metadata for each file they use Different systems/programs have separate copies of the same data No centralized control of data Programmers must design their own file formats 80% of information systems budget
Duplication of Data
Each application programmer must maintain his/her own data Each application program needs to include code for the metadata of each file Each application program must have its own processing routines for reading, inserting, updating, and deleting data Lack of coordination and central control Non-standard file formats
Duplicate Data
Data changes in one file could cause inconsistencies Compromises in data integrity
A software system that is used to create, maintain, and provide controlled access to user databases
Order Filling System Central database Contains employee, order, inventory, pricing, and customer data
Invoicing System
DBMS
Payroll System
DBMS manages data resources like an operating system manages hardware resources
12
Program-data independence Planned data redundancy Improved data consistency Improved data sharing Increased application development productivity Enforcement of standards Improved data quality Improved data accessibility and responsiveness Reduced program maintenance Improved decision support
New, specialized personnel Installation and management cost and complexity Conversion costs Need for explicit backup and recovery Organizational conflict
Conflicts on data definitions, formats and coding, rights to update Stand-alone DB: not following DB approach
14
Data models
Entities
Graphical sys capturing nature and relationship of data Enterprise Data Modelhigh-level entities and relationships for the organization Project Data Modelmore detailed view, matching data structure in database or data warehouse Noun, describing a person/place/object/event/concept Composed of attributes
Relationships
Database technology involving tables (relations) representing entities and primary/foreign keys representing relationships Chapter 1 2011 Pearson Education, Inc. Publishing as Prentice Hall
Relational Databases
15
P.11
16
17
One order has many order lines; each order line is associated with a single order
One-to-many relationship
18
One product can be in many order lines, each order line refers to a single product
One-to-many relationship
19
Therefore, one order involves many products and one product is involved in many orders
Many-to-many relationship
Chapter 1 2011 Pearson Education, Inc. Publishing as Prentice Hall
20
21
22
CASE Toolscomputer-aided software engineering Repositorycentralized storehouse of metadata Database Management System (DBMS) software for managing the database Databasestorehouse of the data Application Programssoftware using the data User Interfacetext and graphical displays to users Data/Database Administratorspersonnel responsible for maintaining the database System Developerspersonnel responsible for designing databases and software End Userspeople who use the applications and databases
23
Personal databases Two-tier Client/Server databases Multitier Client/Server databases Enterprise applications
24
25
26
27
Integrate all enterprise functions (manufacturing, finance, sales, marketing, inventory, accounting, human resources) Integrated decision support system derived from various operational databases
Data Warehouse
29
First step in database development Specifies scope and general content Overall picture of organizational data at high level of abstraction Entity-relationship diagram Descriptions of entity types Relationships between entities Business rules
30
31
SDLC
Prototyping
33
Implementation Maintenance
34
Purposethorough requirements analysis and structuring Deliverablefunctional system specifications Analysis Analysis
Logical Design Physical Design
Implementation Maintenance
35
Database activity logical database design (transactions, forms, displays, views, data integrity and security)
Implementation Maintenance
36
Purposedevelop technology and organizational specifications Deliverableprogram/data structures, technology purchases, organization redesigns
Physical Design Physical Design Database activity physical database design (define database to DBMS, physical data organization, database processing programs)
Implementation Maintenance
37
Purposeprogramming, testing, training, installation, documenting Deliverableoperational programs, documentation, training materials
Database activity database implementation, including coded programs, documentation, installation and conversion
38
Deliverableperiodic audits
Database activity database maintenance, performance analysis and tuning, error corrections
39
40
41
42
43
44
Database Schema
External Schema
User Views Subsets of Conceptual Schema Can be determined from business-function/data entity matrices DBA determines schema for different users E-R modelscovered in Chapters 2 and 3 Logical structurescovered in Chapter 4 Physical structurescovered in Chapter 5
Conceptual Schema
Internal Schema
45
46
Managing Projects
Projecta planned undertaking of related activities to reach an objective that has a beginning and an end Involves use of review points for:
Incremental commitmentreview of systems development project after each development phase with rejustification after each phase
47
Validation of satisfactory progress Step back from detail to overall view Renew commitment of stakeholders
Business analysts Systems analysts Database analysts and data modelers Users Programmers Database architects Data administrators Project managers Other technical experts
48
49