Systems Analysis & Design

2019-2010
Lecture 1

Mrs. Arazu Sabah

Email: [email protected]
Text book: Alan Dennis, Barbara Wixom, and
David Tegarden: Systems Analysis & Design
(2005)

Slide 1
Key Ideas
The systems analyst is a key person
analyzing the business, identifying
opportunities for improvement, and
designing information systems to
implement these ideas.
It is important to understand and
develop through practice the skills
needed to successfully design and
implement new information systems.

Slide 2
Key Ideas
Many failed systems were
abandoned because analysts tried
to build wonderful systems without
understanding the organization.
The primarily goal is to create value
for the organization.
Quality is satisfaction of
requirements, not ‘goodness’
goodness
Slide 3
Why Systems Analysis and
Design are beneficial?

Systems are created to solve
problems.


Think of the systems approach as
an organized way of dealing with a
problem.

System Analysis and Design, mainly
deals with the software
development activities.
Defining A System


This term is derived from a Greek word systema
which means an organized relationship among
functioning units and components.


A collection of components that work together to
realize some objective forms a system.

Basically there are three major components in every
system

Input

processing

and output.
 Defining A System
count:

Systems Analysis: understanding and
specifying in detail what an information
system should do


System Design: specifying in detail how
the parts of an information system should be
implemented
 Types of Systems

1.Physical or Abstract System(natural

systems)
› Physical system: tangible entities
› static or dynamic in nature.
› Example : system-computer Centre

Desks and chairs are the static parts.

Programs, data, and applications can change according to the
user's needs is dynamic parts.

› Abstract systems are conceptual. These are not

physical entities. They may be formulas,
representation or model of a real system.
2.Open System

Majority of systems are open systems

› open system has many interfaces with its
environment
› can also adapt to changing environmental
conditions
› can receive inputs from, and delivers output to
the outside of system

3.Closed systems: Systems that don't

interact with their environment. Closed
systems exist in concept only.
THE SYSTEMS
DEVELOPMENT LIFE
CYCLE (SDLC)

Slide 9
Major Attributes of the
Lifecycle
The project
Moves systematically through phases
where each phase has a standard set
of outputs
Produces project deliverables
Uses deliverables in implementation
Results in actual information system
Uses gradual refinement

Slide 10
4 Main Project Phases
Planning
Why build the system?
Analysis
What, when, where will the system be?
Design
How will the system work?
Implementation
System construction & delivery
Slide 11
Planning
Identifying business value (is it
worth doing?)
Analyze feasibility (is it
possible?)
Develop work plan (when?)
Staff the project (who?)
Control and direct project
Slide 12
Analysis
Analysis (what do we want?
Who will use the system?)
Information gathering
Process modelling (what
happens?)
Data modelling (… and to
what?)
Slide 13
Design
Design strategy
Architectural design
Interface design (HCI)
Database and file design
Program design (what will the
programs do?)

Slide 14
Implementation
Construction (Programming,
testing, validation etc)
Installation (including
migration, change
management)

Slide 15
Processes and
Deliverables
Process Product

Planning Project Plan

Analysis System Proposal

Design System
Specification

Implementation New System and

Maintenance Plan

Slide 16
SYSTEM DEVELOPMENT
Methodologies

Slide 17
What Is a Methodology?

A formalized approach or series

of steps
Writing code without a well-
thought-out system request
may work for small programs,
but rarely works for large ones.

Slide 18
System Development
Methodologies
1. Structured Design
2. Rapid Application
Development
3. Agile Development

Slide 19
1. STRUCTURED DESIGN
Projects move methodically
from one to the next step
Generally, a step is finished
before the next one begins

Slide 20
Waterfall Development
Method

Slide 21
Pros and Cons (advantages and
disadvantages)of the Waterfall
Method

Pros Cons

Identifies systems Design must be

requirements long specified on paper
before programming before programming
begins begins

Long time between

system proposal and
delivery of new
system

Slide 22
Parallel Development

Slide 23
2. RAPID APPLICATION
DEVELOPMENT (RAD)
Critical elements
CASE tools
JAD sessions
Fourth generation/visualization
programming languages
Code generators

Slide 24
Rapid Application
Development Categories
Phased development
 a series of versions, later combined
Prototyping
 System prototyping
Throw-away prototyping
 Design prototyping

Slide 25
Phased Development

Slide 26
How Prototyping Works

Slide 27
Throwaway Prototyping

Slide 28
3. AGILE DEVELOPMENT
Simple iterative application
development

Extreme programming (XP)

Slide 29
Extreme Programming (XP)

Key principles
 Continuous testing
 Simple coding by pairs of developers
 Close interactions with end users
Testing & Efficient Coding Practices
 Integrative testing environment
Requires…
 Stable and experienced teams
 Small groups of developers (<=10)
Slide 30
Extreme Programming (XP)

Slide 31
Selecting the Appropriate
Methodology
Clarity of User Requirements
Familiarity with the Technology
System Complexity
System Reliability
Length of Time Schedules
Time Schedule Visibility

Slide 32
Criteria for Selecting a
Methodology

Slide 33
Project Team Roles and
Skills
Create your team

Slide 34
Project Team Roles
Business analyst (business value)
Systems analyst (IS issues)
Infrastructure analyst (technical issues –
how the system will interact with the
organization’s hardware, software,
networks, databases)
Change management analyst (people and
management issues)
Project manager (budget, time, planning,
managing)
Slide 35
Summary
The Systems Development Life Cycle (SDLC)
consists of four stages: Planning, Analysis,
Design, and Implementation
The Major Development Methodologies:
Structured Design
 Waterfall Method
 Parallel Development
Rapid Application Development (RAD)
 Phased Development
 Prototyping (system prototyping)
 Throwaway Prototyping (design prototyping)
Agile development
 eXtreme Programming
Project Team Roles
Slide 36
Summary -- Part 2
There are five major team roles:
business analyst
systems analyst
infrastructure analyst
change management analyst
project manager.

Slide 37
 Assignment 1#
What are the phases of systems development briefly and provide an example
diagram of any system.

Assignment 2#
On what bases you are going to create your own group.

Assignment 3#
So far what you have learned from this module(SYSTEMS ANALYSIS &
DESIGN) use your lecture, books or net Pdfs to design your idea and select a
topic for yourself and write about it.

Slide 38