The structure of the RAD life cycle is designed to ensure that developers build the systems that users really need. The life cycle has four stages:
* Requirements Planning
* User Design
* Construction
* Implementation
Each stage starts only after approval from the user executive whose money is going to be spent (i.e., the Sponsor).
Maintenance dominates the cost of applications. In many organizations, software maintenance activities consume three quarters of the total Life-cycle expenditures and IT human resources. The RAD methodology must lower the cost and time for maintenance as much as for new development.
Previous : Characteristics of the RAD Development Path
Section Overview : Methodology
Overview : Table of Contents
This page was last built on April 18, 1997.