Oose

Q)Explain in detail RAD software life cycle model [M-2012]
(Rapid Application Development Model)
Ans:
Builds on the Incremental model with emphases on short development cycle.
 In other words high speed waterfall model
 Components are build using this model as a fully functional units in a relatively short time
 It assumes that the system can be modularized
 RAD will fail if you don’t have strong and skillful teams
 High performance might be an issue
The Phases of RAD Model
 Business modeling.
 The information flow among business functions is modeled in a way that answers the following questions:
 What information drives the business process?
 What information is generated?
 Who generates it?
 Where does the information go?
 Who processes it?
 Data modeling.
 The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business.
 The characteristics (called attributes) of each object are identified and the relationships between these objects defined
 Process modeling.
 The data objects defined in the data modeling phase are transformed to achieve the information flow necessary to implement a business function.
 Processing descriptions are created for adding, modifying, deleting, or retrieving a data object.
Drawbacks of RAD Model
 For large but scalable projects, RAD requires sufficient human resources to create the right number of RAD teams.
 RAD requires developers and customers who are committed to the rapid-fire activities necessary to get a system complete in a much abbreviated time frame. If commitment is lacking from either constituency, RAD projects will fail.
 Not all types of applications are appropriate for RAD. If a system cannot be properly modularized, building the components necessary for RAD will be problematic. If high performance is an issue and performance is to be achieved through tuning the interfaces to