Software Engineering | RAD Model vs Traditional SDLC
Detailed explanation of RAD model can be read here.
| RAD | Traditional SDLC | |
|---|---|---|
| 1. | Stages are not well defined. | Structured Methodology and well-defined stages. |
| 2. | Different stages of application development can be reviewed and repeated as the approach is iterative. | Follows a predictive, inflexible and rigid approach for application development. |
| 3. | The use of automated RAD tools and techniques enable faster and easier prototypes which are then used to develop the final product. | Prototyping is difficult and requires more time and effort. |
| 4. | It is not necessary to know all the requirements beforehand. | All the requirements should be known before starting the project due to rigidity of the models. |
| 5. | Easier to accomodate changes. | Difficult to accommoadate changes due to sequencial nature of models |
| 6. | Extensive customer feedback leading to more customer satisfaction and better quality of final software. | Limited customer feedback. |
| 7. | It involves minimal documentation. | Stringent and extensive documentation of the entire project process is necessary. |
| 8. | Separate small teams can be assigned to individual modules. | As there is no modularisation, a larger team is required for different stages with strictly defined roles. |
| 9. | Generally preferred for projects with shorter time durations and budgets large enough to afford the use of automated tools and techniques. | Used for projects with longer development schedules and where budgets do not allow the use of expensive and powerful tools. |
| 10. | Use of reusable components helps to reduce the cycle time of the project. | The use of powerful and efficient tools requires highly skilled professionals. |
Recommended Posts:
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.
