32

Chapter 2 METHODOLOGY This chapter discusses the software development methodology utilized by the researcher. It presents the scope and delimitation of the study, data gathering tools, and sources of data. Software Development Methodology The Waterfall Model describes a development method that is linear and sequential. Waterfall development has distinct goals for each phase of development. This methodology abstracts the essential activities of software development and lists them in their most primitive sequence of dependency. The researcher utilized this software model because it is particularly useful for the system to be developed with the presence of its sequential stages. The whole process of software development is divided into separate process stages. The stages in Waterfall model include problem identification stage, feasibility study, requirements analysis, design, development and testing, implementation, Post implementation review and maintenance. Each stage iterates until it is completed. All of these stages are cascaded to each other so that second stage is started as and when defined set of goals are achieved for first stage

Methodology

33

and it is signed off. All the methods and processes undertaken in Waterfall Model are more visible. The Waterfall model has eight (8) stages as shown in Figure 1 below. Figure 1 Waterfall Model
Problem Identification

Feasibility Study

Requirements Analysis

Design

Development and Testing

Implementation

Post Implementation Review

Maintenance

Methodology

34

Problem Identification. At this stage before a system can be developed it is essential that the problem, which the proposed new system would solve, is clearly identified. In congruent to the study, to identify the problems of the existing processes, the researcher have requested a permission to the College Director and Head doctor (refer to Appendix A and B) to conduct a series of interview to the medical personnel and to conduct personal observation in the Medical and Dental Services (MDS) office. Upon granting the permission for the interview, the researcher utilized the interview guide (refer to Appendix C and Appendix E) to gather the problems that occur on the MDS office. Based on the collated summary of responses (refer to Appendix D and F) the problems were known. Feasibility Study. This stage aims to understand the problem and decide whether or not it is worthwhile proceeding to the next stage. With the identified problems gathered, each problem was thoroughly studied by the researcher to attest if the problems would justify the need for the development of a computer-based information system. After a thorough study done by the researcher to the problems identified which was supplemented with the data gathered from the summary of responses of the respondents (see Appendix D and Appendix

Methodology

35

F), the possibility of developing an information system would provide solutions to the problems of the MDS. Requirements Analysis. In this phase a detailed investigation of the current system is conducted to find out how it works and what is required of the new system. Aside from the interview conducted by the researcher, personal observations and document analysis was also utilized to investigate the existing processes done on the current system of the MDS. The researcher identified the processes of the existing processes along the areas on storage, access and security, and control measures. After analyzing the existing processes, the requirements needed in the proposed systems were identified. Design Stage. Before the starting of an actual coding, it is highly important to understand what is to be created and what it should look like. The requirement specifications from the third stage are studied in this stage and the design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining the overall system architecture. At this stage the researcher, prepared a blue print of the system to be developed based on the process flow of the existing processes and identified the system flow of the proposed system which includes the design for the interface

Methodology

36

for each user level, the coding structure and database design. Development and Testing. Once the design is drawn, the work is divided into modules or units and actual coding is started. The system is first developed in small programs called units, which are integrated in the next stage. Each unit is developed and tested for its functionality. Testing mainly verifies if the modules or units meet their specifications. At this stage the researcher started the coding of the proposed system by dividing the system into modules. Each module was tested to check if it had met the system requirements and if there are errors identified. Implementation. As specified above, the system is first divided in units which are developed and tested for their functionalities. These units are integrated into a complete system during implementation phase and tested to check if all modules or units coordinate between each other and the system as a whole behaves as per the specifications. After successfully testing the software, it is delivered to the customer. After a through testing on the system modules by the researcher, the modules were coordinated into the whole system. And before it is implemented a pilot testing is to

Methodology

37

be conducted to identify possible errors that might occur during the deployment. And once the errors are treated, the proposed system is now read to be implemented. Post implementation review. The project is reviewed to discover what went wrong (if there are any), otherwise a review is conducted to accurately meet the clients needs. At this stage the researcher and the medical personnel would conduct a review on what constraints does the system have, what are the problems encountered and how to resolve it, in order to come up with a recommendation for the individuals who would maintain system. Maintenance. This phase of the Waterfall Model is virtually the never ending phase. Generally, problems with the system developed, which are not found during the development stage come up after its practical use starts, so the issues related to the system are solved after deployment of the system. Not all the problems are discovered directly during the tests but sometimes they occur during implementation. Thus, maintenance is necessary. Finally this stage is the last on the waterfall model, at this stage the researcher would observe the feedback loops and allow for corrections to be incorporated into the study. For example a problem/update in the design phase

Methodology

38

requires a revisit to the specifications phase. When changes are made at any phase, the relevant documentation should be updated to reflect that change. Scope and Delimitation The study aimed to design and develop an efficient and reliable Patient Information System for Lorma Colleges. The proposed system shall have a web-based user interface which would run on an Intranet network connection. The proposed system developed would be able to provide a computer - based management of patient profile, management of patient medical records, automatic retrieval of medical history, medical and dental consultation, diagnosis and treatment, follow-up check up alerts on both the doctors and patients, back-up mechanism and report generation needed by the Medical and Dental services office However, the Patient Information System does not include the medical inventory of medicines and equipments. The respondents are the Medical and Dental Doctors, College Nurse and school patients. Data Gathering Techniques Different gathering techniques is utilized by the researcher to obtain pertinent information in the development of the system.

Methodology

39

Structured Interview. This technique was utilized by the researcher to specifically identify the existing processes in the PIS, the problems encountered by the Medical and Dental Services Office and to identify the requirements needed in the development of the proposed system. An interview guide was develop specifically for the medical personnel and school patients. Document Analysis. This technique was chosen by the researcher to analyze, review and study the usability of the forms which are being utilized by the Medical personnel for the purpose of identifying the input and output of the proposed system. The following medical forms reviewed are Annual physical examination form (See Appendix H for sample), Employees medical profile form (See Appendix I for sample), Dental health record form (See Appendix K for sample) and Consultation form (See Appendix J for sample). Observation. This was conducted by the researcher to gain information on the existing procedures of the Medical and Dental Services of the college to suffice the additional data needed for the system. Sources of Data With the series of interview conducted by the researcher, the main source of data are the medical personnel which comprises the college physician, college

Methodology

40

dentist and college nurse. To supplement the interview with the medical personnel, the researcher conducted a personal observation on the existing processes. And to attest the interview and observation, the researcher randomly interviewed the school patients. In order to gain the necessary data from the school patients, the researcher utilized the slovins formula to get the number of respondents for sampling. Based on the slovins formula the following are the results: a. Employee respondents N=

n= 192 employees

b. Student repondents n=

n= 345 students

Methodology

41

Table 1 Summary of Respondents Respondents Lorma Medical and Dental Doctors School Nurse/Clinic Personnel Students Employees (teaching and non-teaching) Total No. of Respondents 2 1 345 192 540