Information System

An Information system comprises all the

components such as hardware, software,
communication systems that collect,
manipulate and distribute data or information.
Component
 Hardware
Software
Communication system
Data
1
 Information system in business
In business environment IS typically support
business processes and operations, decision
making and competitive strategies.
Aim: To make organization more productive
and profitable and to gain competitive
advantage
Transaction processing system(TPS)
Management Information system(MIS)
Executive Information system(EIS)
2
 Contd..
Decision support system(DSS)
Expert system(ES)
Strategic Information System(SIS)
Customer relationship management system
Enterprise resource planning systems
Office automation systems
Decision support system

3
 Data VS Information
• What is data? • What is information?
– Data can be defined in – Information is data that
many ways. Information have been organized and
science defines data as communicated in a
coherent and meaningful
unprocessed information.
manner.
– Collection of raw data. – Data is converted into
– Unstructured does not information, and
have context and may not information is converted
be relevant to the receiver. into knowledge.
– Knowledge; information
evaluated and organized so
that it can be used
purposefully.
4
 Contd..

Data Information Knowledge Action

5
 Open VS Close System
• An open system is a • A closed system is a
collection of interacting system that resists the
software, hardware and inclusion and integration
human components. of new ideas.
• It is designed to satisfy • Not adopting new and
the stated needs. feasible ideas, a close
• It contains components system doesn’t serve the
with interface
specifications that are
fully defined.

6
 Information quality attribute
Software quality is the degree to which the
software possesses a desired combination of the
following attributes:
• Performance- is the degree to which a system or
component accomplishes its designated functions
within the given constraints such as speed,
accuracy etc.
• Dependability-reliance of the service it provide. It
is concerned with the occurrence of the failure.
(8 September 2010- Second Lecture)

7
 Contd..
• Security- complete freedom from danger i.e
protection of the system data against
disclosure, modification or destruction.
• Safety – it is concerned with the occurrence of
the accidents.

8
 What is a database?
A database is any organized collection of data.
A collection of related pieces of data:
 Representing/capturing the information about a
real-world enterprise or part of an enterprise.
 Collected and maintained to serve specific data
management needs of the enterprise.
 Activities of the enterprise are supported by the
database and continually update the database

9
 DBMS
Defined as a collection of interrelated data and
a set of programs to access the data.
A Database Management System (DBMS) is a
software package designed to store and
manage databases.

10
 Contd..
A database management system (DBMS) such
as Access, FileMaker, Oracle or SQL Server
which provides the software tools to organize
data in a flexible manner. It includes tools to
add, modify or delete data from the database,
ask questions (or queries) about the data stored
in the database and produce reports
summarizing selected contents.

11
 Advantages of DBMS
Control of data redundancy
Data consistency
More information from same amount of data.
Sharing of data
Improve of security
Improve of data integrity
Improve data accessibility and responsiveness

12
 Disadvantage
• Complexity
• Size
• Cost of DBMS
• Additional hardware cost
• Performance
• Higher impact of failure

13
 Purpose of Database System

In the early days, database applications were

built on top of file systems
Drawbacks of using file systems to store data:
 Data redundancy and inconsistency
 Multiple file formats, duplication of information in different files
 Difficulty in accessing data
 Need to write a new program to carry out each new task
 Data isolation — multiple files and formats
 Integrity problems
 Integrity constraints (e.g. account balance > 0) become part of program
code
 Hard to add new constraints or change existing ones

14
 Contd..
The range of database can be divided into five
categories:
 Personal Database-support one user-improve
personal productivity.
 Workgroup-a relatively small team of people who
collaborate on the same project or application.
 Departmental database-functional unit within an
organization, larger than workgroup and is
responsible for a more diverse range of functions.
15
 Contd..
 Enterprise database- the entire organization or
enterprise or many different departments
database. Such database are intended to
support organization –wide operations and
decision making.
 Internet database- database of huge
information available in internet.

16
 Level of abstraction
3rd Lecture-14.09.10)

• A database abstraction layer is an

application programming interface which
unifies the communication between a
computer application and databases.
• Database abstraction layers reduce the amount
of work by providing a consistent API to the
developer and hide the database specifications
behind this interface as much as possible

17
 Levels of abstraction
The database description consists of a schema
at each of these three levels of abstraction:
 Conceptual level
 physical level
 View level

18
 Levels of Abstraction
Logical level: describes data stored in
database, and the relationships among the data.
 The conceptual or logical level describes the
stored data in terms of the data model of the
DBMS.

