SYSTEMS ANALYSIS

AND
DESIGN
INTRODUCTION
1

Systems Analysis and Design is

the process people use to create
(automated) information systems

Systems
Analysis
& Design

Information
System
2

Is there an official name?

Systems Analysis and Design!

Software Engineering!
Information Systems Enginee

Systems Engineering!
Information Systems Develop
Other names...!

Which
one?
3

Systems Analyst
A title given to a person who studies
the problems and needs of an
organization looking for improvement
opportunities.

Other names:

Software Engineer
Systems Engineer
Software Developer
Programmer/Analyst
Nerd or Hacker! (joking!)
4

SYSTEMS ANALYSIS AND

DESIGN: A Condensed
(Informal) Perspective

An idea

Completed
Design and
ImplementationInformation
System
Time

Analysis

SYSTEMS ANALYSIS AND

DESIGN: A Complete (Formal)
Perspective

Systems Planning

Systems Analysis

Systems Design

Systems
Implementation

Planning
Evolution

Analysis

ImplementationDesign

Systems Evolution
6

System
Natural

Fabricated
Information
Systems

Automated
Information
Systems

Others

Others

Business problems come in all sizes

Name & Address Book

CD Collection

Course Registration

Reservations

Student Grades

Payroll

ATM machine & Banking in General

Check-Out Counters at Retail Stores

Order Fulfillment - Mail or Web Ordering

Examples: Manufacturing

Securities Portfolio Management

Space Shuttle Flight

Election Results

Video Games (Arcade and Home)

System
A

SYSTEM is a set of:

interrelated

components

working together

for a common

purpose

A Generic System
Model
(with Six
Components)
SYSTEM
processing

boundary

controls

inputs
feedback

outputs

Examples:
Automobile
Student Registration S
Others...
10

System Model Hierarch

Template
bigger
Suprasystem

System
smaller
Subsystem

Example

Water Vehicles
Cruise Ship
Staterooms
11

An INFORMATION SYSTEM is:

a type of fabricated system
used by one or more persons
to help them accomplish some task or
assignment they have
An Information System:
includes the 3 aspects of a
system
supports policies &
procedures
has three additional
components - data, people,

data

people

procedures
12

An AUTOMATED INFORMATION SYSTEM IS:

a type of fabricated system
used by one or more persons
to help them accomplish some task
or assignment they have
utilizes hardware and software in
addition to data, people, procedures
plus all the aspects of a system

data

people

software procedure
hardware
13

An AUTOMATED INFORMATION
SYSTEM has three basic
characteristics to consider:
DATA

FUNCTIONS

BEHAVIOR

DATA - input, output, or already stored

electronically

FUNCTIONS - transformations or actions taken

BEHAVIOR - the observable effects from interaction

(Plus the six system components: input, output, processing, control,

14

Systems Analysis and Design is

the process people use to create
(automated) information systems

data

SA&D

software

people

procedure

hardware
15

 The

people who do SYSTEMS ANALYSIS and DESIGN

produce information systems that are:

used internally within the organization
sold commercially via mail/web order or retail

store
imbedded in products

16

What makes Systems Analysis

and Design a difficult activity?

Initially, problem domains (areas) tend to have poorly defined

BOUNDARIES

Problem domain SOLUTIONS are artificial

Problem domains are DYNAMIC

Problem domain solutions usually require INTERDISCIPLINARY

knowledge and skills

Systems Analysts KNOWLEDGEBASE is continually expanding

Systems Analysis and Design is a highly COGNITIVE activity

Working with PEOPLE

17

Systems Analysts interactions with people during Systems

Steering
Committee*

Users*

Managers*

SYSTEMS
ANALYST

Database
Administrators

* = Stakeholders

Vendors

Programmers
& Tech. Staf

Systems Analyst
may be acting as
a Project Manager
for some of these
interactions.
18

What does a Systems Analyst

Studies the problems and needs of
an organization looking for
improvement opportunities for:

increasing revenue/profit

decreasing costs

improving quality of service

19

What is a Systems Analyst respon

Effective and efficient:

CAPTURE of input data

PROCESSING & STORAGE of data

DELIVERY of timely and accurate

information
20

Skills and Competencie

Environments/Tools
of a Systems Analyst
Methodologies

Methods & Techniques

Concepts & Principles
Problem
Solving &
People
Skills

PLUS:
Functional Business
Knowledge
Verbal & written
communication skills
Systems Analysis and Design
21
work experience

General Model of Information Systems Development (Partnership)

Stakeholder
Requirements
(1)

Continued
Involvement
(5)

Information
System (6)

Requirements Specification
Analysis
(3)

Problem
Definition
Skills (2)

Design
and
Implementation

Problem
Solution
Skills (4)
Information
Technology
Staff
22

Systems Analysis and Design Activities and Deliverables

DESIGN
ANALYSIS
Activities:
Systems Planning
Feasibility Study (optional)
Requirements Determination
Conceptual Design
User Acceptance
Prototyping (optional)
Deliverables:
Requirements Specification
Prototype (optional)

Activities:
Physical Design
Prototyping (optional)
Software Construction/Purchase
User Documentation - Deliverable
Testing
Training
User Acceptance
Conversion
Implementing the system
Deliverable:
Information System

Two (2) additional on-going activities:

Project Management

Project Documentation - Scaffolding

23

Systems Analysis and Design Project O

Labor intensive

Smallest team = you

Next smallest team = you and one other (user)

Average team = several systems analysts and

users

Articulation of the business problem is difficult

Users and systems analysts come in all sizes and

shapes
24

Where Do Systems Analysis

and Design Projects Come
From?

Problems - something needs to

be fixed

Opportunities - good deals

Directives - do itor else

... and are bounded by Constraints

25

Design and
Implementation

Analysis

SYSTEMS DEVELOPMENT LIFE CYCLE (SD

Planning

Feasibility Study (optional)

Requirements Determination

Conceptual Design

Physical Design

Construction and/or Purchase (prototype)

Training

Conversion - old to new

Implementation

Evolution - maintenance & enhancements

26

Sequential or Traditional SDLC

Begin

End

1. Planning for an information system

2. Feasibility Study (optional)
3. Requirements Determination (gathering)
4. Conceptual design
5. Physical design and/or purchase and/or prototyping
6. Conversion from current system to new/changed system
7. Training
8. Implementation
9. Evolution for enhancements and maintenance

Waterfall or Staircase
SDLC
Begin
Planning
Feasibility Study

Requirements Determination
Conceptual Design
Physical Design
Conversion
Training
Implementation
Evolution
End
27

Iterative SDLC

Spiral SDLC
SDLC Activities

Planning
Feasibility Study
Requirements Determination
Conceptual Design
Physical Design
Conversion
Training
Implementation
Evolution

Risk Analysis

Verification/Test

28

Boehm, 1988

29

Principles to Guide Systems Analysis

The system is for the user

A Work Breakdown Structure should be used (ie., SDLC)

Systems analysis and design is iterative and overlapping

Information systems are capital investments for the business

Project manager may have the authority to cancel a project

Project documentation is important all along the way

Senior management approval/support is very important

30

QUITTING

TIME

31
31