An Approach to Software
Development Life Cycle (SDLC)

             By

         Betty Baker
Table of Contents
1. Introduction............................................................................................
An Approach to Software Development Life
             Cycle (SDLC)

1. Introduction
The Software Development Life Cycle (S...
2.3 Coding

During the coding phase, the software is written. Depending upon the complexity
of the design, this phase cons...
3.2 Coding

The coding phase consisted of phases referred to as Mini Code Locks. A mini
code lock was a snapshot of the co...
Upcoming SlideShare
Loading in …5
×

An Approach To Software Development Life Cycle

1,992 views
1,905 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,992
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

An Approach To Software Development Life Cycle

  1. 1. An Approach to Software Development Life Cycle (SDLC) By Betty Baker
  2. 2. Table of Contents 1. Introduction......................................................................................................................3 2. Waterfall Approach..........................................................................................................3 2.1 Requirements.............................................................................................................3 2.2 Design........................................................................................................................3 2.3 Coding........................................................................................................................4 2.4 Test.............................................................................................................................4 2.5 Maintenance...............................................................................................................4 3. Modified Implementation................................................................................................4 3.1 Systems Engineering..................................................................................................4 3.2 Coding........................................................................................................................5 3.3 Test.............................................................................................................................5 3.4 Maintenance...............................................................................................................5 2
  3. 3. An Approach to Software Development Life Cycle (SDLC) 1. Introduction The Software Development Life Cycle (SDLC) can be implemented in an organization in many ways. In this document, I will explain the phases of the Waterfall approach and explain how one organization implemented a modified version of this process. 2. Waterfall Approach One approach (commonly referred to as the Waterfall approach) consists of five phases: Requirements, Design, Coding, Test and Maintenance. 2.1 Requirements The Requirements Phase is comprised of gathering requirements, writing the scope document and preliminary Requirements Specification, reviewing the specification with the customers, preparing the final Requirements Specification, and gaining key stakeholder approval for the Requirements Specification through a formal Requirements Review. 2.2 Design In the Design phase, the Requirements Specification is used as the basis for the Design Specification. The Design Specification explains how the requirements will be implemented. If the software requires user interaction, a storyboard may be used to help determine the design. If the software does not require user interaction, a flow chart may be all that is needed. The Design Specification will also include information on programming languages, platforms and operating systems that will be used for the application. 3
  4. 4. 2.3 Coding During the coding phase, the software is written. Depending upon the complexity of the design, this phase consists of unit testing by individual developers, and various levels of integration testing by subsystem owners. 2.4 Test During this phase, full system test is performed to insure that the system performs to specification. The test specifications should have been completed in the prior phases for use during system test. 2.5 Maintenance During the maintenance phase, the software is used in production. Issues with the tool and new requirements are captured in a ticketing system and reviewed for implementation in future releases. 3. Modified Implementation One modified implementation of the Waterfall approach consists of four phases: Systems Engineering, Coding, Test, and Maintenance. 3.1 Systems Engineering The Systems Engineering phase combined the Requirements and Design phases. In this phase, requirements for new features and bug fixes were elicited from the customer. Additional requirements were gathered from existing requirements in the requirements ticketing system. Scope documents and Systems Engineering Specifications were created that documented the requirements and included user implementation details that would typically be included in the design phase. 4
  5. 5. 3.2 Coding The coding phase consisted of phases referred to as Mini Code Locks. A mini code lock was a snapshot of the code at a particular date in the complete coding cycle. Each release typically consisted of two mini code locks and a final code lock. 3.3 Test During the test phase, an Integration and Test team performed system test on the complete system. This phase began after the first mini code lock. The integration and test team reset the software baseline after each mini code lock date. The final test was run against the final code lock. 3.4 Maintenance This phase is the same as the Maintenance phase in the standard Waterfall approach defined in the approach defined above. 5

×