Scribd
Upload
90 views

Chapter 2 - SDLC Concepts - Modified

The document provides an introduction to the software development lifecycle (SDLC). It discusses that the SDLC includes products like software and documentation, as well as processes that define key areas and involve communication, standards, planning, tools, and quality assurance. It also notes that SDLC models, like the sequential V-model and waterfall model, describe the phases and relationships between activities in software development from requirements to maintenance. Following a defined process is important for project management and addressing increasing complexity in software.

Uploaded by

Mohammed Anas
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
90 views

Chapter 2 - SDLC Concepts - Modified

The document provides an introduction to the software development lifecycle (SDLC). It discusses that the SDLC includes products like software and documentation, as well as processes that define key areas and involve communication, standards, planning, tools, and quality assurance. It also notes that SDLC models, like the sequential V-model and waterfall model, describe the phases and relationships between activities in software development from requirements to maintenance. Following a defined process is important for project management and addressing increasing complexity in software.

Uploaded by

Mohammed Anas
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 11

SDLC – A Brief Introduction

Product, Process and Methods


 Product
includes some of: hardware , software , documentation , installation, etc.

 Process
 Process defines a framework for a set of key process areas that must be established for
effective delivery of software engineering technology.
 involvesall of: communication (internal and external) , standards (definition and
adherence) , planning and monitoring , tools and methodologies , quality assurance

 Role of Processes
 Increasingly, software suppliers recognize that software development process
capability is a key source of competitive advantage.
 Competition forces suppliers to improve processes to meet the conflicting demands of
higher quality, lower cost, and compressed schedules.

 Method
 Methods provides the technical “how to’s” for building software
Some Root Causes for Failure
 Inaccurate understanding of end-user-needs

 Ad hoc requirements management

 Ambiguous and imprecise communication

 Overwhelming complexity

 Undetected inconsistencies in requirements, design and implementations

 Insufficient testing resulting in late discovery of serious flaws

 Poor software quality

 Failure to attack risk

 Insufficient use of automation tools


What is SDLC ?
 The various activities which are undertaken when developing software
are commonly modeled as a software development lifecycle.

 The software development lifecycle begins with the identification of a


requirement for software and ends with the formal verification of the
developed software against that requirement.

 The software development lifecycle does not exist by itself, it is in fact


part of an overall product lifecycle.

 Within the product lifecycle, software will undergo maintenance to


correct errors and to comply with changes to requirements.

 The simplest overall form is where the product is just software, but it
can become much more complicated, with multiple software
developments each forming part of an overall system to comprise a
product.
SDLC Models
 There are a number of different models for software development lifecycles
which explains the series of steps through which the product progresses.

 Life cycle models describe the interrelationships between software


development phases.

 It specifies the relationships between project phases, including transition


criteria, feedback mechanisms, milestones, baselines, reviews, and deliverables.

 Typically, a life cycle model addresses the following phases of a software


project: requirements phase, design phase, implementation, integration, testing,
operations and maintenance.
Importance of Lifecycle Models
 Provide guidance for project management
 what major tasks should be tackled next? milestones!
 what kind of progress has been made?

 The necessity of lifecycle models


 character of software development has changed
– early days: programmers were the primary users
– modest designs; potential of software unknown
 more complex systems attempted
– more features, more sophistication  greater complexity, more chances for
error
– heterogeneous users
1. Sequential Model

 The models used for the software development lifecycle have been sequential,
with the development progressing through a number of well defined phases.

 The sequential phases are usually represented


 V Model
 Waterfall Model.
a. V Model

Requirement User Acceptance


Specifications Testing

High Level System


Design Testing

Detail Integration
Design Testing

Program Unit
Specification Testing

Coding
b. Waterfall Model

Requirements
Specification
Architectural
Design
Detailed
Design
Code and Unit
Testing
Software
Integration
System
Integration
Acceptance
Testing
Q&A
Thank You

You might also like