Theoretical

12 Theoretical Model This section discusses the theories and concept used in the course of designing and developing the thesis. In this study, the proponents used the Prototyping Method for the development of the project. The main goal of prototyping is to come up with a solution to the problem and to present solution in an electronic form used as a visual air to help convey to the client an assumption to the problem. It helps to provide specifications for final solution. It should be designed to specifically address the problems identified and to provide data to the customer that will be used when implementing the final solution. This method is concerned with developing different proposed concepts through software or hardware prototypes, and evaluating them. In general the process is termed ‘rapid’ prototyping. The development of a simulation or prototype of the future system can be very helpful, allowing users to visualize the system and provide feedback on it. Thus it can be used to clarify user requirements options. Later on in the lifecycle, it can also be used to specify details of the user interface to be included in the future system. Prototyping requires user involvement and allows them to see and interact with a prototype allowing them to provide better and more complete feedback and specifications. The presence of the prototype being examined by the user prevents many misunderstandings and miscommunications that occur when each side believe the other understands what they said. Since users know the problem domain better than anyone on the development team does, increased interaction can result in final product that has greater tangible and intangible quality. The final product is more likely to satisfy the user’s desire for look, feel and performance. [3]

13 Steps in Prototyping consist of four (4) steps namely: (1) Identify the user’s basic requirements. The system designer works with user only long enough to capture his/her basis information needs. (2) Develop an initial prototype. The system designer creates a working prototype quickly, using fourth-generation software, interactive multimedia, or computer aided software engineering (CASE) tools. (3) Use the prototype. The user is encouraged to work with the system in order to determine how well the prototype meets his/her needs and to make suggestions for the improvement of the prototype. (4) Revise and enhance the prototype. The system designer notes all changes the user requests and refines the prototype accordingly. After the prototype has been revised, the cycle returns to step3 and step4 are repeated until the user is satisfied. When no more iteration is required, the approved prototype then becomes an operational prototype that furnishes the final specifications for the application. Sometimes, the prototype itself is adopted as the production version of the system. [4] Figure 2 shows the Theoretical Paradigm of the study.