INFORMATION SYSTEMS
AND TECHNOLOGY
Instructor
Dr. Manjunath Kamath, Associate Professor of Industrial Engineering and
Management
322 EN, 744-9132 (Direct, Voice Mail); 744-6055 (Main Office); 744-4654 (Fax)
E-Mail: mkamath@okstate.edu;
CCIM URL: www.okstate.edu/cocim
Office Hours: M 4 pm – 5 pm; TTh 11 am – noon; F 1pm - 2pm
Graduate Assistant
Mr. Mukul Patki
502 EN, 744-7202 (Direct, Voice Mail); 744-6055 (Main Office); 744-4654 (Fax)
E-Mail: patki@okstate.edu
Office Hours: Th 2pm - 4 pm
COURSE DESCRIPTION
Catalog Description
For current and potential engineering and technology
managers.
Knowledge of information systems and
technology to lead the specification, selection,
implementation, and integration of information technology
in manufacturing and service organizations. Management
issues involved in the use of information technology in
organizations.
Prerequisites
Graduate standing or consent of instructor.
COURSE OBJECTIVES
To develop an awareness of modern information
systems concepts, such as database architectures,
computing architectures, application architectures, the
Internet, and Intranets, and their impact on
organizational performance.
To identify the different phases in the design,
development, implementation, and maintenance of
effective information systems.
To understand the basics of content creation,
management, and distribution.
COURSE OBJECTIVES
To understand and evaluate commercially available
systems and solutions for data management and report
generation.
To develop an understanding of the technical and
human issues involved in managing, controlling, and
administering information technologies.
To explore “new” organizational structures (e.g. virtual
corporations) resulting from the use of modern
information systems and technology.
PRIMARY REFERENCES
Alter S. (1999), Information Systems: A Management Perspective,
Third
Edition,
Prentice-Hall,
Inc.,
New
Jersey.
(www.prenhall.com/alter)
Comer, D.E. (1997), The Internet Book, Second Edition, Prentice-Hall,
Inc.,NewJersey.
(http://vig.prenhall.com/acadbook/0,2581,0138901619,00.html)
TECHNICAL REFERENCES
Comer D.E. (1995) Internetworking with TCP/IP Volume I:
Principles, Protocols and Architectures, Third Edition, PrenticeHall, Inc., New Jersey.
Orfali R., D. Harkey and J. Edwards (1999), Client/Server Survival
Guide, Third Edition, John Wiley.
Yeager N.J. and R.E. McGrath (1996), Web Server Technology:
The Advanced Guide for World Wide Web Information Providers,
Morgan Kaufmann Publishers.
OTHER REFERENCES
Gupta, U. (2000), Information Systems Success in the 21st Century, PrenticeHall, Inc., New Jersey.
Haag, S., M. Cummings and J. Dawkins (2000), Management Information
Systems for the Information Age, Second Edition, Irwin McGraw-Hill, Boston.
Stair, R.M. (1996), Principles of Information Systems: A Managerial Approach,
Second Edition, Boyd and Fraser Publishing Company, Boston.
Turban E., E. McLean and J. Wetherbe (1996), Information Technology for
Management, John Wiley and Sons, Inc., New York.
Whitten, J.L. and L.D. Bentley (1998), Systems Analysis and Design Methods,
Fourth
Edition,
Irwin
McGraw-Hill,
Boston.
(www.tech.purdue.edu/textbooks/sadm)
GRADING POLICY
Method of Instruction
Two seventy-five minute class periods per week. Class will consist of
lecture and discussion.
Grading Policy
Graded work will be weighted as follows:
Mid-term Examination
20%
Homework (8-10 sets)
30%
Term Paper
25%
Final Examination
25%
GRADING POLICY
 Grades will be given on a 90, 80, 70, 60 basis. The instructor
reserves the right to lower the curve as circumstances warrant.
 Homework assignments are expected to be well organized and
neatly presented. They will be graded and returned to the student.
 Academic dishonesty will not be tolerated. When the instructor
feels beyond reasonable doubt that dishonesty has occurred, he
will take disciplinary action in accordance with university policies
and procedures.
Spring Syllabus Attachment
www2.okstate.edu/acad/sylatsp00.html
TENTATIVE COURSE
OUTLINE
Introduction to the Course
1
Information System Framework and Development
Zachman's framework; phases in system development.
1
Current Trends in Information System Development and Application
ERP; web-based systems; e-commerce; globalization.
2
Types of Information Systems
1
Transaction processing systems; management information systems; decision
support systems; etc.
TENTATIVE COURSE
OUTLINE
Databases and Database Management Systems
3
File systems vs. databases; database management systems; database topology; data
warehouses.
Computing and Communication Architectures
3
Centralized vs. distributed systems; client/server architectures; LANs; WANs; etc.
Application Development
Programming languages; operating systems; html; XML; etc.
2
Internet, Intranets, and Extranets
4
Protocols - TCP/IP, http; web-servers; browsers; domain names; security technologies; etc.
Information Systems Development
Methodologies; data, process and object models; CASE tools; prototyping.
3
TENTATIVE COURSE
OUTLINE
Data Management
2
Evaluating commercial systems; report generation; online analytical processing
(OLAP); etc.
New Organizational Structures
Virtual/extended enterprises; supply chain systems.
2
Organizational, Human and Ethical Issues
4
Impact on strategic planning, business processes and organizational performance;
privacy and security issues; information ergonomics.
Directions for New Technology
1
INFORMATION SYSTEMS
An arrangement of people, data, processes,
interfaces and geography that are integrated for
the purposes of supporting and improving the
day-to-day operations in a business, as well as
fulfilling the problem-solving and decisionmaking information needs of business managers
Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design
Methods, pp. 38, Fourth Edition Irwin McGraw-Hill, Boston
MAIN IDEA DISCUSSED BY
ZACHMAN
There is a set of architectural
representations produced over the
process of building a complex engineering
product representing the different
perspectives of the different participants.
Generic
Building
Airplanes
Ballpark
Bubble
Charts
Architect’s
Drawing
Architect’s
Plans
Contractor’s
plans
Shop Plans
Concepts
Owner’s
Representation
Designer’s
Representation
Builder’s
Representation
Out-of-context
Representation
Machine Language
Representation
Product
---Building
Work breakdown
structure
Engineering design
Manufacturing
engineering design
Assembly/fabrication
drawings
Numerical code
programs
Airplane
Information
Systems
Scope/Objectives
Model of the
business
Model of the
IS
Technology Model
Detailed
description
Machine language
description
Information System
INFORMATION SYSTEM
PERSPECTIVES
S
System
Y
Owners
S
T
E
System
M
INFORMATION SYSTEM SCOPE
(purpose and vision; goals and objectives; costs and benefits)
INFORMATION SYSTEM REQUIREMENTS
Users (WHAT the system “is” and “must do” independent of technology)
A
N
INFORMATION SYSTEM DESIGN
System
A
Designer
(HOW the system will be implemented using technology)
L
Y
S
INFORMATION SYSTEM COMPONENTS
System
T
Builders
(the actual, technical implementation of the system)
S
Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design
Methods, Fourth Edition Irwin McGraw-Hill, Boston
CLASSIFICATION OF
STAKEHOLDERS
System owners pay for the system to be built
and maintained
System users are the people who actually use
the system to perform or support the work to be
completed
System designers are the technical specialists
who design the system to meet the customer
requirements
System builders are the technical specialists
who construct, test and deliver the system into
operation
MAIN IDEA DISCUSSED BY
ZACHMAN
The same product can be described, for
different purposes, in different ways,
resulting in different types of descriptions.
DIFFERENT DESCRIPTIONS
OF THE SAME PRODUCT
Material description: It talks about
WHAT the thing is made of
Functional Description: It talks about
HOW the thing works
Location Description: It talks about
WHERE the flows exist
I/S ANALOGS FOR THE
DIFFERENT DESCRIPTIONS
DESCRIPTION I DESCRIPTION II DESCRIPTION III
Product
Bill-of-materials Functional
Specification
Descriptive PartModel
relationshippart
Information Data model
System
Analog
I/S
Entitydescriptive relationshipmodel
entity
Drawings
Input-processoutput
Site-link-site
Process model
Network model
Processprocess-output
Node-line-node
FOCUSES
DATA: the raw material used to create useful
information
PROCESSES: the activities that carry out the
mission of the business
INTERFACES: how the system interacts with
people and other systems
GEOGRAPHY: where the data is captured and
stored; where the processes happen; where the
interfaces happen
WHITTEN-BENTLEY’S ADAPTATION OF
ZACHMAN’S FRAMEWORK
S
System
Y
Owners
S
T
E
System
M
System
Data
System
Processes
System
Interfaces
Business
Subjects
Business
Functions
System
Context
System
Geography Methodology
Operating
Location
Data
Business
Interface Communication
Users Requirements Processes Requirements Requirements
A
N
A
L
Y
S
T
S
System
Designer
Database
Schema
Application
Schema
Interface
Schema
System
Builders
Database
Programs
Application Component
Programs
Programs
Survey
Phase
Study
Phase
Network
Schema
Configuration
Phase
Network
Programs
Construction
Phase
WHITTEN-BENTLEY’S ADAPTATION
OF ZACHMAN’S FRAMEWORK
System
Data
System
Processes
System
Interfaces
System
Geography Methodology
S
Operating
Business
System
Business
Y
Location
Functions
Context
Subjects
S
Not
Ongoing Unit/business
Information
System
T
synonymous
activities
the new
Owners
about
the
E
with
that support system should
resources
to
M
the business interface with computer
be managed
center
A
Business
CommunicaN
Data
tion
Processes
Interface
A
Requirements
Requirements
L System How the data Discrete Requirements Technology
activities
How users independent
Y Users is or should
having inputs, interact with information
S
be
resource
outputs and the system
T
implemented
requirements
start/end times
S
Survey
Phase
Study
Phase
WHITTEN-BENTLEY’S ADAPTATION
OF ZACHMAN’S FRAMEWORK
S
Y
S
T
E
M
A
N
A
L
Y
S
T
S
System
System
System
System
Data
Processes
Interfaces Geography Methodology
Database
Interface
Application
Network
Schema
Schema
Schema
Schema
Translation of Implementa- Properties,
Model
System
data
system states, indentifying Configuration
tion of
Designer requirements
Phase
bus.processes events and all centers
into databases
their
using
involved in
responses an application
computers
Application
Network
Programs Component
Programs
Database
Language
Machine
Programs
Programs
based
readable Construction
GUIs System Closest to
Builders database representation Visual BASIC specifications
Phase
of what a
of computer
Delphi
technology
process
Powerbuildercommunication
foundation
should do
parameters
INTERESTING FEATURES
OF THE FRAMEWORK
Each element on either axis of the matrix
is explicitly differentiable from all other
elements on that one axis.
These representations are not merely
successive levels of increasing detail but
are actually different representations.
Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design
Methods, Fourth Edition Irwin McGraw-Hill, Boston
SYSTEM DEVELOPMENT
PHASES
1
Unplanned System Problem
Survey
Phase
Planned
System
Project
System
Users
8
Production System
Delivery
Phase
Project and
System Scope
Operational
System
2
7
Study
Phase
Construction
Phase
System
Objectives
Design
Specifications
3
Definition
Phase
Business
Requirements
6
Business
Requirements
4
Targeting
Phase
Prototypes
Information
Technology
Vendors
Design
Phase
Design
Requirements
Technology
Requirements
System
Owners
Business Requirements
Technology
Integration
Requirements
Request
for
Proposals
5
Purchasing
Phase
(if necessary)
Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design
Methods, Fourth Edition Irwin McGraw-Hill, Boston
Proposals