Tourism Database Management System Using Data Warehouse Approach

CHAPTER FOUR: PROPOSED METHODOLOGY
4.1    SYSTEM METHODOLOGY
For any system to be developed it must undergo some processes or stages to become a complete system. So system methodology is a scheme that is employed to structure, plan and control the way toward building up a functional system (Itinfo.am, 2016).
There are numerous methodology used in the development of project, amongst others RAD and Agile methodology will be given more consideration in order for the developer to choose and justify a preferable methodology. Once it comes to system development methodology, choosing the appropriate one depending on the type of the project poses difficulty for the developer. A well-defined meticulously followed methodology for the development of the system will ensure the completion of the project on time, under budget and according to customer specification (Mymanagementguide.com, 2010).
Agile is a system development methodology used in developing a system incrementally utilizing short iteration of 1 to 4 weeks so that the improvement is adjusted to the changing business needs. Agile methodology requires that the process of development be broken down into different section wherein each segment is handled by an individual, and not just that, the development of the project involves so many number of developers, the completion of a project is determined by how cooperative the developers are (www.tutorialspoint.com, 2016).
With the agile methodology it is imperative that there should be a scrum master who will be saddled with the responsibility of calling for several face-to-face meetings with the various developers and a representative of the organization the system is being developed for, the company representative is authorized to follow up in the interest of the organization, answer the questions of the developers in the middle of iteration. With this kind of approach the drawback of one person could affect the progress and completion of the project. But this is not same with the Rapid Application Development (RAD) (www.tutorialspoint.com, 2016). For with the various disadvantages associated with agile methodology the developer adopted Rapid Application Development methodology to develop the system.
Rapid Application Development (RAD) is a methodology to develop software/system that requires least planning for fast prototyping. Rapid Application Development (RAD) enables organizations in developing systems quicker and it likewise helps in minimizing development cost and keeps up quality of the system. This strategy is accomplished by means of chain of checked strategies to create system in a particular manner. Also, the Rapid Application Development methodology makes it conceivable to create quality products quicker with low cost, in this manner valuable assets can be saved. RAD (Rapid Application Development) can be likened as a type of agile procedure. The Rapid Application development methodology is interactive in nature. Rapid Application Development makes for the development of a high quality system. Rapid Application Development (RAD) consist of four basic phases. Each of the phases will be considered in relationship to the proposed system. The following are the four phases in Rapid Application Methodology:
1.    Requirements planning phase
2.    User design phase
3.    Construction phase
4.    Implementation phase (Naz and Khan, 2015)
4.1.1    REQUIREMENTS PLANNING PHASE
This is also known as the Model Description Phase (MDP). This phase characterizes the business
functions and data subject matter areas of knowledge that the system will bolster and decides the system's scope. The collection of data was done via the use of verbal interviews with tourism sector decision makers of the Malaysia Ministry of Tourism and Culture, staffs of ISC INNOVATORS, tourists visiting Malaysia, and department of statistics, Malaysia,. Also face to face interview with personnel in the Nigeria tourism sector to gather information required for the development of the proposed system. Additionally, Microsoft Project was created to keep the developer on track, steer clear of completion confusion of the various requirements, giving a visual course of events to beginning and completing a particular task, offers a more justifiable and paramount strategy for keeping up timescale-based task and deliverables followed on daily (Blueink.biz, 2016).
Please refer to appendix A for the graphical design of Rapid Application Development (RAD). Also refer to appendix C for the Microsoft Project plan.
Refer to appendix B for the result of interview