System Analysis and

Design
Grading System:

The following are the course requirements:

Preliminary and Midterm Term
A. Class Standing 60%
a. Quizzes 30%
b. Recitation (boardwork, class discussion) 20%
c. Assignment/Case Study 10%
B. Major Examination 40%
TOTAL 100%

Final Term
A. Individual Project 30%
B. Group Project 70%
TOTAL 100%
Programming languages
are not at a high enough
level of abstraction to
facilitate discussions about
design.

- Martin Fowler (Software Designer)

Abstraction layers hide the details of
other layers from the working layer

Patrons Consume Food

Servers Serve Food Models

Chefs Prepare Food Pseudo-code

Restaurant Purchases Raw

Code
Ingredients
 Types of Models

Entity Relationship Diagrams UML

Chens Notation Class Diagram Data Flow Diagram
Use Case Diagram Context-Level
IDEF 1X Notation Sequence Diagram Higher Levels
Crows Foot Notation Activity Diagram
Types of Models
Entity Relationship Diagrams
Chens Notation
IDEF 1X Notation
Crows Foot Notation
Chens Notation
Relationships
Entities
Example:
Students

Attributes
Example:
Phone number
Address
Age
IDEF1X Notation
Entity Name

Attributes
Crows Foot Notation
Relationships

Entity Name

Attributes
UML
Class Diagram
Use Case Diagram
Sequence Diagram
Activity Diagram
Data Flow Diagram
Context-Level
Higher Levels

External Entity

Process

Data Flow Direction

Data Store
Data Flow Diagram
Context-Level
Single Process
Higher Levels
Multiple Process
 The Need
Installing a system without proper planning
leads to great user dissatisfaction and
frequently causes the system to fall into disuse.
-Fowler, M. UML Distilled, 3ed
 System Analysis and Design

is an interrelated set of components that

function together to achieve an outcome.

The term system is derived form the Greek

word systema, which means an organized
relationship among functioning units or
components.

A collection of components that work

together to realize some objective forms a
system.
 System Analysis and Design

Three major components in every system: Input, Processing

and Output

INPUT PROCESS OUTPUT

FEEDBACK
 Systems
Can Be Composed of Subsystems

System

Subsys A Subsys B Elemental

Part C

Subsys A-1 SubsysB-1

Subsys A-2 SubsysB-2

Subsys A-3 Elemental

part B1
 What is subsystem?
A subsystem is simply a system within a
system.
Automobile is a system composed of
subsystems:
Engine system
Body system
Frame system
Each of these subsystem is composed of
sub-sub --systems.
Engine system: carburetor system, generator
system, fuel system, and so son
 System Analysis and Design

Elements of a System
Purpose - the reason it exists or the
reference point for measuring its success.

Subsystems - parts or elements which

perform specified tasks that are
compatible with the goals of the larger
system which these are parts.
 System Analysis and Design

Environment - the people, facilities, rules,

policies, and regulations that surround a
system.
Boundary - the perimeter or line of
demarcation, between a system and the
environment.
Connections - transmit the flow of
material and information that coordinate
the systems components.
Control Mechanisms - rules and logic that
govern the individual subsystems and the
interactions among them
 System Analysis and Design

Classification of System
Physical or Abstract Systems
Physical systems are tangible entities that
may be static or dynamic in operation.
Example : system-computer centre
Desks and chairs are the static parts
Programs, data, and applications can change
according to the user's needs.

Abstract systems are conceptual or non-

physical entities.
Example: formulas, representation or model
 System Analysis and Design
Classification of System
Open or Closed Systems

An open system has many interfaces with its

environment.

A closed system is isolated from environmental

influences.

Man-Made Information Systems

Information system is the basis for interaction between the

user and the analyst.

Main purpose-manage data for a particular organization.

 System Analysis and Design

Characteristics of a System
Organization - Organization implies
structure and order.
Example:
Hierarchical organization in a company.
Computer system: organization of various
components like input devices, output devices,
CPU and storage devices
 System Analysis and Design

Characteristics of a System
Interaction - Interaction refers to the manner
in which each component functions with other
components of the system.

Example: the main memory holds the data that

