Chapter 5

• System Analysis

5-1
 What is Systems Analysis ?
Systems analysis – a problem-solving technique that
decomposes a system into its component pieces for the
purpose of studying how well those component parts work
and interact to accomplish their purpose.

Systems design – a complementary problem-solving

technique (to systems analysis) that reassembles a system’s
component pieces back into a complete system—hopefully,
an improved system. This may involves adding, deleting,
and changing pieces relative to the original system.

Information systems analysis – those development phases

in an information systems development project the primarily
focus on the business problem and requirements,
independent of any technology that can or will be used to
implement a solution to that problem.
5-2
 Repository
Repository – a location (or set of locations)
where systems analysts, systems designers,
and system builders keep all of the
documentation associated with one or more
systems or projects.
• Network directory of computer-generated files that
contain project correspondence, reports, and data
• CASE tool dictionary or encyclopedia (Chapter 3)
• Printed documentation (binders and system
libraries)
• Intranet website interface to the above components
5-3
 Model-Driven Analysis Methods

Model-driven analysis – a problem-solving

approach that emphasizes the drawing of pictorial
system models to document and validate both
existing and/or proposed systems. Ultimately, the
system model becomes the blueprint for designing
and constructing an improved system.

Model – a representation of either reality or vision.

Since “a picture is worth a thousand words,” most
models use pictures to represent the reality or
vision.
5-4
 Model-Driven Approaches
• Traditional Approaches
• Structured Analysis
• Focuses on the flow of data through processes
• Key model: data flow diagram
• Information Engineering
• Focuses on structure of stored data
• Key model: entity relationship diagram
• Object-Oriented Approach
• integrates data and process concerns into objects
• Object – the encapsulation of the data (called properties) that
describes a discrete person, object, place, event, or thing, with
all the processes (called methods) that are allowed to use or
update the data and properties. The only way to access or
update the object’s data is to use the object’s predefined
processes.
• Unified Modeling Language (UML)
5-5
 A Simple Data Model

5-6
 A Simple Object Model

5-7
 Accelerated Systems Analysis

Accelerated systems analysis

approaches emphasize the construction
of prototypes to more rapidly identify
business and user requirements for a new
system.

prototype – a small-scale, incomplete,

but working sample of a desired system.
• Accelerated systems analysis approaches
• Discovery Prototyping
• Rapid Architected Analysis
5-8
 Discovery Prototyping

Discovery prototyping – a technique used to

identify the users’ business requirements by
having them react to a quick-and-dirty
implementation of those requirements.

• Advantages
• Prototypes cater to the “I’ll know what I want when I see it” way
of thinking that is characteristic of many users and managers.
• Disadvantages
• Can become preoccupied with final “look and feel” prematurely
• Can encourage a premature focus on, and commitment to, design
• Users can be misled to believe that the completed system can be
built rapidly using prototyping tools
5-9
 Rapid Architected Analysis

Rapid architected analysis – an approach that

attempts to derive system models (as described
earlier in this section) from existing systems or
discovery prototypes.

• Reverse engineering – the use of technology that

reads the program code for an existing database,
application program, and/or user interface and
automatically generates the equivalent system
model.
5-10
 Requirements Discovery

Requirements discovery – the process,

used by systems analysts of identifying or
extracting system problems and solution
requirements from the user community.

5-11
 Requirements Discovery
Methods
• Fact-finding – the process of collecting information
about system problems, opportunities, solution
requirements, and priorities.
• Sampling existing documentation, reports, forms, databases,
etc
• Research of relevant literature
• Observation of the current system
• Questionnaires and surveys
• Interviews
• Joint requirements planning (JRP) –use of facilitated
workshops to bring together all of the system owners,
users, and analysts, and some systems designer and
builders to jointly perform systems analysis.
• Considered a part of a larger method called joint application
development (JAD), a more comprehensive application of the
5-12 JRP techniques to the entire systems development process.
 Business Process Redesign

Business process redesign (BPR) – the

application of systems analysis methods
to the goal of dramatically changing and
improving the fundamental business
processes of an organization,
independent of information technology.

5-13
 Agile Methods
Agile method – integration of various
approaches of systems analysis and design for
applications as deemed appropriate to problem
being solved and the system being developed.
• Most commercial methodologies do not impose a
single approach on systems analysts.
• Instead, they integrate all popular approaches into a
collection of agile methods.
• System developers are given the flexibility to select
from a variety of tools and techniques to best
accomplish the tasks at hand,
• Hypothetical FAST methodology operates this way.

5-14
 FAST Systems Analysis Phases
• Scope Definition Phase
• Is the project worth looking at?

• Problem Analysis Phase

• Is a new system worth building?

• Requirements Analysis Phase

• What do the users need and want from the new system?

• Logical Design Phase

• What must the new system do?

• Decision Analysis Phase

• What is the best solution?
5-15
 Context of Scope Definition
Phase

5-16
 Key Terms for Scope Definition
Phase
Steering body – a committee of executive business and
system managers that studies and prioritizes competing
project proposals to determine which projects will return
the most value to the organization and thus should be
approved for continues systems development.
• Also called a steering committee.

