1.1Purpose and Scope3
1.2Rapid Application Development3
1.2.2Rapid Application Development Model5
1.2.3Martin’s Approach to RAD8
1.2.4Aspects of RAD10
1.2.5Advantages and Disadvantages of RAD13
List of Figures
Figure 1: Software Engineering a layered Technology 1
Figure 2: Waterfall Model 3
Figure 3 : RAD Model 7
Figure 4: Martin’s Approach8
Figure 5 : Rapid Development 13
Software Engineering’s definition as developed by IEEE is ‘The application of a systematic, disciplined, quantifiable approach to the development, operation and maintenance of software; that is the application of engineering to software. ’
Figure 1: Software Engineering a layered Technology 
Software Engineering is a layered technology. The basis of software engineering is the quality focus. Process layer is the foundation of software engineering which helps in holding the technology together resulting in developing quality software. Methods provide the technical support for building the software. Tools provide automated and semi- automated support for methods and process. The software process is established by defining activities that are applicable to all the software development cycle regardless of the complexity.
A process model for software engineering is chosen based on the nature of the project and application, the methods and tools to be used, and the controls and deliverables that are required. Software engineering work at many different levels of resolution, It can be used at the macro level when the entire application is considered, at a mid-level when program components are being engineered, and even at the line of code level. There are various process models for software engineering. Each model has their own characteristic that assist in controlling and co-ordination the real software, but the core characteristic is somewhat the similar. Following is the list of process models
• The linear Sequential model
• Prototype Model
• Rapid Application Development model(RAD)
• Evolutionary Software Process model
o The Incremental model
o Spiral Model
o Concurrent Development Model.
2 Purpose and Scope
The purpose of this document is to understand Rapid Application Development model in software development resulting in understanding where RAD model can be utilized to its fullest. In the document we would be covering how classic waterfall model work, how RAD is different along with the important aspects of RAD along with pros and cons of the RAD approach.
3 Rapid Application Development
1 Waterfall model
Classic life cycle or waterfall model
Waterfall model follows a sequential approach to software development which progresses through analysis, design, coding, testing and support. [pic]
Figure 2: Waterfall Model 
The system view is essential when software must interact with other elements such as hardware, people etc. System engineering and analysis encompass requirements gathering at the system level with a small amount of top level design and analysis. Information engineering encompasses requirements gathering at the strategic business level and at the business area level. In the requirement gathering phase or the analysis phase as mention in the above figure analysis needs to be done as to what is the required function, behavior, performance and the interface. Once all the information is gathered it is reviewed by the analyst and the Business. The design process translates requirements into a representation of the software that can be assessed for quality before coding begins. Like...