Fundamentals of IT

Information System Building Blocks
Introduction
The chapter will address the following questions:

What is the difference between data and information? What is the the product called an information system? What are six classes of information system applications and how they interoperate? What is the role of information systems architecture in systems development? What are four groups of stakeholders in information systems development and the unique role of the systems analyst in relation to the four groups? Could you be able to recognize categories of systems users and managers who become stakeholders in systems development?
Prepared by Kevin C. Dittman for Systems Analysis & Design Methods 4ed by J. L. Whitten & L. D. Bentley
Copyright Irwin/McGraw-Hill 1998

Introduction
The chapter will address the following questions:
Can you differentiate between a perspective and a view as it relates to information systems architecture? What are four perspectives of the DATA focus for an information system? What are four perspectives of the PROCESS focus for an information system? What are four perspectives of the INTERFACE focus for an information system? What are four perspectives of the GEOGRAPHY focus for an information system?

A Review of Fundamentals of Information Systems
What is the difference between Data and Information?
Data are raw facts about the organization and its business transactions. Most data items have little meaning and use by themselves. Information is data that has been refined and organized by processing and purposeful intelligence.
Information Systems transform data into useful information.
An information system is an arrangement of people, data, processes, interfaces, and geography that are integrated for the purpose 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.
3

Transaction Processing Systems Business transactions are events that serve the mission of the business.
Transaction processing systems are information system applications that capture and process data about (or for) business transactions. They are sometimes called data processing systems.

Management Information Systems Management Information Systems supplement transaction processing systems with management reports required to plan, monitor, and control business operations.
A management information system (MIS) is an information system application that provides for management-oriented reporting, usually in a predetermined, fixed format.

Decision Support Systems Decision Support Systems are concerned with providing useful information to support the decision process.
A decision support system (DSS) is an information system application that provides its users with decision-oriented information whenever a decision making situation arises. When applied to executive managers, these systems are sometimes called executive information systems. A DSS is designed to support unstructured decisions.

Expert Systems Expert Systems are an extension of the decision support system.
An expert system is an information system application that captures the knowledge and expertise of a problem solver or decision maker, and then simulates the thinking of that expert for those who have less expertise. Expert systems are implemented with artificial intelligence technology, often called expert system shells.
10

Office Information Systems Office Information Systems are concerned with getting all relevant information to all those who need it.
Office information systems support the wide range of business office activities that provide for improved work flow and communications between workers, regardless of whether or not those workers are physically located in an office. Office information systems may use the following technologies:
Electronic forms technology Work group technology Electronic messaging technology Office automation suite technology Imaging technology
11

Personal and Work Group Information Systems Personal and Work Group Information Systems typically are built using personal computer technology and software.
Personal information systems are those designed to meet the needs of a single user. They are designed to boost an individuals productivity. Work group information systems are those designed to meet the needs of a work group. They are designed to boost the groups productivity.
12

Information need Any Manager Transaction Data Management Information System
Transaction Processing System
Data Data
Management information
Transaction information
Data and messages
Business Database
Data snapshots
Read-only data Business Data Warehouse
Decision Support System
Problem
Any User Office Information System Captured data
Decision support information Executive inquiry Read-only data Executive Information System
Any Decision Maker or Executive
Communications between users and within groups
Data
Data Personal data Shared data Personal Information System Expert System Personal information Rules
Executive information
Problem
Personal data
Any User
Solution Personal Files & Databases Expertise Database
Any Relevant User
13

A Framework For Information Systems Architecture
What is an Information Systems Architecture?
An information systems architecture provides a unifying framework into which various people with different perspectives can organize and view the fundamental building blocks of information systems. Stakeholders have different views of the system and each has something at stake in determining the success of the system. Stakeholders can be broadly classified into four groups: System Owners System Users System Designers System Builders
14

