SYSTEMS ANALYSIS AND DESIGN

What is ahead of us?

Terminologies

Creating a System Design

Components of an Information System

Categories of Companies

Characteristics of Information System

SYSTEMS ANALYSIS AND DESIGN

What is ahead of us?

Characteristics of a System

Types of System

Kinds of System

Organizational Structure

Systems Development Techniques and Tools

Systems Development Life Cycle

Next
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Terminologies:
INFORMATION TECHNOLOGY(IT)
It is a combination of hardware, software and
telecommunications systems that support business
operations, improve productivity and help managers make
decisions.
It is any system designed to gather, process, or
distribute information.

SYSTEM
It is an inter-related set of components with an identifiable
boundary, working together to produce a specific result.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Terminologies:
SYSTEMS ANALYSIS AND DESIGN
It is a complex organizational process whereby a computer-
based information systems are developed and maintained.

ORGANIZATION
It consists of the whole enterprise, specific departments or
individual workgroups.

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

So how are you going to create a system design?

BUSINESS PROFILE
It is a company’s overall functions, processes, organizations,
products, services, customers, suppliers, competitors,
constraints and future direction.

BUSINESS MODEL
Graphically represents business functions that consists of
business processes, such as sales, accounting, and
purchasing, which perform specific tasks.
BUSINESS PROCESS REENGINEERING
It is when the company attempts to simplify operations or
reduce costs.
Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Information System Components

People
Hardwa
re
Process

Softwar
e Data
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Information System Components

Where:

HARDWARE
Refers to the physical layer of the information system.

♠ Computers ♠
Scanners
♠ Networks ♠ Digital Capture
Devices
♠ ♠ Technology-
Communications based
Equipment infrastructure
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Information System Components

SOFTWARE
Refers to programs and instructions.
TWO TYPES OF SOFTWARE:
SYSTEM SOFTWARE – controls the computer and includes
the operating system, device drivers that communicate with
hardware, and utilities that handle tasks such as converting
data into different form, virus protection and creating
backups.

APPLICATION SOFTWARE – consists of programs that

support users and enable companies to carry out business
functions.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

Information System Components

DATA
An information system transforms data into useful information.
PROCESS
Sometimes called as procedures, describe the tasks that
users, managers, and IT staff members perform.
PEOPLE
Provide valuable information to managers and users within
and outside the company.

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

CATEGORIES OF COMPANIES

PRODUCTION-ORIENTED
Primarily manufacture and sell products, such as the microchips.

SERVICE-ORIENTED
Primarily offer information and services, or sell goods
produced by others.

INTERNET-DEPENDENT FIRM
Often called as dot-com companies.
Primarily transacts their business on a commercial website.
Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

CHARACTERISTICS OF IS

ϑ INTERFACE

ϑ BOUNDARY
SYSTEM BOUNDARY – indicates where one system ends
and another system begins.

ϑ SPECIALIZED BUSINESS NEEDS

ϑ SIZE, GROWTH FORECAST OF THE COMPANY

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

CHARACTERISTICS OF A SYSTEM
COMPONENTS
It is an irreducible part or aggregation of parts that make
up a system, also called a subsystem.
INTER-RELATED COMPONENTS
Dependence of one subsystem on one or more subsystem.
BOUNDARY
It is the line that marks the inside and outside of a system and
which sets off the system from its environment.

PURPOSE
It is the overall goal or function of a system.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

CHARACTERISTICS OF A SYSTEM

OUTPUT
It is whatever a system returns to its environment in
order to fulfill its purpose.

CONSTRAINTS
It is a limit to what a system can accomplish.

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

TYPES OF A SYSTEM

OPEN SYSTEM
Interacts freely with their environment, taking in input and
returning output.

CLOSED SYSTEM
It does not interact with the environment.

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

KINDS OF SYSTEMS
TRANSACTION PROCESSING SYSTEM(TPS)
It is a computerized information systems developed to
process large amounts of data for routine business
transaction.
OFFICE AUTOMATION SYSTEMS(OAS)
It supports data workers who do not usually create new
knowledge but rather use information for analysis to transform
data or manipulate it in some way and then share it or formally
disseminate it throughout the organization.
KNOWLEDGE WORK SYSTEMS
It supports professional workers such as scientists, engineers,
and doctors by aiding them to create new knowledge and
contribute it to their organization or to the society at large.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

KINDS OF SYSTEMS
MANAGEMENT INFORMATION SYSTEM
Computerized information systems that work because of the
purposeful interaction between people and computers. By
requiring people, software and hardware to function in
concert. MIS support a broader spectrum on organizational
tasks than transaction processing systems, including
decision analysis and decision making.
DECISION SUPPORT SYSTEM
It is a higher-level class of computerized information
systems. It is similar to the traditional management
information systems in that they both depend on a database
as a source of data.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

KINDS OF SYSTEMS

EXPERT SYSTEM
It is also called knowledge-based system. It captures and
uses knowledge of an expert for solving a particular problem
experienced in an organization.

Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

