The RAD method of software development structures the life cycle of the project in five phases (including 3 systemics). Initialization prepares the organization and determines the scope and terms of communication. The framework defines a space for objectives, solutions and resources. The design models the solution and validates its systemic coherence. Construction is realised in an active prototype (permanent validation). The completion is reduced to a final quality control at the pilot site.
Initialization means preparation of the organization and communication. This phase allows the team to set the overall project scope, structure the work topics in themes, select the relevant stakeholders and initiate a dynamic project. This phase is about 6% of the project supported.
Framing is analysis and expression of the requirements. The requirements specification is the responsibility of users. They express their needs during group interviews. It is generally expected there will be 2 to 5 days of sessions per committee (theme). This phase is about 9% of the project.
Users are also involved in design and modeling. They are involved in refining and validating organizational models: flux, treatment, data. They also validate the first level prototype with ergonomics and kinematics of general application. It is expected there will be between 4 and 8 days of sessions per commission. This phase represents about 23% of the project. During the design phase, the parallelization of the work is possible.
Construction is implementation and prototyping. During this phase, the RAD team (SWAT) must build the application, module by module. The user continues to participate actively in the detailed specification and validation of prototypes. Several iterative sessions are needed. This phase is about 50% of the project. Beginning with the construction phase, to the parallelization of the work there can be added serialization. \
Completion is receipt and deployment. Partial revenues having been obtained in the previous step, it is needed at this stage to formalize a global delivery and transfer system in operation and maintenance. This phase represents about 12% of the project.
The ZD Milestone (Zero Defect) is an integration of the iteration technically and functionally validated daily. The FOCUS (or SHOW) is a presentation of the iteration of of the delivery just ended. This demonstration is performed by the user or users involved in the prototyping bound for all other players in the project. To push the quality of the code to the extreme, these steps can be replaced by the XP practices of software engineering.
The RAD method, without being bound to tools, recommends the use of programming tools for graphical user interface (CASE), which allow for quick prototypes. In this regard, we must not confuse the RAD method (which comes from the current Agile approaches) which seeks functional application quality and technique, with RAD tools, including the automatic generation of code often called "dirty".
Usually this approach to development involves trade offs between usability, functionality, and speed of execution. The reduced end user functionality arises from a more focused project, and results in reduced complexity. There is also a greater emphasis on simplicity of design and usability of the GUI.
Written by Lawrence Reaves for UDig - http://www.udig.com - providing effective hiring strategies and recruitment pinciples to place the best IT candidates in rewarding positions. We learn about potential employees as people beyond their techincal skills. Call 1-800-259-8344 to see how we can help.
EasyPublish this article: http://submityourarticle.com/articles/easypublish.php?art_id=280252