RAD And V Models of SDLC

SDLC - Software Development Life Cycle

What is SDLC ?
SDLC is a structured process that aims at developing high quality software, at the lowest cost with shortest production time. International standard for software lifecycle process is defined in ISO/IEC 12207.

SDLC Stages:

1. Plan
2. Design
3. Implement (Develop)
4. Test
5. Deploy
6. Maintain

SDLC Models:

1. Waterfall Model (1970s to 90s)
2. Prototyping Model
3. Iterative Model
4. Spiral Model
5. V-shaped Model
6. Agile
7. Scrum
8. Kanban

V-shaped Model
This model is also known as Verification and Validation model, and is an extension of Waterfall model with testing phase integrated in each SDLC stage. Thus, in this model, Testing and Development goes in Parallel.

Requirements <----------> Acceptance Testing
Specification <--------> System Testing
Architectural Design <------> Integration Testing
Detailed Design <-------> Unit Testing
< Coding >

The coding phase connects validation phase and verification phase.

Pros:

• Highly disciplined model, easy to understand and manage
• Effective for projects where requirements are fixed and well understood

Cons:

• Less adaptive to change
• Not appropriate for large and complicated projects
• Working software is produced towards the end only

RAD Model
RAD (Rapid Application Development) is a combination of Prototyping and Iterative models. In this model a working model of the product is rapidly developed and iterated to fit the requirement of the customer. This also means the writing of the software phase itself involves collecting requirement for the development phase.
In RAD model there is minimal planning as the product changes rapidly with each iteration. Unlike V-shaped model where the working product is only obtained towards the end, in RAD model workable product (prototype) is delivered on every iteration.

• Phases of RAD
• Business modeling
• Data Modeling
• Process Modeling
• Application Generation
• Testing and Turnover

These phases are iterated over and over until the required product is reached.

Pros:

• Highly adaptive to change
• Reduced development time
• Least planning required
• Feedback oriented

Cons:

• System must be modular to be iterative
• High cost for smaller projects due to multiple iterations
• Demands user's involvement
• Highly skilled developers needed

DevOps Internship Assignment | Week 1_