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 DescriptionFor 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.

PrerequisitesGraduate 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, Prentice-Hall, 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 REFERENCESGupta, U. (2000), Information Systems Success in the 21st Century, Prentice-Hall, 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 POLICYMethod of InstructionTwo seventy-five minute class periods per week. Class will consist of lecture and discussion.

Grading PolicyGraded 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 Attachmentwww2.okstate.edu/acad/sylatsp00.html

TENTATIVE COURSE OUTLINE

Introduction to the Course 1

Information System Framework and Development 1Zachman's framework; phases in system development.

Current Trends in Information System Development and Application 2ERP; web-based systems; e-commerce; globalization.

Types of Information Systems 1Transaction processing systems; management information systems; decision support systems; etc.

TENTATIVE COURSE OUTLINE

Databases and Database Management Systems 3File systems vs. databases; database management systems; database topology; data warehouses.

Computing and Communication Architectures 3Centralized vs. distributed systems; client/server architectures; LANs; WANs; etc.

Application Development 2Programming languages; operating systems; html; XML; etc.

Internet, Intranets, and Extranets 4Protocols - TCP/IP, http; web-servers; browsers; domain names; security technologies; etc.

Information Systems Development 3Methodologies; data, process and object models; CASE tools; prototyping.

TENTATIVE COURSE OUTLINEData Management 2

Evaluating commercial systems; report generation; online analytical processing (OLAP); etc.

New Organizational Structures 2Virtual/extended enterprises; supply chain systems.

Organizational, Human and Ethical Issues 4Impact 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 decision-making 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 InformationSystems

Ballpark BubbleCharts

Concepts Scope/Objectives

Owner’sRepresentation

Architect’sDrawing

Work breakdownstructure

Model of thebusiness

Designer’sRepresentation

Architect’sPlans

Engineering design Model of theIS

Builder’sRepresentation

Contractor’splans

Manufacturingengineering design

Technology Model

Out-of-contextRepresentation

Shop Plans Assembly/fabricationdrawings

Detaileddescription

Machine LanguageRepresentation

---- Numerical codeprograms

Machine languagedescription

Product Building Airplane Information System

INFORMATION SYSTEM PERSPECTIVESSYSTEM

ANALYSTS

SYSTEM

ANALYSTS

System Owners

System Owners

System Users

System Users

System Designer

System Designer

System Builders

System Builders

INFORMATION SYSTEM SCOPE(purpose and vision; goals and objectives; costs and benefits)

INFORMATION SYSTEM SCOPE(purpose and vision; goals and objectives; costs and benefits)

INFORMATION SYSTEM REQUIREMENTS(WHAT the system “is” and “must do” independent of technology)

INFORMATION SYSTEM REQUIREMENTS(WHAT the system “is” and “must do” independent of technology)

INFORMATION SYSTEM DESIGN(HOW the system will be implemented using technology)

INFORMATION SYSTEM DESIGN(HOW the system will be implemented using technology)

INFORMATION SYSTEM COMPONENTS(the actual, technical implementation of the system)

INFORMATION SYSTEM COMPONENTS(the actual, technical implementation of the system)

Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design

Methods, Fourth Edition Irwin McGraw-Hill, Boston

CLASSIFICATION OF STAKEHOLDERSSystem owners pay for the system to be built

and maintainedSystem 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 FunctionalSpecification

Drawings

DescriptiveModel

Part-relationship-part

Input-process-output

Site-link-site

InformationSystemAnalog

Data model Process model Network model

I/Sdescriptivemodel

Entity-relationship-entity

Process-process-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

SYSTEM

ANALYSTS

SYSTEM

ANALYSTS

System Owners

System Owners

System Users

System Users

System Designer

System Designer

System Builders

System Builders

Business Subjects

Business Subjects

Data Requirements

Data Requirements

Database Schema

Database Schema

Database Programs

Database Programs

Business Functions

Business Functions

Business Processes

Business Processes

Application Schema

Application Schema

Application Programs

Application Programs

System Context

System Context

Interface Requirements

Interface Requirements

