WELCOME

WORKSHOP ON

DESIGN OF INFORMATION SYSTEMS FOR

BUSINESS ORGANIZATIONS

by

A. K. RAMANI
DIRECTOR, IIPS, DAVV, INDORE
[email protected]

February 23 , 2002 A. K. Ramani 1

MOTIVATION

$ 10 Billion Industry
Shift of focus in research from Computation
towards Information Management
Broadening application areas, like weather,
genetic, entertainment, CAE, data warehousing,
data mining, and decision making.
Advances in areas, like visualization, robotics,
optical storage, high speed communications

February 23 , 2002 A. K. Ramani 2

 Motivation
Limited understanding of DB principles and techniques for
advanced information management.
Next generation DBs will need MM support, complex
objects, real-time, rule processing…
Co-operation in Scientific, engineering, commercial
problems will need large scale heterogeneous distributed
DBs
Requirements: Efficiency, Resilience, Access control,
Persistence

February 23 , 2002 A. K. Ramani 3

CHALLENGE OF DB TECH.

DBMSs to organize, create, and maintain

collections of information.
Challenge is to apply DB technology in new
and important areas in scientific databases,
design databases, business, and utility
databases and many more.

February 23 , 2002 A. K. Ramani 4

SCENARIO

An Instant Virtual Enterprise (IVE) is a group

of companies, that do not routinely function as
a unit, come together to respond to a proposal
of CIM. The task involves CAD, production,
QA, Product planning, resource management
etc.
In such an environment it is necessary for IVE
companies to exchange and cooperatively
manage the large amount of data.

February 23 , 2002 A. K. Ramani 5

SCENARIO

A personnel information system provides

information tailored to an individual, and
delivered via a GPS of laptop, and access internet
from any where any time, from waking up to bed
time. Weather report, day special events,
appointments, diet, best route, news headlines,
sporting events, best investments, list of tasks,
start of sale, best air ticket, best return route,
preview of next day, by querying remote DBs.

February 23 , 2002 A. K. Ramani 6

AIM

The aim of this workshop is to

help you developing an
understanding of database
development techniques in
information management
applications, and become an
expert database developer.

February 23 , 2002 A. K. Ramani 7

OBJECTIVES

To familiarize with the concept of database

development.
To present the various steps in the approach
to database development.
To see an example of a DBMS oriented
approach.

February 23 , 2002 A. K. Ramani 8

EVOLUTION OF DATABASE TECHNOLOGIES

February 23 , 2002 A. K. Ramani 9

FILE SYSTEM

Sequential Records
Index for random Access
Open, Close, Read, Write, Delete
Redundancy, inconsistency, poor
data sharing,low productivity etc.

February 23 , 2002 A. K. Ramani 10

FILE SYSTEM

A conventional File Processing System

February 23 , 2002 A. K. Ramani 11

FILE SYSTEM

_ In file processing,each dept has own IS

– For new system, new programs are needed
Disadvantages
– Program data dependence - All program to be changed for any
change in file designs ( Record Formats)
– Duplication – Data inconsistency
– Poor Data Sharing – Incompatible files.
– Lengthy Development Times
Every new application start from scratch low productivity
High maintenance cost 80% cost

February 23 , 2002 A. K. Ramani 12

DATABASE MODELS

Hierarchical & Network Systems

– Complex record structures
– Difficult to change application programs

STAFF
Employee

Program Faculty

Class

Course
DORM
STD

February 23 , 2002 A. K. Ramani 13

RELATIONAL MODEL

Relational DB Systems
– Data in Tables form
– Simple SQL
– Example DB2,ORACLE,INGRESS
– Difficult to handle Complex data &
Relation ships

February 23 , 2002 A. K. Ramani 14

DATABASE MODELS

Object Oriented Modeling

STAFF
Employee

Program Faculty

Class

Course
DORM
STD

February 23 , 2002 A. K. Ramani 15

OBJECT MODEL

Student Faculty
Name,DOB,GPA
is advised by Name,Rank Salary
take Course Advice
------ Research
------ ------
Take
Teach

Course Class
Title,Credit Time
Pre requisite Assign Lab

February 23 , 2002 A. K. Ramani 16

 Object oriented model
For complex Relationships
UML (Unified Modeling Language)
Easy to maintain & Change
Improved Productivity

February 23 , 2002 A. K. Ramani 17

INTRODUCTION TO DBMS

