SYSTEMS

ANALYSIS AND
DESIGN

By Dr. Cheruiyot w.k, PhD

JKUAT-ICSIT
Computing Department

1
 Systems Analysis and
Design is the process
people use to create
(automated) information
systems

Systems
Analysis Information
& Design System

2
 Is there an “official” name?

Systems Analysis and Design!

Software Engineering!
Information Systems Engineering

Systems Engineering!
Information Systems Development

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 Analysis Design and Completed

ImplementationInformation
System
Time
5
 SYSTEMS ANALYSIS AND
DESIGN: A Complete (Formal)
Perspective

 Systems Planning
 Systems Analysis Planning

 Systems Design Evolution Analysis

 Systems
Implementation Design
Implementation
 Systems Evolution

6
 System
Natural Fabricated

Information Others
Systems

Automated Others
Information
Systems
7
 ess “problems” come in all sizes and sha
ness sh
 Name & Address Book
 CD Collection
 Course Registration
 Reservations
 Student Grades
 Payroll
 ATM machine & Banking in General
 Check-Out Counters at Retail Stores

Examples: Order Fulfillment - Mail or Web Ordering



 Manufacturing
 Securities Portfolio Management
 Space Shuttle Flight
 Election Results
 Video Games (Arcade and Home)

8
 System

A SYSTEM is a set of:

 interrelated
components
 working together
 for a common
purpose

9
 A Generic System
Model
(with Six
Components)
SYSTEM
processing

boundary controls
inputs
feedback outputs

Examples:
• Automobile
• Student Registration System
• Others...
10
System Model Hierarchy
Template Example

Suprasystem
“bigger” Water Vehicles

System Cruise Ship

Subsystem
“smaller” 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 data people
• supports policies &
procedures
• has three additional procedures
components - data, people,
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

data people
 …plus all the aspects of a system

software procedures

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

he six system components: input, output, processing, control, feedback and boun
14
 Systems Analysis and Design is
the process people use to create
(automated) information systems

data people

SA&D
software procedures

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 Analyst’s KNOWLEDGEBASE is continually expanding

 Systems Analysis and Design is a highly COGNITIVE activity

 Working with PEOPLE

17
ms Analyst’s interactions with people during Systems Analysis &

Steering
Users* Committee*

Managers* SYSTEMS
ANALYST Vendors

Database Programmers
Systems Analyst
Administrators & Tech. Staff
may be acting as
a Project Manager
for some of these
interactions.
* = Stakeholders
18
What does a Systems Analyst do?

Studies the problems and needs of

an organization looking for

improvement opportunities for:

 increasing revenue/profit

 decreasing costs

 improving quality of service 19

hat is a Systems Analyst responsible fo

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
work experience
21
General Model of Information Systems Development (“Partnership”)

Stakeholder

Requirements Information
(1) Continued System (6)
Involvement
(5)

Requirements Specification Design

Analysis (3) and
Implementation

Problem
Problem
Definition
Solution
Skills (2)
Skills (4)

Information
Technology
Staff
22
Systems Analysis and Design Activities and Deliverables

DESIGN
ANALYSIS Activities:
Activities: • Physical Design
• Prototyping (optional)
• Systems Planning • Software Construction/Purchase
• Feasibility Study (optional) • User Documentation - “Deliverable”
• Requirements Determination • Testing
• Conceptual Design • Training
• User Acceptance • User Acceptance
• Prototyping (optional) • Conversion
Deliverables: • Implementing the system
• Requirements Specification Deliverable:
• Prototype (optional) • Information System

Two (2) additional on-going activities:

• Project Management • Project Documentation - “Scaffolding”
23
 ms Analysis and Design Project Observa
ems
 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 it…or else…”

... and are bounded by Constraints

25
YSTEMS DEVELOPMENT LIFE CYCLE (SDLC
 Planning
Analysis

 Feasibility Study (optional)

 Requirements Determination
 Conceptual Design
 Physical Design
 Construction and/or Purchase
Implementation

(prototype)
Design and

 Training
 Conversion - old to new
 Implementation
 Evolution - maintenance &
enhancements
26
 Sequential or Traditional SDLC
“Begin” 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
“End” 9. Evolution for enhancements and maintenance

Waterfall or Staircase
SDLC
“Begin”
Planning
Feasibility Study
Requirements Determination
Conceptual Design
Physical Design
Conversion
Training
Implementation
“End” Evolution

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 & Desig

 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