Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of RAD
12030142005 RAPID APPLICATION
DEVELOPMENT Contents Why Do You Need to be RAD?
What is Rapid Application Development (RAD)?
Why Do You Need to be RAD?
The History of RAD
Essential Aspects of RAD What is Rapid Application Development (RAD)? Lifecycle designed to give much faster development and higher-quality results Takes advantage of automated tools and techniques
Replaces hand-design and coding processes with automated design and coding
In addition to being more stable,RAD is a more capable process, as it is much faster and less error prone than hand coding. The History of RAD It is a process through which the development cycle of an application is expedited.
Rapid Application Development thus enables quality products to be developed faster, saving valuable resources. In response to these rigid, cascading, one-way steps of Stagewise or Waterfall Models of development, Spiral Model is introduced.
Spiral Model is a risk-driven, as opposed to code-driven, uses process modeling rather than methodology phases Tom Gilb’s Evolutionary Life Cycle is based on an evolutionary prototyping rationale where the prototype is grown and refined into the final product. The formulation of the methodology called Rapid Iterative Production Prototyping (RIPP) James Martin then extended the work done in RIPP which has become known as RAD Essential Aspects of RAD Construction - Also known as the Development Stage, this stage completes the construction of the physical application system, builds the conversion system, and develops user aids and implementation work plans.
Implementation - Also known as the Deployment Stage, this stage includes final user testing and training, data conversion, and the implementation of the application system. Requirements Planning - Also known as the Concept Definition Stage, this stage defines the business functions and data subject areas that the system will support and determines the system’s scope.
User Design - Also known as the Functional Design Stage, this stage uses workshops to model the system’s data and processes and to build a working prototype of critical system components. THANK YOU Fundamentals of the RAD methodology thus include: Fundamentals of the RAD methodology thus include: Combining the best available techniques and specifying the sequence of task that will make those techniques most effective
Using evolutionary prototypes that are eventually transformed into final product.
Using workshops,instead of interviews,to gather requirements and review design.
providing guidelines for success and describing ptfalls to avoid Methodology People The key players in a Rapid Application Development project include: Sponsor
Requirement Planning Team
User Design Team
User Review Board
Project Manager Management Achieving high-speed development is a complex process
If bureaucracy and political obstacles stand in the way or if users are not appropriately involved
Management must be totally committed to RAD in order to manage the change in culture.
They must be prepared to motivate both users and IT staff
To successfully introduce rapid development, management must pay careful attention to human motivation. Tools The RAD methodology uses both computerized tools and human techniques to achieve the goals of high-speed and high quality.
Power tools are required to overcome the problems involved with software development
These power tools can change the methods of construction by using design-automation techniques, code generation, and computer aided planning and analysis.
The power tools utilized in Rapid Application Development are Computer-Aided Systems Engineering (CASE) tools. RAD LifeCycle Peoples Sponsor - A high-level user executive who funds the system and is dedicated to both the value of the new system and to achieving results quickly.
User Coordinator - A user appointed by the Sponsor to oversee the project from the user perspective.
Requirements Planning Team - A team of high-level users who participate in the Joint Requirements Planning workshop.
User Design Team - A team of users who participate in the design workshop. This team should be comprised of both high-level users from the Planning Team and lower-level users with a more detailed knowledge of the system.
User Review Board - A team of users who review the system after construction and decide whether modifications are necessary before cutover.