SOFTWARE DEVELOPMENT LIFE CYCLE

(SDLC)
 • Development of application systems and other
software is governed by a company - defined
SDLC or Software Development Life Cycle.
• The life cycle presents the idea that all software
development goes roughly through a common
process.
SOFTWARE • You go through analysis, design, construction,
testing and implementation.
DEVELOPMENT • This SDLC is a mix of the different life cycle
approaches.
LIFE CYCLE • The life cycle standardizes the procedures and
outputs of the various software development
phases.
• By knowing the procedures and required outputs,
we can give a pretty good estimate of how long a
project will take.
 SDLC Objectives

To define the To introduce

To provide
activities to be consistency among
checkpoints for
carried out in a many software
management
software development
control for go/no-go
development projects in the same
decisions.
project. organization.
 Study

Analysis

Design
Phases in Construction
SDLC
System Test

Implementation

Maintenance
 Objectives
To identify the responsible users and
the parameters of the system.
To identify current deficiencies in the
user's environment.
To establish goals and objectives for a
Study Phase new system.
To determine whether it is feasible to
automate the system and, if so,
suggest some acceptable scenarios.
To prepare a project plan that will be
used to guide the remainder of the
project.
 • All software development and change is
usually triggered by a user request. This
marks the first major step in the SDLC.
This phase should have identified the
following:
Project scope and objectives,
Study Phase constraints, disclaimers and
dependencies
Supported functions
Cost/benefits or justification
Broad alternative solutions
Study Phase Deliverables
• Project Study Documentation - This report
establishes the basis on which the project is to be
conducted by describing the objectives, scope, plans,
responsibilities, key assumptions, costs and
deliverables for the project
• Project Risk Assessment - This report documents the
potential exposures of continuing the project. Some
of the factors considered include type of application,
skill and knowledge of the project team members,
use of new technology, and sophistication of the
user. The conclusions of the assessment must be
clear enough to either support the estimates and
projects plans or to prompt adjustment to estimates,
contingencies and assumptions to reduce high risk
areas.
Study Phase Deliverables

• Cost/Benefit Analysis - This report documents

estimated development and operations costs and
compares these to the estimated benefits. ISG is
responsible for providing systems costs and IS
benefits. The user must supply User costs and
benefits
• Feasibility Study - This report establishes the
technical, operational, economic feasibility of the
project.
 Objectives
To familiarize designers with the operation of
the existing system.
To transform the user requirements into a
structured specification.

Business requirements will be fully specified and

analyzed to establish the objectives and scope of a
Analysis Phase system.

For application systems development, the most

commonly used technique is the data flow diagram,
there are also specified procedures for data
gathering. This calls for interviews with users,
questionnaires and other data-gathering methods
such as the Joint Application Design Methodology.
Analysis Phase Deliverables
• Functional Specification - full business conditions and
requirements to be supported by the system.

• Functional Specification Walkthrough and

Documentation - administration of a technical
walkthrough and documentation of
available/potential technical alternatives including
new skill requirements
 Objectives
To validate the findings of the Analysis Phase.
To complete and document the proposed
System for the proposed system.
To prepare detailed Project plans for the
completion of the project.
The Design phase is the next major phase in
Design Phase the SDLC. It is an important phase since the
System Design document defines specifically:
o What the system will do and how it will
meet the user requirements?
o How the system will interface with its
environment?
o How and when the system will be made
available?
o How much the system will cost to develop,
operate and maintain?
 External Design

In external design, the conceptual

solutions proposed by the Analysis Phase
are looked at in more details.
Major new functions are proposed and
changes to existing functions defined.
Important inputs and outputs are also
defined at this point.
Design Phase In addition, external design outlines which
part of the system is to be automated and
which will remain manual.
It is common in external design to consider
a number of alternative solutions, involving
different degrees of automation.
One of this alternative is then chosen as
the preferred solution.
 Internal Design

It is only when a preferred solution is

chosen that internal design starts.
In internal design, the database and
program modules are designed and
detailed user procedures are documented.
Design Phase The interfaces between the system users
and computers are also defined.
These interfaces define exactly what the
user will be expected to do to use the
system.
Design Phase Deliverables
• Proposed Systems Flow
• Database/File Design
• User Transaction Descriptions
• Control and Auditability Features
• Hardware/Software Configurations
• Draft users guide, operations manual, system
documentation
• Walkthrough documentation
• Detailed Project Plan
 Objectives
To specify, code, test and integrate all
system modules as defined in the
Design Phase.
To maintain the integrity of the
Construction Design, adjusting it for justified,
approved changes.
Phase To prepare for System Test and
Implementation Phase.
To complete draft documentation.
 The Construction phase defines the period in the
