W2: Information Management Concepts and
Fundamentals
File Systems - are used by a manager of any small
organization to track necessary data
Disadvantages: Lengthy development time; Difficulty of
getting quick answers; Complex system administration;
Lack of security and limited data sharing; Extensive
Programming
Five Major Parts of a Database System: Hardware;
Software : OS Software.. DBMS Software… Application
programs and utility software; People: Systems
Administrators… Database Administrators… Database
Designers.. Systems Analysts and Programmers.. End
users; Procedures; Data
Database- • is a shared collection of related data
used to support the activities of a particular
organization.
• can be viewed as a repository of data that is
defined once and then accessed by various users
A database has the following properties:
•It is a representation of some aspect of the real world
or a collection of data elements (facts) representing
real- world information.
•A database is logical, coherent and internally
consistent.
•A database is designed, built and populated with data
for a specific purpose.
•Each data item is stored in a field.
•A combination of fields makes up a table. For example,
each field in an employee table contains data about an
individual employee.
Database Management System - is a collection of
programs that manages the database structure and
control access to the data stored in the database … A.
Traditional Banking System B. Bank DBMS
Characteristics and Benefits of a Database
•Self-describing nature of a database system
•Insulation between program and data
•Support for multiple views of data
•Sharing of data and multiuser system
•Control of data redundancy
•Enforcement of integrity constraints
•Restriction of unauthorized access
•Data independence
•Backup and recovery facilities
Information Management
The infrastructure used to collect, manage, preserve,
store and deliver information
The guiding principles that allow information to be
available to the right people at the right time
The view that all information, both digital and
physical, is an asset that requires proper management
The organizational and social contexts in which
information exists
• Is an umbrella term that encompasses all the systems
and processes within an organization for the creation
and use of corporate information
• More than just technology; it is about the business
processes and practices that underpin the creation and
use of information
• It is also about the information itself, including the
structure of information (“information
architecture”), metadata, content quality, and more.
Purpose of Information Management • Design,
develop, manage, and use information with insight and
innovation
• Support decision making and create value for
individuals, organizations, communities, and societies
W3: Database SystemConcepts and Architecture
Data Model -A collection of concepts that can be used
to describe the structure of a database – provides the
necessary means to achieve data abstraction
Data Abstraction - Refers to the suppression of details
of data organization and storage, and the highlighting
of the essential features for an improved
understanding of data
Three Categories of Data Models According to Types of
Concepts Used in Describing Database Structure:
1. High-level or Conceptual Data Models
2. Low-level or Physical Data Models
3. Representational or Implementation Data Models
Schemas and Instances
Database Schema- the description of the database--
includes descriptions of the database structure, data
types, and the constraints on the database
Schema Diagram- An illustrative display of (most
aspects of) a database schema
Schema Construct- A component of the schema or an
object within the schema e.g STUDENT, COURSE
Database state: The actual data stored in a database at
a particular moment in time. This includes the collection
of all the data in the database. Also called database
instance (or occurrence or snapshot).
Database state- Refers to the content of a database at a
moment in time
Initial Database State- Refers to the database state
when it is initially loaded into the system
Valid State- A state that satisfies the structure and
constraints of the database
Distinction- The database schema changes very
infrequently---- The database state changes every time
the database is updated
Schema is also called intension
State is also called extension
Three-Schema Architecture (3 Levels)
1. Physical Level 2. Conceptual Level 3. External Level
Data Independence--- The capacity to change the
schema at one level of a database system without
having to change the schema at the next higher level
Two Types of Data Independence
1. Logical Data Independence 2. Physical Data
Independence
Week 4: Data Languages and Interfaces
Database Languages
•Used to create and maintain database
Data Definition Language (DDL)
Data Manipulation Language (DML)
Data Control Language (DCL)
Data Query Language (DQL)
Types of DML
High-Level or Non-procedural Language
For example, the SQL relational language
Are “set”-oriented and specify what data to retrieve
rather than how to retrieve it.
Also called declarative languages
Low Level or Procedural Language
Retrieve data one record-at-a-time
Constructs such as looping are needed to retrieve
multiple records, along with positioning pointers
DBMS Interfaces
Interfaces- A set of commands or menus through which
a user communicates with a program
Menu-based Interfaces for Web Clients or Browsing
Forms-based Interfaces
Graphical User Interfaces
Natural Language Interfaces
Speech Input and Output
Interfaces for the DBA
Centralized DBMS - Combine everything into single
system including – DBMS software, hardware,
application programs, and user interface processing
software •User can still connect through a remote
terminal-however, all processing is done at centralized
site
A Physical Centralized Architectures
Basic 2-tier Client-Server Architectures
• Specialized Servers with Specialized Functions • Print
server • File server • DBMS server • Web server • Email
server • Clients can access the specialized servers as
needed
Logical two-tier client server architecture
Clients 1. Provide appropriate interfaces through a
client software module to access and utilize the various
server resources 2. Clients may be diskless machines or
PCs or Workstations with disks with only the client
software installed 3. Connected to the servers via some
form of a network 4. LAN: local area network, wireless
network, etc.
DBMS Server
Provides database query and transaction services to
the clients
Relational DBMS servers are often called SQL servers,
query servers, or transaction servers
Applications running on clients utilize an Application
Program Interface (API) to access server databases via
standard interface such as: ODBC: Open Database
Connectivity standard … JDBC: for Java programming
access
Client and server must install appropriate client
module and server module software for ODBC or JDBC
Two Tier Client-Server Architecture
A client program may connect to several DBMS,
sometimes called the data sources
Data sources can be files or other non-DBMS software
that manages data
Other variations of clients are possible
Three Tier Client-Server Architecture
Common for Web applications
Intermediate Layer called Application Server or Web
Server: 1. Stores the web connectivity software and the
business logic part of the application used to access the
corresponding data from the database server 2. Acts
like a conduit for sending partially processed data
between the database server and the client
Three-tier Architecture can enhance security
Database server only accessible via middle tier
Clients cannot directly access database server
Classifications of DBMS
Based on the data model used :
• Traditional: Relational, Network, Hierarchical
• Emerging: Object-Oriented, Object-relational
Other classifications
• Single-user (typically used with personal
computers) vs. Multi-user (most DBMS)
• Centralized (uses a single computer with one
database) vs. Distributed (uses multiple computers,
multiple databases)
Database Models- the architecture that the DBMS uses
to store objects within the database and relate them to
one another
Hierarchical Model
Network Model
Relational Model
Object-Oriented Model
Object-Relational Model
W5: ENTITY-RELATIONSHIP DIAGRAM
ER Model
• introduced by Peter Chen in 1971
• yields a graphical representation of entities and their
relationships in database structure
• usually represented by an Entity Relationship Diagram
• based on the following components:
Entity Attributes Relationship
Components of ER Model
Entity- Can be a real-world object, either animate or
inanimate, that can easily identifiable
• Entity Set- Is a collection of similar types of entities….
May contain entities with attribute sharing similar
values… Need not be disjoint
Entity-Set and Keys
• Super Key − A set of attributes (one or more) that
collectively identifies an entity in an entity set.
• Candidate Key − A minimal super key is called a
candidate key. An entity set may have more than one
candidate key.
• Primary Key − A primary key is one of the candidate
keys chosen by the database designer to uniquely
identify the entity set.
Relationship- describe the association among entities
Attributes • characteristic of an entity • All attributes
have values
Types of Attributes
Simple attribute Composite attribute
Derived attribute Single-value attribute
Multi-value attribute
Types of Relationship
One-to-one - One entity from entity set A can be
associated with at most one entity of entity
One-to-many - One entity from entity set A can be
associated with more than one entities of entity set B
however an entity from entity set B, can be associated
with at most one entity.
Many-to-one- More than one entities from entity set A
can be associated with at most one entity of entity set
B, however an entity from entity set B can be
associated with more than one entity from entity set
Many-to-many- One entity from A can be associated
with more than one entity from B and vice versa.
• Cardinality- specifies how many instances of an entity
relate to one instance of another entity
• Cardinality Notations
Crow’s Foot Notation Bachman Style Martin Style
ER Diagram
• can express the overall logical structure of a database
in a graphical way
• uses graphic representations to model the database
components
• Components of an ER Diagram
Entity - Entities are represented by means of rectangles.
Rectangles are named with the entity set they
represent. • The term entity is often used instead of
“table” • Think of them as nouns

Attributes- Attributes are the properties of entities.

Attributes are represented by means of ellipses.

• If the attributes are composite, they are further

divided in a tree like structure.

• Multivalued attributes are depicted by double ellipse.

• Derived attributes are depicted by dashed ellipse.

Relationship- Relationships are represented by

diamond-shaped box. Name of the relationship is
written inside the diamond-box. All the entities
(rectangles) participating in a relationship, are
connected to it by a line.

Generalization-- a number of entities are brought

together into one generalized entity based on their
similar characteristics.

Specialization- is the opposite of generalization. In

specialization, a group of entities is divided into sub-
groups based on their characteristics.

Steps to Create an ERD

Entity Identification > Relationship Identification >

Cardinality Identification > Identify Attributes > Create
ERD

3 Levels of Abstraction

Conceptual .. Logical… Physical Data Model

CRUD -create, read, update, and delete

In computer programming, create, read, update,

and delete (CRUD) are the four basic functions of
persistent storage. Alternate words are sometimes
used when defining the four basic functions of
CRUD, such as retrieve instead of read, modify
instead of update, or destroy instead of delete