System

Analysis and
Design
 System Analysis and
Design

System
is an interrelated set of components that
function together to achieve an outcome.

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 of 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 system’s components.
Control Mechanisms - rules and logic that
govern the individual subsystems and the
interactions among them
 System Analysis and
Design

Systems analysis
is the study of a business
problem domain for the purpose
of recommending improvements
and specifying the business
requirements for the solution.
 System Analysis and
Design

Nature of analysis
• Identify the operation of the existing
system;
• Understand what the existing system is
doing;
• Understand the need of the users;
• Decide on what the new system should
be doing;
• Decide on how the new system will
function.
 System Analysis and
Design

Systems design
is the specification or
construction of a technical,
computer-based solution for the
business requirements
identified in a systems analysis.
 System Analysis and
Design
Needs for System analysis and
design
 it seeks to systematically analyze
data input or data flow, processing or
transformation of data, data storage
and information output within the
context of a particular business
 System Analysis and
Design
used to analyze, design and
implement improvements in the
functioning of business that can be
accomplished through the use of
computerized information system

lends structure to the analysis

and design of information system,
 System Analysis and
Design
Business system
is a collection of policies, procedures,
methods, people, machines, and other
elements that interact and enable the
organization to achieve its goals.
Information system
is a collection of interrelated components
that collect, process, store, and provide as
output the information needed to
complete a business task
 System Analysis and
Design
Components of an Information
System
• Work Practice - methods and procedures
used by people and technology to perform
work.
• Information - can include formatted data,
text, images and sounds.
• People - persons, who enter, process, and use
data.
• Information Technology - includes
hardware and software that perform one or
more data processing tasks.
 System Analysis and
Design
Need of an information system
growing size of the organization and the number
of competitors
growing ability of computers to process large
amount of data with great speed
dramatic increase in volumes of data generated
advances in communication technologies to
permit faster data transmission
increase in pace of business transactions
much more sophisticated technology today
 System Analysis and
Design

Types of Information Systems

Transaction Processing Systems (TPS)
TPS process large amount of data for
routine business activities or transactions.
A transaction is an event that generates or
modifies data that is eventually stored in
an information system
 System Analysis and
Design
Office Automation Systems (OAS)
OAS support general office work for handling and
managing documents and facilitating
communication.

Management Information Systems (MIS)

MIS provide a standard reports for managers
about transaction data. MIS work on the
purposeful interaction between people and
computers.
 System Analysis and
Design

Decision Support Systems (DSS)

DSS are designed to help organizational decision

makers identify and choose between options or
decisions. DSS depend on a database as a
source of data
 System Analysis and
Design
Expert Systems (ES)

Expert systems (also called knowledge-based

system) perform a task that would otherwise
be performed by a human expert. Some
expert systems are designed to take the
place of human expert, while others are
designed to aid them.
 System Analysis and
Design

Executive Information Systems (EIS)

EIS provide a generalized computing and

communication environment to senior
managers to support strategic decisions. EIS
are designed to facilitate senior managers’
access to information quickly and
effectively.
 System Analysis and
Design
General System Principles
1. The more specialized a system is, the less
able it is to adapt to different
circumstances.
2. The more general-purpose a system is,
the less optimized it is for any particular
situation. But the more the system is
optimized for a particular situation, the less
adaptable it will be to new circumstances.
 System Analysis and
Design
3. The larger the system is the more of its
resources that must be devoted to its
everyday maintenance.
4. Systems are always part of larger
systems, and they can always be partitioned
into smaller systems.
5. Systems grow. This principle could not be
true for all systems, but many of the
systems with which we are familiar do grow,
because we often fail to take it into
account when we begin developing the
system.
 System Analysis and
Design

Different classes of actors in an

information system
System sponsors/owners – pay for the
system to be built and operated and set the
vision and priorities for the system. System
sponsors may also be system users and
they generally come from the ranks of
executives and managers.
 System Analysis and
Design

Different classes of actors in an

information system
System users – are the people who
actually use the system on a regular basis
to support the operation and management
of the organization. System users are also
internal system customers and they come
from all levels of the organization.
 System Analysis and
Design

Different classes of actors in an

information system
System designers – are technical
specialists that translate the business
requirements into a feasible technical
solution. Thus, they view an information
system in terms of a design blueprint to
guide the construction of the final system
 System Analysis and
Design

Different classes of actors in an

