CS 6206/IT 6216/IF 6203

SYSTEM ANALYSIS AND DESIGN

1
 References
• Systems Analysis And Design In A Changing
World. John W. Satzinger, Robert B. Jackson,
Stephen D. Burd
• System Analysis And Design Fifth Edition. Alan
Dennis, Barbara Haley Wixom, Roberta M.
Roth

2
Topic One: Introduction to Systems Analysis
and Design

3
 Systems Analysis and Design
Systems Analysis and Design (SAD) is a broad
term for describing methodologies for
developing high quality Information System
which combines Information Technology,
people and Data to support business
requirement.

4
 Information System
An information system is a set of interrelated
computer components that collects, processes,
stores (usually in a database), and provides as
output the information needed to complete
business tasks.

5
Systems analysis and design (SA&D) is about
providing the tools and techniques to you, the
developer, so you can understand the need
(business need), capture the vision, define a
solution, communicate the vision and the
solution, build the solution and direct others in
building the solution, confirm that the solution
meets the need, and launch the solution
application.

6
 Systems analysis
Systems analysis consists of those activities
that enable a person to understand and
specify what the new system should
accomplish.
Systems analysis describes in detail the
“what” that a system must do to satisfy the
need or to solve the problem.

7
 Systems design
Systems design consists of those activities that
enable a person to describe in detail the system
that solves the need.
Systems design describes “how” the system will
work. It specifies in detail all the components of
the solution system and how they work together
to provide the desired solution.

8
 Systems Development Life Cycle
Initial development of a new system is usually done
as a project.
A project is a planned undertaking that has a
beginning and an end and produces some definite
result.
To manage a project with analysis, design, and
other development activities, you need a project
management framework to guide and coordinate
the work of the project team.

9
Systems Development Life Cycle (SDLC) the
entire process consisting of all the activities
required to build, launch, and maintain an
information system.

10
The SDLC includes all the activities that are
part of systems analysis, systems design,
programming, testing, and maintaining the
system as well as other project management
processes that are required to successfully
launch and deploy the new information
system.

11
Here are six core processes required in the development of
any new application:

1. Identify the problem or need and obtain approval to proceed.

12
An information systems development process
is the actual approach used to develop a
particular information system.

13
 Agile Development
An information systems development process
that emphasizes flexibility to anticipate new
requirements during development.

14
The basic philosophy of Agile Development is that
neither team members nor the user completely
understands the problems and complexities of a new
system, so the project plan and the execution of the
project must be responsive to unanticipated issues.
It must be agile and flexible. It must have procedures in
place to allow for, anticipate, and even embrace
changes and new requirements during the
development process.

15
 Iterative Development
An approach to system development in which
the system is "grown" piece by piece through
multiple iterations.

16
Core components are developed first and then
additional components are added. It is called
“iterative” because the six core development
processes are repeated over and over again to add
additional functionality to the overall system. In
other words, there is one big project, which consists
of many mini-projects, and the information system
is grown piece by piece.

17
Figure below illustrates how an iterative Agile project might be executed

18
There are several benefits to iterative development.
For one, portions of the often system can
sometimes be deployed sooner. If there are core
functions that provide basic support, these can be
deployed in an early iteration.
A second benefit is that by taking a small portion
and developing it first, many tough problems can be
addressed early in the project.

19
Many of today’s systems are so large and complex that
it is impossible to remember and understand
everything.
By focusing on only a small portion, the requirements
are fewer and easier to grasp and solve.
Finally, developing a system in iterations makes the
entire development process much more flexible and
able to address new requirements throughout the
project.

20
A key element of iterative development is choosing a
part of the solution system that can be done in two to
four weeks.
During one iteration, often all the core development
processes are involved, including programming and
system-wide testing, so the result is a part of the
working system, even though it may only have a
portion of the functionality that is ultimately required.

21