Aim
Introduce different concepts of DBMS, in context of
Information System development.
Objectives
– Define database & related terms
– Understand DBMS components , role & DBMS architecture
– Limitations of Conventional File System
– Introduce DB approach , ER concept , Categories of DB
applications & issue
– Advantage of DB approach
– Evolution of DBMS

February 23 , 2002 A. K. Ramani 18

WHAT IS A DATABASE

Database is a data bank, where data can be stored manipulated

and retrieved in a speedy manner, efficiently and error free.
A database is a model of structures of reality
The use of a database reflect processes of reality
A database system is a software system which supports the
definition and use of a database
DDL: Data Definition Language
DML: Data Manipulation Language

DML
REALITY DATABASE SYSTEM
• structures
DATABASE
• processes
DDL

February 23 , 2002 A. K. Ramani 19

WHAT IS A DATABASE

Database is a representation of a part of real world in terms of

computable objects.
E = {Object,Attributes,Data}, where E is an Entity.
D = {E1,E2,………En}, where D is database
– How to implant changes in database
By using a set of software modules.
– DBMS = Database + S/W modules
Data
Base
S/W DB
Applications
Tools
Data
base

Applications DB S/W Data

February 23 , 2002 A. K. Ramani 20
 Data
– is a known (valued) fact.
– is a value to an attribute
– can be recorded on computer media
Example : This house has four rooms.
Database = Object + data + attributes
– Data can comprise of facts,which may include numeric,text,
images, sound & multimedia.
– Database is an organized collection of logically related data
where data can be stored easily, manipulated,retrieved.
– Data becomes information when processed.
– Meta Data are data that describe the properties of data,
include data definitions, data sizes, rules, constraints etc.

February 23 , 2002 A. K. Ramani 21

DATABASE COMPONENTS

Data Collection
– Data - Stores facts
– Information – Extracted & derived data for a specific purpose
DBMS Software
– Efficiently and reliably manages data storage, retrieval, data update (Insert,
Modify, Delete)
Automated Tools
– For design,query and application development
Database Users
– End Users
– Data Analysts & Application Programmer
– DB designers
– DBA

February 23 , 2002 A. K. Ramani 22

DEFINITION

Field
– It is a set of bytes to represent some values,lowest
level of database ( or logical structure)
Record
– Group of logically related fields,records accessed
via S/W
File
– A group of identical records,accessible via system
software
Database
– A set of related files , accessed via system software.
February 23 , 2002 A. K. Ramani 23
 Insert Picture of slide 5

February 23 , 2002 A. K. Ramani 24

WHEN TO USE DBMS
Use a DBMS when this is important

●persistent storage of data

●centralized control of data
●control of redundancy
●control of consistency and integrity
●multiple user support
●sharing of data
●data documentation
●data independence
●control of access and security
●backup and recovery

February 23 , 2002 A. K. Ramani 25

WHEN NOT TO USE DBMS

Do not use a DBMS when

●the initial investment in hardware, software,

and training is too high
●thegenerality a DBMS provides is not
needed
●the overhead for security, concurrency
control, and recovery is too high
●data and applications are simple and stable
●real-time requirements cannot be met by it
●multiple user access is not needed

February 23 , 2002 A. K. Ramani 26

DBMS ARCHITECTURE

Transactions
Database System

Applications programs / Queries

Software Modules
Software for queries / Programs

Software to access data base

Meta Data DB
DATABASE DESIGN

The purpose of database design is to create a

database which

is a model of structures of reality

supports queries and updates modeling processes
of reality
runs efficiently

DB approach is total integration and sharing of

data throughout the organization

February 23 , 2002 A. K. Ramani 28

IS PLANNING

Goal : Business Strategies supported upon IT 3 Steps

1. Identify strategic planning factors
• Goals : Growth Rate……..
• Success Factors : Quality,On-time…..
• Problem Areas : Competition….
Set priorities of needs of IS & DB
2. Identify Corporate Planning objects
1. Organizational Units – Various depts
2. Locations – business places
3. Business Functions – business processes like product development
4. Entity Types : Categories of data about people,places &
things managed by company
5. Information System : Application S/W & supporting
procedures.

February 23 , 2002 A. K. Ramani 29

IS PLANNING

Develop list of Entities that support the business activities

– An entity is an object/concept that is important to business, e,g,
CUSTOMER,PRODUCT,EMPLOYEE,ORDER etc
– Identification & definition of Entities.
Develop Enterprise Data Model to show association among entities.
Also called as E-R models.

Customer Product
Places has
is Placed by is for
Order Order Line
Contains is contained
in

February 23 , 2002 A. K. Ramani 30

