Presentation On Software Development Life Cycle (SDLC)

What is Sdlc ?

•        SDLC is the framework that describes the activities performed at each stage of a software development project. 

•        Software life-cycle defines how different phases of the life cycle are managed.

•       Software life cycle describes phases of the software cycle and the order in which those phases are executed.

Phases In Sdlc

 There are following six phases in Software development life cycle :

1. Requirement gathering and analysis
2. Design
3. Implementation or coding
4. Testing
5. Deployment
6. Maintenance
7. Business requirements are gathered in this phase.
8.   This phase is the main focus of the project managers and stakeholders. 
9.   Meetings with managers, stakeholders and users are held in order to determine the requirements like; Who is going to use the system? How will they use the system? What data should be input into the system?  What data should be output by the system? 
10.   These are general questions that get answered during this phase.

Design Phase

•        In this phase the system and software design is prepared from the requirement specifications which were studied in the first phase.

•        System Design helps in specifying hardware and system requirements and overall system architecture.

•        The system design specifications serve as input for the next phase.

Implementation / Coding 

•       On receiving system design documents, the work is divided in modules/units and then actual coding is started.

•        Since, in this phase the code is produced so it is the main focus for the developer.

•        This is the longest phase of the software development life cycle.

Testing

•       After the code is developed it is tested against the requirements to make sure that the product is actually solving the needs

  During this phase  user acceptance testing  (UAT) are done.

Deployment

•      After successfully testing the product is delivered to the customer for their use.

•       Deployment starts after the software is appropriately tested, approved for release 

 Maintenance

•      When the customers start using the developed system then the actual problems comes up and needs to be solved from time to time.

 In this process the care is taken for the developed product .

Software development models

•      Waterfall model

•       Code-and-fix model

•       Evolutionary model

•       Rapid prototyping model

•       Spiral model

Waterfall Model

•      Requirements – defines needed information, function, behavior, performance and interfaces.

•       Design – data structures, software architecture, interface representations, algorithmic details.

•       Implementation – source code, database, user documentation, testing.

Waterfall Model

Waterfall  Strengths

•        Easy to understand, easy to use

•        Provides structure for inexperienced staff

•        Sets requirements stability

•        Good for management control.

•        Works well when quality is more important than cost or schedule

Waterfall  Deficiencies

•      All requirements must be known up front

•        High risk for new systems

•        Little opportunity for customers to preview the system.