Scribd
Upload
8 views10 pages

Overview of RAD Framework Benefits

RAD (Rapid Application Development) became popular in the early 1990s. The DSDM consortium was formed in 1994 to develop management structures and an industry standard definition for RAD. RAD works well for standalone applications that use APIs/libraries and don't require high performance. It is suited for projects with narrow product distribution, constrained scope, reliability that is not critical, and strong timeboxing constraints. RAD does not work as well for projects requiring interoperability, optimal performance, or wide product distribution.

Uploaded by

Rochana Ramanayaka
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
8 views10 pages

Overview of RAD Framework Benefits

RAD (Rapid Application Development) became popular in the early 1990s. The DSDM consortium was formed in 1994 to develop management structures and an industry standard definition for RAD. RAD works well for standalone applications that use APIs/libraries and don't require high performance. It is suited for projects with narrow product distribution, constrained scope, reliability that is not critical, and strong timeboxing constraints. RAD does not work as well for projects requiring interoperability, optimal performance, or wide product distribution.

Uploaded by

Rochana Ramanayaka
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd

A Framework for RAD

DSDM (and Topics)

History of RAD
RAD became popular in early 90s DSDM consortium 1994 To produce mgt. structures and industry standard definition Made user involvement in all aspects of project

When RAD works


Applications are standalone APIs / class libraries can be used very much Performance is not critical Product distribution is narrow (in-house) Project scope is constrained

... When RAD works


Reliability is not critical Systems are easily modularizable Product is aimed at a high end IS market Project has strong micro-schedule constraints (time boxes) The required technology is fairly stable

When RAD does not work


Interoperability required, with existing programs Optimal performance required Cannot make use of high-end IS tools Product will be widely distributed (mass market) Product is life or time critical

... When RAD does not work


System cannot be modularized Performance Target of the applications maybe too high for RAD (eg. OS or computer games)

Advantages of RAD
Deliverables maybe easier to port (due to high level of abstractions) Early visibility (of final product) Greater Flexibility Reduction of Manual Coding Possibly fewer defects (due to case tool use) Reduction of Cost (time is money)

...Advantages of RAD
Shorter development cycle Standardized look and feel

Disadvantages of RAD
Tools might be expensive Harder to measure progress Maybe less efficient (not handcrafted code) Prototype may not scale up Third party components unnecessary functionality without needed functionality

...Disadvantages of RAD
Reduced features due to reuse Standardized look and feel (undistinguished)

You might also like