Project Management Presentation Rapid Application Development

Project Management Presentation Rapid Application Development By Paul Killian

What is Rapid Application Development? Rapid Application Development (RAD) is a software development process through which the development cycle of an application is expedited. Thus, RAD enables quality products to be developed faster, saving valuable resources. - The RAD process was developed initially by James Martin in 1991. - It involves iterative development and the construction of prototypes. - The RAD work breakdown structure is designed for speed. - The 3 most important RAD management techniques are: Prototyping : An approach based on creating a demonstratable result as early as possible, and then refining that result based on feedback and changing requirements. Iteration : Incremental development based on refinement Timeboxing : Focuses attention on delivery above all else. Under a timebox scope can change but delivery cannot.

What is Rapid Application Development (cont.)‏
Typically staffed with small teams
Teams usually include developers and end-users for the application
Close, daily cooperation between business people and developers
Small, iterative development cycles
Unity of vision and purpose
Informal communication
Simple project management
Working software is delivered frequently (weeks rather than months)‏
Even late changes in requirements are welcome
Regular adaption to changing circumstances
Simplicity – no desire to add extra components when not necessary
Projects developed by trusted individuals
RAD Project Common Attributes:

RAD (cont.)
An important, fundamental principle of iterative development is that each iteration delivers a functional version of the final system. It is a properly engineered, fully working portion of the final system and is not the same as a prototype. For example, the first iteration might deliver 100% of 10%, the second iteration 100% of 25%, etc.
Image Source: http://www.optaros.com/de/services/optaros_assembly_methodology

Other 'Heavyweight' Development Methods The Waterfall Method The traditional software development cycle follows a rigid sequence of steps with a formal sign-off at the complete of each step. A complete, detailed requirements analysis is done that attempts to capture the system requirements. Users are forced to sign-off on the specification before development proceeds to the next step. This is followed by a complete system design and then development and testing.

The Waterfall Method (cont.)‏ The Waterfall Method is a heavily regulated, regimented, micro-managed development process. It is seen by many as bureaucratic, slow, demeaning, and inconsistent with the ways that software engineers actually perform effective work. Agile software development practices (such as RAD) were developed as part of a reaction against the 'heavyweight' methods

Contrasting The Development Methods Image Source: http://credata.com/research/rad.html

PROs for Rapid Application Development
Increased speed development through methods including rapid prototyping, virtualization of system related routines, and other techniques.
Decreased end-user functionality (Hence reduced complexity )‏
Larger emphasis on simplicity and usability of GUI design

CONs for Rapid Application Development
Reduced scalability
Reduced features when RAD developed application prototype evolves into a finished product
Reduced features occur due to timeboxing when features are pushed to later versions in order to finish a release in a short amount of time
The data needs to already exist

When to use RAD Rapid Application Development is not appropriate for all projects - Yes: Focused scope where the business objects are well defined and narrow. - No: Broad scope where the business objectives are obscure or broad -Yes: Data for project already exists - No: Large amount of data needs to be created or inputted - Yes: Decisions can be made by a small number of people - No: Many people must be involved in decisions on the project - Yes: The project team is small - No: The project team is large, or there are multiple co-ordinated teams - Yes: The technical requirements are reasonable and well within capabilities - No: The technical requirements are tight for the resources used.

What Application Development Methods does Integrys use? Waterfall Methods or RAD Methods?

BOTH!
What Application Development Methods does Integrys use?

References http://www.creativedata.com/research/rad.html en.wikipedia.org/wiki/Rapid_application_development csweb.cs.bgsu.edu/maner/domains/RAD.htm www.gantthead.com/process/processMain.cfm?ID=2-19516-2 www.mariosalexandrou.com/methodologies/rapid-application-development.asp

Project Management Presentation Rapid Application Development

by Samuel90

Accessibility

Categories

Upload Details

Usage Rights

Statistics