BIC 21003

Systems Analysis and Design

Session 2016/2017

Introduction
Lecturer
RUHAYA BINTI AB. AZIZ(Coordinator)
Contact: ruhaya@uthm.edu.my ,No 17, Aras 3.

Phone: 07 453 3765

HANNANI BT AMAN
Contact: hanani@uthm.edu.my, No 10, Aras 2.

Phone: 07 453 3710

Lecture Plan: RPP04

2

Chapter 1 Outline
Software and System Development
Skill and Role in Group Work Development

Project: System analyst.

Information System
The Systems Development Life Cycle (SDLC).
Strategic Plan

Copyright 2011 John Wiley & Sons, Inc.

1-3

Scenario
A real estate group in the federal government

cosponsored a data warehouse with an IT

department.
A formal proposal was written by IT in which
were estimated to be
at 8months,
$800, 000.

IT department proceeded with the project

before hearing whether the proposal was ever

accepted.

The project actually lasted 2 years because

requirement gathering took 9 months instead

of one an a half,
The planned user base grew from 200 to
2500,
The approval process to buy technology for
project took a year.
3 weeks prior to technical delivery, the IT
Director cancelled the project.
This failed endeavor cost the organization
$2.5mil.

INTRODUCTION
The

systems development life cycle

(SDLC) is the process of determining how
an information system (IS) can support
business needs, designing the system,
building it, and delivering it to users.
The key person in the SDLC is the systems
analyst, who analyzes the business
situation, identifies the opportunities for
improvements, and designs an IS to
implement the improvements.
Copyright 2011 John Wiley & Sons, Inc.

1-6

System development
System is defined as:
-a set of interrelated components that
produces specific results.
-a set of interrelated components that
working together to achieve certain objective.

Information System
A grouping of (people, objects, processes)

that provides information about the

organisation and its environment
This information should be useful to
members and clients of that organisation
Environment -important elements outside
the organisation. For example the firms
competitors as well as it customers.
Organisation -bank, business, hospital,
university, and any other group of people
trying to achieve a common objective or
working together

The Components:
Hardware: Consists of everything in the physical

layer of the information system

Software: refers to programs that control the
hardware and produce the desired information or
results.
Data: the raw material that an information system
transforms into useful information
Process: describe the tasks and business functions
that users, managers, and IT staff members
perform to achieve specific results.
People: any stakeholders that involve with the
system including users, system analyst,
programmers, network administrators and other IT
staff members.

Types of Information
Systems
An organization consists of many people

with different interests, specialties, and

levels.
How a single information system can
provide all the information that an
organization needs?
There is no such single information system.
An organization should have different info
systems for different interests, specialties,
and levels.
10

Decision-Making Levels of an
Organization

11

Decision-Making Levels of an
Organization
Executive level (top)
Long-term decisions
Unstructured decisions
Managerial level (middle)
Decisions covering weeks and months
Semistructured decisions
Operational level (bottom)
Day-to-day decisions
Structured decisions

12

sic systems model for all Info. Systems

13

Type of Information System

Transaction processing system
a system to capture and process the detailed information
necessary to update data on the fundamental operations
of an Management Information System
a set of systems which helps management at different
levels to take better decisions by providing the necessary
information to managers. Does not provide decision.
Decision Support System
a computer-basedinformation systemthat supports

business or organizational decision-makingactivities.

Offers decision.

Expert System
a computer system that emulates the decision-making
ability of a human expert
14

Role in Software Development

project
Project Manager
Requirements Analyst
System Analyst
Network administrator
Programmer
User
Etc

THE SYSTEMS ANALYST

The systems analyst plays a key role in IS

development projects.
The systems analyst works closely with all
project team members so that the team
develops the right system in an effective way.
Systems analysts must understand how to
apply technology in order to solve problems.
Systems analysts may serve as change
agents who identify organizational
improvement needed, design systems to
implement those changes, and train and
motivate others to use the systems.
Copyright 2011 John Wiley & Sons, Inc.

1-16

Systems Analyst Skills

Technical Must understand the technical

environment, technical foundation, and

technical solution.
Business Must understand how IT can be
applied to business situations.
Analytical Must be problem solvers.

Copyright 2011 John Wiley & Sons, Inc.

1-17

(contd)

Interpersonal Need to communicate

effectively.
Management Need to manage
people and to manage pressure and
risks.
Ethical - Must deal fairly, honestly, and
ethically with other project members,
managers, and systems users.
Copyright 2011 John Wiley & Sons, Inc.

1-18

Systems Analyst Roles