information system
System builders – are technical
specialists who build, test, and deliver
the information system. Thus, they view
an information system in terms of the
actual working hardware and software to
implement the system.
 System Analysis and
Design

Different classes of actors in an

information system

System analysts – are people who

determine the requirements that must
be met by the information system.
 System Analysis and
Design

Roles of the Systems Analyst

Systems Analyst as Consultant

The systems analyst acts as a consultant
to a business and therefore, may be hired
to address specific information systems
issues within a business
 System Analysis and
Design

Roles of the Systems Analyst

Systems Analyst as Supporting Expert

The systems analyst draws on professional

expertise concerning computer hardware
and software and their uses in the
business.
 System Analysis and
Design

Roles of the Systems Analyst

Systems Analyst as Agent of Change
They are an agent of change whenever they
perform any of the activities in the SDLC and are
present in the business for an extended period.
Also, as an agent of change, the systems analyst
advocates a particular avenue of change involving
the use of information systems.
System Analysis and
Design
 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.
 System Analysis and
Design
SDLC methodology follows the
following steps
1. The existing system is evaluated.
Problems are identified. These can be
done through system user interview and
with support personnel consultation.
2. The new system requirements are
defined. The problems in the existing
system must be addressed with specific
proposals for improvement.
 System Analysis and
Design
3. The proposed system is designed. Plans
are laid out involving physical
construction, hardware specifications,
operating systems, programming,
communications, and security issues.
4. The new system is developed. New
components and programs must be
obtained and installed. System users
must be trained with the new system, and
all aspects of performance must be
tested.
 System Analysis and
Design

5. The system is put into use. The new

system can stepped in, according to
application or location. Then, the old
system is gradually replaced.
6. The new system should be evaluated
once it is up and running. Maintenance
must be kept up rigorously at all times.
System users should be updated with the
latest modifications and procedures.
System Analysis and
Design
 System Analysis and
Design

Planning Phase
Project planning is the process of
defining clear, discrete activities, and the
work needed to complete each activity
within a single project.
Primary objectives of this phase
Identify the scope of the new system ensure
that the project is feasible develop a
schedule, resource plan, and budget for the
remainder of the project
 System Analysis and
Design
The activities that a systems analyst
perform during the project planning phase
include the following:
Define the problem – define precise
business problem and scope of the
required solution
Confirm project feasibility – feasibility
analysis is conducted
 System Analysis and
Design

Produce the project schedule – detailed

listing of tasks and activities
Staff the project – detailed listing of
required staff
Launch the project – initiation of the
project
 System Analysis and
Design
Analysis Phase

The primary objective of the analysis

phase is to understand and document the
business needs and the processing
requirements of the new system. This
phase is basically a discovery process
 System Analysis and
Design

The activities in this phase include

the following:

Gather information – observing the users

as they do their work; by interviewing and
asking questions to the users; by reading
existing documents about procedures,
business rules, and job responsibilities;
and by reviewing existing automated
systems
 System Analysis and
Design
Define system requirements – drawing
diagrams to express and model the new
system’s processing requirements
Build prototypes for discovery of
requirements – reviewing working prototypes
of alternatives
Prioritize requirements – important needs
must be identified and given priority for
development
 System Analysis and
Design

Generate and evaluate alternatives –

building the system inhouse, buying a
software package, or contracting to a third
party to develop and install a new system
Review recommendations with
management – recaps the results of the
analysis phase activities to make decisions
about an alternatives
 System Analysis and
Design

Design Phase

This phase is where the technical blueprint

of the system is created.

The primary objective of the design phase is

to design the solution system based on the
requirements defined and decisions made
during the analysis phase.
 System Analysis and
Design
The activities done during this phase
are
Design and integrate the network –
configuring computer equipment, network,
and operating system platforms that will
house the new information system
Design the application architecture –
consists of using the diagrams showing the
system’s requirements that were
developed during analysis
 System Analysis and
Design
Design the user interfaces – consists of
forms, reports, screens, and sequences of
interactions
Design the system interfaces – design of the
method and details of the communication
between the new information system and
existing system must be precisely defined
Design and integrate the database –
database for the specific system must be
integrated with information databases of
other systems already in use
 System Analysis and
Design

Prototype for design details – ensure

that prototypes function correctly in the
operating environment; test and verify
alternative design strategies by building
prototypes of the new systems
Design and integrate the system
controls – every new system must
include adequate mechanisms to
protect the information and assets of the
organization
 System Analysis and
