Chapter 1

Introduction to System
Analysis and Design

Introduction
System Analysis and Design
refers to the process of examining a
business situation with the intent of
improving
it
through
better
procedures and methods.
relates to shaping organizations,
improving performance and achieving
objectives for profitability and growth.

1-2

Nature of Analysis and

Design
Systems analysis and design is a
systematic approach to identifying
problems,
opportunities,
and
objectives;
analyzing
the
information flows in organizations;
and
designing
computerized
information systems to solve a
problem
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-3

System Definition
derived form the Greek word
systema,
which
means
an
organized
relationship among
functioning units or components.
A system exists because it is
designed to achieve one or more
objectives.
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-4

Over View of System Analysis

and Design
Systems development can generally be
thought of as having two major components:
System design
the process of planning a new business
system or one to replace or complement
an existing system. But before this
planning can be done, we must
thoroughly understand the old system
and determine how computers can best
be used to make its operation more
effective.
1-5

Over View of System Analysis

and Design
System analysis
the process of gathering and
interpreting
facts,
diagnosing
problems,
and
using
the
information
to
recommend
improvements to the system. This
is the job of the systems analyst.
1-6

Systems Analyst
Systems analysts act as
Outside consultants to businesses
Supporting experts within a business
As change agents
Analysts are problem solvers, and
require communication skills
Analysts must be ethical with users
and customers
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-7

Business System Concepts

The word system is widely used. It has
become fashionable to attach the word system
to add a contemporary flair when referring to
things or processes. People speak of
investment
system,
delivery
system,
information
system,
education
system,
computer system etc.
System may be referred to any set of
components, which function in interrelated
manner for a common cause or objective.
1-8

Business System Concepts

Definition: System
derived form the Greek word systema, which
means an organized relationship among
functioning units or components. A system
exists because it is designed to achieve one or
more objectives.
an orderly grouping of interdependent
components linked together according to a
plan to achieve a specific objective.

1-9

Business System Concepts

The study of systems concepts, then, has three
basic implications:
1. A system must be designed to achieve a
predetermined objective.
2. Interrelationships and interdependence
must exist among the components.
3. The objectives of the organization as a
whole have a higher priority than the
objectives of its subsystems.
1-10

Characteristics of a System
Organization
implies structure and order
It is the arrangement of components that helps to
achieve objectives.
Interaction
Interaction refers to the manner in which each
component functions with other components of the
system.
Interdependence
Interdependence
means
that
parts
of
the
organization or computer system depend on one
another. They are coordinated and linked together
according to a plan.
1-11

Characteristics of a System
Integration
Integration refers to the holism of systems.
Synthesis follows analysis to achieve the central
objective of the organization.
Central objective
The last characteristic of a system is its central
objective. Objectives may be real or stated.
Although a stated objective may be the real
objective, it is not uncommon for an
organization to state one objective and operate
to achieve another.
1-12

Elements of a System
Outputs and Inputs
A major objective of a system is to produce an
output that has value to its user.
Processor(s)
The processor is the element of a system that
involves the actual transformation of input into
output. It is the operational component of a
system. Processors may modify the input totally
or partially, depending on the specifications of
the output.

1-13

Elements of a System
Control
The control element guides the system. It
is the decision making subsystem that
controls the pattern of activities governing
input, processing, and output. In an
organizational context, management as a
decision making body controls the
inflow, handling and outflow of activities
that affect the welfare of the business.

1-14

Elements of a System
Feedback
Control in a dynamic system is achieved by feedback.
Feedback measures output against a standard in
some form of cybernetic procedure that includes
communication and control. Output information is fed
back to the input and / or to management (Controller)
for deliberation. After the output is compared against
performance standards, changes can result in the
input or processing and consequently, the output.
Feedback may be positive or negative, routing or
informational. Positive feedback reinforces the
performance of the system. It is routine in nature.
Negative feedback generally provides the controller
with information for action.
1-15

Elements of a System
Environment
The environment is the suprasystem within
which an organization operates. It is the
source of external elements that impinge on
the system. In fact, it often determines how a
system must function.
Boundaries and interface
A system should be defined by its boundaries
the limits that identify its components,
processes and interrelationship when it
interfaces with another system.
1-16

Types of System
Physical or Abstract
Physical systems are tangible entities
that may be static or dynamic in operation.
Abstract systems are conceptual or nonphysical entities. They may be as
straightforward
as
formulas
of
relationships among sets of variables or
models the abstract conceptualization of
physical situations. A model is a
representation of a real or a planned
system.
1-17

Open and Closed Systems

Systems are described as either
Open
Free-flowing information
Output from one system becomes input to
another

Closed with restricted access to

information
Limited by numerous rules
Information on a need to know basis
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

2-18

Types of System
Man Made Information Systems
(Information System)
a set of devices, procedures and
operating systems designed around user
based criteria to produce information and
communicate it to the user for planning,
control and performance. In systems
analysis, it is important to keep in mind
that considering an alternative system
means improving one or more of these
criteria.
1-19

