- RAD (rapid application development) is a concept that products can be developed faster and of higher quality through:
- Gathering requirements using workshops or focus groups
- Prototyping and early, reiterative user testing of designs
- The re-use of software components
- A rigidly paced schedule that defers design improvements to the next product version
- Less formality in reviews and other team communication
Some companies offer products that provide some or all of the tools for RAD software development. (The concept can be applied to hardware development as well.) These products include requirements gathering tools, prototyping tools, computer-aided software engineering tools, language development environments such as those for the Java platform, groupware for communication among development members, and testing tools. RAD usually embraces object-oriented programming methodology, which inherently fosters software re-use. The most popular object-oriented programming languages, C++ and Java, are offered in visual programming packages often described as providing rapid application development.
 |
Learn more about Traditional software models (RUP, V-Model, CMM, Waterfall) |
| Can traditional project management and agile development coexist?: Are traditional project managers and agile practitioners fundamentally at odds? Or can they live together and even complement each other? |
| Survey: Agile interest high, but waterfall still used by many: While there's a strong interest in new software development techniques, SearchSoftwareQuality.com's recent survey found that many still follow traditional development practices. |
  |
CMMI: Good process doesn't always lead to good quality: Having a process such as CMMI in place doesn't guarantee quality software or systems, says Bill Curtis, co-author of CMM. You can still have defects. |
| Addressing software quality issues with development models, methods: Each development model has its own practices for building quality software. The challenge is determining which one fits your needs. The resources here can help you decide. |
| Testers debate differences between waterfall, Agile test automation: Two professional testers continue the timeless debate, agile vs waterfall, which is the best methodology for test-driven software development. |
| Test-driven testing face-off: Waterfall vs. Agile: Most software test pros pick a preferred methology and stand by it, in this tip two testers square-off, one advocating for agile development, the other in the waterfall corner. |
| Solving problems with session-based test management: A veteran software tester gives real-life examples of using session-based test management in Scrum, RUP and in a completely ad hoc environment. |
| Best practices for moving testers from waterfall to agile development: Software testers moving from a waterfall environment to the agile development model don't have to be driven to the head-banging stage of frustration. |
| CONTRIBUTORS: |
Vic Berry and Anja Naumann |
| LAST UPDATED: |
15 Feb 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|

 |
More resources from around the web:
|


');
// -->



|