Project charter – the final deliverable for the preliminary

investigation phase. A project charter defines the project
scope, plan, methodology, standards, and so on.
• Preliminary master plan includes preliminary schedule and
resource assignments (also called a baseline plan).
• Detailed plan and schedule for completing the next phase of the
project.
5-17
 Sample Request for System
Services

5-18
 Sample Problem Statements

5-19
 Context of Problem Analysis
Phase

5-20
 Key Terms of the
Problem Analysis Phase
Cause-and-effect analysis – a technique in which
problems are studied to determine their causes and
effects.
In practice, effects can be symptomatic of more deeply
rooted problems which, in turn, must be analyzed for
causes and effects until the causes and effects do not
yield symptoms of other problems.

Context Diagram – a pictorial model that shows

how the system interacts with the world around it
and specifies in general terms the system inputs and
outputs.
5-21
 Sample Cause-and-Effect
Analysis

5-22
 Sample Context Diagram

5-23
 Key Terms of the
Problem Analysis Phase (cont.)
Objective – a measure of success. It is something that you
expect to achieve, if given sufficient resources.
• Reduce the number of uncollectible customer
accounts by 50 percent within the next year.
• Increase by 25 percent the number of loan
applications that can be processed during an eight-
hour shift.
• Decrease by 50 percent the time required to
reschedule a production lot when a workstation malfunctions.

Constraint – something that will limit your flexibility in

defining a solution to your objectives. Essentially, constraints
cannot be changed.
• The new system must be operational by April 15.
• The new system cannot cost more than $350,000.
• The new system must be web-enabled.
5-24 • The new system must bill customers every 15 days.
 System Improvement Report
Outline
I. Executive summary (approximately 2 pages)
A. Summary of recommendation
B. Summary of problems, opportunities, and directives
C. Brief statement of system improvement objectives
D. Brief explanation of report contents
II. Background information (approximately 2 pages)
A. List of interviews and facilitated group meetings conducted
B. List of other sources of information that were exploited
C. Description of analytical techniques used
III. Overview of current system (approximately 5 pages)
A. Strategic implications (if project is part of or impacts
existing IS strategic plan)
B. Models of the current system
1. Interface model (showing project scope)
2. Data model (showing project scope)
3. Geographical models (showing project scope)
4. Process model (showing functional decomposition only)
5-25
 System Improvement Report
Outline (cont.)
IV. Analysis of the current system (approx. 5-10 pages)
A. Performance problems, opportunities, cause-effect analysis
B. Information problems, opportunities, cause-effect analysis
C. Economic problems, opportunities, cause-effect analysis
D. Control problems, opportunities, cause-effect analysis
E. Efficiency problems, opportunities, cause-effect analysis
F. Service problems, opportunities, and cause-effect analysis
V. Detailed recommendations (approx. 5-10 pages)
A. System improvement objectives and priorities
B. Constraints
C. Project Plan
1. Scope reassessment and refinement
2. Revised master plan
3. Detailed plan for the definition phase
VI. Appendixes
A. Any detailed system models
B. Other documents as appropriate
5-26
 Context of Requirements
Analysis Phase

5-27
 Key Terms of
Requirements Analysis Phase
Functional requirement – a description
of activities and services a system must
provide.
• inputs, outputs, processes, stored data

Nonfunctional requirement – a
description of other features,
characteristics, and constraints that
define a satisfactory system.
• Performance, ease of learning and use, budgets,
deadlines, documentation, security, internal
auditing controls
5-28
 Key Terms of Requirements
Analysis Phase (cont.)
Use case – a business scenario or event for
which the system must provide a defined
response. Use cases evolved out of object-
oriented analysis; however, their use has
become common in many other methodologies
for systems analysis and design.

5-29
 Key Terms of Requirements
Analysis Phase (cont.)
Timeboxing – a technique that delivers information
systems functionality and requirements through
versioning.
1. The development team selects the smallest subset of the system
that, if fully implemented, will return immediate value to the
systems owners and users.
2. That subset is developed, ideally with a time frame of six to nine
months or less.
3. Subsequently, value-added versions of the system are
developed in similar time frames.

• A mandatory requirement is one that must be fulfilled by the

minimal system, version 1.0
• A desirable requirement is one that is not absolutely essential to
version 1.0. It may be essential to the vision of a future version.
5-30
 Key Terms of Decision Analysis
Phase
• Technical feasibility – Is the solution technically
practical? Does our staff have the technical expertise to
design and build this solution?

• Operational feasibility – Will the solution fulfill the

users’ requirements? To what degree? How will the
solution change the users’ work environment? How do
users feel about such a solution?

• Economic feasibility – Is the solution cost-effective?

• Schedule feasibility – Can the solution be designed

and implemented within an acceptable time period?
5-31
 Typical System Proposal
Outline
I. Introduction
A. Purpose of the report
B. Background of the project leading to this report
C. Scope of the report
D. Structure of the report
II. Tools and techniques used
A. Solution generated
B. Feasibility analysis (cost-benefit)
III. Information systems requirements
IV. Alternative solutions and feasibility analysis
V. Recommendations
VI. Appendices
5-32