Scribd
Upload
215 views15 pages

Systems Analysis and Design: Chapter1: The Systems Analyst and Information Systems Development

Uploaded by

drive share
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
215 views15 pages

Systems Analysis and Design: Chapter1: The Systems Analyst and Information Systems Development

Uploaded by

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

Systems Analysis and Design

5th Edition

Chapter1: The Systems Analyst and


Information Systems Development

Alan Dennis, Barbara Haley Wixom, and Roberta Roth

© Copyright 2011 John Wiley & Sons, Inc. 1-0


PROJECT IDENTIFICATION AND
INITIATION
 A project is identified when someone in the
organization identifies a business need to build
a system.
 A need may surface when an organization
identifies unique and competitive ways of using
IT.
 To leverage the capabilities of emerging
technologies such as cloud computing, RFID,
Web 2.0

© Copyright 2011 John Wiley & Sons, Inc. 1-1


Project sponsor
 The project sponsor is a person (or group) who has
an interest in the system’s success
 The project sponsor will work throughout the SDLC
to make sure that the project is moving in the right
direction from the perspective of the business.
 The project sponsor serves as the primary point of
contact for the project team.
 The size or scope of the project determines by the
kind of sponsor that is involved.

© Copyright 2011 John Wiley & Sons, Inc. 1-2


(cont’d)
 The project sponsor has the insights needed to
determine the business value that will be
gained from the system.
 Tangible value can be quantified and measured
easily (reduction in operating costs).
 An intangible value results from an intuitive
belief that the system provides important, but
hard-to-measure benefits to the organization.

© Copyright 2011 John Wiley & Sons, Inc. 1-3


System Request
The document that describes the
business reasons for building a system
and the value that system is expected
to provide.
The project sponsor usually completes
this form as part of a formal system
selection process within the
organization.
© Copyright 2011 John Wiley & Sons, Inc. 1-4
(cont’d)
 The business requirements of the project refer
to the business capabilities that the system
will need to have.
 The business value describes the benefits that
the organization should expect from the
system.
 Special issues are included on the document
as a catchall category for other information
that should be considered in assessing the
project.
© Copyright 2011 John Wiley & Sons, Inc. 1-5
(cont’d)
 The completed system request is submitted
to the approval committee for
consideration.
 The committee reviews the system request
and makes an initial determination of
whether to investigate the proposed
project or not.
 If so, the next step is to conduct a feasibility
analysis.
© Copyright 2011 John Wiley & Sons, Inc. 1-6
FEASIBILITY ANALYSIS
Feasibility analysis guides the
organization in determining whether
to proceed with a project.
Feasibility analysis also identifies the
important risks associated with the
project that must be managed if the
project is approved.
© Copyright 2011 John Wiley & Sons, Inc. 1-7
(cont’d)
 As with the system request, each organization has
its own process and format for the feasibility
analysis, but most include techniques to assess
three areas:
– Technical feasibility
– Economic feasibility
– Organizational feasibility
 The results of evaluating these three feasibility
factors are combined into a feasibility study
deliverable that is submitted to the approval
committee at the end of project initiation.
© Copyright 2011 John Wiley & Sons, Inc. 1-8
Technical Feasibility
Technical feasibility is the extent to
which the system can be successfully
designed, developed, and installed
by the IT group.
It is, in essence, a technical risk
analysis that strives to answer the
question: “Can we build it?”
© Copyright 2011 John Wiley & Sons, Inc. 1-9
(cont’d)
 Risks can endanger the successful completion
of a project. The following aspects should be
considered:
– Users’ and analysts’ should be familiar with the
application.
– Familiarity with the technology
– Project size
– Compatibility of the new system with the
technology that already exists
© Copyright 2011 John Wiley & Sons, Inc. 1-10
Economic Feasibility
Economic feasibility analysis is also
called a cost-benefit analysis, that
identifies the costs and benefits
associated with the system.
This attempts to answer the
question: “Should we build the
system?”
© Copyright 2011 John Wiley & Sons, Inc. 1-11
Organizational Feasibility
 Organizational feasibility of the system is how well
the system ultimately will be accepted by its users
and incorporated into the ongoing operations of the
organization.
 There are many organizational factors that can have
an impact on the project, and seasoned developers
know that organizational feasibility can be the most
difficult feasibility dimension to assess.
 In essence, an organizational feasibility analysis is to
answer the question “If we build it, will they come?”

© Copyright 2011 John Wiley & Sons, Inc. 1-12


(cont’d)
 One way to assess the organizational feasibility is to
understand how well the goals of the project align
with the business objectives and organizational
strategies.
 A second way to assess the organizational feasibility
is to conduct stakeholder analysis.
 A stakeholder is a person, group, or organization that
can affect a new system
- Project champion
- System users
- Organizational management
- Other stakeholders
© Copyright 2011 John Wiley & Sons, Inc. 1-13
SUMMARY
 The Systems Analyst is the key person in the development
of information systems.
 The Systems Development Lifecycle consists of four
stages: Planning, Analysis, Design, and Implementation.
 Project Identification and Initiation recognize a business
need that can be satisfied through the use of information
technology.
 System Request describes the business value for an
information system.
 A Feasibility Analysis is used to provide more detail about
the risks associated with the proposed system.

© Copyright 2011 John Wiley & Sons, Inc. 1-14

You might also like