CHAPTER ONE
System Development Life
Cycle
1
INTRODUCTION
Systems analysis and design (SAD) is a proven
methodology that helps both large and small business
acquire the rewards of utilizing information to its full
capacity.
SAD mainly deals with the software
development activities.
The systems development life cycle (SDLC) is central
to the development of information system. 2
Systems Analysis
It is a process of:
Collecting and interpreting facts,
Identifying the problems,
and decomposition of a system into its
components.
Analysis specifies what the system
should do.
Systems Design
It is the process of designing the elements of a
system such as the architecture, modules, and
components, interfaces etc.
It can be a new system or replacing an existing
system by defining its components to satisfy
the specific requirements.
Design focuses on how to accomplish the
objective of the system.
What is a system?
A system is an interrelated set of components
with an identifiable boundary, working
together for some purpose.
A system has the following characteristics.
Interrelated components
A boundary
A purpose
An environment
Interface
Input
Output
Constraints
System and its
Components
A system is made up of components
A component is either an irreducible part or an
aggregate of parts, also called a subsystem.
The simple concept of a component is very powerful.
Just as with an automobile, we can repair or upgrade the
system by changing individual components without having to
make changes throughout the entire system.
6
System and its
Components
The components are interrelated; that is, the
function of one is somehow tied to the functions
of the others.
A system has a boundary, in which all of its
components are contained and which establishes
the limits of a system, separating the system from
other systems.
Components with in the boundary can be changed
whereas things outside the boundary cannot be
changed
7
System and its
Components
All of the components work together to achieve some
overall purpose for the larger system: the system's
reason for existing.
A system exist with in an environment.
8
System and its
Components
Usually the system interacts with its environment,
exchanging, in the case of an information system, data
and information.
The points at which the system meets its environment
are called interfaces, and there are also interfaces
between subsystems.
The interface has several special, important function.
9
System and its
Components
Because interface functions are critical in
communication between system components or a system
and its environment, interfaces receive much attention
in the design of information system.
It is the design of good interfaces that permits different
systems to work together without being too dependent
on each other.
10
System and its
Components
A system must face constraints in its functioning
because there are limits on:
what it can do and how it can achieve its purpose within its
environment.
Some of these constraints are imposed inside the
system (a limited number of staff available) and others
are imposed by the environment (due dates or
regulation) 11
System development life
cycle (SDLC) phases
The common methodology for systems
development (SDLC).
The phases are:
Planning and selection
Project identification and selection
Initiating and planning
Analysis
Requirement determination
Requirement structuring
Design, and
Implementation and operation.
SDLC diagram
1. System planning and
selection
In Systems Planning and Selection
There are Two Main Activities
Identification and selection
First, someone or group of individuals identifies the need for a
new or enhanced system.
The system priority board selects one of the systems based on
the priority set by the analyst.
1. System planning and
selection
Initiation and planning
The second task systems initiation and planning
phase is to investigate the system and determine the
proposed system’s scope.
The team of systems analysts then produces a
specific plan for the proposed project for the team to
follow.
A feasibility study is conducted.
This baseline project plan (BPP) customizes the
standardized SDLC and specifies the time and
resources needed for its execution.
2. ANALYSIS
Analysis has several sub phases.
Requirements determination.
1.
The analyst work with users to determine what the users want from a proposed system.
Using careful study of any current systems (manual and computerized), that might be
replaced or enhanced as a part of this project.
Requirements structuring
2.
structuring the requirements according to their interrelationships and eliminate any
redundancies.
3. Generating alternative initial designs to match the requirements.
• In the final sub phase,
– you compare these alternatives to determine which best
meets the requirements within the:
• cost, labor and technical levels the organization is willing to
commit to the development process.
• The output of the analysis phase is a description of
(but not a detailed design for) the alternative
solution recommended by the analysis team.
17
3. System Design
• The third phase is devoted to designing the new or enhanced
system.
• During design, the description of the recommended
alternative solution will be converted into logical and then
physical system specifications.
• You must design all aspects of the system:
– from input and output screens to reports, databases, and computer
processes.
• You must then provide the physical specifics of the system
you have designed:
– either as a model or as detailed documentation, to guide those who will
build the new system.
18
• That part of the design process that is independent of any
specific hardware or software platform is referred to as logical
design.
• Turning the logical specifications into physical ones is referred
to as physical design.
• During physical design, the analyst team must determine
many of the physical details necessary to build the final
system.
• The final product of the design phase is the physical system
specifications in a form ready to be turned over to
programmers and other system builders for construction.
19
4. System Implementation & operation
The final phase of the SDLC is a two-step process:
System Implementation and operation.
Implementation includes coding, testing, and
installation.
During coding, programmers write the programs that make
up the system.
During testing, programmers and analysts test individual
programs and the entire system in order to find and correct
errors.
20
During installation, the new system becomes a part
of the daily activities of the organization.
The second part of the fourth phase of the SDLC is
operation.
During operation, programmers make the changes
that users ask for and modify the system to reflect
changing business conditions (maintenance).
21
Approaches to System analysis & Design
In any given SDLC phase, the project can
return to an earlier phase if necessary.
Sometimes the life cycle is iterative; that is
phases are repeated as required until an
acceptable system is found.
22
Approaches to System analysis & Design
There are Three approaches that streamline
(modernize) and improve the systems
analysis and design process.
Rapid application development (RAD),
Prototyping,
Joint application designs (JAD), and
participatory design (PD)
23
Rapid application Development (RAD)
RAD methodologies emphasize gaining user
acceptance of the human-system interface and
developing core capabilities as quickly as possible.
The fundamental principle of any RAD methodology
is to delay producing detailed system design
documents until user requirements are clear.
Prototyping is a form of rapid application
development, or RAD.
24
Prototyping
Designing and building a scaled-down but working
version of a desired system is known as prototyping.
A prototype can be developed with a computer-aided
software engineering (CASE) tool.
CASE tool, a software product that automates the
SDLC steps.
CASE tools make prototyping easier and more creative.
Throw-away prototyping vs Evolutionary prototyping
25
Figure 3.3 The prototyping methodology
26
Joint Application Design
Users, mangers, and system developers are brought
together for a series of intensive structured meetings.
The aim of JAD is:
to collect information system requirements and reviewing
system designs.
The basic idea behind JAD is to bring structure to
the requirements determination phase of analysis
and to the reviews that occur as part of design.
27
JAD Session
28
Participatory Design
Participatory Design (PD) represents a viable
alternative approach to the SDLC.
Each user has an equal voice in determining system
requirements and in approving system design.
An elected group of users controls the process.
29
THANK YOU!
30
