This chapter presents the methodology used by the researcher to obtain results for the study. It includes the research design, SDLC used, the data gathering procedure, research instrument, and the statistical tools that will interpret and analyze tallied and tabulated data.
The study is classified under the descriptive method of research since the bases of its findings are on the prevailing perception and reactions of the beneficiaries. The process of descriptive research goes beyond mere gathering and tabulation of data. It involves the elements or interpretation of the meaning or significant of what is described. Thus description is often combined with the comparison and contrast involving classifications, interpretation and evaluation. It involves collections of data to answer questions concerning the current status of the study. With this research type, it is essential that the researcher already has a clear view or picture of the fact being studied before the data collection procedure is carried out. The researcher opted to use this research method considering the objective to obtain first hand data from the respondents. The descriptive method is advantageous for the researcher due to its flexibility; this method can use either qualitative or quantitative data or both, giving the researcher greater options in selecting the instrument for data-gathering. With the proposed study, locating items in the supermarkets would be easier and faster. Wasted time and effort of the customers especially those in a hurry would be minimized. It is important for the supermarket to gain the loyalty of its customers and with the help of the proposed product locator system, it will greatly satisfy the customers.
Method Used in Developing the Software Product
The proponents used the Rapid Application Development (RAD) approach in developing the proposed software. RAD is a software development methodology that focuses on building applications in a very short amount of time; traditionally with compromises in usability, features and/or execution speed. The term has recently become a marketing buzzword that generically describes applications that can be designed and developed within 60-90 days, but it was originally intended to describe a process of development that involves application prototyping and iterative development. If requirements are well understood and defined, and then project scope is constrained, the RAD process enables a development team to create a “fully functional system” within a very short time period. RAD reduces the development time and reusability of components help to speed up development. All function is modularized so it is easy to work with.
Figure 3.1 Rapid Application Development (RAD) Model
The structure of the RAD lifecycle is thus designed to ensure that developers build the systems that the users really need. This lifecycle, through the following four stages, includes all of the activities and tasks required to scope and define business requirements and design, develop, and implement the application system that supports those requirements. In requirements planning phase, also known as the concept definition stage, this stage defines the business functions and data subject areas that the system will support and determines the system’s scope. In user design phase, also known as the functional design stage, this stage uses workshops to model the system’s data and processes and to build a working prototype of critical system components. This stage is consisting of three more stages. First is the demonstrate stage which needs a provable result as early as possible, and then refine that result. The second one is the refine stage wherein the refinement is based on the feedback of the client and eventually from the users of system. And third, the develop stage wherein the system processes must be expressed through inputs and outputs to scope...