Business analyst - Focuses on the IS

issues surrounding the system.

Systems analyst - Focuses on the
business issues surrounding the system.
Infrastructure analyst - Focuses on
technical issues
Change management analyst - Focuses
on the people and management issues
surrounding the system installation.
Project manager - Ensures that the
project is completed on time and within
budget, and that the system delivers the
expected vale to the organization.
Copyright 2011 John Wiley & Sons, Inc.

1-19

Career Paths for Systems Analysts

Copyright 2011 John Wiley & Sons, Inc.

1-20

THE SYSTEMS DEVELOPMENT LIFE

CYCLE (SDLC)

Copyright 2011 John Wiley & Sons, Inc.

1-21

(contd)
The SDLC is composed of four fundamental phases:

Planning
Analysis
Design
Implementation
Each of the phases is composed of steps, which rely

on techniques that produce deliverables (specific

documents that explain various elements of the
system).
Copyright 2011 John Wiley & Sons, Inc.

1-22

Planning
This phase is the fundamental process of

understanding why an information system

should be built, and determining how the
project team will go about building it.

Copyright 2011 John Wiley & Sons, Inc.

1-23

The planning phase has two steps:

1. During project initiation, the systems
business value to the organization is
identified (How will it lower costs or
increase revenues?).
2. During project management, the
project manager creates a work plan,
staffs the project, and puts techniques in
place to help the project team control
and direct the project through the entire
SDLC.
Copyright 2011 John Wiley & Sons, Inc.

1-24

Analysis
The analysis phase answers the questions of

who will use the system, what the system

will do, and where and when it will be used.
During this phase the project team

investigates any current system(s), identifies

improvement opportunities, and develops a
concept for the new system.

Copyright 2011 John Wiley & Sons, Inc.

1-25

The analysis phase has three steps:

1. Analysis strategy: This is developed to guide
the projects teams efforts. This includes a study
of the current system and its problems, and
envisioning ways to design a new system.
2. Requirements gathering: The analysis of this
information leads to the development of a
concept for a new system. This concept is used
to build a set of analysis models.
3. System proposal: The proposal is presented to
the project sponsor and other key individuals
who decide whether the project should continue
to move forward.
Copyright 2011 John Wiley & Sons, Inc.

1-26

Design
The design phase decides how the system

will operate, in terms of the hardware,

software, and network infrastructure; the user
interface, forms, and reports that will be used;
and the specific programs, databases, and
files that will be needed.

Copyright 2011 John Wiley & Sons, Inc.

1-27

The design phase has four steps:

1. Design Strategy: This clarifies whether the
system will be developed by the company or
outside the company.
2. Architecture Design: This describes the
hardware, software, and network
infrastructure that will be used.
3. Database and File Specifications: These
documents define what and where the data
will be stored.
4. Program Design: Defines what programs
need to be written and what they will do.
Copyright 2011 John Wiley & Sons, Inc.

1-28

Implementation
During the implementation phase, the system

is either developed or purchased (in the case

of packaged software) and installed.
This phase is usually the longest and most
expensive part of the process.

Copyright 2011 John Wiley & Sons, Inc.

1-29

The implementation phase has three

steps:

1. System Construction: The

system is built and tested to make
sure it performs as designed.
2. Installation: The old system is
turned off and the new one is
turned on.
3. Support Plan: Includes a postimplementation review as well as a
systematic way for identifying
changes needed for the system.
Copyright 2011 John Wiley & Sons, Inc.

1-30

Analogy of Building A
House
1. Basic Idea given
2. Simple Drawing , show to customer, refined

until both agrees.

3. A Blueprints, show details of a house.
4. House is built follow the blueprint with some
changes and decisions by customer.
.Can you map this step with Creating A

System???

SUMMARY
The Systems Analyst is the key person in the

development of information systems.

The Systems Development Lifecycle
consists of four stages: Planning, Analysis,
Design, and Implementation.

Copyright 2011 John Wiley & Sons, Inc.

1-32

Copyright 2011 John Wiley & Sons, Inc.

All rights reserved. Reproduction or translation of
this work beyond that permitted in Section 117 of
the 1976 United States Copyright Act without the
express written permission of the copyright owner is
unlawful. Request for further information should be
addressed to the Permissions Department, John
Wiley & Sons, Inc. The purchaser may make backup copies for his/her own use only and not for
redistribution or resale. The Publisher assumes no
responsibility for errors, omissions, or damages,
caused by the use of these programs or from the
use of the information contained herein.
Copyright 2011 John Wiley & Sons, Inc.

1-33