has to be operated by the ALU.

Interdependence - Interdependence means

that parts of the organization or computer
system depend on one another.
 System Analysis and Design

Characteristics of a System
Interdependence - Interdependence means
that parts of the organization or computer
system depend on one another.

Component linkage
Component dependence
Characteristics of a System System Analysis and Design

Integration- refers to the holism of systems.

- How subsystems are tied together to achieve
the system objective

Central Objective - Objectives may be real

objectives.
-Should be known in early phases of analysis
 Stakeholders: Players in the
Systems Game
A stakeholder is any person who has an
interest in an existing or new
information system. Stakeholders can
be technical or nontechnical workers.
Stakeholders Classification
For information systems, the stakeholders can
be classified as:
IS manager
Systems analysts in systems development
Programmers in systems development
End user in systems development
Supporting End user in development
Business managers in systems development
Other IS managers/Technicians in system
development
 IS Manager in Systems
Development
The manager of an IS department may have a direct role in
the systems development process if the organization is
small.
IS mangers are more involved in allocating resources to and
overseeing approved system development projects rather
than in the actual project development process.
There are several IS managers in any medium to large IS
department.
The manger of an entire IS department may have the title Chief
Information Officer and may report to the president or chairman of
the firm.
Each division of the IS department will also have a manager
Director of IS development, IS operation manger, IS programmer
director, etc.
Who are the System Analyst?

Consultant
Supporting Expert
Agent of Change
Problem Solver
Communicator
 Systems Analysts
Systems analysts are the key individuals in the
systems development process.
A systems analyst studies the problems and needs of
an organization to determine how people, data,
processes, communications, and information
technology can best accomplish improvements for
the business.
The organizational role most responsible for the
analysis and design of information systems.
 Skills of a Successful
Systems Analyst
Analytical skills
Understanding of organizations.
Problem solving skills
System thinking
Ability to see organizations and information
systems as systems
Technical skills
Understanding of potential and limitations
of technology.
1.31
 Skills of a successful
systems analyst
Managerial skills
Ability to manage projects, resources, risk and
change
Interpersonal skills
Effective written and oral communication
skills
Help you work with end user as well as other
system analysts and programmers
1.32
 The analyst is responsible
for:
The efficient capture of data from its
business source,
The flow of that data to the computer,
The processing and storage of that data by
the computer, and
The flow of useful and timely information
back to the business and its people.
 System Analysis and Design

a self-contained
system within a
larger system
 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!
35
 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.
System Analysis and Design
(SAD)
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
Definition of SAD:
The complex organizational process whereby
computer-based information systems are
developed and maintained.
Business Process
Business Drivers for an
Information Systems
Globalization of the Economy
Electronic Commerce and Business
Security and Privacy
Collaboration and Partnership
Knowledge Asset and Management
Continuous Improvement and Total
Quality Management
Business Process Redesign
Globalization of the Economy
Information systems and applications
must be internationalized.
Most information systems ultimately
require information consolidation for
performance analysis and decision
making
Electronic Commerce and Business

Basic types of e-commerce and e-business

Marketing of corporate image, products
and services
Business-to-consumer (B2C)
Business-to-business (B2B)
E-commerce
E-business
the buying and selling of goods the use of the Internet to
and services by using the conduct and support day to day
Internet business activities
Security and Privacy

How will the business continue in the

event of a breach of disaster ?
How can the business protects its digital
assets from the outside threats?
Collaboration and Partnership

Businesses interoperate their information

system with one another
Knowledge Asset Management

knowledge
data
information
Continuous Improvement and Total
Quality Management
Business Processes
Total Quality Management
Business Process Redesign

Involves making substantive changes to

business process across a larger system
Implementation
built it
buy it
Tools of the System
Analyst
 Stages of the Cycle
1. Problem definition
2. Feasibility study
3. Analysis
4. Design
5. Implementation
6. Maintenance
 System Analysis and Design

Systems Development Life Cycle

The systems development life cycle (SDLC)

