Rapid Application Development (in 2003)
•Télécharger en tant que PPTX, PDF•
1 j'aime•683 vues
This is a presentation created in 2003 on Rapid Application Development, a methodology evolved from Structured Systems Analysis and Design & Waterfall models which tend to focus on planning work tasks while RAD focuses on development and prototyping. Note: 12 years later, in 2015, the prevailing methodologies include Agile models which further optimize cutover from requirements-to-solutions in a feature-driven cross-functional team. Although Agile is a solid concept on its own, the actually implementation of a project lifecycle involves many of the same key concepts as RAD. This is further detailed in the 1993 book, “Inside RAD: How to Build a Fully Functional System in 90 Days or Less”, a journal of an actual 90 day project using RAD.
Recommandé
Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
Rapid Application Development (in 2003)
- 1. Mary Irene Paras Manay CIS321A - systems analysis and design
- 2. RAPID APPLICATION DEVELOPMENT A process for developing a system… a METHODOLOGY.
Notes de l'éditeur
- 01 - RAD Hello. This is a presentation created in 2003 on Rapid Application Development, a methodology evolved from Structured Systems Analysis and Design & Waterfall models which tend to focus on planning work tasks while RAD focuses on development and prototyping. Note: 12 years later, in 2015, the prevailing methodologies include Agile models which further optimize cutover from requirements-to-solutions in a feature-driven cross-functional team. Although Agile is a solid concept on its own, the actually implementation of a project lifecycle involves many of the same key concepts as RAD. This is further detailed in the 1993 book, “Inside RAD: How to Build a Fully Functional System in 90 Days or Less”, a journal of an actual 90 day project using RAD.
- 02 - What is RAD? RAD stands for Rapid Application Development It is a process for developing a business system… a methodology. It is based on speedy development without losing, if not gaining, quality in product. SPEED and QUALITY is achieved by three key techniques: Prototyping - which means producing results that can be demonstrated as soon as possible for feedback. Iteration - repetition; means cycling through a new prototype until the desired system is achieved. Timeboxing - since prototyping and iteration can go on forever without a deadline. Timeboxing provides one. In timeboxing, the scope of a project may change, but the deadline does not.
- 03 - Stages of a RAD Project These are the 8 stages that a project using RAD goes through. The first 3 in red and the last 1 in red are the stages that most projects generally go through. However, it is the 4 stages in the middle that distinguishes a RAD project from others.
- 04 - Plan Project The first 3 stages are pretty self explanatory. The first stage is the Plan Project Stage, in which the Project IDEA is turned into the Project Plan. The Project Plan serves as a contract between the Project Sponsor, Project Manager, and Project Team. This is what the Project Plan is made up of. Everything in it, such as the scope, objectives, risks, and standards must be discussed and defined by the Project Manager and Sponsor. The budget and schedule are also discussed and defined. Once the Project Plan is approved, the next stage can begin.
- 05 - Activate Project This stage mainly deals with equipping the project participants with knowledge about the project and readily available resources. These resources include the Project Image which is created when informing the participants & stakeholders about the project, the environment that the project will be completed in, and a project team that is trained to do the job.
- 06 - Control Project The control stage is for managing the project and its team. This is done by the Project Manager. This is important for two main reasons: motivating participants to get work done and for monitoring to make sure work is done in time and with quality. Assignments are given at this point and if there are any problems, they are dealt with. The output for this stage is the Project Results, which is not only composed of the Project Plan and Project Resources, but also the tasks, the progress, team evaluation, and risk assessment. Everyone is welcome to put in their own suggestions for the better of the project.
- 07 - Now for the stages UNIQUE to Rapid Application Development Requirements Planning User Design Rapid Construction Transition
- 08 - Requirements Planning This is where the requirements for the system, as opposed to the project, are defined. To avoid misunderstanding of the system goals, the business management and Information Systems management meets to make sure they both have an agreed understanding of the goals. The Requirements Planning stage is completed in a series of workshops. The information produced in these workshops is all kept in a repository with the help of Integrated-Computer Aided Systems Engineering tools. The workshops do not generate paperwork. Firstly, the current system is analyzed. This is done by a RAD Workshop Leader. He familiarized himself with the system and information in the repository. Then, in a JRP (Joint Resource Planning) workshop, he meets along with managers who will be affected by the system (end-users) and defines the system requirements, during which an outline for the system area model is built and the system scope is defined. The cost and schedule for system development are then estimated and the results of the workshop are handed over to the Executive Sponsor of the project. If he approved, the project moves on to User Design.
- 09 - User Design User Design is just that - end-users designing the system. The business processes and data associated with the proposed system are analyzed. Procedures in the system structure are developed as automated or manual. Possible dialogs and screen layouts are developed for the most important procedures. and finally, the Transition Plan for changing the current system into the new is developed.
- 10 - Rapid Construction In this stage, the design of the proposed system output in the previous stage is turned into an accepted business system. First, software to implement the propose system is created and tested. Then, the actual system is built using that software. All this is done by repeating the cycle of generating, modifying, and testing code until the system is complete. After an accepted business system is made, the team prepares for the next stage
- 11 - Transition The main purpose of this stage is to install the business system created in the previous stage into the business. Developers train future users of system on how to operate it. They convert data that needs to be converted for integration into the new system. And they install the new system, leaving the business with a new fully operating business system.
- 12 - End Project Although the business system is now in operation. This stage is still necessary to officially end the project. A completion report is prepared and project results are turned over to the sponsor. Also, resources that were used in the project are released for use in other projects and what not. The Completion Report consists of all the information involving the project. It contains the Project Results, which were updated throughout the project and containing the progress of the project. It contains all the technical information regarding the system structure. And it contains lessons learned during the project, the final numbers, and evaluation on the project Team.
- 13 - A project for RAD? SCOPE: focused and goals clear DATA: must pre-exist. If data capacious amounts of data need to be analyzed or created, it can't be used. DECISION-MAKING: be made by a small network of people that are readily available. TEAM-SIZE: small size of six or less TECHNOLOGY: defined technology to be used. It should be familiar to the developers and tested. REQUIREMENTS: the technology being used must be capable of meeting the expected requirements.