Interface Schema

Interface Schema

Component Programs

Component Programs

Operating Location

Operating Location

Communica-tion

Requirements

Communica-tion

Requirements

Network Schema

Network Schema

Network Programs

Network Programs

Survey Phase

Survey Phase

Study Phase

Study Phase

ConfigurationPhase

ConfigurationPhase

Construction Phase

Construction Phase

System Data

System Data

System ProcessesSystem

ProcessesSystem

InterfacesSystem

InterfacesSystem

GeographySystem

Geography MethodologyMethodology

WHITTEN-BENTLEY’S ADAPTATION OF ZACHMAN’S FRAMEWORK

SYSTEM

ANALYSTS

SYSTEM

ANALYSTS

System Owners

System Owners

System Users

System Users

Business Subjects

Information about the

resources to be managed

Business Subjects

Information about the

resources to be managed

Data RequirementsHow the datais or should

be implemented

Data RequirementsHow the datais or should

be implemented

Business FunctionsOngoing activities

that support the business

Business FunctionsOngoing activities

that support the business

Business ProcessesDiscrete activities

having inputs, outputs and

start/end times

Business ProcessesDiscrete activities

having inputs, outputs and

start/end times

System Context

Unit/businessthe new

system should interface with

System Context

Unit/businessthe new

system should interface with

Interface Requirements

How users interact with

the system

Interface Requirements

How users interact with

the system

Operating Location

Not synonymous

with computer

center

Operating Location

Not synonymous

with computer

center

Communica-tion

RequirementsTechnology independent information

resourcerequirements

Communica-tion

RequirementsTechnology independent information

resourcerequirements

Survey Phase

Survey Phase

Study Phase

Study Phase

System Data

System Data

System ProcessesSystem

ProcessesSystem

InterfacesSystem

InterfacesSystem

GeographySystem

Geography MethodologyMethodology

WHITTEN-BENTLEY’S ADAPTATION OF ZACHMAN’S FRAMEWORK

SYSTEM

ANALYSTS

SYSTEM

ANALYSTS

System Designer

System Designer

System Builders

System Builders

Database Schema

Translation of data

requirementsinto databases

Database Schema

Translation of data

requirementsinto databases

Database ProgramsClosest to database

technology foundation

Database ProgramsClosest to database

technology foundation

Application Schema

Implementa-tion of

bus.processes using

computers

Application Schema

Implementa-tion of

bus.processes using

computers

Application ProgramsLanguage

basedrepresentation

of what a process

should do

Application ProgramsLanguage

basedrepresentation

of what a process

should do

Interface Schema

Properties,system states,events and

their responses

Interface Schema

Properties,system states,events and

their responses

Component ProgramsGUIs -

Visual BASICDelphi

Powerbuilder

Component ProgramsGUIs -

Visual BASICDelphi

Powerbuilder

Network SchemaModel

indentifyingall centers involved in

an application

Network SchemaModel

indentifyingall centers involved in

an application

Network ProgramsMachine readable

specificationsof computer

communicationparameters

Network ProgramsMachine readable

specificationsof computer

communicationparameters

ConfigurationPhase

ConfigurationPhase

Construction Phase

Construction Phase

System Data

System Data

System ProcessesSystem

ProcessesSystem

InterfacesSystem

InterfacesSystem

GeographySystem

Geography MethodologyMethodology

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

Survey Phase

2

Study Phase

3

Definition Phase

4

Targeting Phase

6

Design Phase

7

Construction Phase

5

Purchasing Phase

(if necessary)

8

Delivery Phase

System Users

System Owners

Information Technology

Vendors

Unplanned System Problem

Planned System Project

Project and System Scope

System Objectives

Business Requirements

Technology Requirements

Design Requirements

Technology Integration

Requirements

Design Specifications

Prototypes

Operational System

Business Requirements

Business Requirements

Request for

Proposals

Proposals

Production System

Source: Whitten, J.L. and L.D. Bentley(1998), Systems Analysis and Design

Methods, Fourth Edition Irwin McGraw-Hill, Boston