is a conceptual model that describes the
phases involved in an information system
development project, from an initial
feasibility study through maintenance of
the completed application.
Why do we need the SDLC?
The software crisis of the late 60s and early
70s
Systems were delivered years late
They were over budget
Unreliable
Difficult to maintain
Did not do what was required
Planning with Models
SE projects usually live with a fixed financial
budget. (An exception is maintainance?)

Additionally, time-to-market places a strong

time constraint.

There will be other project constraints such

as staff.
 designers
programmers managers

money staff

Project constraints

Computing
resources time

Examples of Project Constraints

It provides a fixed generic framework that
can be tailored to a specific project.
Project specific parameters will include:
Size; (person-years)
Budget;
Duration.

project plan = lifecycle model + project parameters

There are hundreds of different lifecycle models
to choose from, e.g:
waterfall,
code-and-fix
spiral
rapid prototyping
unified process (UP)
agile methods, extreme programming (XP)
COTS
 What does the SDLC do?
Systems Development Life Cycle was an
attempt to establish a structured approach
to systems development.
For management, each stage of the life
cycle was a milestone with an associated
date and set of deliverables.
Project planning is the art of scheduling the
necessary activities, in time, space and across
staff in order to optimise:
It is impossible to measure rate of progress
except with reference to a plan.
 Deliverables
Each stage has an associated set of
deliverables
Sets of documents produced at each stage
in the life cycle
Project Visibility
Unlike other engineers
(e.g. civil, electronic, chemical etc.)
software engineers do not produce anything
physical.
It is inherently difficult to monitor an SE
project due to lack of visibility.
1. Problem Definition
The problem definition forms the basis of
the problems and requirements list.
It records all problems and requirements
mentioned by clients in interviews, or
which are subsequently discovered during
analysis of the system.
 Problem Definition Report
the purpose
To provide a written statement of the user's
current problems and requirements; to get
agreement with the user.
To ensure that the right problem is being
tackled
To force the user to become involved
To define the current state of the system
and the required end state
 Problem Definition Report
the sections
Problem
Objectives
Scope
Preliminary ideas
Recommended action
2. Feasibility Study
Feasibility study - is there a practical solution to the problem
outlined in the initial problem definition.
In particular, the feasibility study examines the technical,
financial and organisational feasibility of the project:
Can it be done?

Can we afford it?

Will the proposed new system fit in with existing

procedures?

Feasibility study report

Presented by the system developer to the user

Decision is made whether or not to proceed.

3. Analysis
Deliverable from the analysis stage is the Specification of
requirements
Logical model of the required system
States WHAT the system is to do
Says nothing about HOW to implement it
Includes
Data flow diagrams
Data dictionary
Process definitions
E/R model
Entity life histories or state diagrams
4. Design
This has two stages:
Provides several different solutions to the
problem
Selects one solution and specifies it in
detail
Design Alternative
solutions
A very cheap solution which does the job
and no more.
A medium price solution which does the
job well and is convenient for the user;
How solutions may differ
System boundaries;
Automation boundaries; could remain
manual.
Hardware
Software
Design strategies
User interface
Costs
5. Implementation
Program listings, test plans and supporting
documentation
Manual of operating procedures
Manual of clerical procedures
User manual
Hardware on which the system will run
The system must be installed at the
clients' site on their equipment
Changeover from the old to the new system
supervised
Often a hand-holding period
6. Maintenance
Starts as soon as the system is handed over
Term maintenance often euphemism for
finding and correcting errors
True maintenance is modifying the system
to meet evolving client requirements
System developer must start again at the
beginning of the cycle
Summary
Stage Content Deliverable

1. Problem Definition What is the problem? Problem Definition Report - statement of

problems, scope and objectives
objectives of new system

2. Feasibility Study Is there a feasible Feasibility Study Report - rough cost benefit
solution quick look analysis
ahead to see if you can - system scope and objectives cost benefit
do something about the analysis
problem

3. Analysis What must be done to Specification of Requirements logical

solve the problem model of required system

4. Design How should the problem Technical Design Specification includes program
be solved specifications, hardware specifications, cost
estimates and an implementation schedule

5. Implementation Do it Working system, includes program listings and

documentation, test plan, hardware, operating
procedures, clerical procedures

6. Maintenance Modify system as Working system - Operational system, modified

necessary and documented as required