SYSTEM DEVELOPMENT

LIFE CYCLE
(SDLC)
System and Development Life Cycle (SDLC)

Is a process used by a systems analyst to develop an

information system, including requirements, validation,
training, and user ownership. Any SDLC should result in
a high quality system that meets or exceeds customer
expectations, reaches completion within time and cost
estimates, works effectively and efficiently in the current
and planned Information Technology infrastructure, and is
inexpensive to maintain and cost effective to enhance.
 The system development life cycle (SDLC) is type of
methodology used to describe the process for building
information systems, intended to develop information
systems in a very deliberate, structured and methodical
way, reiterating each stage of the life cycle.
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

• Systems development life cycle (SDLC) - a

structured step-by-step approach for
developing information systems
• Typical activities include:
• Determining budgets
• Gathering business requirements
• Designing models
• Writing user documentation
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

SDLC PHASE ACTIVITIES

1. Planning •Define the system to be developed
•Set the project scope
•Develop the project plan
2. Analysis •Gather business requirements
3. Design •Design the technical architecture
•Design system models
4. Development •Build technical architecture
•Build databases and programs
5. Testing •Write test conditions
•Perform testing
6. Implementation •Write user documentation
•Provide training
7. Maintenance •Build a help desk
•Support system changes
 SYSTEMS DEVELOPMENT LIFE CYCLE
(SDLC)
• The SDLC has 7 phases:
1. Planning
2. Analysis
3. Design
4. Development
5. Testing
6. Implementation
7. Maintenance
SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)
 Phase 1: Planning
• Planning phase - involves determining a solid
plan for developing your information system
• Three primary planning activities:
1. Define the system to be developed
• Critical success factor (CSF) - a factor simply critical to
your organization’s success
 Phase 1: Planning
2. Set the project scope
• Project scope - clearly defines the high-level system
requirements
• Scope creep - occurs when the scope of the project
increases
• Feature creep - occurs when developers add extra
features that were not part of the initial requirements
• Project scope document - a written definition of the
project scope and is usually no longer than a paragraph
 Phase 1: Planning
3. Develop the project plan including tasks,
resources, and timeframes
• Project plan - defines the what, when, and who
questions of system development
• Project manager - an individual who is an expert in
project planning and management, defines and
develops the project plan and tracks the plan to ensure
all key project milestones are completed on time
• Project milestones - represent key dates for which you
need a certain group of activities performed
Phase 1: Planning
 Phase 2: Analysis
• Analysis phase - involves end users and IT
specialists working together to gather,
understand, and document the business
requirements for the proposed system
 Phase 2: Analysis
• Two primary analysis activities:
1. Gather the business requirements
• Business requirements - the detailed set of knowledge
worker requests that the system must meet in order to
be successful
• Joint application development (JAD) - knowledge
workers and IT specialists meet, sometimes for several
days, to define or review the business requirements for
the system
 Phase 2: Analysis
2. Prioritize the requirements
• Requirements definition document – prioritizes the
business requirements and places them in a formal
comprehensive document
Phase 2: Analysis
 Phase 3: Design
• Design phase - build a technical blueprint of
how the proposed system will work
• Two primary design activities:
1. Design the technical architecture
• Technical architecture - defines the hardware, software,
and telecommunications equipment required to run the
system
 Phase 3: Design
2. Design system models
• Modeling - the activity of drawing a graphical
representation of a design
• Graphical user interface (GUI) - the interface to an
information system
• GUI screen design - the ability to model the information
system screens for an entire system
 Phase 4: Development
• Development phase - take all of your detailed
design documents from the design phase and
transform them into an actual system
• Two primary development activities:
1. Build the technical architecture
2. Build the database and programs
• Both of these activities are mostly performed by IT
specialists
 Phase 5: Testing
• Testing phase - verifies that the system works
and meets all of the business requirements
defined in the analysis phase
• Two primary testing activities:
1. Write the test conditions
• Test conditions - the detailed steps the system must
perform along with the expected results of each step
 Phase 5: Testing
2. Perform the testing of the system
• Unit testing – tests individual units of code
• System testing – verifies that the units of code function
correctly when integrated
• Integration testing – verifies that separate systems
work together
• User acceptance testing (UAT) – determines if the
system satisfies the business requirements
 Phase 6: Implementation
• Implementation phase - distribute the system
to all of the knowledge workers and they
begin using the system to perform their
everyday jobs
• Two primary implementation activities
1. Write detailed user documentation
• User documentation - highlights how to use the system
 Phase 6: Implementation
2. Provide training for the system users
• Online training - runs over the Internet or off a CD-ROM
• Workshop training - is held in a classroom environment
and lead by an instructor
 Phase 6: Implementation
• Choose the right implementation method
– Parallel implementation – use both the old and new
system simultaneously
– Plunge implementation – discard the old system
completely and use the new
– Pilot implementation – start with small groups of
people on the new system and gradually add more
users
– Phased implementation – implement the new
system in phases
 Phase 7: Maintenance
• Maintenance phase - monitor and support
the new system to ensure it continues to
meet the business goals
• Two primary maintenance activities:
1. Build a help desk to support the system users
• Help desk - a group of people who responds to
knowledge workers’ questions
2. Provide an environment to support system
changes
(SDLC) MODEL
WATERFALL MODEL
Is a sequential design
process, often used in software
development processes, in
which progress is seen as
flowing steadily downwards
(like waterfall) through the
phases of Conception,
Initiation, Analysis, Design,
Construction, Testing,
Production/Implementation and
Maintenance.
SASHIMI MODEL

The sashimi waterfall model

suggests a strong degree of
overlap between the phases of
a software development life
cycle. For example,
architectural design and
detailed design maybe partially
completed before requirement
analysis is considered
complete. This approach is
especially suitable for projects
requiring gainful insights into
each layer as they move
through their development life
cycle.
PROTOTYPE

A prototype is an early sample

or model build to test a concept or
process or to act as a thing to be
replicated or learned from.
EVOLUTIONARY MODEL

Companies first would be

release a low functionality version
of a product to selected
customers at a very early stage of
development.

There after work would

proceed in an interactive fashion,
with the design allowed to evolved
to response to the customers
feedback. The approach contrast
with traditional models of software
development and their more
sequential processes.
V-SHAPED MODEL

Just like the waterfall model,

the V-Shaped life cycle is a
sequential path of execution of
processes. Each phase must be
completed before the next
phase begins. Testing is
emphasized in this model more
so than the waterfall model
through. The testing procedures
are developed early in the life
cycle before any coding is done,
during each of phase preceding
implementation.
RAD MODEL

Rapid Application
Development (RAD) is a software
development methodology that
uses minimal planning in favor of
rapid prototyping. The “planning”
of software developed using RAD
is interleaved with writing the
software itself. The lack of
extensive pre-planning generally
allows software to be written
much faster, makes it easier to
change requirements.
SPIRAL MODEL

The Spiral Model is a

software development process
combining elements of both
design and prototyping-in-stages,
in an effort to combine
advantages of top-down and
bottom up concepts. Also know
as the spiral life cycle model (or
spiral development), it is a
system development method
(SDM) used in Information
Technology (IT).
AGILE

Agile software Development

is a group of software
development methodologies
based on iterative and
incremental development, where
requirements and solutions
evolve through collaboration
between self organizing, cross
functional teams. The agile
Manifesto introduced the term in
2001.