Design
Implementation Phase
In the implementation phase, the final
system is built, tested, and installed.

The objective of the activities of this

phase is not only to produce a reliable,
fully functional information system, but
also to ensure that the users are all
trained and that the organization is
ready to benefit as expected from use of
the system.
 System Analysis and
Design
The activities that make up the
implementation phase are

Construct software components –

constructed through various techniques,
development tools, and existing components
Verify and test – prototypes are used to
verify different implementation strategies
and to ensure that the system can handle
the volumes of transactions that will exist
after it is placed in production
 System Analysis and
Design
Convert data – convert to the format
required in the new system Train users
and document the system – users
should understand and use the new
system appropriately
Install the system – new equipment
must be in place and functioning, the
new computer programs must be
installed and working, and the
database must be populated and
available
 System Analysis and
Design
Maintenance Phase

The objective of the maintenance phase

is to keep the system running productively
during the years following its initial
installation. This phase begins only after
the new system has been installed and
put into use, and it lasts throughout the
productive life of the system.
 System Analysis and

The activities occur during Design

maintenance phase are:

Maintain the system – include both fixing the
errors (also known as fixing bugs) and making
minor adjustments to processing requirements
Enhance the system – the company must
approve and initiate an upgrade development
project
Support the users – a help desk is assigned to
answer users’ questions and help increase
their productivity; training new users and
maintaining current documentation
 System Analysis and
Design

Approaches to System Development

There are two general approaches to

systems development and these are:
 Traditional approach
 Object-oriented approach
 System Analysis and
Design

Traditional Approach
Also known as structured system
development, this approach includes three
techniques: structured analysis, structured
design, and structured programming. These
techniques are sometimes called structured
analysis and design techniques (SADT).
 System Analysis and
Design

A structured program is one that has one

beginning and one ending, and each step in
the program execution is composed of one
of three programming constructs:
 A sequence of program statements
 A decision where one set of statements or
another set of statements executes
 A repetition of a set of statements
 System Analysis and
Design

Object-Oriented Approach

object-oriented approach views an

information system as a collection of
interacting objects that work together to
accomplish tasks.
 System Analysis and
Design

Three techniques of object-

oriented approach
Object-oriented analysis defines all
of the types of objects that do the
work in the system and shows what
user interactions are required to
complete the tasks.
 System Analysis and
Design

Object-oriented design defines all of the

additional types of objects necessary to
communicate with people and devices in the
system, shows how the objects interact to
complete the tasks, and refines the
definition of each type of object so it can be
implemented with a specific language or
environment.
 System Analysis and
Design

Object-oriented programming includes

writing of statements using a
programming language to define what
each type of object does.
 System Analysis and
Design
Variations of the systems development
life cycle(SDLC).
The Waterfall Model
The waterfall model describes a
development method that is linear
and sequential. This model is based
on the metaphor that when one
phase was finished, the development
proceeds to the next phase with no
turning back.
System Analysis and
Design
 System Analysis and
Design

The Prototyping Model

Prototyping is a systems development
methodology in which a prototype is
built, tested, and then reworked as
necessary until an acceptable
prototype is finally achieved from
which the complete system or product
can now be developed.
System Analysis and
Design
 System Analysis and
Design

The prototyping model has several

advantages:
 May provide the proof of concept
necessary to attract funding Early
visibility of the prototype gives users an
idea of what the final system looks like
 Encourages active participation among
users and producer Enables a higher
output for user
 System Analysis and
Design

Cost effective (Development costs

reduced)
 Increases system development speed
 Assists to identify any problems with
the efficacy of earlier design,
requirements analysis and coding
activities
 Helps to refine the potential risks
associated with the delivery of the
system being developed
 System Analysis and
Design

The Spiral Model

The spiral model is an SDLC model used

in information technology that combines
the features of the prototyping model
and the waterfall model.
System Analysis and
Design
 System Analysis and
Design
The spiral model can be generalized
in the following steps
1. The new system requirements are
defined in details. This involves
interviewing a number of users
representing all external or internal users
and other aspects of the existing system.
2. An initial design is created for the new
system.
 System Analysis and
Design
3. A first prototype of the new system is
constructed from the initial design. This is
usually a scaled-down system, and represents
an approximation of the characteristics of the
final product.
4. A second prototype is evolved by a fourfold
procedure: (1) evaluating the first prototype in
terms of its strengths, weaknesses, and risks;
(2) defining the requirements of the second
prototype; (3) planning and designing the
second prototype; (4) constructing and testing
the second prototype.
 System Analysis and
