Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Information
Systems
9th Edition
Marshall B. Romney
Paul John Steinbart
16-1
Introduction to Systems
Development and
Systems Analysis
Chapter 16
16-2
Learning Objectives
16-3
Learning Objectives
4. Discuss the various types of
feasibility analysis, and calculate
economic feasibility.
5. Explain why systems change triggers
behavioral reactions, what form this
resistance to change takes, and how
to avoid or minimize the resulting
problems.
6. Discuss the key issues and steps in
systems analysis.
16-4
Introduction
Ann Christy was promoted to controller of
Shoppers Mart (SM).
She determined the following:
Store managers cannot obtain information
other than what is contained on SM’s
periodic, preformatted reports.
The sales and purchasing departments
cannot get timely information about what
products are or are not selling well.
16-5
Introduction
16-6
Introduction
16-8
Introduction
16-9
Learning Objective 1
16-10
The Systems Development
Life Cycle
What are the five steps in the
systems development life cycle
(SDLC)?
1. Systems analysis
2. Conceptual design
3. Physical design
4. Implementation and conversion
5. Operations and maintenance
16-11
The Systems Development
Life Cycle: Systems Analysis
Systems Analysis
Do initial investigation
Do system survey
Do feasibility study Conceptual
Determine information needs Design
and system requirements
Deliver systems requirements
16-12
The Systems Development
Life Cycle: Conceptual Design
Conceptual Design
Identify and evaluate
design alternatives
Develop design specifications Physical
Design
Deliver conceptual design
requirements
16-13
The Systems Development
Life Cycle: Physical Design
Physical Design
Design output
Design database
Implementation
Design input and Conversion
Develop programs
Develop procedures
Design controls
Deliver developed system
16-14
The Systems Development
Life Cycle: Implementation and
Conversion
Implementation and Conversion
Develop plan
Install hardware and software
Train personnel, test the system
Operation
Complete documentation
and
Convert from old to new system Maintenance
Fine-tune and review
Deliver operational system
16-15
The Systems Development
Life Cycle: Operation and
Maintenance
Feasibility analysis
Operation and Maintenance and decision points:
Operate system Economic
Feasibility
Modify system
Technical Feasibility
Do ongoing maintenance
Legal Feasibility
Deliver improved system
Scheduling
Feasibility
Systems
Operational
Analysis Feasibility
16-16
Learning Objective 2
16-17
The Players
16-18
The Players
16-19
The Players
16-20
The Players
16-21
The Players
16-22
The Players
16-23
Learning Objective 3
16-24
Planning Systems
Development
Why is planning an important step in
systems development?
– consistency
– efficiency
– cutting edge
– lower costs
– adaptability
16-25
Planning Systems
Development
What types of systems development
plans are needed?
– project development plan
– master plan
16-26
Planning Techniques
Two techniques for scheduling and
monitoring systems development activities
are:
1 PERT (program evaluation and review
technique)
• PERT requires that all activities and the precedent
and subsequent relationships among them be
identified.
2 Gantt chart
• A bar chart with project activities listed on the left-
hand side and units of time across the top
16-27
Planning Techniques:
Gantt Chart
16-29
Feasibility Analysis
16-30
Feasibility Analysis
16-32
Feasibility Analysis
16-33
Learning Objective 5
16-34
Behavioral Aspects of
Change
Individuals involved in systems
development are agents of change
who are continually confronted by
people’s reaction and resistance to
change.
The best system will fail without the
support of the people it serves.
16-35
Behavioral Aspects of
Change
Why do behavioral problems occur?
– personal characteristics and
background
– manner in which change is introduced
– experience with prior changes
– communication
– disruptive nature of the change
process
– fear
16-36
Behavioral Aspects of
Change
How do people
resist AIS
changes?
– aggression
– projection
– avoidance
16-37
Behavioral Aspects
of Change
How can behavioral problems be
overcome?
– meet needs of the users
– keep communication lines open
– maintain a safe and open atmosphere
– obtain management support
– allay fears
– solicit user participation
– make sure users understand the system
16-38
Behavioral Aspects of
Change
– How can behavioral problems be
overcome? (continued)
– provide honest feedback
– humanize the system
– describe new challenges and opportunities
– reexamine performance evaluation
– test the system’s integrity
– avoid emotionalism
– present the system in the proper context
– control the users’ expectations
– keep the system simple
16-39
Learning Objective 6
16-40
Systems Analysis
16-43
End of Chapter 16
16-44