Database Management System
Data – is used to process information
- Stored of representation of meaning objects or events
Two Types of Data
Structured Data – Number, text,
- Flat or lightweight materials
Unstructured Data – data that are composed of images or videos or documents
- Big data or big objects
Information – data process to increase knowledge in the person using the data
Not all information is stored in database
Database - organize collection of logically related data
Metadata – data that describes the properties and context of user data
Including the data types, field sizes, allowable values, and data context
Database Management System – software package designed to define, manipulate, retrieve
And manage data in a database
Data Presentation and Summarization
1. Data in context helps the users understand the data
2. Graphical displays turn data into useful information that top administrators can use
For decision making and interpretation
File Processing
Disadvantages of File Processing
1. Program Data Dependence – all programs maintain metadata for each file they use
2. Duplicate of Data – Different systems and programs have separates copies of the same
Data
3. Limited Data Sharing – No central control of data
4. Lengthy Development Times – Programmers must design their own file format
5. Excessive Program Maintenance – 80% of the information systems budgets
The Database Approach
1. Centralized Repository of Shared Data
2. Data is now managed by a controlling agent
3. Stored in a standardized convenient system
Database Management System
it is a software package designed to define, manipulate, retrieve and manage data in a database
Advantages of Database Approach
1. Program-data independence
2. Planned data redundancy
3. Enhancement of Standards
4. Increased application development productivity
5. Improved data consistency
6. Improved data sharing
7. Improved data quality
8. Improved decision support
9. Improved data accessibility and responsiveness
10. Reduced program maintenance
Cost and Risks of the Database Approach
1. Organizational Conflict
2. New Specialized Personnel
3. Installation and Management cost and complexity
4. Conversion Cast
5. Need for explicit backup and recovery
WEEK 2
The Database Development Process
Two Approaches Database
System Development Life Cycle (SDLC)
1. Time Consuming but comprehensive
2. Detailed, well planned development process
3. Long Development Cycle
Prototyping (Rapid Applications Development)
1. Cursory attempt at conceptual data modeling
2. Define database during development of initial prototype
3. Repeat implementation and maintenance activities with new prototype versions
SYSTEM DEVELOPMENT LIFE CYCLE
Planning – terminal or starting development
Analysis – set up the detailed specification
Logical Design – detailed specification and integrate database views into conceptual
data model and define new database
Physical Design – where we develop technology
Implementation – training materials, hire personnel
Maintenance – for monitoring, enhancement, improvement
Purpose – preliminary understanding
Deliverable – request for study
Database activity - enterprise modeling and early conceptual data modeling
PROTYPING DATABASE METHODOLOGY
Identify the problem – composes of planning and analysis
Develop Initial Prototype
Implement and use prototype
Revise and Enhance Prototype
Three Schema Architecture
External Schema
1. User Views
2. Subset Of Conceptual Schema
3. Can be determined from business function data entity matrices
Conceptual Schema
1. E-R Models
Internal Schema
2. Logical Structure
3. Physical Structure
Managing Projects
Project – a planned undertaking of related activities to reach an objective that has a
beginning and an end
Initiated and planned in the planning stage of SDLC
Executed during analysis, design, and implementation
Closed at the end of implementation
People Involved in Managing Projects
Business Analysts
Systems Analysts
Database Analysts and Data Modelers
Project Managers
Users
Programmers
Other Technical Experts
Evolution of Database System
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
Range of Database Application
Personal Databases
Two-tier and N-tier Client/Server databases
Enterprise Applications
1. Enterprise Resource Planning (ERP) systems
--Integrate all enterprise functions
2. Data warehousing implementations
Modeling Approaches (WEEK 2 LAB)
There are three approaches to modeling: top-down, bottom-up, and targeted. All three
approaches meet a different need, so you may be involved in projects that use different
approaches. In this course, you focus most on top-down modeling which involves building a
model a model from scratch and following it through to completion.
Top-Down Model
- Building a model from scratch or used for designing new database
- It gathers information about business requirements, and proceeds to
define processes, a logical model of the data, one or more relational
models, and one or more physical models for each relational model.
Bottom-Up Model
- used in Existing System or modifies an existing database definition.
- It builds database design based on either metadata extracted from an
existing database or a file with DDL code that implements an existing
database. And you reverse engineer the logical model from the relational
model.
Targeted Modeling
- maintains the existing models by adapting to new requirements.
- Depending on the requirements, you must determine which model to
modify.
WEEK 3 (LEC)
BUSINESS RULES
