Introduction to Systems

Development and Systems Analysis

Chapter 20

Copyright © 2015 Pearson Education, Inc.

20-1
 Learning Objectives
 Explain the five phases of the systems development life cycle.

 Discuss the people involved in systems development and the roles they
play.

 Explain the importance of systems development planning and describe

planning techniques.

 Discuss the various types of feasibility analysis and calculate economic

feasibility.

 Explain why system changes trigger behavioral reactions, what form this
resistance to change takes, and how to avoid or minimize the resulting
problems.

 Discuss
Copyright theEducation,
© 2015 Pearson key issuesInc. and steps in systems analysis.
20-2
 1. Introduction
 Why need to improve the information system?
 Changes in user or business needs
 Technology changes
 Improved business process
 Competitive advantage
 Productivity gains
 System integration
 System age and need to be replaced

Copyright © 2015 Pearson Education, Inc.

20-3
 Recent Significant IT Failures

Copyright © 2015 Pearson Education, Inc.

20-4
 2. Systems Development Life Cycle (SDLC)

Copyright © 2015 Pearson Education, Inc.

20-5
 Processes and Deliverables

Copyright © 2015 Pearson Education, Inc.

20-6
 Who Is Involved in the SDLC?
 Information Systems Steering
Committee
 Executive level, plans and
oversees IS function;
facilitates coordination with
integration of systems
activities
 Project Development Team
 Plan and monitor project
progress
 Programmers
 Write and test programs
according to analysts
specifications
Copyright © 2015 Pearson Education, Inc.
 Systems Analysts
 Determine information
needs, prepare specifications
for programmers
 Management
 Get users involved in the
process, provide support for
development projects, align
projects to meet
organizations strategic needs
 Users
 Communicate needs to
system developers, help
design and test to ensure
complete and accurate
processing of data
20-7
 3. Systems Development Planning
Proper planning provides for achieving goals
and objectives
For systems development, two plans needed:
Master Plan
 Long-range and authored by steering committee
outlining prioritized projects and timetables
Project Development Plan
 Specific to a project and authored by the project
team identifies people, hardware, software, and
financial resources needed

Copyright © 2015 Pearson Education, Inc.

20-8
 Planning Techniques
Diagram that depicts all
project activities that
Program evaluation and require time and
review technique resources with
(PERT) completion estimates.
Determines critical
path.

Bar chart that organizes

activities on the left
hand side and project
Gantt chart time scheduled with a
bar drawn to show the
progress to date for that
Copyright © 2015 Pearson Education, Inc. particular activity. 20-9
 Reasoning for Returning to SDLC

20-
Copyright © 2015 Pearson Education, Inc.
10
 Business Case (Feasibility Analysis)
Do benefits of new system justify the costs
Economic (time and resources) to implement?

Technical Can we use existing technology?

Does new system comply with regulations,

Legal laws, and contractual obligations?

Can the system be developed in the time

Scheduling allotted?

Do we have the people to design and

Operational implement the system? Will people use the
Copyright © 2015 Pearson Education, Inc. new system?
20-11
 Capital Budgeting
• Calculate the number of years required
Payback period for the net savings to equal the initial
cost of investment

• Estimate future cash flows with

Net Present discounted rate for (time value of
Value (NPV) money)

Internal Rate • Calculates the interest rate that makes

of Return the present value of total costs equal to
(IRR) the present value of total earnings
Copyright © 2015 Pearson Education, Inc.
20-12
 4. Why People Resist Change?
 Fear
 Of failure, the unknown,
losing status
 Lack of top-management
support
 If the top management is not
supportive why should the
employee change?
 Bad prior experiences
 Bad experience with prior IS
changes
 Poor communication
 Employees need to
understand why change is
necessary
Copyright © 2015 Pearson Education, Inc.
 Disruption
 Additional requests for
information and additional
burdens of time is distracting
and prompts negative feelings
 Manner change is introduced
 Approaches are different for
top level and lower level
employees
 Biases and emotions
 Personal characteristics and
background
 Age
 Open to technology and
comfortable with it
20-13
 5. How to Prevent Behavioral Problems
• Management support
▫ Provide resources and
motivation
• Satisfy user needs
• Involve users
▫ Participation improves
communication and
commitment
• Reduce fears, emphasize
opportunities
• Avoid emotionalism
• Provide training
Copyright © 2015 Pearson Education, Inc.
• Performance evaluation
▫ Reevaluate to ensure
performance standards are
consistent with the new
system
• Keep open communications
• Test the system prior to
implementation
• Keep system simple
▫ Avoid radical changes
• Control user’s expectations
▫ Be realistic
20-14
 6. Phase 1: Systems Analysis

Copyright © 2015 Pearson Education, Inc.

20-15