INFORMATION SYSTEMS FRAMEWORK
INFORMATION SYSTEM FOCUSES
SYSTEM OWNERS
INFORMATION SYSTEM SCOPE (purpose and vision; goals and objectives; costs and benefits)
S Y S T E M
SYSTEM USERS
INFORMATION SYSTEM REQUIREMENTS (WHAT the system "is" and "must do" independent of technology)
A N A L Y S T S
SYSTEM DESIGNERS
INFORMATION SYSTEM DESIGN (HOW the system will be implemented using technology)
SYSTEM BUILDERS
INFORMATION SYSTEM COMPONENTS (the actual, technical implementation of the system)
Data Technology
Software Technology
Interface Technology
Networking Technology
15

Perspectives - The People Side of Information Systems
What are Information Workers?
The term information worker (also called knowledge worker) was coined to describe those people whose jobs involve the creation, collection, processing, distribution, and use of information. System owners are an information system's sponsors and chief advocates. They are usually responsible for budgeting the money and time to develop, operate, and maintain the information system. They are also ultimately responsible for the systems justification and acceptance.
System Owners
16

System Users
System users are the people who use (and directly benefit from) the information system on a regular basis capturing, validating, entering, responding to, storing, and exchanging data and information. There are many classes of system users including: Internal Users
Clerical and service workers Technical and professional staff Knowledge workers are a subset of information workers whose responsibilities are based on a specialized body of knowledge. Supervisors, middle managers, and executive managers
17

System Users
There are many classes of system users including: (continued) Remote and Mobile Users External Users
18

System Designers
System designers translate users' business requirements and constraints into technical solutions. They design the computer files, databases, inputs, outputs, screens, networks, and programs that will meet the system users' requirements. They also integrate the technical solution back into the day-to-day business environment.
19

System Designers
Todays system designers tend to focus on technical specialties. Database designers have a DATA focus. Software engineers and programmers have a PROCESS (or program) focus. Personal computing specialists and systems integrators usually have an INTERFACE focus. Network and telecommunications specialists have a GEOGRAPHY focus.
20

System Builders
System builders construct the information system components based upon the design specifications from the system designers. In many cases, the system designer and builder for a component are one and the same. The applications programmer is the classic example of a system builder.
21

The Role of the System Analyst
For the system owners and users, the analyst typically constructs and validates their views. For the system designers and builders, the analyst (at the very least) ensures that the technical views are consistent and compatible with the business views.
22

Building Blocks - Expanding The Information System Framework
There are at least four distinct focuses in a system.

DATA - the raw material used to create useful information. PROCESSES - the activities (including management) 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.
23

DATA FOCUS PROCESS FOCUS INTERFACE FOCUS GEOGRAPHY FOCUS
SYSTEM OWNERS (scope)
System Owners' views of DATA
System Owners' views of PROCESSES
System Owners' views of INTERFACES
System Owners' views of GEOGRAPHY
S Y S T E M A N A L Y S T S
SYSTEM USERS (requirements)
System Users' views of DATA
System Users' views of PROCESSES
System Users' views of INTERFACES
System Users' view of GEOGRAPHY
SYSTEM DESIGNERS (specification)
System Designers' views of DATA
System Designers' views of PROCESSES
System Designers' views of INTERFACES
System Designers' views of GEOGRAPHY
SYSTEM BUILDERS (components)
System Builders' views of DATA
System Builders' views of PROCESSES
System Builders' views of INTERFACES
System Builders' views of GEOGRAPHY
Data Technology
Software Technology
Networking Technology
24

FOCUS ON SYSTEM DATA FOCUS ON SYSTEM PROCESSES FOCUS ON SYSTEM INTERFACES FOCUS ON SYSTEM GEOGRAPHY
Marketing
Advertising
Sales
O rders
Cancellations
Services
Decomposition Diagram
r eje c ted or der
C us to mer s c us tomer number
c r edit
C hec k c r edit app ro v ed o rd er
or der with v alid pr oduc ts Valida te pr odu c ts
or der
Valida te v alid or der c us tomer
Ord er s app ro v ed or der pic k in g R elea s e tic k et or der
or der without v alid c us tomer
pr ic es
qua ntity Pr odu c ts in s toc k
Data Flow Diagram
O rder Processing Program
Initiation Routine
Process an O rder
Shutdow n Routine

