Scribd
Upload
9 views2 pages

Rapid Application Development Methodology

This document summarizes a project design that uses Rapid Application Development (RAD). RAD focuses on processes over planning and uses fast prototyping and feedback to develop efficient and effective systems quickly. The RAD methodology consists of four phases: requirements planning to define overall needs, user design where users and developers collaborate to create a design, construction where an interactive process allows changes as the program is developed, and cutover which is the implementation and testing stage.

Uploaded by

Mikee Trinidad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views2 pages

Rapid Application Development Methodology

This document summarizes a project design that uses Rapid Application Development (RAD). RAD focuses on processes over planning and uses fast prototyping and feedback to develop efficient and effective systems quickly. The RAD methodology consists of four phases: requirements planning to define overall needs, user design where users and developers collaborate to create a design, construction where an interactive process allows changes as the program is developed, and cutover which is the implementation and testing stage.

Uploaded by

Mikee Trinidad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Project Design

This study is based in Rapid application development (RAD). It is a software


development system which focuses on processes instead of planning. This
methodology is on a fast phase and its feedback will also be their instrument for
effective and efficient system. This method is more on prototyping. It is basically
requirements planning, user design, construction, and cut over or implementation. RAD
approach is more on adaptability to cope with users needs.
The RAD methodology consists of four phases:
1.

Requirements Planning. This phase is the preliminary system design analysis


which overall requirements for the system are defined, a team is identified, and
feasibility is determined. It is very important because this will determine the needs of
user.

2.

User Design. This phase is the creation of the systems design. Users with the
system analysts, designers and programmer collaborate in a joint application
development to interactively create a design that will fit the business and its users. The
session gets all of the stakeholders together to have a structured discussion about the
design of the system. Application developers also sit in on this meeting and observe,
trying to understand the essence of the requirements.

3.

Construction. This phase is the application after the planning and the creation of
design. This is an interactive process, and changes can be made as developers are

working on the program to distinguish the appropriate system to developedw.

4.

Cutover. This phase is the implementation stage. It is tested accordingly to what


it is expected to provide. The new system prototype will require documentation and
attention to provide feedback about the process.

You might also like