Advantages of RAD Software Development
- The time required to develop the software is drastically reduced due to a reduced requirement analysis business requirements documentation and software requirement specification) and planning stage.
- All the software prototypes produced can be kept in a repository for future use. The re-usability of the components also enhances the speediness of the process of software development.
- It is much easier for a project manager to be accurate in estimating project costs which of course means that project cost controls are easier to implement and manage as well.
- It is a big cost saver in terms of project budget as well as project time and cost due to re-usability of the prototypes.
- If a component is being picked for the repository, it is already tested and hence need not be tested again. This helps in saving time required for testing.
- The project management requirements are collected in a dynamic manner. Every time there is a prototype ready, requirements are studied and matched. If there are any additional requirements, these are then included in the next prototype built.
- There is a strong and continuous participation of the project sponsor who keeps giving feedback in the whole process. Hence the end user satisfaction level is higher when the end result is produced.
- It promotes better documentation through written test cases.
Disadvantages of RAD Software Development
- This method may not be useful for large, unique or highly complex projects
- This method cannot be a success if the team is not sufficiently motivated and nor is unable to work cohesively together.
- Success depends on the extremely high technical skills of the developers.
- There are times when the team ignores necessary quality parameters such as consistency, reliability and standardization. Hence this can make project quality management hard to implement during the project management life cycle