ORGANIZATIONAL STRUCTURE
TOP MANAGEMENT MIDDLE MANAGEMENT
Develops long-range Focuses their goals on a
plans, called strategic shorter time frame and
plans that define the develops plans to achieve
company’s overall business objectives in a
mission and goals. process called tactical
Usually answers the planning.
They delegate authority
question HOW.
and responsibility to team
Strategic Planning
leaders or supervisors
focuses on issues that
and then provide
affect the company’s
direction, necessary
future survival and
resources, and feedback
growth, including long-
on performance as tasks
term IT plans.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

ORGANIZATIONAL STRUCTURE

LOWER MANAGEMENT OPERATIONAL EMPLOYEES

Supervisors and team Primarily use TP systems to
leaders oversee enter and receive data
operational employees they need to perform their
and carry out day-to- jobs.
day operational plans. Empowerment gives
They coordinate employees more
operational tasks, responsibility and
make necessary accountability.
decisions, and ensure
that the right tools,
materials and trainings Home
are available.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEM DEVELOPMENT TECHNIQUES AND TOOLS

MODELING
It produces a graphical representation of a
concept or process that systems developers can
analyze, test and modify.
⇒BUSINESS MODEL/REQUIREMENTS
MODEL – describes business functions that an information system
must support.

⇒ DATA MODEL – describes data structures and design.

⇒ NETWORK MODEL – portrays the design and protocols
of telecommunications links.

⇒ PROCESS MODEL – describes system logic and

processes that programmers use to develop necessary code modules.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEM DEVELOPMENT TECHNIQUES AND TOOLS

PROTOTYPING
It involves the creation of an early working
version of the information system or its components.
It tests system concepts and provides an
opportunity to examine input, output, and user
interfaces before
It can serve asfinal decisions
an initial are
model made.
that is used as a
benchmark to evaluate the completed system, or the
prototype itself can develop into the final version of
the system.
Disadvantage: Important decisions might be
made too early, before business or IT issues are
thoroughly understood. If a prototype is based on
careful fact-finding and modeling techniques,
however, it can be an extremely valuable tool.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEM DEVELOPMENT TECHNIQUES AND TOOLS

COMPUTER-AIDED SYSTEMS ENGINEERING

It is a technique that uses powerful
programs, called CASE TOOLS – helps
systems analysts develop and maintain
information systems. It provides an
overall framework for systems
development and support a wide
variety of design methodologies,
including structured analysis and
object-oriented analysis.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEM DEVELOPMENT TECHNIQUES AND TOOLS

CASE CATEGORIES:

UPPER CASE TOOLS - support the

modeling process and produce a
logical design of the information
system.
LOWER CASE TOOLS – speeds the
development process by generating
source code based on the logical
model.
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEM DEVELOPMENT TECHNIQUES AND TOOLS

JOINT APPLICATION DEVELOPMENT AND RAPID

APPLICATION DEVELOPMENT

JAD – involves team-based fact-

finding techniques.

RAD – speeds the development

process by generating source code
based on the logical model. Home
 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN

SYSTEMS DEVELOPMENT LIFE CYCLE

SYSTEMS DEVELOPMENT LIFE CYCLE

INITIATION/PLANNING
To generate a high-level view of the intended
project and determine the goals of the project.
The feasibility study is sometimes used to present
the project to upper management in an attempt to
gain funding. Projects are typically evaluated in
three areas of feasibility: economical, operational,
and technical. Furthermore, it is also used as a
reference to keep the project on track and to
evaluate the progress of the MIS team. The MIS
is also a complement of those phases. This
phase is also called the analysis phase.
 SYSTEMS DEVELOPMENT LIFE CYCLE

REQUIREMENTS GATHERING AND ANALYSIS

The goal of systems analysis is to determine
where the problem is in an attempt to fix the
system. This step involves breaking down the
system in different pieces and drawing diagrams
to analyze the situation. Analyze project goals,
break down functions that need to be created, and
attempt to engage users so that definite
requirements can be defined. Requirement
Gathering sometimes require individual/team from
client as well as service provider side to get a
detailed and accurate requirements.
SYSTEMS DEVELOPMENT LIFE CYCLE

DESIGN
In systems design functions and operations are described
in detail, including screen layouts, business rules, process
diagrams and other documentation. The output of this stage
will describe the new system as a collection of modules or
subsystems.

The design stage takes as its initial input the requirements

identified in the approved requirements document. For each
requirement, a set of one or more design elements will be
produced as a result of interviews, workshops, and/or
prototype efforts.
SYSTEMS DEVELOPMENT LIFE CYCLE

DESIGN
Design elements describe the desired software
features in detail, and generally include functional
hierarchy diagrams, screen layout diagrams, tables
of business rules, business process diagrams,
pseudocode, and a complete entity-relationship
diagram with a full data dictionary. These design
elements are intended to describe the software in
sufficient detail that skilled programmers may
develop the software with minimal additional input.
SYSTEMS DEVELOPMENT LIFE CYCLE