19
 Contd
 In a relational DBMS, the conceptual schema
describes all relations that are stored in the
database.
 In university database, these relations contain
information about entities, such as students
and faculty, and about relationships, such as
students enrollment in courses.

20
 Contd..
Students(sid: string, name: string, login: string,
age: integer, gpa: real)
Faculty(d: string, fname: string, sal: real)
Courses(cid: string, cname: string, credits: integer)
Rooms(rno: integer, address: string, capacity:
integer)
Enrolled(sid: string, cid: string, grade: string)
Teaches(d: string, cid: string)

21
 Contd..
Physical level describes how a record is
stored. Essentially, the physical level
summarizes how the relations described in the
conceptual schema are actually stored on
secondary storage devices such as disks and
tapes.

22
 Contd..
View level-defines a view or views of the
database for particular users.
 Any given database has exactly one
conceptual schema and one physical schema
because it has just one set of stored relations,
but it may have several external schemas, each
tailored to a particular group of users.

23
 View of Data
An architecture for a database system

24
 Data Model
A data model is an abstract model that
describes how data are represented and
accessed.
Data models formally define data elements
and relationships among data elements for a
domain of interest.

25
 Contd..
• Data models are a collection of tools for
describing data, data relationships, data
sementics and data constraints.
• Data models are
 Entity-relationship model
 Relational model
 Network model
 Object model
26
Contd..

27
 Entity
An entity is a concept or concrete thing in the
real world that we want to model in a database.
Atomic real world item.
Anything that can be distinguished from any
other thing.
Eg book, customer, payment mode etc.

28
 Entity set
Collection of similar entities.
Same set of attributes
Has a key
Each attribute has a domain.

29
 Weak entities
Existance depends on some other entity.
a Weak Entity is an entity that cannot be
uniquely identified by its attributes alone;
therefore, it must use a foreign key in
conjunction with its attributes to create a
primary key.
claims, orders and invoices,

30
 Strong entities

• Exists independently of other entity types.

31
 Attributes
(4th Lecture-16.09.10)

A property of an entity type.

An entity is represented by a set of attributes,
that is descriptive properties possessed by all
members of an entity set.
Example:
customer = (customer-id, customer-name,
customer-street, customer-city)
loan = (loan-number, amount)

32
 Contd..
Domain – the set of permitted values for each
attribute.
Types of attributes
 Simple attribute
 Composite attribute
 Single valued
 Multivalve
 Derived
33
 Relationship
Represents an association between two or more
entities.
It is a link between two entities, and it tells
something about which relationships exists
between our entities.

34
 Degree of Relationship
It is the number of entities associated with the
relationship.
The n-ary relationship is the general form for
degree n.

35
 connectivity
Describes the mapping of associated entity
instances in the relationship.
The values of connectivity are “one” or
“many”

36
 Cardinality
It expresses the specific number of entity
occurrences associated with one occurrence of
the related entity.
The basic types of connctivity for relations
are:
• One-to-one
• One-to-many
• Many-to-many

37
 Contd..

One to one One to many

 Contd..

Many to one Many to many

 Keys
(5th Lecture, 20/9/10)

Minimum set of attributes whose values

uniquely identify an entity in the set.
It identifies a set of attributes that
distinguish entities from each other.
Super key
Candidate key
Primary key

40
 E-R Model
• Originally proposed by Peter in 1976.
• It is a conceptual data model that views the
real world as entities and relationships.

41
 E-R Diagrams

 Rectangles represent entity sets.

 Diamonds represent relationship sets.
 Lines link attributes to entity sets and entity sets to relationship sets.
 Ellipses represent attributes
 Double ellipses represent multivalued attributes.
 Dashed ellipses denote derived attributes.
 Underline indicates primary key attributes (will study later)
E-R Diagram With Composite, Multivalued, and Derived
Attributes
Relationship Sets with Attributes
 Cardinality Constraints
• We express cardinality constraints by drawing
either a directed line (), signifying “one,” or
an undirected line (—), signifying “many,”
between the relationship set and the entity set.
• E.g.: One-to-one relationship:
– A customer is associated with at most one loan via the relationship borrower
– A loan is associated with at most one customer via borrower
 One-To-Many Relationship

• In the one-to-many relationship a loan is

associated with at most one customer via
borrower, a customer is associated with
several (including 0) loans via borrower
 Many-To-One Relationships

• In a many-to-one relationship a loan is associated with

several (including 0) customers via borrower, a customer
is associated with at most one loan via borrower