IS PLANNING

Entities
– Customer : People / Companies / potential customer
– Order : Purchase of 1 or more items
– Product : Items produced for selling
– Order Line : Details of each product (quantity price ) sold on a
particular customer
Apply Business Rules For Relation Ships
Each Customer places >= 1 Order
Each order is placed by one Customer
Each order contains >=1 L (ask slide 10)
Each L is contained in One Customer Order (O)
Each product has >=1 L
Each order line is for one product

February 23 , 2002 A. K. Ramani 31

IS PLANNING

ER Model
– Tells how organization functions and constraints
– Emphasizes on data & process by considering data, relationships &
business rules.
Relational Databases
– Data is viewed in form of tables
– Tables are based upon entities of ER model and contains attributes of an
entity and its instances (value)
– Few attributes are common among tables e.g. ID nos., Employee number
Historical and summarized information (ask it) data base is
called Data Ware House ( D-Mgt ask it) to assist DSS.
Data base application program can perform actions like Create,
Read, Update, Delete etc.

February 23 , 2002 A. K. Ramani 32

DATABASE DEVELOPMENT

Area of Application
Perspective
Work-Processes
Guidelines for Work-Processes in
the development of the application

February 23 , 2002 A. K. Ramani 33

AREA OF APPLICATION
Development of medium to large size data intensive applications
Data intensive:
– lots of data
– little processing
– insertions, deletions, updates,
– queries
What is medium to large?
Small is:
– well-defined project
– short development time
– no long-term maintenance
– few people; little turnover
– no critical resources
– small risk of failure
– small cost of failure
Why only medium to large?
– the methodology is an insurance policy
– cost of using methodology is high
February 23 , 2002 A. K. Ramani 34
PERSPECTIVE

Business process is well-designed

Documents are known
Tasks are known
System boundary is known
One database schema unifying all views can be
designed
– difficult: interests, goals, power, politics
– problems with the methodology?
– problems with the organization?
– or-gan-i-za-tion: “an entity created to pursue a shared
set of goals”

February 23 , 2002 A. K. Ramani 35

WORK PROCESSES

Business process (re-)design

Analysis

Management
Specification
Design
Implementation
Testing
Operation
Maintenance

February 23 , 2002 A. K. Ramani 36

GUIDELINES FOR WORK-PROCESSESE

Purpose: what we do?

Input: what we start with?
Output: what we end with?
Tool: what we use?
Technique: how we use it?
Organization: who does what?

February 23 , 2002 A. K. Ramani 37

TIME AND MANAGEMENT

waterfall model; this is not prototyping

iteration necessary
work vs. time vs. people
estimating resources is very difficult
analysis specification design implementation test
work-process

time

February 23 , 2002 A. K. Ramani 38

CATEGORIES OF DB APPLICATION

Type User Architecture Size

1. PC 1 Desktop
Megabytes
2. WorkGroup 5-25 Client/Server (2 Tier) M-G
bytes
3. Department 25-100 Client/Server (3 Tier) G bytes
4. Enterprise > 100 Client/server (Distributed) G-Terabytes

February 23 , 2002 A. K. Ramani 39

DATABASE ISSUE

Optimized Database Design

Integrity of Database

Performance

Security

Redundancy & Consistency

Distributed Database Designs

February 23 , 2002 A. K. Ramani 40

ADVANTAGES OF DB APPROACH

Program-Data Independence
– Metadata & programmes are independent
Minimal Redundancy
– Single logical structure
Data Consistency
– Each value stored on one place
Data Sharing
– To form report from more than 1 table
Increased Productivity in Development
– Saves cost/time
Enforcement of Standards
– Feasible
Improved Data Quality
– Enforce constraints
– Data Management approach
Simplicity in Data Access
– Select * from product where Product_name =“Computer” ;
It is a SQL command
Easy Maintenance
– Y2k Problem
February 23 , 2002 A. K. Ramani 41
DISADVANTAGES

Expensive New H/W , Operating Cost

Complex Development/Implement
Recovery more difficult
Vulnerability to failure
Organizational Conflicts strong top management support
must.

February 23 , 2002 A. K. Ramani 42

FUTURE TREND AND SUMMARY

Future Trends
– Object – Relational Databases
– Distributed Databases
• Distributed to multiple locations,transparent
– Content Addressable
– Interface other technologies like AI, TV, Natural
Language Interface
Summary
– Database & related terms
– DB approach,Advantages
– Categories,Evolution
– Future Trends

February 23 , 2002 A. K. Ramani 43