Software Development Life Cycle

Presented By

MS70 – Group 2

1
 Key Contents
 Definition

 The SDLC Activities

 Planning
 Implementation, testing and documenting
 Deployment and maintenance

 Software Development Models

 Waterfall Model
 Spiral Model

 Which Model Should I Choose?

 SDLC with an example

 Conclusion
2
 Definition
 A software development process, also known
as a software development lifecycle, is a
structure imposed on the development of a
software product.

3
 The SDLC Activities

 Planning
 Design, implementation and testing
 Deployment and maintenance

4
 Planning
 Extracting the requirements
 Incomplete, ambiguous, or even contradictory
requirements are recognized
 Planning the total project(time/cost estimation
and resource allocation)
 Frequently demonstrating live code may help
reduce the risk that the requirements are
incorrect
 Scope Document: Analysis of the scope of the
development should be determined and clearly
stated

5
 Design, implementation and
testing
 Aim is to create the architecture of the total
system
 Describes desired features and operations in
detail, including screen layouts, business
rules, process diagrams, pseudocode and other
documentation
 Implementation is the execution of a plan
 Software engineers program the code for the
project

6
 Testing
 Software testing is an integral and important part of the software
development process

 Detect software failures so that defects may be discovered and

corrected

 Examination of code as well as execution of that code in various

environments and conditions as well as examining the aspects of code
 Verification: Process of evaluating a system or component to determine
whether the products of a given development phase satisfy the conditions
imposed at the start of that phase.
 Validation: Process of evaluating a system or component during or at the
end of the development process to determine whether it satisfies specified
requirements.

7
 Deployment
 Process that make a software system available
for use

 Consists of several interrelated activities with

possible transitions between them

 Customized according to specific

requirements or characteristics

 These activities can occur at the producer site

or at the consumer site or both

 Release, install and activate, deactivate, adapt,

update, built-in, version tracking, uninstall,
retire
8
 Maintenance
 Modification of a software product after delivery to
correct faults, to improve performance

 Take more time than the initial development

 Bug Tracking System tools are often deployed at this

stage of the process to allow development teams to
interface with customer/field teams testing the
software to identify any real or perceived issues.

 Categories:
 Corrective maintenance
 Adaptive maintenance:
 Perfective maintenance:
9  Preventive maintenance
 Software Development
Models
 Waterfall Model
 Spiral Model
 Iterative and Incremental
development
 Agile development
 Magic Box Model

10
 Waterfall Model
 The waterfall model shows a process,
where developers are to follow these
phases in order:

1. Requirements specification
(Requirements analysis)

2. Software Design

3. Integration Testing (or Validation)

4. Deployment (or Installation)

5. Maintenance

11
 Waterfall Model (contd.)
 In a strict Waterfall model, after
each phase is finished, it proceeds to
the next one.
 Reviews may occur before moving
to the next phase which allows for
the possibility of changes.
 Gate: Phase completion criteria- the
project must pass through to move
to the next phase.
 Waterfall discourages revisiting and
revising any prior phase once it's
complete.

12
 Advantages of Waterfall
Model
  

 Very simple and easy to implement

 Well suited for small projects     

 Testing is inherent to each of the phases of this

model.    

 Rigid and each of the phases has certain

deliverables and a review process immediately
after a particular phase is over.

13
 Disadvantages of Waterfall
 
Model
 All requirements must be known upfront.

 It is high risk.        

 Cannot be guaranteed that one phase of this

model is perfect before we move on to the
immediate next phase in the model. 

 Not suited for long or complex projects or

projects where the requirements can
change.       

 The deliverable software is produced late

during the life cycle.

14
 Spiral Model
 Risk management at regular stages in the development cycle
 Activities:
1. Formulate plans to: identify software targets, selected to
implement the program, clarify the project development
restrictions;
2. Risk analysis: an analytical assessment of selected programs, to
consider how to identify and eliminate risk;
3. Implementation of the project: the implementation of software
development and verification;

15
 Spiral Model (contd.)

16
 Spiral Model (contd.)
 Risk-driven spiral model, emphasizing the conditions of options and
constraints in order to support software reuse, software quality can help as a
special goal of integration into the product development.

 Restrictive conditions:
 spiral model emphasize risk analysis, but require customers to accept and
believe that much of this analysis, and make the relevant response is not easy,
therefore, this model is often adapted to large-scale internal software
development.
 If the implementation of risk analysis will greatly affect the profits of the
project, then risk analysis is meaningless, therefore, spiral model is only
suitable for large-scale software projects.
 Should look for possible risks, an accurate analysis of risk, otherwise it will
lead to greater risk.

17
 Advantages of Spiral Model
   
 Strong support for Risk Analysis       
 Well suited for complex and large
projects        
 Deliverable is produced early       
 Uses prototyping as a risk reduction
technique

18
 Disadvantages of Spiral
Model
       
 High cost
 Risk Analysis very difficult       
 Not suited for small projects       
 Needs considerable Risk Assessment

19
 Which Model Should I
Choose?
Factors:
 The Scope of the Project     
 The Project Budget       
 The organizational
environment        
 Available Resources

20
 SDLC with an
example

21
 Library Management
System
 Requirements

1. This software will allow members to register.

2. Only registered members will be allowed to lend

an item from the system.

3. User can add items (Books, CD etc) to the

system.

4. System will allow searching for items in the

system based on Author name, book name, user
name etc

22
 Library Management
System (contd.)
 Design phase

1. Registration

2. Item Management

3. Lending

4. Search for Books

5. Search for Members

23
 Library Management
System (contd.)
 Registration

Database structure:

 Table Name : UsersTable

 SchemaId : Number

 Name : String (50)

 Address : String (100)

 Email : String (50)

 DateOfRegistration : DateTime

We have defined 4 fields in the table above. You can add

more fields.
24
 Library Management
System (contd.)
 Item Management
 Before we let a user to lend a book from the library, we need to keep the list of items available in the
library.
 We will develop a feature to add/edit/delete items in the library.
 An item (Book, CD etc) in the library can have the following properties:
1. Name
2. Author
3. Total number of books (we may have more than one copy of the same book)
Let us define database schema for this:
1. Id : Number (Autonumber)
2. Name : StringCount : Number
You may add more fields like Publisher Name, Book Category etc.

25
 Library Management
System (contd.)
 Lending

 This feature includes the following:

1. Allow a member to take a book from library

2. Return a book to the library

We need the following fields:

1. Id : Autonumber

2. BookId : Number - This is the ID of the book

3. UserId : Number - Id of the member who lend the book

4. DateOfLend : DateTime

26 5. DateOfReturn : DateTime- this field will filled only at the time of return
 Library Management
System (contd.)
 Search for Books
 User should be able to search for books
by Book Name, author name etc. The
results can be displayed using a datagrid.
 User must be able to select a record from
the search results.

27
 Conclusion
 Software Development Life Cycle (SDLC) is the
process of developing information systems through
analysis, planning, design, implementation,
integration maintenance and testing of software
applications. 
 SDLC is also known as information systems
development or application development.    
 Success of the SDLC process :      
 Scope Restriction        
 Progressive Enhancement        
 Pre-defined Structure        
 Incremental Planning at each of the stages

28
 Thank You

29