Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF.

SOFTWARE DEVELOPMENT
LIFE CYCLE (SDLC)
LECTURE 3

Asma Sajid
 Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF. 2

Software life cycle Process

• A process involves activities, constraints and resources
that produces an intended output.
• Each process activity, e.g., design,
must have entry and exit criteria—why?
• A process uses resources, focuses to constraints (e.g.,
a schedule or a budget)
• A process is organized in some order or sequence,
structuring activities as a whole.
• A process has a set of guiding principles or criteria that
explain the goals of each activity.
• A Software development life cycle (SDLC) is a process.
 Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF. 3

SDLC Introduction
• SDLC can be defined as;
 A framework that describes the activities performed at each stage of a
software development project.
• Consists of multiple phases. Each phase has set of
activities to be performed under given constraints and
produce an output.
• Completion of each phase completes some of
milestones of project.
 Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF. 4

Software Process Activities

1. Software specification
 The functionality of the software and constraints on its operation must be
defined.

2. Software design and implementation

 The software to meet the specification must be produced.

3. Software validation
 The software must be validated to ensure that it does what the customer
wants.

4. Software evolution
 The software must evolve to meet changing customer needs.
 Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF. 5

SDLC Phases

Preliminary
Investigation

System
Maintenance
Analysis

System
System Design
Implementation

System
Development
Phases of the System Development
Life Cycle (SDLC)
1. Preliminary Investigation
 Assesses feasibility and practicality of system
 This phase is also called system initiation phase.

2. System Analysis
1. Study old system and identify new requirements
2. Defines system from user's view

3. System Design
1. Design new/alternative system
2. Defines system from technical view
 Six Phases of the SDLC

4. System Development
 New hardware and software is acquired, developed, and tested.
 Activities of coding and some types of testing is done in it.

5. System Implementation
1. System installation on client machines.
2. Training of users is also part of this phase.

6. System Operation & Maintenance

1. Daily operation
2. Periodic evaluation and updating
 Phase 1: Preliminary Investigation

• Determine if a new system is needed

• Three primary tasks:

1. Define the problem
1. By observation and interview, determine what information is needed by whom,
when, where and why

2. Suggest alternative solutions

3. Prepare a short report
Phase 2: System Analysis

• In depth study of the existing system to

determine what the new system should do.
 Expand on data gathered in Phase 1
• In addition to observation and interviews,
examine:
 Formal lines of authority (org chart)
 Standard operating procedures
 How information flows
 Reasons for any inefficiencies
 Phase 2: System Analysis
Tools Used
• Checklists - list of questions
• Top-down analysis - start with top level
components, break down into smaller parts
through each successive level
• Grid charts - to show relationship between
inputs and outputs
• System flowcharts - charts flow of input data,
processing, and output which show system
elements and interactions
Phase 2: System Analysis

Documentation Produced
• Complete description of current system and
its problems
• Requirements for new system including:
 Subject
 Scope Software Requirements
Specification (SRS)
 Objectives Document

 Benefits
• Possible development schedule
 Phase 3: System Design
• Uses specifications from the systems
analysis to design alternative systems
• Evaluate alternatives based upon:
 Economic feasibility - Do benefits justify costs?

 Technical feasibility - Is reliable technology and

training available?
 Operational feasibility - Will the managers and
users support it?
 Phase 3: System Design
Tools Used
• Computer-Aided Simulation Environment
(CASE) tools are software-based products
designed to help automate the production of
information systems.
• Examples:
 Diagramming Tools
 Data Repositories
 Prototyping Tools
 Test Data Generators
 Documentation Tools
 Project Management Tools
 Phase 3: System Design

Documentation Produced
• System Design Report
 Describe Alternatives including:

Inputs/Outputs
Processing
Storage and Backup
 Recommend Top Alternative based upon:

System Fit into the Organization

Flexibility for the future
Costs vs. benefits
 Phase 4: System Development
• Build the system to the design specifications
1. Develop the software
Purchase off-the-shelf software OR
Write custom software
2. Acquire the hardware
3. Test the new system
Module (unit) test - tests each part of system
Integration testing - tests system as one unit
4. Create manuals for users and operators
 Phase 5: System Implementation
1. Convert from old (legacy) system to new system
2. Train users
3. Compile final documentation
4. Evaluate the new system- How?
 Phase 5: System Implementation
1. Types of Conversion
 Direct/plunge/crash approach – entire new system completely replaces entire
old system, in one step
 Parallel approach - both systems are operated side by side until the new
system proves itself
 Pilot approach - launched new system for only one group within the business --
once new system is operating smoothly, implementation goes company-wide
 Phased/incremental approach - individual parts of new system are gradually
phased-in over time, using either crash or parallel for each piece.

2. User Training
 Ease into system, make them comfortable, and gain their support
 Most commonly ignored.
 Can be commenced before equipment delivery
 Outside trainers sometimes used
 Phase 6: Operations & Maintenance
Types of changes:
 Physical repair of the system
 Correction of new bugs found (corrective)
 System adjustments to environmental changes
 Adjustments for users’ changing needs (adaptive)
 Changes to user better techniques when they become available
(perfective)

Evaluation Methods
 Systems audit - performance compared to original specifications

 Periodic evaluation - “checkups” from time to time, modifications if

necessary
 Deliverables of the SDLC
Approved Feasibility Abort Project
Preliminary Study
Investigation Goto next phase
Problem Goto Previous phase
System Specifications
Analysis
System
Design Specifications
Design
Coded and
System
Tested System
Development
Begin building
System System converted
new system Implementation Users trained
System
Maintenance
Operational System
Documentation completed
 Asma Sajid; College of Computer Science & Information Studies (c2sis), GCUF. 20

Summary
Phase Tasks Output Artifacts
Preliminary 1. Define the problem
2. Determine what information is needed by whom, • Short Report
investigation when, where and why. • Feasibility Report
(Input Document 3. Suggest alternative solutions
= SOW)
1. Detailed study of the existing system to determine
what the new system should do.
2. Examine and analyze:org chart, SOPs, information • SRS Document
System flows, reasons for any inefficiencies. • Possible development schedule
Analysis
Tools used: Checklists, Top-down analysis, Grid,
System flowcharts

1. Analysis to design alternative for system on basis

of feasibility based questions and their answers. • System Design Report
System Design
Tools Used: CASE Tools like ; Diagramming Tools,
Data Repositories, Prototyping Tools
1. Develop the software • Code
2. Acquire the hardware
Development 3. Test the new system
• Testing Report
4. Create manuals • User manuals
1. Convert from legacy to new system
2. Train users
Implementation 3. Compile final documentation
• Deployed System
4. Evaluate the new system

Maintenance Physical, corrective & adaptive repair of the system • Audit report