BUILDING/CODING
Modular and subsystem programming code will
be accomplished during this stage. Unit testing
and module testing are done in this stage by the
developers. This stage is intermingled with the
next in that individual modules will need testing
before integration to the main project. Planning
in software life cycle involves setting goals,
defining targets, establishing schedules, and
estimating budgets for an entire software
project.
SYSTEMS DEVELOPMENT LIFE CYCLE

TESTING

The code is tested at various levels in

software testing. Unit, system and user
acceptance testing are often performed.
This is a grey area as many different
opinions exist as to what the stages of
testing are and how much if any iteration
occurs.
SYSTEMS DEVELOPMENT LIFE CYCLE

TYPES OF TESTING:
≈ Data Set Testing
≈ Unit Testing
≈ System Testing
≈ Integration Testing
≈ Module Testing
≈ Automation Testing
≈ User Acceptance Testing
SYSTEMS DEVELOPMENT LIFE CYCLE

OPERATIONS AND MAINTENANCE

The deployment of the system
includes changes and enhancements
before the decommissioning or sunset
of the system. Maintaining the system
is an important aspect of SDLC. As
key personnel change positions in the
organization, new changes will be
implemented, which will require
system updates.
SYSTEMS DEVELOPMENT LIFE CYCLE

SDLC Phases Related to Management Controls Home

SYSTEMS ANALYSIS AND DESIGN

What is ahead of us?

Systems Analyst

Roles of Systems Analyst

Qualities of Systems Analyst

The Interview

Search Procedure
SYSTEMS ANALYSIS AND DESIGN

SYSTEMS ANALYST – is an
individual charged with the
responsibility of accessing
business data flow
problems, planning,
modifying, evaluating, and
implementing systems. Back to Main Menu
ROLES OF SYSTEMS ANALYST

1. AS A CONSULTANT
– an analyst maybe
hired specifically to
address information
systems issues within
a business.
 ROLES OF SYSTEMS ANALYST

2. AS A SUPPORTING EXPERT – an
analyst is drawing upon professional
expertise concerning computer
hardware and software and their
uses in the business. It is a small
modification or decision that is being
made in a single department. An
analyst here is not managing the
project but merely serving as a
resource for those who are.
ROLES OF SYSTEMS ANALYST

3. AS A CHANGE AGENT
– he is a person who
serves as a catalyst for
change, develops a plan
for change, and works
with others in
facilitating that change. Back to Main Menu
QUALITIES OF A SYSTEMS ANALYST

1.Analyst is a problem solver

2.Views the analysis problem as
a challenge
3.Enjoys devising workable
solutions
4.Must be a communicator
5.Must be self-discipline
6.Must self-motivated
Back to Main Menu
THE INTERVIEW

INTERVIEWING – is a
continuous that is used
by the analyst to
gradually build a model of
the system and to gain
understanding of any
system problems.
 THE INTERVIEW

2 Key Factors in Successful

Interview
1. Choose people to
interview.

2. Finding the right way

to conduct an individual
Back to Main Menu
 THE INTERVIEW

Interview Plan
a. Users to be
interviewed

b. Sequence in which the

users are interviewed
 THE INTERVIEW

TIPS:
 The interview plan is often based on the
current organizational structures, which is
made of organizational units.

 In both the initial and later interviews, the

analyst should always endeavor to find leads
on where to get more information.

 The interview process follows a fairly

structured path.

 Do not expect to obtain all of the information

 THE INTERVIEW(PREPARATION)

 Begin by defining the purpose of

the interview.
 Select the person/group to be
interviewed.
 Do your homework.
 Prepare specific questions aimed at
the individual/group you are
planning the interview.
 THE INTERVIEW ITSELF

OPENING
 Establish rapport.

 Identify yourself, the topic you plan to

discuss, the purpose of the interview.

 Be honest.

 Tell the interviewee why he was chosen for

the interview.

 Begin with a brief period of small talk.

 THE INTERVIEW ITSELF

THE BODY
 Have your first question prepared –
open question

 Concentrate on how and why

 Begin with relatively broad, open

questions and specific follow-up
questions

 Listen to the answers


 THE INTERVIEW ITSELF

THE BODY
 Delete questions that seem unimportant

 Bypass questions that have already

been answered

 Avoid needlessly complex questions

 Avoid attacks

 Avoid excessive use of technical jargon

 THE INTERVIEW ITSELF

THE BODY
 Ask probing questions but do not cross
examine

 Avoid attacking the other person’s

credibility

 Jot down key notes

 Do not be a compulsive note taker

 THE INTERVIEW ITSELF

CLOSING
 Pay attention to the time

 Ask permission to continue

 Thank the subject for

cooperating
 THE INTERVIEW ITSELF

FOLLOW-UP
 Identify the person, the
date, the place and the topic
of the interview.

Back to Main Menu