1.

Schedule Planning
1.1. Suggested system development methodology

Introduction

RAD first introduce on 1991 in James Martin’s book titled “Rapid Application
Development” (Andrew Powell-Morse, 2016). RAD itself is very popular among developers
since it’s a development methodology that have many tools and technique to produce or coded
application and software quickly (Techopedia, 2019). This methodology also focusing on
creating prototype before produce a final product. RAD (Rapid Application Development) is
development model that focusing on rapid or quick feedback, meaning it suits for small project
that need only short time to finish. Developers can decide or make any new update into the
project without start over to the very beginning development schedule.

This methodology is suitable for Tom and Sue’s proposed system. First, this project must
be finish immediately after being proposed to support the business process. As for that, this
methodology is suitable because RAD itself is a methodology that only need a short
development time, approximately in 3 month. Second, because this project need to finish in a
short period of time, then the developer team need to have user feedback as soon as it can. This
requirement is suitable with this methodology technique, which is this technique are focusing
on user feedback by creating prototype to be tested.

These are phases that need to follow by the developer by using the Rapid Application
Development:
 Planning Phase: During this phase, developer need to gather requirement from stake
holder and the other user. In this process, the Bickford will give the requirement
and idea for the project.
 User Design: Start for modelling the system and creating the prototype to be tested
for getting the user feedback.
 Construction: Finished with the prototype, developer team will start to design,
coding and perform some testing. To meet the requirement that already collected,
the team will perform many testing to avoid any error and bug.
 Cutover: This is the final phase in this methodology technique. In this phase, full-
scale testing will be performed as a last testing before officially release the system.
1.2. Gantt Chart