0% found this document useful (0 votes)
2 views46 pages

13. Information Systems

information system

Uploaded by

ranatanzeem795
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views46 pages

13. Information Systems

information system

Uploaded by

ranatanzeem795
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 46

CHAPTER 12A

The Basics of Information Systems


PURPOSE OF INFORMATION SYSTEMS
 Information systems
 Collects,stores and organizes information
 Retrieves value from data
 Harness many types of data
 Computer’s reason for existence

12A
-2
PURPOSE OF INFORMATION SYSTEMS
 Components of an information system
 Physical means of storing information
 Procedures for ensuring data integrity
 Rules regarding data use and distribution
 Means of distributing the data
 Tools to organize the data
TYPES OF INFORMATION SYSTEMS
 Office automation systems
 Performs various office tasks
 Allows users to efficiently handle data
 Tedious tasks become simple
 Built using off-the-shelf systems
 Allow seamless integration of data
TYPES OF INFORMATION SYSTEMS
 Transaction processing systems (TPS)
 Transaction is a complete event
 Completed in a series of steps
 Tracksand processes transactions
 Each step is monitored
 Details sent to the appropriate person
 Errors must be remedied immediately
TYPES OF INFORMATION SYSTEMS
 Management information systems (MIS)
 Toolsfor managers and decision makers
 Organizes and evaluates information
 Summarizes reports based on need
 Managers require different views of data
MANAGEMENT INFORMATION SYSTEM
TYPES OF INFORMATION SYSTEMS
 Decision support system
 Organizes information for better decisions
 Different data and criteria are evaluated
 Often based on spreadsheet software
 Provides tailored and structured reports
TYPES OF INFORMATION SYSTEMS
 Expert systems
 Perform tasks done by a person
 Analyze data and suggest an action
 Requires a large knowledge base
 Inference engines
 Analyze the data
 Make the decisions
EXPERT SYSTEM
INFORMATION SYSTEMS
TECHNOLOGY
 Intranets
 Privatenetwork using internet technology
 Employees use to access data
 Databases are stored on the Intranet
 Access to outside users is blocked
INFORMATION SYSTEMS
TECHNOLOGY
 Extranets
 Outside access to an intranet
 Goal is to simplify a process
 Just-in-time inventory
 Manufacturer keeps little material in stock
 Arranges to have stock delivered daily
INFORMATION SYSTEMS
TECHNOLOGY
 Virtual Private Networks
 Secure connection over the Internet
 Tunneling provides security
 Data transmitted in an encrypted packet
 Employees use to work from home
 Networks use to connect securely
 Once established, the VPN is transparent
VIRTUAL PRIVATE NETWORK
INFORMATION SYSTEMS
TECHNOLOGY
 Electronic data interchange (EDI)
 Electronictransfer of data
 Data transferred in a precise manner
 Networks often share an information system
 Over time can save organizations money
INFORMATION SYSTEMS
TECHNOLOGY
 Data warehousing
 Provides 24x7 access to data
 Fault tolerant
 Data security
INFORMATION SYSTEMS
TECHNOLOGY
 Data scrubbing
 Provides
for data consistency and validity
 Compares data to a set of rules
 Failures are repaired or removed
 Should be performed at all levels
 Data entry
 Storage

 As rules change data is rescrubbed


INFORMATION SYSTEMS HARDWARE
 Server farms
 Collection of servers and mainframes
 Servers work together
 Servers are either distributed or collected
 Uses of server is critical
INFORMATION SYSTEMS HARDWARE
 Enterprise storage
 Methods and technologies to store data
 Efficiently store large amounts of data
 Data is accessible at all times
 RAID and NAS are two types
INFORMATION SYSTEMS HARDWARE
 RAID
 Redundant Array of Inexpensive Disks
 Links a number of hard drives
 Provides data redundancy
 Can speed access to data
 RAID 0
 Disk striping
 RAID 1
 Disk mirroring
 RAID 3, 4, and 5
 Disk striping with parity
RAID 1 MULTIPLE DISK MIRROR
INFORMATION SYSTEMS HARDWARE
 NAS
 Network Attached Storage
 Disk storage connected to network media
 Disk system processes and delivers data
 Storage Area Networks (SAN)
