RAD Rapid Application Development is a methodology used in software making. It is all about being fast and at the same time developing high quality software. To achieve this planning is kept at a minimal and prototyping is done rapidly. The time saved by the reduced planning is used in writing the software and thus makes the whole process faster.
Lack of extensive planning also makes it easier to change requirements. Prototyping and structured techniques are utilized to define requirements of the users and also to design the final system. Creation starts with data models and business process models. These are developed using structured techniques. In the next stage prototyping is used to verify requirements. Sometimes this RAD approach compromises performances and functionality in exchange for faster development.
There are four phases of RAD. The first is the requirements planning phase. It combines systems analysis and systems planning both of which are phases of SDLC. IT staff, managers, users and members come together to agree on project scope, constraints, requirements and needs. The phase ends when the team agrees on these key issues and is authorized to go ahead.
The next phase is user design. Users come together with systems analyst to make prototypes and models that represent the inputs, outputs and other system processes. A combination of CASE tools and JAD techniques is used to change user needs to models that work.
Construction is the third phase. Its focus is on software and program development. It entails software creation, programming, unit integration, coding and system testing. In this phase users still continue to participate by making suggestions and changes on screens and reports as they are developed.
Cut over is the last phase of RAD Rapid Application Development. It is all about testing, conversion of data, changing to the new system and user training. It is clear this method is compressed as compared to the older techniques. Therefore a system is created and operated in a much shorter time.
Lack of extensive planning also makes it easier to change requirements. Prototyping and structured techniques are utilized to define requirements of the users and also to design the final system. Creation starts with data models and business process models. These are developed using structured techniques. In the next stage prototyping is used to verify requirements. Sometimes this RAD approach compromises performances and functionality in exchange for faster development.
There are four phases of RAD. The first is the requirements planning phase. It combines systems analysis and systems planning both of which are phases of SDLC. IT staff, managers, users and members come together to agree on project scope, constraints, requirements and needs. The phase ends when the team agrees on these key issues and is authorized to go ahead.
The next phase is user design. Users come together with systems analyst to make prototypes and models that represent the inputs, outputs and other system processes. A combination of CASE tools and JAD techniques is used to change user needs to models that work.
Construction is the third phase. Its focus is on software and program development. It entails software creation, programming, unit integration, coding and system testing. In this phase users still continue to participate by making suggestions and changes on screens and reports as they are developed.
Cut over is the last phase of RAD Rapid Application Development. It is all about testing, conversion of data, changing to the new system and user training. It is clear this method is compressed as compared to the older techniques. Therefore a system is created and operated in a much shorter time.
About the Author:
Click here for more information about What RAD Rapid Application Development Is About .
0 nhận xét:
Post a Comment