The Database Environment

and Development Process

Slides in this presentation contain

hyperlinks. JAWS users should be able to
get a list of links by using INSERT+F7
Learning Objectives (1 of 2)
1.1 Define terms
1.2 Name limitations of conventional file processing
1.3 Explain advantages of databases
1.4 Identify costs and risks of databases
1.5 Distinguish between operational and informational data
management
1.6 List components of database environment
Learning Objectives (2 of 2)
1.7 Identify categories of database applications
1.8 Explain prototyping and agile development approaches
1.9 Explain roles of individuals
1.10 Explain differences between personal, multi-tiered,
and enterprise data management
1.11 Explain three-schema architectures (external,
conceptual, internal)
Definitions
• Database: organized collection of logically related data
• Data: stored representations of meaningful objects and
events
– Structured: numbers, text, dates
– Unstructured: images, video, documents
• Information: data processed to increase knowledge in
the person using the data
• Metadata: data that describes the properties and context
of user data
Figure 1-1 Converting Data to Information (1 of 2)

(a) Data in context

Figure 1-1 Converting Data to Information (2 of 2)

(b) Summarized data

Table 1-1 Example Metadata for Class Roster
• Descriptions of the properties or characteristics of the data, including
data types, field sizes, allowable values, and data context

Name Type Length Min imum Max imum Description Source

Course Alphanumeric 30 Blank Blank Course ID and name Academic Unit

Section Integer 1 1 9 Section number Registrar

Semester Alphanumeric 10 Blank Blank Semester and year Registrar
Name Alphanumeric 30 Blank Blank Student name Student I S
ID Integer 9 Blank Blank Student I D (SSN) Student I S
Major Alphanumeric 4 Blank Blank Student major Student I S
GPA Decimal 3 0.0 4.0 Student grade point average Academic Unit
Disadvantages of File Processing
• Program-Data Dependence
– All programs maintain metadata for each file they use
• Duplication of Data
– Different systems/programs have separate copies of the same
data
• Limited Data Sharing
– No centralized control of data
• Lengthy Development Times
– Programmers must design their own file formats
• Excessive Program Maintenance
– 80% of information systems budget
Figure 1-2 Old File Processing Systems at
Pine Valley Furniture Company
The Database Approach (1 of 2)
• Data models
– Graphical diagram capturing nature and relationship of data
– Enterprise Data Model – high-level entities and relationships for the
organization
– Project Data Model – more detailed view, matching data structure in
database or data warehouse
• Entities
– Noun form describing a person, place, object, event, or concept
– Composed of attributes

• Relationships
– Between entities
– Usually one-to-many (1: N) or many-to-many (M : N), but can also be
one-to-one (1:1)
Figure 1-3 Comparison of Enterprise- and
Project-Level Data Models
(a) Segment of an enterprise (b) Segment of a project data model
data model
The Database Approach (2 of 2)
• Relational Databases
• Database technology involving tables (relations) representing entities
and primary/foreign keys representing relationships (see Figure 1-
17)
Advantages of the Database Approach
• 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
Costs and Risks of the Database Approach
• New, specialized personnel
• Installation and management cost and complexity
• Conversion costs
• Need for explicit backup and recovery
• Organizational conflict
Figure 1-5 Integrated Data Management
Framework
Components of the Database Environment
• Data modeling and design tools – automated tools used to design databases and
application programs

• Repository – centralized storehouse of metadata

• Database Management System (D BMS) – software for managing the database

• Database – storehouse of the data

• Application Programs – software using the data

• User Interface – text, graphical displays, menus, etc. for user

• Data/Database Administrators – personnel responsible for maintaining the database

• System Developers – personnel responsible for designing databases and software

• End Users – people who use the applications and databases

Figure 1-6 Components of the Database
Environment
The Database Development Process
• SDLC
– System Development Life Cycle
– Detailed, well-planned development process
– Time-consuming, but comprehensive
– Long development cycle
• Prototyping
– Rapid application development (RAD)
– Cursory attempt at conceptual data modeling
– Define database during development of initial prototype
– Repeat implementation and maintenance activities with
new prototype versions
Systems Development Life Cycle (S DLC)
• The traditional methodology used to develop, maintain, and replace
information systems
• Five main steps:
1. Planning – preliminary understanding of business situation.
Enterprise model and conceptual data modeling.
2. Analysis – thorough analysis of business situation, leading to
functional requirements. Detailed conceptual data modeling.
3. Design – logical and physical database design, to develop
technology and organization.
4. Implementation – writing programs, building databases, testing,
installing, training, and documenting.
5. Maintenance – monitoring, repairing, and enhancing.
From Figure 1-8 Database Development
Activities During the SDLC
Alternative Information Systems
Development Approaches
• Traditional SDLC: methodical, structured, and time
consuming
• Rapid Application Development (RAD): faster and more
adaptive, especially when a database is already in place
• Several flavors:
– Prototyping
– Agile methodologies
– eXtreme programming
– Scrum
– DSDM (dynamic system development methodologies)
Figure 1-9 The Prototyping Methodology
and Database Development Process
Figure 1-10 Three-Schema Architecture
• Different people have different views
of the database
• External Schema
– User Views
– Subsets of Conceptual Schema
– Can be determined from
business-function/data entity
matrices
– DBA determines schema for
different users
• Conceptual Schema (ER models)

• Internal Schema (logical and physical

structures)
Managing People Involved in Database
Development
• Project – a planned undertaking of related activities to
reach an objective that has a beginning and an end
• Initiated and planned in planning stage of SDLC
• Executed during analysis, design, and implementation
• Closed at the end of implementation
Database Project Team Members (1 of 2)
• Business analysts – analyze business situation and
establish requirements
• Systems analysts – like business analysts, but also have
technical expertise for overall information systems
• Database analysts and data modelers – analysts who
focus on database
• Users – the “customers” communicate their needs to
analysts
• Programmers – coders of the programs that interact with
the database