Systems Development Life Cycle

System Development Methodology

Standard process
followed in an organization
Consists of:
Investigation
Design
Coding
Testing
Implementation
Maintenance
Enhancement
Retirement

1
2
3
Systems Development Life Cycle
Series of steps used to manage the phases of
development for an information system

Each phase has a specific outcome and

deliverable
Individual companies use customized life cycle

4
 Phases of the Systems
Development Life Cycle
Systems Planning and Selection
Two Main Activities
Identification of need
Investigation and determination of scope
Systems Analysis
Study of current procedures and information systems
Determine requirements
Generate alternative designs
Compare alternatives
Recommend best alternative
5
Continued.
System Design
Logical Design
Concentrates on business aspects of the system (flow of
information)
Physical Design
Technical specifications (h/w and anti-hacking concerns)
Implementation and Operation
Implementation
Hardware and software installation
Programming
User Training
Documentation

6
7
 Phases of System Development
Life Cycle
1. Recognition of Need-What is the
Problem/Preliminary Survey/Initial
Investigation
2. Feasibility Study
a. Technical feasibility
b. Economical
c. Operational
Request Approval

8
Continued

3. Determination of system requirements

4. Design system
5. Development of software(coding)
6. System testing
7. Implementation, evaluation &
maintenance

9
 Approaches to Development
Prototyping
Building a scaled-down working version of the
system
Advantages:
Users are involved in design
Captures requirements in concrete form
Rapid Application Development (RAD)
Utilizes prototyping to delay producing system
design until after user requirements are clear

10
 Prototyping
Proposed Advantages Disadvantages in practice
Improved user Prototypes are used as
communication is
Users like it Integration often
Low risk difficult
Avoids over-design Design flaws
Experimentation and Poor performance
innovation Difficult to manage
Spreads labor to user process
department Creates unrealistic
expectations
Documentation is
difficult
Continued

Joint Application Design (JAD)

Users, Managers and Analysts work together
for several days
System requirements are reviewed
Structured meetings

12
 Other models
used for SDLC

13
Waterfall Model for System Development
This model is often known as the "classical life cycle" or
"linear sequential model". This model is derived from
conventional engineering cycle. It encompasses all the
activities discussed above. It is so called, because of

It's diagrammatic representation. All the steps are followed by

each other. An activity starts only when the previous activity
has been completed. For example, as per the waterfall model,
maintenance

Phase is started only when the implementation phase has been

completed.
14
Prototyping
Developer meets customer and define the overall objectives
for the software, identifies whatever requirements are known
and outlines areas where further definition is necessary.
A design then occurs.
Iterations occur, as the prototype is tuned to satisfy the needs
of the customer, at the same time enabling the developer to
better understand what needs to be done.
Advantage: of prototyping over waterfall lies in the fact
that in the current situation, organizations and environment
are changing fastly. This may lead to a change in need of
information. SDLC is a long process often running into
months.
15
The Spiral Model
The spiral model is one that couples the iterative nature
of prototyping with controlled and systematic aspect of
the linear sequential or waterfall model.
It provides the potential for rapid development of
incremental versions of the system.
In a spiral model, a software is developed in a series of
incremental releases. During each iteration, the
incremental release might be a paper model or
prototype.
During later iterations, increasingly more complete
versions of the engineered system are produced.

16
17
Continued
The spiral model is divided into a number of framework activities, also called
task regions. Typically, there are six task regions:
Customer/user communication: Establish effective
communication between developer and user.
Planning: Define resources, timeliness and other project related
information.
Risk analysis: Uses both technical and management risk.
Engineering: Build one or more representations of application.
Construction and release: Construct, test, install and provide user
support.
Customer evaluation: User provides feedback based on
evaluation of software.

18