Design
5. At the customer's option, the entire project
can be aborted if the risk is deemed too great.
Risk factors might involve development cost
overruns, operating-cost miscalculation, or any
other factor that could, in the customer's
judgment, result in a less-than satisfactory
final product.
6. The existing prototype is evaluated in the
same manner as was the previous prototype,
and, if necessary, another prototype is
developed from it according to the fourfold
procedure outlined above.
 System Analysis and
Design
7. The preceding steps are iterated until
the customer is satisfied that the refined
prototype represents the final product
desired.
8. The final system is constructed based
on the refined prototype.
9. The final system is completely
evaluated and tested. Routine
maintenance is carried out on a
continuing basis to prevent large-scale
failures and to minimize downtime.
 System Analysis and
Design
The advantages of using a spiral model are:
 Estimates of the budget and schedule
become more realistic as work progresses
because of the questions that have been
raised
 Easier to cope with the changes inherent
to software development
 Software engineers can start working on
the project earlier rather than wading
through a lengthy early design process
 System Analysis and
Design

Extreme Programming (XP)

eXtreme Programming (XP) is a

discipline of system development
that
follows a specific structure that is
designed to simplify and expedite the
process of developing new software.
 System Analysis and
Design

The Unified Process (UP)

The Unified Process is an object-

oriented system development
methodology offered by Rational
Software, which was recently
acquired by IBM.
 System Analysis and
Design
The UP is designed to reinforce six “best
practices” for system development that
are common to many system
development methodologies. These
are:
Develop iteratively
 Define and manage system
requirements
 Use component architectures
 Create visual models
 Verify quality
 Control changes
 System Analysis and
Design

There are four phases under UP and these

include:
1. Inception – defines the scope of the
project by specifying use cases
2. Elaboration – focuses on several
iterations that take part of the system and
define the requirements, design the solution,
and implement the solution
 System Analysis and
Design

3. Construction – continue to build the

system using additional iterations that also
include requirements, design, and
implementation
4. Transition – turn the system over to the
end users and focus on end-user training,
installation, and support
 System Analysis and
Design

Agile Modeling

Agile modeling is a practice-based

methodology for modeling and
documentation of software-based
systems.
 System Analysis and
Design

The following are core practices of the Agile

modeling:
Iterative and Incremental Modeling – Apply the
right models, create several models in parallel,
and model in small increments.
Teamwork – Model with others, get active
stakeholder participation, encourage collective
ownership, and display models publicly.
Simplicity – Create simple content, illustrate
models simply, and use the simplest modeling
tools.
Validation – Consider testability, and then
prove the model is right with code.
 System Analysis and
Design

Rapid Application Development

(RAD)
Rapid application development is a
system development methodology that
emphasizes speed of development
through extensive user involvement in
the rapid, iterative, and incremental
construction of a series of functioning
prototypes of a system that eventually
evolves into the final system
System Analysis and
Design
 System Analysis and
Design

In the requirements planning phase,

high-level users decide on what
functions the application should
feature.
In the user design phase, the users are
characterized as being engaged in
discussing the non-technical design
aspects of the system, with the
assistance of the analysts.
 System Analysis and
Design

In the construction phase, any designs that

were created in the previous phase are
further enhanced with RAD tools.
In the cutover phase, the old application will
be replaced with the new one. The newly
developed application is tested, users are
trained, and organizational procedures are
changed before the cutover occurs.
 System Analysis and
Design

The RAD methodology has several

advantages:
 It is useful for projects in which the user
requirements are uncertain or imprecise.
 It encourages active user and
management participation, which
increases end-user enthusiasm for the
project.
 Projects have higher visibility and
support because of the extensive user
involvement throughout the process.
 System Analysis and
Design

Errors and omissions tend to be

detected earlier in prototypes than in
system models.
 The iterative approach is a more
“natural” process because change is an
expected factor during development
 System Analysis and
Design
Joint Application Development
(JAD)
Joint application development is a systems
development methodology that involves
the client or end users in the design and
development of an application, through a
succession of collaborative workshops
called JAD sessions.
 System Analysis and
Design

A major advantage of JAD is that

allows for the simultaneous gathering
and consolidating of large amounts of
information. However, a drawback of
JAD is that it opens up a lot of scope of
inter-personal conflict.