INFORMATION MANAGEMENT
Module 1: Database
Environment and Development
Process
MODULE 1 SUBTOPIC 1
THE DATABASE ENVIRONMENT
At the end of the chapter, the learner should be able to:
➢ 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
• Database: is an organized collection of structured
information, or data, typically stored electronically in a
computer system. (oracle.com)
• Data: is made up of small facts without context.
• Structured data: data that fits neatly into data tables and includes discrete data
types such as numbers, short text, and dates.
• Unstructured: data that doesn’t fit neatly into a data table because its size or nature:
for example, audio, and video files and large text documents (aws.amazon.com)
• Information: If you give data context, then you have
information. Knowledge is gained when information is
consumed and used for decision making (oracle.com).
Figure 1: Example of a Class Roster
Graphical displays turn data into useful information that managers can use for decision making and
interpretation
Figure 2: Pie chart of FY19 Budget Request Figure 3: Graph chart of Share of Recent
High School Graduates Enrolling in College,
by Income Group
Metadata: is "data about data," providing context and details
about a data set, object, or resource, like author, creation
date, file size, or keywords, which helps in organizing,
managing, and finding information more efficiently.
Descriptions of the properties or characteristics of the data, including data types, field
sizes, allowable values, and data context
• File Processing systems
These are traditional methods for storing and managing
data using individual computer files.
Data is stored in files, which can be organized into
directories or folders.
Database Systems 1
• Program-Data Dependence
• All programs maintain metadata for each file they use
Figure 4: Old File processing systems at Pine Valley
Furniture Company
• Duplication of Data
• Different systems/programs have separate copies of the same
data
Figure 4: Old File processing systems at Pine Valley
Furniture Company
• Limited Data Sharing
• No centralized control of data
Figure 4: Old File processing systems at Pine Valley
Furniture Company
Database Systems 1
• Lengthy Development Times
• Programmers must design their own file formats
Database Systems 1
• Excessive Program Maintenance
• 80% of information systems budget
• Heavy program maintenance load in organizations that relied
on traditional file processing systems.
Question: How do we solve these disadvantages?
Database Systems 1
• Central repository of shared data
• Data is managed by a controlling
agent
• Stored in a standardized,
convenient form
Requires a Database Management System (DBMS)
Database Systems 1
• A software
system that is used to create, maintain, and
provide controlled access to user databases
Order Filing
System
Invoicing Central database
System DBMS
Contains employee,
order, inventory,
pricing, and
Payroll customer data
System
Figure 5: Database Management System Structure
Database Systems 1
1. Program-data independence
2. Planned data redundancy
3. Improved data consistency
4. Improved data sharing
5. Increased application development productivity
Database Systems 1
6. Enforcement of standards
7. Improved data quality
8. Improved data accessibility and responsiveness
9. Reduced program maintenance
10.Improved decision support
Database Systems 1
1. New, specialized personnel
2. Installation and management cost and complexity
3. Conversion costs
4. Need for explicit backup and recovery
5. Organizational conflict
Data models
– Graphical system capturing nature and relationship of data
– Enterprise Data Model (EDM) – is a high-level, integrated framework that provides a unified view of an
organization’s data, ensuring consistency and standardization across all systems.
– Project Data Model - is a detailed representation of the data requirements and structures specific to a
single project, focusing on how data will be organized, stored, and used within that project’s scope.
Entities
– Noun form describing a person, place, object, event, or concept
– Composed of attributes
Relationships
– Between entities
– Usually one-to-many (1:M) or many-to-many (M:N)
Relational Databases
– Database technology involving tables (relations) representing entities and primary/foreign keys representing
relationships
Figure 6: Components of the Database Environment
• CASE Tools–computer-aided software
engineering tools are software application
that supports system development by
automating tasks such as analysis, design,
coding, and testing to improve efficiency
and accuracy
• Repository–centralized storehouse of metadata
• Database Management System (DBMS) –
software for managing the database
• Database–storehouse of the data
• Application Programs–software using the data
• User Interface–text and graphical displays to
users
• 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
END OF MODULE 1
SUBTOPIC 1
MODULE 1 SUBTOPIC 2
DATABASE DEVELOPMENT
PROCESS
At the end of the chapter, the learner should be able to:
• Describe database system development life cycle
• Explain prototyping and agile development approaches
• Explain roles of individuals
• Explain the three-schema architecture for databases
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
Database Systems 1
Planning
Analysis
Logical Design
Physical Design
Implementation
Maintenance
Database Systems 1
Purpose–preliminary understanding
Deliverable–request for study
Planning
Planning
Database activity–
enterprise modeling
Analysis
and early conceptual
data modeling
Logical Design
Physical Design
Implementation
Maintenance
Database Systems 1
Purpose–thorough requirements analysis
and structuring
Planning Deliverable–functional system specifications
Analysis
Analysis Database activity–thorough
and integrated conceptual
data modeling
Logical Design
Physical Design
Implementation
Maintenance
Database Systems 1
Purpose–information requirements elicitation
and structure
Deliverable–detailed design specifications
Planning
Database activity–
Analysis logical database design
(transactions, forms,
displays, views, data
Logical Design
Logical Design integrity and security)
Physical Design
Implementation
Maintenance
Database Systems 1
Purpose–develop technology and
organizational specifications
Planning Deliverable–program/data
structures, technology purchases,
organization redesigns
Analysis
Logical Design Database activity–
physical database design
Physical Design
Physical Design (define database to DBMS,
physical data organization,
database processing programs)
Implementation
Maintenance
Database Systems 1
Purpose–programming, testing,
training, installation, documenting
Planning Deliverable–operational programs,
documentation, training materials
Analysis
Database activity–
database implementation,
Logical Design
including coded
programs, documentation,
Physical Design installation and
conversion
Implementation
Implementation
Maintenance
Database Systems 1
Purpose–monitor, repair, enhance
Planning Deliverable–periodic audits
Analysis Database activity–
database maintenance,
performance analysis
Logical Design
and tuning, error
corrections
Physical Design
Implementation
Maintenance
Maintenance
Database Systems 1
Figure 8: Three-schema architecture
External Schema Different
• User Views people have
different views
• Subsets of Conceptual Schema
of the
• Can be determined from business- database…these
function/data entity matrices are the external
• DBA determines schema for different users schema
Conceptual Schema The internal
• E-R models schema is the
Internal Schema underlying
design and
• Logical structures implementation
• Physical structures
Database Systems 1
• 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 Systems 1
• Business analysts
• Systems analysts
• Database analysts and data modelers
• Data/Database administrators
• Project managers
• Users
• Programmers
• Database architects
• Other technical experts
Database Systems 1
Driven by four main objectives:
• Need for program-data independence ➔ reduced maintenance
• Desire to manage more complex data types and structures
• Ease of data access for less technical personnel
• Need for more powerful decision support platforms
Figure 9: Evolution of database technologies
Database Systems 1
Figure 9: Evolution of database technologies
Database Systems 1
Figure 9: Evolution of database technologies
Database Systems 1
Figure 9: Evolution of database technologies
Database Systems 1
Figure 9: Evolution of database technologies
Database Systems 1
Figure 10.1: Evolution of database technologies
Database Systems 1
Database architecture refers to the overall design and structure of a database system, including the
hardware and software components that make up the system, the way the data is organized and
stored, and the way s in which the data can be ac ce sse d and manipulated.
Figure 10: Database Architectures
Database Systems 1
Figure 10: Database Architectures
Database Systems 1
Figure 10: Database Architectures
Database Systems 1
• Personal databases
• Multitier client/server databases
• Enterprise applications
• Enterprise resource planning (ERP) systems
• Data warehousing implementations
Database Systems 1
Table 1.5 Summary of Database Application
Type of Database or Application Typical Number of Users Typical Size of Database
Personal 1 Megabytes
Two-tier 5-100 Megabytes-gigabytes
Three-tier 100-1000 Gigabytes
Enterprise resource planning >100 Gigabytes-Terabytes
Data warehousing >100 Terabytes-petabytes
Database Systems 1
Figure 11: Multitiered client/server database architecture
Figure 12: Computer System for Pine Valley Furniture Company
Database Systems 1
• Bagui, Sikha. (2023). Database Design Using Entity-Relationship
Diagrams. Boca Raton: CRC Press.
• Davidson, Louis. (2021). Pro SQL server relational database design and
implementation: best practices for scalability and performance. New York,
NY: Apress.
• Cellier, Peggy. (2020). Machine Learning and Knowledge Discovery in
Databases: International workshops of ECML PKDD 2019.Springer, 2020.
• (2020). Data Management Technologies and Applications: 7th International
Conference. DATA 2018, Porto, Portugal, July 26-28, 2018, revised
selected papers -- Switzerland : Springer.
• Mukesh Soni, Manish M. Patel. (2019). SQL, PL/SQL: The Programming
Language of Oracle. Lap Lambert Academic Publishing
• Taylor, A. G. (2019). SQL for dummies (9th ed.). Hoboken, NJ: For
Dummies.
END OF SUBTOPIC 2
END OF MODULE 1