INFORMATION SYSTEMS HARDWARE
 Backup
 Protects files and settings
 Can restore data to an earlier point
 Crucial to any information system
 Transaction rollback
 Logs changes to a file
 Changes are undone when necessary

 Tape backup
 Copies files to a tape
 Files need recopied when necessary
INFORMATION SYSTEMS HARDWARE
 Nonstop and redundant systems
 Mission critical system
 Must run 24x7
 Most information systems mission critical
 Redundant systems are backup computers
 Backup takes over when necessary
INFORMATION SYSTEMS HARDWARE
 Scalable and interoperable systems
 Scalability
 Defines a systems ability to grow
 Software and hardware grows

 Interoperable systems
 Work with other systems
 Little configuration is needed
INFORMATION SYSTEMS DEPARTMENT
 Integral part of any organization
 Maintains equipment, software and data

 Enables other employees to function

 Requires highly trained employees

 Various names
 Information Systems (IS)
 Information Technology (IT)
 Management Information Systems (MIS)
CHAPTER 12A
End of Chapter
CHAPTER 12B
Building Information Systems
SYSTEMS DEVELOPMENT LIFE CYCLE
 Organized way to build information systems
 Consists of five phases
 Entire usable life of the system

12B
-29
SDLC

12B
-30
SYSTEMS DEVELOPMENT LIFE CYCLE
 Phase 1: needs analysis
 Users identify a need
 Solves three main problems
 Define the problem
 Present possible solutions

 Determine the best solution

 Technology analysts talk with users


 Define the problem using a description tool
 A solution is presented to a manager

12B
-31
SYSTEMS DEVELOPMENT LIFE CYCLE
 Phase 2: Systems design
 Solution is defined
 Data storage
 User interface

 Reports

 Several design tools


 Top down design
 Bottom up design

 CASE tools used to build prototypes


 Computer aided software engineering

12B
-32
SYSTEMS DEVELOPMENT LIFE CYCLE
 Phase 3: Development
 Solution to the problem is built
 Programmers play a key role
 Solutions may be purchased
 Solutions may be built locally
 Technical writers create instructions
 Solution is repeatedly tested

12B
-33
SYSTEMS DEVELOPMENT LIFE CYCLE
 Phase 4: Implementation
 Installation
of hardware and software
 Users must convert to the solution
 Direct conversion
 Parallel conversion

 Phased conversion

 Pilot conversion

 Trainers and support personnel are critical

12B
-34
SDLC CONVERSION

12B
-35
SYSTEMS DEVELOPMENT LIFE CYCLE
 Phase 5: Maintenance
 ITprofessionals continue to monitor
 Bugs are fixed
 New features are added
 Users often suggest bugs or features

12B
-36
EVOLVING SYSTEM DESIGN METHODS
 Problems with SDLC
 SDLC is an old process
 Very slow process
 Companies need to respond quickly

12B
-37
EVOLVING SYSTEM DESIGN METHODS
 Rapid Application Design (RAD)
 Develops IS systems quickly
 Several products exist
 Slightly different development phases

12B
-38
RAD SDLC

12B
-39
EVOLVING SYSTEM DESIGN METHODS
 RAD Phase 1: Requirements planning
 Requirements for project are defined
 Joint requirements planning (JRP)
 Involves programmers and managers
 Managers from affected departments provide
guidance

12B
-40
EVOLVING SYSTEM DESIGN METHODS
 RAD Phase 2: User design
 Joint application design (JAD)
 System analysts and users
 User provides the details
 System analyst solve the technical details

12B
-41
EVOLVING SYSTEM DESIGN METHODS
 RAD Phase 3: Rapid construction
 ISprofessionals develop the project
 A variety of tools can be used
 Users approve each portion

12B
-42
EVOLVING SYSTEM DESIGN METHODS
 RAD Phase 4: Transition
 System is tested on sample data
 Users are trained on the sample
 New system runs parallel to existing
 Phase complete when bugs are gone
 Old system removed

12B
-43
EVOLVING SYSTEM DESIGN METHODS
 RAD Phase 5: Maintenance
 Traditionallynot part of RAD
 All systems need periodic maintenance

12B
-44
EVOLVING SYSTEM DESIGN METHODS
 Object Oriented Systems Analysis
 OOSA
 Project elements are defined using objects
 Objects are self contained programming constructs
 Objects have data and functionality

 Objects are linked together


 Java and C++ are typical tools

12B
-45
CHAPTER 12B
End of Chapter

You might also like