Categories
Information systems fall into one of the
following eight categories:
Transaction processing systems (TPS)
Office automation systems (OAS)
Knowledge work systems (KWS)
Management information systems (MIS)
Decision support systems (DSS)
Expert systems (ES)
Group decision support systems (GDSS)
Executive support systems (EES)
1-20

Developing Information
System
In developing an information
system. Most organization find it
beneficial to use a standard set of
steps,
called
System
Development Methodology to
develop
and
support
their
information system

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-21

Systems Development Life

Cycle
Most common methodology for
system development in many
organization
The systems development life cycle
is a systematic approach to solving
business problems
It is divided into seven phases
Each phase has unique activities
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-22

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-23

Phase 1
Identifying
Problems
Opportunities gain competitive edge
Objectives discover what the business is trying to
do.
Personnel involved
Analyst
User management
Systems management
Output
Feasibility report

Copyright 2002 by Prentice Hall, Inc.

1-24

Phase 2
Determining information
requirements
Interview management, operations
personnel
Gather systems/operating documents
Use questionnaires
Observe the system and personnel
involved
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-25

Phase 2
Human Computer Interaction
What are the users physical strength and
limitation.
In other words, What needs to be done to
make the system audible, legible and safe?
How can the new system be designed to be
easy to use, learn and remember?
How can the system be made pleasing or
even fun to use.
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-26

Phase 2
Learn the who, what, where, when, and
how, and the why for each of these
Who the people who are involved
What the business activities
Where the environment in which the
work take place
When the timing
How how the current procedures are
performed under study
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-27

Phase 2
Personnel involved
Analyst
User management
User operations workers
Systems management

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-28

Phase 3
Analyzing system needs
Create data flow diagrams
Document procedural logic for data flow
diagram processes
Complete the data dictionary
Make semistructured decisions
Prepare and present the system proposal
Recommend the optimal solution to
management
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-29

Phase 3
Personnel involved
Analyst
User management
Systems management

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-30

Phase 4
Designing the recommended system
Design the user interface
Design output
Design input

Design system controls

Design files and/or database
Produce program specifications
Produce decision trees or tables
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-31

Phase 4
Personnel involved
Analyst
System designer
User management
User operations workers
Systems management

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-32

Phase 5
Developing and documenting software
Design computer programs using
structure charts, Nassi-Schneiderman
charts, and pseudocode
Walkthrough program design
Write computer programs
Document software with help files,
procedure manuals, and Web sites with
Frequently Asked Questions
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-33

Phase 5
Personnel involved
Analyst
System designer
Programmers
Systems management

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-34

Phase 6
Testing and maintaining the
system
Test and debug computer programs
Test the computer system
Enhance system

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-35

Phase 6
Personnel involved
Analyst
System designer
Programmers
Systems management

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-36

Phase 7
Implementing and evaluating the
system
Plan conversion
Train users
Purchase and install new equipment
Convert files
Install system
Review and evaluate system
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-37

Phase 7
Personnel involved
Analyst
System designer
Programmers
User management
User operations workers
Systems management
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-38

Agile Modeling
Development Process(Agile
Methodology)
A software development approach
based on values, principles and core
practices.
Four values
Communication
Simplicity
Feedback
Courage
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-39

Agile Modeling
Development Process(Agile
Methodology)

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-40

Agile Modeling
Development Process(Agile
Methodology)
Exploration
Adopting a playful and curious attitude
toward the work environment, its
problems, technologies and people.

Planning
Idea of planning game.
Main players (development team;
business customer)
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-41

Agile Modeling
Development Process(Agile
Methodology)
Iterations to the first release
Typically Iteration cycles of testing,
feedback and change)
3 weeks in duration

Productionizing Several activities

occur during this phase.
Feedback cycle speeds up.
Software revision
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-42

Agile Modeling
Development Process(Agile
Methodology)
Product released, but may be
improved by adding other features.

Maintenance
New features may be added
Customer Suggestion

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-43

Object-Oriented Analysis
and Design
Object-oriented (O-O) analysis and
design is used to build objectoriented programs
This includes not only data but the
instructions about operations that
manipulate the data

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-44

Types of Object-Oriented
Analysis and Design
There are three types of objectoriented analysis and design:
Object-oriented analysis (OOA)
Object-oriented design (OOD)
The Unified Modeling Language
(UML), a standardized object-oriented
modeling language

Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-45

Nature of Analysis and

Design
Structured analysis and design
provides a systematic approach to
developing systems and is cyclic in
nature
Analysis and design errors detected
in the later phases of the systems
development life cycle cost more to
fix than if detected in earlier phases
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-46

Alternate Methodologies
Alternate methodologies are
available for analyzing systems
These include
Prototyping
ETHICS
Project champions
Soft Systems Methodology
Multi-view
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-47

Choosing Which Systems

development Method to
use.
Activities involved:
Understand the organization first
Budget the time and resources, develop
project proposal
Interview organizational members and
gather detailed data by using
questionnaires
Sample data from existing reports observe
how business is currently transacted.
Kendall & Kendall

Copyright 2002 by Prentice Hall, Inc.

1-48

Assignment/Quiz
Received letter from organization.

1-49