3.1.3 RapidApplication Development Model (RAD)The rapidapplication development approach relies on adaptability and the need to modifyrequirements in response to knowledge acquired as the project progresses.
Prototypes and rapid cycles of repetitive development are often used toaccelerate development and to benefit from early feedback from business users.After each repeat, developers can fine-tune and validate features withstakeholders. Generally, RAD’s approaches to software development have been placedless emphasis on planning and greater focus on the process.RAD is typicallydivided into four basic phases that complement the process. Planning: The first step where all developers, designers, engineersand technology personnel meet together to discuss project requirements andspecifications. The prototype needs are thus identified and agreed upon. Design: Once the design needs are collected, the prototypes andfeedback from the user experiences where they help in the design of the modeland the overall architecture of the application. Development: With design and model real work starts with development.
- Thesis Statement
- Structure and Outline
- Voice and Grammar
At this stage, basic encryption, architecture and integration with back-endservices occur. With the rapid application development model, there can beimprovements that are made according to the need of the project. Release: The final transition is where the rapid applicationlaunches. The development team moves components from the test environment toproduction.
The application is deployed where the user can now use it toincrease business efficiency.Advantages of RapidApplication Development Model•It is adaptable and flexible for changes.•It is easier to transfer delivered as scripts, high level abstractions Use intermediate symbols.
•There is a decrease in manual encryption. Because of the code generators andreuse.• Each stage in RAD provideshigh priority functions to the customer.3.
1.4 WaterfallModelWaterfall modelbasically is about tradition engineering approach that is applied to suchsoftware engineering. . It is also called the LinearChain Life Cycle Model.
The project contains a set of specific stages. At eachstage, there is a set of activities that must occur in a particular order, anda set of results called (“deliveries”) that must be produced andsigned as completed by the project manager for each stage before the next stageis started.At the end of eachcertain stage, revision and revision of anyearlier stage once completed didn’t receive any encouragement from the strictwaterfall approach.Advantages ofwaterfall model:• Simple model, easy to understand and use.• Each stage has aneasy manage outputs and a review process.
• In this process,the stages are processed and completed each time. For that they never interferewith each other.• it’s well workedfor small projects where each require is easy to understand. Disadvantages ofwaterfall model: • Oncethe application is in the testing phase, it is difficult to come back andchange something that was not wellthought out at the concept stage.• Atany work programs are such produced until late all through the life cycle.•Highly risk amount • complexobject-oriented projects are not good processed at this approach.• Notsuitable for projects with moderate to high risk requirements for change.