SDLC when the system, planned and formulated
during the previous phases, is actually
constructed.

This phase now includes specifications of the

Construction modules, coding, unit verification and completion
of integration testing.
Phase
By the end of the phase, a complete data
processing system is assembled and ready for
system testing and implementation; user
documentation and organizational requirements
will be available in draft form; user's guide and
operations manual will be available in draft and
System Test plans will be finalized.
Construction Phase Deliverables
• Detailed Program Specifications
• Tested Programs
• Tested Integrated Programs
• Test Script and Data
• Draft System Documentation
• Draft Operations Manual
• Draft Users Guide
• Walkthrough Documentation
 Objectives
To confirm that the User's requirements are
satisfied by the system.
To ensure that all operational characteristics of
the system are optimize prior to
implementation.
To ensure that implementation plans are
System Test complete.
To obtain User and ISG Management
Phase concurrence to continue with implementation.

The System Test phase is a critical period in the

SDLC. At the end of the Development phase, the
system will contain all required functional
components. It will be fully operational and will
conform to the requirements as interpreted by the
development team.
 • Acceptance Tests, also conducted by the User,
are used to simulate live operations of the
entire system including manual procedures,
forms and processing schedules. Transactions
representing all valid and erroneous input will
be processed against simulated files and
System Test databases and against the documented
acceptance criteria. Decisions are then made to
Phase either implement the system or further improve
its operation.

• By the end of the System Test phase, the user

will have a complete and approved package.
System Test Phase Deliverables
• Operational System
• Final System Documentation
• Final Operations Manual
• Final User's Guide
• Production Turn-over
 Objectives
To complete smooth conversion and
implementation of all system functions and
procedures.
To obtain DCOD acceptance of the production
system.

• Every implementation is unique and will have its own

Implementation problems and concerns.
Phase • By the end of the System Test phase, planning for
conversion and installation is completed and agreement
to implement has been obtained from everyone
connected with the project.
• This phase spans the period from the end of Acceptance
Testing to the final completion of the project. The
nature and duration of the activities will be governed to
the major extent by the implementation strategy
selected for the system.
 • "Direct", "Pilot", and "Parallel" strategies
require all system functions to be available from
the beginning. "Staged" and "Evolutionary"
methods usually result in longer
implementation periods. In these cases,
implementation of some system components
will occur while other components are still in
Implementation Development or System Test Phases.

Phase • The major activities completed during the

Implementation phase include conversion of
data, creation and initial loading of files and
database, implementation of user procedures,
technical installation of the system, final
cleanup of the project, and turnover to DCOD.
 Parallel

FOUR COMMON Phased / Staged / Evolutionary

METHODS OF
SYSTEM
IMPLEMENTATION Pilot

Direct
Parallel Implementation
When the new system is used at the same time as the old system the two systems
are said to be running in parallel.

Advantages:
• Users can can compare the output of the old system with the output of the new
system, to ensure correctness
• There is little risk of data loss because the known-good system is running

Disadvantages:
• Users must take more time to enter data into two different systems
• Data could be different in two different systems if there is intensive data entry.
Phased Implementation
When small parts of the new system gradually replace small parts of the old
system, the implementation method is said to be phased.

Advantages:
• Training can be completed in small parts
• A failure of the new system has minimal impact because it is only one small part
• Issues around scale can be addressed without major impact.

Disadvantages:
• This implementation method takes more time to get the new system fully online
than other methods.
• There is a possibility of data loss if part of the new system fails.
Pilot Implementation
When a small group of users within an organization uses a new system prior
to wider use, the system is said to be piloted.

Advantages:
• Training can be supported by pilot group
• Failure or problems can be identified and addressed without wide-spread
impact to the organization

Disadvantages:
In a pilot, issues of scale can cause problems. For example, the system might
work well for 10 users, but not for 1000.
Direct Implementation
When a new system is implemented without any phased or pilot
implementation, it is said to be direct. The old system is retired, and the new
system goes live.

Advantages:
• If the system is not critical, this can be a good method for implementation

Disadvantages:
• If you are not sure the system will work, this method of implementation
may not be a good idea
System Test Phase Deliverables
• Production System
• Service Level Agreement
 Objectives
To eliminate errors in the working system
during its working life and to tune the system
to any variations in its working environment.
• There are always some errors detected that
deficiencies are found as a system is brought into
Maintenance operation and changes are made to remove these
deficiencies.
Phase • If a major change to a system is needed, a new
project may have to be set up to carry out the
change. This new project will then proceed
through all the above life cycle phases.