Check Customer Credit
G et an O rder
Validate an O rder
File an O rder
(facilitation)
Check Product Data
Check Credit Data
Release an O rder
Customers
Products
O rders
Structure Chart
VALIDATE_AN_ORDER. REPEAT UNTIL NO_MORE_ORDERS PERFORM CUSTOMER_VALIDATIO REPEAT UNTIL NO_MORE_ORDER PERFORM PRODUCT_VALIDATI END REPEAT. PERFORM CREDIT_CHECK. IF CREDIT_CHECK 'BAD' THEN
COBOL Program
Database Technology
COBOL Compiler on IBM 3090 MVS
Networking Telchnology
25

Building Blocks of Data

Data is the raw material used to produce information. Goal is to capture and store business data using database technology.
26

Business Subjects
Customers order zero, one, or more products. Products may be ordered by zero, one, or more customers.
Data Requirements
CUSTOMER customer-no customer-name customer-rating balance-due PRODUCT product-no product-name unit-of-measure unit-price quantity-available
ORDER order-no order-date products-ordered quantities-ordered
Database Schema
P RODUCT CUSTOME R product_no [Alpha(10)] INDE X customer_no [Alpha (10)] INDE X product_name [Alpha(32)] customer_name [Alpha(32)] unit_of_measure [Alpha(2)] customer_rating [Alpha(1)] INDE X unit_price [Real(3,2)] balance_due [Real(5,2)] quantity_av ailable [Integer(4)]
(facilitation)
ORDE R_P RODUCT ORDE R ORDE R.order_no order_no [Alpha(12)] INDEX P RODUCT.product_no order_date [Date(mmddyyyy) CUSTOME R.customer_noquantity_ordered [Integer(2)
Database Programs
CREA TE TA BLE CUSTOMER (customer_no CHA R(10) NOT NULL customer_name CHAR(32) NOT NULL customer _rating CHA R(1) NOT NULL balance_due DECIMA L(5,2) CREA TE INDEX cust_no_idx on CUSTOMER CREA TE INDEX cust_rt_idx on CUSTOMER
Database Technology
Software Technology
27

Building Blocks of Processes

PROCESSES deliver the functionality of an information system. Processes perform the work in a system. The goal is to automate appropriate processes with software technology.
32

Business Subjects
Business Functions
Marketing
SYSTEM OWNERS
Advertising Sales
(scope)
O rders Cancellations Services
Data Requirements
Business Process Reqts.

r eje c ted or der C us tomer s c r edit C hec k c r edit app rov ed o rd er c us tomer number or der w ith v alid pr oduc ts Validate pr oduc ts
SYSTEM USERS
or der
(requirements)
Validate v alid or der c us tomer
Ord ers app rov ed or der pic k ing R eleas e tic k et or der
or der w ithout v alid c us tomer
pr ic es
Pr oduc ts
qua ntity in s toc k
Database Scehma
Application Schema
Or der Pr ocessing Pr ogram

Check Custom er Cr edit
Initiation Routine
Pr ocess an Or der
Shutdown Routine
Get an Or der
Validate an Or der
File an Or der
(facilitation)
Check Pr oduct Data
Check Cr edit Data
Release an Or der
Custom er s
Pr oducts
Or ders
Database Structures
Application Programs
VALIDATE_AN_ORDER. REPEAT UNT IL NO_MORE_ORDERS PERFORM CUST OM ER_VALIDAT IO REPEAT UNT IL NO_MORE_ORDER PERFORM PRODUCT _VALIDATI END REPEAT . PERFORM CREDIT _CHECK. IF CREDIT_CHECK 'BAD' THEN
Database Technology
Software (and Hardware) Technology
33

Building Blocks of Interfaces
There are two critical components to information system Interfaces. Information systems must provide effective and efficient interfaces to the systems users. Information systems must interface effectively and efficiently to other information systems, both within the business, and increasingly with other businesses information systems. Technologies exist to implement interfaces. Technologies exist that can almost completely eliminate human error or intervention. Technologies exist for system integration.
40

Business Subjects
Business Functions
System Context
Accounts Receivable Database
SYSTEM OWNERS
Customer Or der
Cr edit
Or der Management System
Picking Or der
War ehouse
(scope)
Cr edit Voucher
Bank
Data Requirements
Input/Output Reqts.
F ire c ra c k e r Sa l e s
Database Scehma
Application Schema
Interface Schema
N e w C us t ome r C us tome r Form Logon Orde r A c c e pt e d C ha nge of A dd re s s
N e w O rde r
Orde r H e lp C omp le t e Orde r Form
Firs t O rde r
(facilitation)
R e q ue s t Orde r H e lp
R e q ue s t Produc t Look up
H e lp +
R e q ue s t Produc t Look up H e lp
Produc t Look up H e lp C omple te
Produc t Look up
Database Structures
Component Programs
On Ev ent Help.ButtonClick Do Change Focus HelpDialog On Ev ent OKButton Do Begin {proecdure} End On Ev ent CancelButton Do
Database Technology
41

Building Blocks of Geography
Information systems geography describes: the distribution of DATA, PROCESSES, and INTERFACES (the other building blocks) to appropriate business locations the movement of data and information between those locations The inclusion of GEOGRAPHY in the framework is driven by the trend towards distributed computing. Distributed computing is the decentralization of applications and databases to multiple computers across a computer network.
47

The most popular application of distributed computing is called client/server computing. In a client/server computing application, information system building blocks are distributed between client personal computers and server shared computers. The clients and servers effectively interoperate to share the overall workload.
48

Distributed computing is being driven by several trends. Organizations that can gain faster access to critical information have a competitive advantage. Organizations that can extend their information systems to include their customers and suppliers have a competitive advantage. Organizations operate in more locations, national and international, then ever before.
49

Business Subjects
Business Functions
System Context
Operating Locations
Data Requirements
Input/Output Reqts.
Communication Reqts.
ED I C us t orde r St . Louis HQ c a t a log c ha nge s Produc ts C a t a log
W est C us t ome rs
s hip orde r
Ea s t C us t ome rs c re dit
c re dit Indy W a re hous e s e rv ic e
LA Of f ic e
s hip orde r
s hip orde r
NY Of f ic e
Ma inte na nc e R e c ords
Database Scehma
Application Schema
Interface Schema
Network Schema
C ommunic a tions C ont rolle r
St . Louis Ma infra me
N T Se rv e r LA PB X N T Se rv e r N Y Et he rne t LA N /N T
(facilitation)
Et he rne t LA N /N T
Indy A IX Se rv e r C lie nt PC C lie nt PC
C lie nt PC
C lie nt PC
Ent e rne t LA N A IX/La n Ma na ge r
Database Structures
Component Programs
Network Programs
Cre ate AccountType = Sale s Cle rk Se t Orde rDir.Rights =full Se t Cus tom e rDir.Rights =full Se t ProductDir.Rights =re ad Se t Orde rAppDir.Rights =copy
Database Technology
50

Business Subjects
Customers order zero, one, or more products. Products may be ordered by zero, one, or more customers.
Business Functions
Marketing
System Context
Accounts Receivable Database Cr edit
Operating Locations
Advertising
Sales
Custom er
Or der
Or der Managem ent S ystem
P icking Or der
W ar ehouse
Cr edit V oucher
Orders
Cancellations
Services
Chapters 5, 6
Chapters 5, 7
Chapters 5, 7
Bank
Chapters 5, 8
Data Requirements
CUST OMER custo mer-no custo mer-name custo mer-ratin g balan ce-due PRO DUCT pro duct-no pro duct-name un it-of-measure un it-price qu antity-available
Business Processes
rejected order Customers customer number credit Check credit
Interface Requirements
Fi recracker Sal es
Communication Reqts.
E DI Cust order S t. Louis HQ catalog changes P r oducts Catalog
order with valid products valid order Validate products
approved order
West Custom ers
ship order
E ast Custom ers credit
order
Validate customer
credit
Orders approved order

LA Office ship order Indy War ehouse ser vice ship order NY Office
Chapters 5, 6
O RDER ord er-no ord er-date pro ducts-ordered qu antities-ord ered
order without valid customer
prices
Chapters 5, 7
Products
quantity in stock
Release order
picking ticket
Chapters 5, 13, 14
Chapters 5, 8
Maintenance Recor ds
Database Scehma
PRODUCT CUSTOMER product_no [Alpha(10)] INDEX customer_no [Alpha (10)] INDEX product_name [Alpha(32)] customer_name [Alpha(32)] unit_of_measure [Alpha(2)] customer_rating [Alpha(1)] INDEXunit_price [Real(3,2)] balance_due [Real(5,2)] quantity_available [Integer(4)]
Application Schema
Order Processing Program Initiation Routine Process an O rder Shutdown Routine
Interface Schema
New Custom er Custom er For m Logon Or der Accepted Change of Addr ess
Network Schema
Com m unications Contr oller S t. Louis Mainfr am e
New Or der
NT S er ver LA
Get an Order Validate an O rder File an Order
Or der Help C om plete
Or der Form
Fir st Or der
P BX
(facilitation)
Request Or der Help
ORDER order_no [Alpha(12)] INDEX order_date [Date(mmddyyyy) CUSTOMER.customer_no
ORDER_PRODUCT ORDER.order_no PRODUCT.product_no quantity_ordered [Integer(2)
Check Customer Credit
Check Product Data
Check Credit Data
Release an Order
Request P r oduct Lookup
NT S er ver NY E ther net LAN /NT
E ther net LAN /NT
Help +
Request P r oduct Lookup Help

Indy AIX S er ver Client P C Client P C
Chapter 12
Customers
Chapters 11, 16
Products
Orders
Chapters 11, 13, 14, 15
P r oduct Lookup Help Com plete
P r oduct Lookup
Client P C
Client P C
Chapter 11
E nter net LAN AIX /Lan Manager
Database Structures
CREATE TABLE CUSTOMER (customer_no CHAR(10) NOT NULL customer_name CHAR(32) NOT NULL customer _rating CHAR(1) NOT NULL balance_due DECIMAL(5,2) CREATE INDEX cust_no_idx on CUSTOMER CREATE INDEX cust_rt_idx on CUSTOMER
VALIDAT E_AN_ORDER. REPEAT UNT IL NO_MORE_ORDERS PERFORM CUST OMER_VALIDATIO REPEAT UNT IL NO_MORE_ORDER PERFORM PRODUCT _VALIDAT I END REPEAT . PERFORM CREDIT_CHECK. IF CREDIT _CHECK 'BAD' T HEN
Component Programs
On Ev ent Help.ButtonClick Do Change Focus HelpDialog On Ev ent OKButton Do Begin {proecdure} End On Ev ent CancelButton Do
Network Programs
Create AccountT ype = SalesClerk Set OrderDir.Rights=full Set CustomerDir.Rights=full Set ProductDir.Rights=read Set OrderAppDir.Rights=copy
any good DB course
any good programming course
any good programming course
any good data communication course
Database Technology
56

Summary

Introduction A Review of Fundamentals of Information Systems A Framework For Information Systems Architecture Perspectives - The People Side of Information Systems Building Blocks - Expanding The Information System Framework
57

Fundamentals of IT

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Fundamentals of IT

Diunggah oleh

Hak Cipta:

Format Tersedia

Information System Building Blocks

The chapter will address the following questions:

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

The chapter will address the following questions:

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

What is the difference between Data and Information?

Information Systems transform data into useful information.

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Transaction Processing System

Data and messages

Read-only data Business Data Warehouse

Decision Support System

Any User Office Information System Captured data

Any Decision Maker or Executive

Communications between users and within groups

Solution Personal Files & Databases Expertise Database

Any Relevant User

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

What is an Information Systems Architecture?

Information System Building Blocks

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

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

What are Information Workers?

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

The Role of the System Analyst

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

There are at least four distinct focuses in a system.

Copyright Irwin/McGraw-Hill 1998

Information System Building Blocks

SYSTEM OWNERS (scope)

System Owners' views of DATA

System Owners' views of PROCESSES

System Owners' views of INTERFACES

System Owners' views of GEOGRAPHY

SYSTEM USERS (requirements)