Solving Business Problems with Information Systems

A system approach to problem solving

Developing Information System Solution
I

Developing A system approach to problem solving

 Information Systems Development

The systems approach to problem solving applied to

the development of information system solutions to
business problems.
 The Systems Approach
The systems approach to problem solving
Recognize and define a problem or opportunity using
systems thinking
Develop and evaluate alternative system solutions
Select the system solution that best meets your
requirements
Design the selected system solution
Implement and evaluate the success of the designed
system
 The Systems Approach (continued)

Systems Thinking
Seeing interrelationships among systems rather than
linear cause-and-effect chains when events occur
Seeing processes of change among systems rather than
discrete snapshots of change, whenever change occurs.
 Developing Information System Solution
(The Systems Development Cycle)
Investigation
Analysis
Design
Implementation
Maintenance
Prototyping
The rapid development and testing of working models
of new applications in an interactive, iterative process.
Prototyping (continued)

The prototyping process

 Starting the Systems Development Process

Systems Investigation Phase

Feasibility studies
Organizational feasibility
Economic feasibility
Technical feasibility
Operational feasibility
Starting the Systems Development Process (continued)
Starting the Systems Development Process (continued)
Starting the Systems Development Process (continued)

Cost/Benefit Analysis
Tangible costs
Intangible costs

Tangible benefits
Intangible benefits
Starting the Systems Development Process (continued)
 Systems Analysis
Systems analysis is an in-depth study of end user
information needs that produces functional requirements.

Traditionally involves a detailed study of

Information needs of the company & end users
Activities, resources, & products of one or more of the present
information systems
The IS capabilities required to meet information needs of the
company, the end users, and all business stakeholders that may use
the system
 Organizational analysis

Management structure
The people
Business activities
Environmental systems
The current information system
 Systems Analysis (continued)

Analysis of the present system

Analyze how the present system..
Uses hardware
Uses software
Is networked
Uses people resources to convert data resources into
information products.
How the IS activities of input, processing, output, storage, and
control are accomplished.
 Systems Analysis (continued)
Functional requirements analysis
What type of information does each business activity require?
Format, volume, frequency, response times
What are the information processing capabilities required?
Input, processing, output, storage, control

Finally, develop functional requirements

End user information requirements that are not tied to the
hardware, software, network, data, and people resources

Goal identify what should be done, not how to do it.

 Systems Design

Specifies HOW the system will meet the information

needs of users

Focuses on three major products

User interface design
Data design
Database structures
Process design
Processing and control procedures
Systems Design (continued)

User interface design

Focuses on supporting the interactions between end
users and the computer-based applications
Display screens
Interactive user/computer dialogues
Audio responses
Forms, documents, and reports
Systems Design (continued)

System specifications
Formalizes the design of the applications user interface
methods & products
Formalizes database structures
Formalizes processing and control procedures
 End User Development

Information Systems professionals play a consulting role

Training in the use of application packages

Assistance with the selection of hardware and software

Assistance in gaining access to organization databases

Assistance in the analysis, design, and implementation of your

application
 End User Development (continued)

The application development process

Input
What data are available? From what sources? In what form?
Processing
What operations or transformation processes will be required to
convert available inputs into the desired output?
What software package can best perform the required operations?

Output
What information is needed and in what form?
Storage
Control
How will you protect against accidental loss or damage to end user
files?
End User Development (continued)
Section II: Implementing e-Business Systems
Implementation
This is the actual deployment of the information
technology system.

Follows the investigation, analysis, and design stages

of the systems development cycle.
Implementing New Systems
Evaluating Hardware, Software, & Services

May require suppliers to present bids and proposals

based on system specifications
Minimum acceptable physical & performance
characteristics for all hardware and software
requirements are established
Large businesses and government agencies formalize
requirements by listing them in a Request for Proposal
(RFP) or a Request for Quotation (RFQ)
 Evaluating Hardware, Software, and Services (continued)

May use a scoring system for evaluation

Determine evaluation factors and assign points

Performance of hardware and software must be

demonstrated and evaluated
May use benchmark test programs
Evaluating Hardware, Software, and Services (continued)
Hardware evaluation factors
Performance
Speed, capacity, throughput
Cost
Lease or purchase price
Cost of operations and maintenance
Reliability
Risk of malfunction & maintenance
requirements
Error control and diagnostic features
Connectivity
Easily connected to WANs and LANs
that use different types of network
technologies and bandwidth
alternatives?
Scalability
Can it handle the processing demands
of end users, transactions, queries, &
other processing requirements?
Compatibility
With existing hardware and software?
With hardware & software provided
by competing suppliers?
Technology
Year of product life cycle
Does it use a new, untested
technology?
Does it run the risk of obsolescence?
Ergonomics
human factors engineered?
User-friendly?
Safe, comfortable, easy to use?
Software
Is system software and application
software available that can best use
this hardware?
Support
Is support available?
 Evaluating Hardware, Software, and Services (continued)
Software evaluation factors
Flexibility
Can it handle our processes easily
without major modification?
Security
Does it provide control
procedures for errors,
malfunctions, and improper use?
Connectivity
Web-enabled?
Language
Is the programming language
familiar to internal software
developers?
Hardware
Does existing hardware have the
features required to best use this
software?
Documentation
Well-documented? Help screens
and helpful software agents?
Quality
Bug free?
Efficiency
Well-developed system of
program code that does not use
much CPU time, memory
capacity, or disk space?
Other factors
Performance, cost, reliability,
availability, compatibility,
modularity, technology,
ergonomics, scalability, and
support characteristics
Evaluating Hardware, Software, and Services (continued)
Evaluating information system Services Accessibility
Performance Services from local or regional sites?

Past performance in view of past promises Customer support center?

Customer hot line?
Systems development
Are website and other e-business
Business position
developers available? Quality and cost Financially strong with good industry
market prospects?
Maintenance
Is equipment maintenance provided?
Hardware
Quality and cost Provide a wide selection of compatible
hardware devices and accessories?
Conversion
What systems development & installation
Software
services will they provide during the Offer a variety of useful e-business
conversion period? software and application packages?
Training
Provided? Quality and cost
Backup
Are similar computer facilities
available nearby for emergency
backup purposes?
Other Implementation Activities
Testing Training
May involve website performance End users must be trained to operate a
testing new e-business system or
Testing and debugging software implementation will fail
Testing new hardware May be limited in scope or may involve
Reviewing prototypes of displays,
all aspects of the proper use of the new
reports, and other output system
Managers and end users must be
Should occur throughout the
development process educated in how the new technology
impacts business operations and
Documentation management
Sample data entry screens, forms, and
reports are examples.
Serves as a method of communication
among the people responsible for
developing, implementing, and
maintaining the system
A detailed record of the systems design
Important in diagnosing errors &
making changes
 Other Implementation Activities (continued)

Conversion methods
Parallel
Both old and new systems are operated until the project
development team and end users agree to switch completely
Phased
Only parts of the new application or only a few locations at a
time are converted
Pilot
One department or other work site serves as a test site

Plunge
A direct cutover to the newly developed system
 Other Implementation Activities (continued)

Information systems Maintenance

Systems maintenance

Post implementation review

 Thank You

shiferawsm@gmail.com
 ?
What are the most important factors you would use in evaluating computer
hardware and computer software development?

From Parallel, Phased, Pilot and Plunge method of conversion which method is
the best approach of converting old system with the new information system
in the Pharmaceutical business and why it is best approach for the
Pharmaceutical business ?