THE MEDICAL GUIDANCE: THE MEDICAL WAYS OF PROPHET MUHAMMAD SAW MOBILE APPLICATION SYSTEM SITI NURATHIRA BINTI ALYASAK BACHELOR OF COMPUTER SCIENCE

Transcription

1 THE MEDICAL GUIDANCE: THE MEDICAL WAYS OF PROPHET MUHAMMAD SAW MOBILE APPLICATION SYSTEM SITI NURATHIRA BINTI ALYASAK BACHELOR OF COMPUTER SCIENCE (SOFTWARE DEVELOPMENT) WITH HONOURS UNIVERSITI SULTAN ZAINAL ABIDIN 2018

2 THE MEDICAL GUIDANCE: THE MEDICAL WAYS OF PROPHET MUHAMMAD SAW MOBILE APPLICATION SYSTEM SITI NURATHIRA BINTI ALYASAK Bachelor of Computer Science (Software Development) With Honours Faculty of Informatics and Computing Universiti Sultan Zainal Abidin, Terengganu, Malaysia AUGUST 2018

3 i

4 DECLARATION I hereby declare that this report is based on my original work except for quotations and citations, which have been duly acknowledged. I also declare that it has not been previously or concurrently submitted for any other degree at University Sultan Zainal Abidin or other institutions. SITI NURATHIRA BINTI ALYASAK Faculty of Informatics and Computing UNISZA Date: MAY 2018 ii

5 CONFIRMATION This is to confirm that this project entitled The Medical Ways of Prophet Muhammad SAW Mobile Application System was prepared and submitted by Siti Nurathira Binti Alyasak (Matric Number: BTAL ) and has been satisfactory in terms of scope, quality and presentation as partial fulfilment of the requirement for the Bachelor of Computer Science (Software Development) with honours in University of Sultan Zainal Abidin. The research conducted and the writing of this report was under my supervisor. Supervisor: EN. MOHD ISA BIN AWANG Faculty of Informatics and Computing UNISZA Date: MAY 2018 iii

6 DEDICATION In the Name of Allah, the Most Gracious and the Most Merciful. Alhamdulillah, for blessing me and giving me the opportunity to undergo and complete this final year project titled The Medical Ways of Prophet Muhammad SAW Mobile Application System. Here, my greatest appreciation goes to my beloved family that give me support as well as encouragement throughout this project. Then, I would like to take this opportunity to express my deepest gratitude to my supervisor, En Mohd Isa Bin Awang, who has always given valuable advice and encouragement at each phase throughout in developing this project successfully. I would like to thank him for giving me the opportunity to learn and work under his guidance, which has been the most memorable experience. Besides, my sincere thanks to my friends that always give support and help to finish up this project. Last but not least, I would like to thank to Faculty of Informatics and Computing for the chance to expose and explore as a degree student with this project. I would like to thank to all my lecturers in this faculty that give me a great support to complete this project. Thank you. iv

7 ABSTRACT Prophetic Medicine simply refers to the actions done and thought said by the Prophet Muhammed with regards to sickness, treatment, nutrition, and hygiene. Prophetic medical traditions exhort humans to not simply stop at following Muhammad's teachings, but encourage them to search for cures as well (OnIslam.net website, 2014). The widely use of information technology and system today urges everybody to use it. User tend to get information via net in every aspect of domains such as education, management and medical (Bhikha & Dockrat, 2015). With the growing of the information system, this medical guidance application will be built to help user to gain any cure of sickness based on the medical ways of Prophet Muhammad SAW. This application is suitable for all ages level which the data are in simple English language which can be understand by the user. Unfortunately, information about the medical ways of Prophet Muhammad SAW was mostly available in physical books. In the internet, there just a few websites that have the information which makes it hard for the user to actually found what information they are looking for. However, if all the information were put together in an application, it can assist user to search for their cure of sickness by following the medical ways of Prophet Muhammad SAW. by only using their devices. All the information was stored in the database and can be easily retrieve whenever there is internet connection. In realizing this solution, the medical guidance application system will be build using mobile computing to make it user - friendly. The application requires user to install the application and it is ready on-the-go. v

8 ABSTRAK Perubatan Nabi merujuk kepada tindakan yang dilakukan dan pemikiran yang dikatakan oleh Nabi Muhammad mengenai penyakit, rawatan, pemakanan, dan kebersihan. Tradisi perubatan nabi menasihati manusia untuk tidak hanya berhenti mengikuti ajaran Nabi Muhammad, tetapi mendorong mereka untuk mencari penawar juga (laman web OnIslam.net, 2014). Penggunaan teknologi maklumat dan sistem hari ini mendesak semua orang menggunakannya. Pengguna cenderung mendapatkan maklumat melalui jaringan dalam setiap aspek domain seperti pendidikan, pengurusan dan perubatan (Bhikha & Dockrat, 2015). Dengan semakin berkembangnya sistem maklumat, aplikasi panduan perubatan ini akan dibina untuk membantu pengguna mendapatkan sebarang penyembuhan penyakit berdasarkan cara perubatan Nabi Muhammad SAW. Malangnya, maklumat mengenai cara perubatan Nabi Muhammad SAW kebanyakannya hanya terdapat dalam bentuk buku. Di internet, hanya terdapat beberapa laman web yang mempunyai maklumat mengenai cara perubatan ini yang menjadikannya sukar bagi pengguna untuk benar-benar menemui maklumat yang dicari. Walau bagaimanapun, jika semua maklumat disusun dalam satu aplikasi, ia dapat membantu pengguna mencari kaedah penyembuhan dengan mengikuti cara perubatan Nabi Muhammad SAW dengan hanya menggunakan alat peranti mereka. Semua maklumat akan disimpan dalam pangkalan data dan boleh diperoleh dengan mudah apabila terdapat sambungan internet. Dalam merealisasikan penyelesaian ini, sistem aplikasi bimbingan perubatan akan dibina menggunakan pengkomputeran mudah alih untuk menjadikannya mesra pengguna. Aplikasi ini memerlukan pengguna untuk memuat turun aplikasi itu dan ianya boleh terus digunakan. vi

9 CONTENTS DECLARATION...ii CONFIRMATION... iii DEDICATION... iv ABSTRACT... v ABSTRAK... vi CONTENTS... vii LIST OF TABLES... x LIST OF FIGURES... xi LIST OF ABBREVIATIONS... xiii LIST OF APPENDICES... xiv 1. CHAPTER 1: INTRODUCTION INTRODUCTION PROJECT BACKGROUND PROBLEM STATEMENT OBJECTIVES SCOPES LIMITATION OF WORK EXPECTED RESULTS CHAPTER 2: LITERATURE REVIEW INTRODUCTION MOBILE APPLICATION SYSTEM EXISTING MOBILE APPLICATION SYSTEM RESEARCH RESEARCH RESEARCH CONCLUSION CHAPTER 3: METHODOLOGY INTRODUCTION SYSTEM DEVELOPMENT PROJECT METHODOLOGY CONTEXT DIAGRAM (CD) vii

10 3.5. DATA FLOW DIAGRAM (DFD) DATA FLOW DIAGRAM LEVEL DATA FLOW DIAGRAM LEVEL ENTITY - RELATIONSHIP DIAGRAM (ERD) FRAMEWORK DATABASE DESIGN SYSTEM REQUIREMENTS SOFTWARE HARDWARE CONCLUSION CHAPTER 4: SYSTEM IMPLEMENTATION AND TESTING INTRODUCTION TEST RESULTS (INTERFACE) INTERFACES Interface: Homepage Interface: Comment PATIENT MODULE Interface: Homepage Patient Interface: Register Interface: Login Interface: Edit Profile Interface: Change Password Interface: Answer Medguide Interface: List Probable Disease Interface: Description Disease Interface: Feedback Disease Interface: Medical Practitioner Interface: List Feedback ADMINISTRATOR MODULE Interface: Homepage Admin Interface: Login Interface: Edit Profile Interface: Change Password Interface: Change Password User Interface: Add Medical Practitioner Interface: List Medical Practitioner viii

11 Interface: Add Disease Interface: List Disease Interface: Manage Symptoms Interface: Report TESTING PATIENT MODULE Test Case for Registration Test Case for Login Test Case for Edit Profile Test Case for Change Password Test Case for Answer Medguide Test Case for Medical Practitioner Test Case for Feedback ADMINISTRATOR MODULE Test Case for Login Test Case for Edit Profile Test Case for Change Password Test Case for Change Password User Test Case for Manage Medical Practitioner Test Case for Manage Symptoms Test Case for Manage Disease Test Case for Report CONCLUSION CHAPTER 5: TESTING AND RESULT INTRODUCTION PROJECT CONTRIBUTIONS PROJECT CONSTRAINTS AND LIMITATION FUTURE WORK CONCLUSION REFERENCES ix

12 LIST OF TABLES Table 3.1 Process and Data Store Table 4.1: Test Case for Registration Table 4.2: Test Case for Login Table 4.3: Test Case for Edit Profile Table 4.4: Test Case for Change Password Table 4.5: Test Case for Answer Medguide Table 4.6: Test Case for Medical Practitioner Table 4.7: Test Case for Feedback Table 4.8: Test Case for Login Table 4.9: Test Case for Edit Profile Table 4.10: Test Case for Change Password Table 4.11: Test Case for Change Password User Table 4.12: Test Case for Manage Medical Practitioner Table 4.13: Test Case for Manage Symptoms Table 4.14: Test Case for Manage Disease Table 4.15: Test Case for Report x

13 LIST OF FIGURES Figure 3.1 Context Diagram (CD) Figure 3.2 Data Flow Diagram (DFD) Figure 3.3 Manage User Figure 3.4 Manage Medical Practitioner Figure 3.5 Manage Symptoms Figure 3.6 Manage Disease Figure 3.7 Answer MedGuide Figure 3.8 Entity - Relationship Diagram (ERD) Figure 3.9 Framework Of The Application System Figure 3.10 DB fypmed Of The System Figure 3.11 Table disease In The DB Figure 3.12 Table feedback In The DB Figure 3.13 Table login In The DB Figure 3.14 Table lookup In The DB Figure 3.15 Table medguide In The DB Figure 3.16 Table symptoms In The DB Figure 3.17 Table user In The DB Figure 3-18 Table comments In The DB Figure 3-19 Table comments In The DB Figure 4-1 : Main Homepage Figure 4-2 : Comment Figure 4-3 : Homepage Patient xi

14 Figure 4-4 : Register Form Figure 4-5 : Login Form Figure 4-6 : Edit Profile Form Figure 4-7 : Change Password Figure 4-8 : Answer Medguide Form Figure 4-9 : List Probable Disease Figure 4-10 : Description Disease Figure 4-11 : Feedback Disease Form Figure 4-12 : Medical Practitioner Display Figure 4-13 : List Feedback Figure 4-14 : Homepage Admin Figure 4-15 : Login Form Admin Figure 4-16 : Edit Profile Admin Figure 4-17 : Change Password Admin Figure 4-18 : Change Password User Figure 4-19 : Add Medical Practitioner Form Figure 4-20 : List Medical Practitioner Figure 4-21 : Add Disease Form Figure 4-22 : List Disease Figure 4-23 : Manage Symptoms Figure 4-24 : Disease Report Figure 4-25 : Patient Report Figure 4-26 : Feedback Disease Report Figure 4-27 : Comment Report xii

15 LIST OF ABBREVIATIONS CD Context Diagram DFD Data Flow Diagram ERD Entity Relationship Diagram FYP Final Year Project DB Database MEDGUIDE Medical Guidance FYPMED Final Year Project Medical xiii

16 LIST OF APPENDICES Appendix 1: Gantt Chart of the Project xiv

17 1. CHAPTER 1: INTRODUCTION 1.1. INTRODUCTION The widely use of information technology and system today urges everybody to use it. Nowadays, user tend to get information via net in every aspect of domains such as education, management and medical. With the growing of the information system, this medical guidance application will be built to help user to gain any cure of sickness based on the medical ways from the Holy Quran and the Sunnah of Prophet Muhammad (SAW). Islam is a complete and perfect way of life that combines the physical and spiritual health of the mankind, whoever studies its teachings can very clearly understand this fact (Al-Jauziyah, 2003). All of its teachings are natural. It keeps a clear vision about all the matters of a human life, and gives perfect directions to make it healthy, physically and spiritually (Maktaba Dar-us-Salam, 2010). Some of the important narrations of the Messenger of Allah related to sickness are narrated in Sahih Muslim: from the hadith of Abu al Zubayr and from Jabir bin Abdullah it relates as follows: for every sickness that Allah created, He also created a remedy, and when the remedy to the disease is found the patient is cured by permission of Allah SWT. (Ozturk, 2016). 1

18 1.2. PROJECT BACKGROUND The Medical Guidance: The Medical Ways of Prophet Muhammad SAW is responsible to gives user a different perspective from a general doctor. Not meant as a replacement for medical treatments or as a diagnostic tool, this medical guidance helps by giving out an idea about a probable disease and how to treat them naturally. This application is best used to consult clinical issues for an Islamic perspective on General Health. It is not just that but patient can also combine the treatment suggested by their physician with a spiritual treatment. This application is suitable for all ages level which the data are in simple English language which can be understand by the patient. This medical guidance application system is developed using Hypertext Pre-processor (PHP) for web and mobile development and MySQL as the database platform. Mobile computing techniques are implemented in the system in order to make it user - friendly. The application requires patient to install the application and it is ready on-the-go. 2

19 1.3. PROBLEM STATEMENT Usually, information about the medical ways of Prophet Muhammad (SAW) was mostly available in physical books. Mostly the books are thick and heavy to be carried anywhere. Patient need to spend a lot of time reading the books in the library and they need to read page by page to know the information. In the internet, there just a few websites that have the information. This website for example like blogs majority were focused on food consumes. This makes it hard for the patient to actually found what information they are looking for. This application will be built to make it user friendly as people tend to use their smartphone in finding resources and will be easier to be carried anywhere OBJECTIVES I. To design a guidance for the patient to look the information about medical ways of Prophet Muhammad (SAW) II. III. To develop the alternative references other than using physical books. To test usability of mobile application in the system. 3

20 1.5. SCOPES The proposed system is developed using Web server and Mobile Computing. The scope will be explained from patient aspect of view and system function. This system considers patient and admin of The Medical Guidance: The Medical ways of Prophet Muhammad SAW as users. The scope of the proposed system is divided into three users as follow: I. Patient Able to register and login as Patient user Able to update profile and change password Able to answer a simple question (med guide) Able to view the description and cure of disease Able to make feedback on the disease Able to view medical practitioner II. Admin Able to login as Admin user Able to update profile and change password Able to manage the medical practitioner Able to manage disease and symptoms Able to view feedback from the user Able to view report of the system 4

21 1.6. LIMITATION OF WORK There are some features that is not cover in this system: I. Patient user cannot edit the content in the application and see the feedback from other patient. II. III. IV. Only admin can see feedback from the patient user. Patient only can access this application using smartphone. Only admin can access this application through web server and mobile phone. V. This proposed system does not rate the feedback EXPECTED RESULTS The expected results of the propose system is: I. To be one of the alternative reference in information technology. II. III. To be the guidance to the patient despite of their sickness. To blow the information to all patient despite of their age level. 5

22 2. CHAPTER 2: LITERATURE REVIEW 2.1. INTRODUCTION A literature review of The Medical Guidance: The Medical Ways of Prophet Muhammad SAW contains the description of previous research of Medicine of the Prophet. Based on the literature review, it increased the knowledge and gave deeper understanding of the proposed application MOBILE APPLICATION SYSTEM A mobile application, most commonly referred to as an app, is a type of application software designed to run on a mobile device, such as a smartphone or tablet computer. Mobile applications frequently serve to provide users with similar services to those accessed on PCs. Apps are generally small, individual software units with limited function. A mobile application also may be known as an app, web app, online app, iphone app or smartphone app. A mobile website is similar to any other website in that it consists of browser-based HTML pages that are linked together and accessed over the Internet (for mobile typically WiFi or 3G or 4G networks). The obvious characteristic that distinguishes a mobile website from a standard website is the fact that it is designed for the smaller handheld display and touch-screen interface. Increasingly, responsive web design is becoming the new standard for websites that are not only mobile-friendly, but that can scale to any sized device - from desktop down to tablet and handheld smartphones. 6

23 2.3. EXISTING MOBILE APPLICATION SYSTEM RESEARCH 1 AUTHOR : Mohammed Feradh Zain (Ossys.org) DATE : updated (January 8, 2018) TITLE : Prophetic / Islamic Medicines in Islam: IslamicMed DESCRIPTION : This app has categorized the principle of Prophet (SAW) medication into 5 concepts which are the true principals of SHIFA / Healing which cure both the heart (soul) & body: 1. Healing by Belief 2. Healing by Aa maal-e-saalehaat, Salaat, Sadaqah, Fast, Quran, Zikr, Duaas & Ruqya, Husn-e-Khulq, abstaining from sins, Istighfaar, etc 3. Healing by the foods 4. Healing by the herbs 5. Healing by HIJAMAH STRENGTHS : Gives perfect directions to make it healthy, physically and spiritually Have all description in details Using many languages in listing the issues WEAKNESSES : Too much text (less pictures) Not compatible with all devices 7

24 8

25 RESEARCH 2 AUTHOR : Bdappsstudio DATE : updated (October 9, 2017) TITLE : Islamic Medicines, Islamic treatment DESCRIPTION : This application brings you some of the natural prophetic medicines in details, which includes Honey, Black Seed, sienna, Olive, Barley and so on. Each of these medicines are discussed, their descriptions, evidence from Quran and Sunnah, constituents, medical uses as well as applications are clearly stated STRENGTHS : Have all description in details Give information about natural remedies in details WEAKNESSES : Only consists medicine using natural remedies 9

26 10

27 RESEARCH 3 AUTHOR : Darussalam Publishers and Distributors DATE : April 5, 2016 TITLE : Islam & General Health Issues DESCRIPTION : A comprehensive hand book for General Health Issues and their cure with reference from Quran and Hadith. This precise and to the point app helps you easily scroll through Health Issues, their Symptoms and Islamic Cures. A must has app for daily health issue references STRENGTHS : Have all description in details Have overview of every issue Can share the information with other application WEAKNESSES : Has been closed down as there is error occur. 11

28 12

29 2.4. CONCLUSION As a conclusion, this chapter discussed two things. There is discussion about mobile application system and the existing application system in order to prove this project functionality. 13

30 3. CHAPTER 3: METHODOLOGY 3.1. INTRODUCTION This chapter explains the methodology design that was used in order to develop this application. The Medical Guidance: The Medical Ways of Prophet Muhammad SAW will undergo some phases from the beginning until project submission SYSTEM DEVELOPMENT The development of the application will follow System Development Life Cycle (SDLC) to ensure the effectiveness of the implementation process. The Medical Guidance: The Medical Ways of Prophet Muhammad SAW will use the iterative and incremental model as the methodology approach. Iterative and incremental development is the combination of iterative design or method and incremental build model for software development. They are extended lasting and extensively use in large development efforts. The advantages of the iterative and incremental model are: Progress can be followed for every whole cycle A functioning product is available at the end of every iteration Product requirements may be change to optimize future iteration Greater flexibility to change the plan Ability to focus its efforts on addressing the most critical risks early in the life cycle 14

31 3.3. PROJECT METHODOLOGY Every development phases will be implemented into application systems from the initial planning, planning, requirement, analysis and design, implementation, testing, evaluation and lastly the deployment phase PHASES The Medical Guidance: The Medical Ways of Prophet Muhammad SAW application system development process are: INITIAL PLANNING PHASE The phase starts with brainstorming the ideas of current problems and system requests. Then, discussion with supervisor to choose a project to be implemented. Literature reviews with the current similar application systems are studied to find the problems of the applications system PLANNING The title has been confirmed including the details project. Problem statement, objectives, and scopes are discussed with the supervisor. Feasibility study has been done to get more info about the medicine of the Prophet REQUIREMENTS The requirements of the application system have been discussed with the supervisor and experienced patients or relatives. After the discussion, the application system need to specify the scope of the disease. General health issues are chosen for the application system. 15

32 ANALYSIS AND DESIGN In this phase, Data Flow Diagram (DFD), Entity Relationship Diagram (ERD) and framework are designed. It helps to understand the process flow of the system. Any changes might occur during development according to user s requirements IMPLEMENTATION The phase also known as code generation phase. Developer writes code based on the previous phase. User interfaces are also included in the phases as they are important in delivering information and messages to the user TESTING Every sub - module needs to be test before implementing it into the application system. Any changes of the coding, error and functionality also will be tested. User interfaces will be tested to ensure they are connected to database and appropriate to the application system EVALUATION The application system will be evaluated to check bugs or errors. Any best practices and techniques that will be used in the first iteration then can be used for the next requirement changes and needed in the next iteration. 16

33 DEPLOYMENT In the last phase, The Medical Guidance: The Medical Ways of Prophet Muhammad SAW is presented and delivered to the end user. Any complement will be given to check whether the application system has been developed correctly or not CONTEXT DIAGRAM (CD) Figure 3.1 Context Diagram (CD) This figure 3.1 shows the data flow in The Medical Guidance: The Medical Ways of Prophet Muhammad SAW application system. There are two main users in this system which is admin and patient. This diagram shows the data flow involving the two main users. 17

34 3.5. DATA FLOW DIAGRAM (DFD) Data Flow Diagram is a two dimensional diagram that explains how data are processed and transferred into the system. DFD consists of entities, processes and data store to show the flow of the data in the system DATA FLOW DIAGRAM LEVEL 0 According to the DFD shown below, there are two entities; Patient and Admin. The processes and data store that involves in the system are as below: Process Process 1.0: Register Data Store D1: User Process 2.0: Manage User Process 3.0: Manage Medical D2: MedPractition Practitioner Process 4.0: Manage Symptoms Process 5.0: Manage Disease Process 6.0: Answer Medguide D3: Symptoms D4: Disease D5: MedGuide D6: Lookup Process 7.0: Manage Feedback D7: Feedback Table 3.1 Process and Data Store 18

35 The DFD figure shown the overall system in one diagram. Every function of the system will interact with their data store which contains tables in the database in order to complete their function 19

36 Figure 3.2 Data Flow Diagram (DFD) 20

37 DATA FLOW DIAGRAM LEVEL MANAGE USER Figure 3.3 Manage User In manage user for 2.1 process, admin and patient enter their data into edit profile process and the information will be send to the data store user. Then the information will be send back to admin and the patient. In manage user for 2.2 process, admin and patient enter their data into change password process and the information will be send to the data store user. Then the information will be send back to admin and the patient. 21

38 MANAGE MEDICAL PRACTITIONER Figure 3.4 Manage Medical Practitioner In manage medical practitioner for 3.1 process, admin enter medical practitioner data into add medical practitioner process and the information will be send to the data store user. Then the information will be send back to admin. In manage medical practitioner for 3.2 process, admin enter medical practitioner data into update medical practitioner process and the information will be send to the data store user. Then the information will be send back to admin. In manage medical practitioner for 3.3 process, admin enter medical practitioner data into delete medical practitioner process and the information will be send to the data store user. Then the information will be send back to admin. 22

39 MANAGE SYMPTOMS Figure 3.5 Manage Symptoms In manage disease for 4.1 process, admin enter symptoms data into add symptoms process and the information will be send to the data store symptoms. Then the information will be send back to admin. In manage disease for 4.2 process, admin enter symptoms data into update symptoms process and the information will be send to the data store symptoms. Then the information will be send back to admin. In manage disease for 4.3 process, admin enter symptoms data into delete symptoms process and the information will be send to the data store symptoms. Then the information will be send back to admin. 23

40 MANAGE DISEASE Figure 3.6 Manage Disease In manage disease for 5.1 process, admin enter disease data into add disease process and the information will be send to the data store disease. Then the information will be send back to admin. In manage disease for 5.2 process, admin enter disease data into update disease process and the information will be send to the data store disease. Then the information will be send back to admin. In manage disease for 5.3 process, admin enter disease data into delete disease process and the information will be send to the data store disease. Then the information will be send back to admin. 24

41 ANSWER MEDGUIDE Figure 3.7 Answer MedGuide In answer medguide for 6.1 process, patient enter medguide data into select symptoms process and the information will be send to the data store medguidet. Then the information will be send back to patient. In answer medguide for 6.2 process, the information from 6.1 process will be list down in the 6.2 process. Patient enter medguide data into view disease process and the information will be send to the data store lookup. Then the information will be send back to patient. 25

42 3.6. ENTITY - RELATIONSHIP DIAGRAM (ERD) An entity - relationship diagram (ERD) illustrates system s entities information and entities relationship. ERD composed of 3 things such as identifying and defining the entities determine entities interaction and the cardinality of the relationship. Figure 3.8 Entity - Relationship Diagram (ERD) The figure above shows the ERD of The Medical Guidance: Medical Ways of Prophet Muhammad SAW application system. The ERD shows the relationships between seven main table. Table login have 2 attributes, table user has 11 attributes, table medguide have 3 attributes, table symptoms have 2 attributes, table lookup have 2 attributes, table disease have 4 attributes and table feedback have 4 attributes. This ERD shows the primary key and the foreign key involve in each table. Transmission of data should be logical by database normalization. 26

43 3.7. FRAMEWORK Figure 3.9 Framework Of The Application System According to the framework, admin need to login to the system to be able to manage user, manage medical practitioner, manage symptoms, manage disease and generate report all by using the web based system. Meanwhile, the patient need to register first before login to the system to use the mobile application system. All the information will be stored in the database. 27

44 3.8. DATABASE DESIGN Figure 3.10 DB fypmed Of The System Figure 3.10 shows the database of the system. The database fypmed consist of nine tables. There are table comments, table disease, table feedback, table login, table lookup, table medguide, table medpractition, table symptoms and table user. Figure 3.11 Table disease In The DB Figure 3.11 shows table disease in the database of the system. There are 4 attributes in the table. The primary key for table disease is diseaseid. All the attributes cannot be null. There is no default for each attributes. 28

45 Figure 3.12 Table feedback In The DB Figure 3.12 shows table feedback in the database of the system. There are 4 attributes in the table. The primary key for table feedback is feedback. The foreign key for table feedback are userid and diseaseid. All the attributes cannot be null. There is no default for each attributes. Figure 3.13 Table login In The DB Figure 3.13 shows table login in the database of the system. There are 2 attributes in the table. There is no primary key for table login. The foreign key for table login are userid. All the attributes cannot be null. There is no default for each attributes. 29

46 Figure 3.14 Table lookup In The DB Figure 3.14 shows table lookup in the database of the system. There are 2 attributes in the table. The foreign key for table feedback are diseaseid and symptomsid. All the attributes cannot be null. There is no default for each attributes. Figure 3.15 Table medguide In The DB Figure 3.15 shows table medguide in the database of the system. There are 3 attributes in the table. The foreign key for table feedback are userid and symptomsid. All the attributes cannot be null. There is no default for each attributes. 30

47 Figure 3.16 Table symptoms In The DB Figure 3.16 shows table symptoms in the database of the system. There are 2 attributes in the table. The primary key for table symptoms is symptomsid. The symptomsname must be unique. There is no foreign key for table symptoms. All the attributes cannot be null. There is no default for each attributes. Figure 3.17 Table user In The DB Figure 3.16 shows table user in the database of the system. There are 10 attributes in the table. The primary key for table user is userid. There is no foreign key for table user. All the attributes cannot be null. There is no default for each attributes. 31

48 Figure 3-18 Table comments In The DB Figure 3.18 shows table comments in the database of the system. There are 3 attributes in the table. There is no foreign key for table user. Only attributes comtext can be null. There is no default for each attributes. Figure 3-29 Table comments In The DB Figure 3.19 shows table medpractition in the database of the system. There are 8 attributes in the table. There is no foreign key for table user. Only attributes nama and phone cannot be null. There is no default for each attributes. 32

49 3.9. SYSTEM REQUIREMENTS In order to develop a proper application system, software and hardware are required. Below are the lists of software and hardware requirements which are been used to develop the system efficiently SOFTWARE Microsoft Office Tools for writing report, proposal and Gantt chart - Tools for preparing slideshow presentation Notepad ++ - Tools for developing PHP Programming XAMPP Server - Tools for connecting with MySQL database Cordova APK / Node.js / Android Studio - Tools for implementing into mobile application EDraw Max - Tools for designing (CD, DFD and ERD) Snipping Tool / Snagit / Jing - Tools for print screen and crop images - Tools for editing images Google Chrome and Android - Platform to display the system Dropbox - Tools for cloud storage of backup data 33

50 HARDWARE Laptop - The laptop used was Asus X452C Series with Intel Core i3 3217U 1.80 GHz, 4.00 GB RAM memory, 64 bit Operating System Smartphone - The smartphone used was Huawei P9 Lite sponsored by Nurnadirah Binti Ngah, Android Operating System Printer - HP Deskjet F2410 printer was used to print document CONCLUSION Every phase is crucial to ensure the development of the proposed system will be implemented correctly and to always follow the flow of the application system. Iterative and incremental model approach is the suitable development model to follow with the system development. Meanwhile, the design methods and system design in this chapter explained the data flow of the system on how the system are working. Database design shows the database that contains tables with required data that are needed in the system. 34

51 4. CHAPTER 4: SYSTEM IMPLEMENTATION AND TESTING 4.1. INTRODUCTION System implementation is the construction of the system and the delivery of it into production. Interfaces and user manual of the system are included in this chapter. This chapter describes the implementation of The Medical Guidance: The Medical Ways of Prophet Muhammad SAW Application System. It consists of two parts of implementation which are for admin and patient TEST RESULTS (INTERFACE) INTERFACES Interface: Homepage 35

52 Figure 4-1 : Main Homepage Figure 4-1 shows the main homepage for login page for all users. When users click on LOGIN button, it will directly go to login page. When users click on REGISTER button, it will directly go to register page. 36

53 Interface: Comment Figure 4-2 : Comment 37

54 Figure 4-2 shows the main navigation for comment page for all users. User can send a comment to the administrator about the system without having to login PATIENT MODULE Interface: Homepage Patient Figure 4-3 shows the homepage for patient. This will be the first page that patient will see after successful login. There are six menu provided at the menu bar which are Home, Manage Profile, Answer Medguide, Medical Practitioner, Feedback and Logout. When the patient clicks on LET S START button, it will directly go to Answer Medguide form. 38

55 Figure 4-3 : Homepage Patient 39

56 Interface: Register Figure 4-4 : Register Form Figure 4-4 shows the register form for patient. Patient are required to fill in all the form of their personal details. After patient registered, system shows a pop-up message to inform user to login after register. 40

57 Interface: Login Figure 4-5 : Login Form Figure 4-5 shows the login form for patient. Patient are required to enter their registered username and password. The system only accepts registered and password so it can verify the designation of the user. 41

58 Interface: Edit Profile Figure 4-6 : Edit Profile Form Figure 4-6 shows the edit profile form for patient. Patient are allowed to update their personal details. After patient change some data and submit and save, system shows a pop-up message to inform patient that the data have been successfully updated. 42

59 Interface: Change Password Figure 4-7 : Change Password Figure 4-7 shows the change password form for patient. Patient are allowed to change their password by entering the old password, and insert new password and confirm password twice. After patient submit and save, system shows a pop-up message to inform patient that the password has been successfully updated. 43

60 Interface: Answer Medguide Figure 4-8 : Answer Medguide Form Figure 4-8 shows the answer medguide form for patient. Patient can tick the symptoms from the list symptoms provided. The date and time have already been inserted for the patient. 44

61 Interface: List Probable Disease Figure 4-9 : List Probable Disease Figure 4-9 shows the List Probable Disease for patient based on their selected symptoms on the previous form. The probable disease list is limited to three diseases only. The higher the frequency, the higher the probability of the disease to be the exact diseases. 45

62 Interface: Description Disease Figure 4-10 : Description Disease Figure 4-10 shows the description of the probable disease. There are three elements that can be read by the patient which is the symptoms of the disease, the description of the disease and the way to cure the diseases. 46

63 Interface: Feedback Disease Figure 4-11 : Feedback Disease Form Figure 4-11 shows the feedback form of the disease. Patient can leave the feedback on the probable disease whether it helps them or can give any opinion based on the disease for a better medical guidance. 47

64 Interface: Medical Practitioner Figure 4-12 : Medical Practitioner Display Figure 4-12 shows the Medical Practitioner Info. Patient can contact any of the medical practitioner available at their place for better references. 48

65 Interface: List Feedback Figure 4-13 : List Feedback Figure 4-13 shows the list feedback of the patient on any of the probable disease. It also helps patient to know their health progress. 49

66 ADMINISTRATOR MODULE Interface: Homepage Admin Figure 4-14 : Homepage Admin Figure 4-14 shows the homepage for admin. This will be the first page that admin will see after successful login. There are six menu provided at the menu bar which are Home, Manage Profile, Manage Medical Practitioner, Symptoms and Disease, Report and Logout. 50

67 Interface: Login Figure 4-15 : Login Form Admin Figure 4-15 shows the login form for admin. Admin are required to enter their registered username and password. The system only accepts registered and password so it can verify the designation of the user. 51

68 Interface: Edit Profile Figure 4-16 : Edit Profile Admin Figure 4-16 shows the edit profile form for admin. Admin are allowed to update their personal details. After admin change some data and submit and save, system shows a pop-up message to inform admin that the data have been successfully updated. 52

69 Interface: Change Password Figure 4-17 : Change Password Admin Figure 4-17 shows the change password form for admin. Admin are allowed to change their password by entering the old password, and insert new password and confirm password twice. 53

70 Interface: Change Password User Figure 4-18 : Change Password User Figure 4-18 shows the change user password form for patient. Admin are allowed to change the password of the user by selecting the username patient, entering the new password and confirm password twice. 54

71 Interface: Add Medical Practitioner Figure 4-19 : Add Medical Practitioner Form Figure 4-19 shows the Add Medical Practitioner form. Admin are required to fill in the form of all the details about Medical Practitioner. After submitted, system shows a pop-up message to inform admin that the details of Medical Practitioner have been successfully inserted into database. 55

72 Interface: List Medical Practitioner Figure 4-20 : List Medical Practitioner Figure 4-20 shows the List Medical Practitioner. Admin can choose whether to update or delete the data about the Medical Practitioner. 56

73 Interface: Add Disease Figure 4-21 : Add Disease Form Figure 4-21 shows the Add Disease form. Admin are required to fill in the form of all the details about disease. The symptoms for every disease are only limited to eight symptoms. After submitted, system shows a pop-up message to inform admin that the details of disease have been successfully inserted into database. 57

74 Interface: List Disease Figure 4-22 : List Disease Figure 4-22 shows the List of Disease. Admin can choose whether to update or delete the data about the disease in the database. 58

75 Interface: Manage Symptoms Figure 4-23 : Manage Symptoms Figure 4-23 shows the List of Symptoms. Admin can delete the data about the symptoms in the database Interface: Report Figure 4-24 : Disease Report 59

76 Figure 4-24 shows the Disease Report. Admin can view the report. The report consists of a list of disease Id, disease name, symptoms, description and the cure. Figure 4-25 : Patient Report Figure 4-25 shows the Patient Report. Admin can view the report. The report consists of a list of username, , address and the gender of the patient who registered in the application system. 60

77 Figure 4-26 : Feedback Disease Report Figure 4-26 shows the Feedback Disease Report. Admin can view the report. The report consists of a list of username patient, date, disease id, disease name and the feedback. Figure 4-27 : Comment Report Figure 4-27 shows the Comment Report. Admin can view the report. The report consists of a list of name, and comments. 61

78 4.3. TESTING The interfaces and user manual described the functions and the flow of the system. User will be able to use the system properly if they follow the user manual. Testing are executed to ensure the systems are developed according to the main objective of the application system and fulfil user requirements. Test cases are included in this chapter. A test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of developing test cases can also help find problems in the requirements or design of an application. In order to define a test, we can say It is a set of conditions or combination of variables under which a tester / engineer will identify whether the application under test is working correctly or not. The table below shows the test cases for the several process of this application system. 62

79 PATIENT MODULE Test Case for Registration Table 4.1: Test Case for Registration Test Case for Registration Step Test Procedure Expected Result Result 1. Patient clicks Application Register 2. Patient fill in required information in the registration form displayed form register 3. Patient clicks Register Validation: If there is empty form, System will have displayed notice: Please fill in the blanks If the password enter is less than 5 and more than 32 character, System 63

80 will have displayed notice: Invalid password length. Must provide between 5 to 32 character If the password enter is not same with confirm password, System will have displayed notice: Password does not match. Please reenter again If the username enter is less than 4 and more than 50 character, System will have displayed notice: Invalid username length. Must provide between 4 and 50 character 64

81 Else Data saved into database and displayed login form for user to login to system 65

82 Test Case for Login Table 4.2: Test Case for Login Test Case for Login Step Test Procedure Expected Result Result 1. Patient clicks Login button from homepage 2. Patient input details Application displayed login form username and password 3. Patient clicks Login Validation: If there is empty form, Application will have displayed notice: Please fill in the blanks Else Application redirect to the Patient Homepage 66

83 Test Case for Edit Profile Table 4.3: Test Case for Edit Profile Test Case for Edit Profile Step Test Procedure Expected Result Result 1. Patient clicks Edit Profile Application displayed profile in an update form version 2. Patient changes any data 3. Patient clicks Submit And Save A pop-up displayed Your profile have been successfully updated and the data are updated to the database and application system displayed the patient homepage 67

84 Test Case for Change Password Table 4.4: Test Case for Change Password Test Case for Change Password Step Test Procedure Expected Result Result 1. Patient clicks Application Change Password displayed change password form 2. Patient enter current password, password confirm new and new password field 3. Patient clicks Submit And Save Validation: If there is empty form, Application will have displayed notice: Enter password Else if the current password does not match, a pop-up displayed Wrong Old Password and 68

85 the application system redirect to the change password form back Else if the new password does not match with the confirm new password, a pop-up displayed Password does not match and the application system redirect to the change password form back Else A pop-up displayed Password have been successfully updated and the data are updated to the database and application system displayed the patient homepage 69

86 Test Case for Answer Medguide Table 4.5: Test Case for Answer Medguide Test Case for Answer Medguide Step Test Procedure Expected Result Result 1. Patient Register Application displayed login form 2. Patient Login Application displayed Patient 3. Patient clicks Let s Start or through navigation Answer Homepage Application displayed Medguide form consist list Medguide symptoms datetime and 4. Patient clicks Next button Application saves the data into database and displayed list probable disease which limit to three 70

87 5. Patient clicks any Application display disease in displayed the List Disease Probable symptoms, description and the cure of the disease 6. Patient can clicks Application Give Feedback displayed Feedback button or Go Back link Form OR Application displayed previous page List Probable Disease 71

88 Test Case for Medical Practitioner Table 4.6: Test Case for Medical Practitioner Test Case for Medical Practitioner Step Test Procedure Expected Result Result 1. Patient Register Application displayed login form 2. Patient Login Application displayed Patient 3. Patient clicks Medical Practitioner Homepage Application displayed a list of Medical Practitioner 72

89 Test Case for Feedback Table 4.7: Test Case for Feedback Test Case for Medical Practitioner Step Test Procedure Expected Result Result 1. Patient Register Application displayed login form 2. Patient Login Application displayed Patient 3. Patient clicks Feedback Homepage Application displayed a list of Feedback that have been sent by the Patient 73

90 ADMINISTRATOR MODULE Test Case for Login Table 4.8: Test Case for Login Test Case for Login Step Test Procedure Expected Result Result 1. Admin clicks Login button from homepage 2. Admin input details Application displayed login form username and password 3. Admin clicks Login Validation: If there is empty form, Application will have displayed notice: Please fill in the blanks Else Application redirect to the Admin Homepage 74

91 Test Case for Edit Profile Table 4.9: Test Case for Edit Profile Test Case for Edit Profile Step Test Procedure Expected Result Result 1. Admin clicks Edit Profile Application displayed profile in an update form version 2. Admin changes any data 3. Admin clicks Submit And Save A pop-up displayed Your profile have been successfully updated and the data are updated to the database and application system displayed the patient homepage 75

92 Test Case for Change Password Table 4.10: Test Case for Change Password Test Case for Change Password Step Test Procedure Expected Result Result 1. Admin clicks Application Change Password displayed change password form 2. Admin enter current password, password confirm new and new password field 3. Admin clicks Submit And Save Validation: If there is empty form, Application will have displayed notice: Enter password Else if the current password does not match, a pop-up displayed Wrong Old Password and 76

93 the application system redirect to the change password form back Else if the new password does not match with the confirm new password, a pop-up displayed Password does not match and the application system redirect to the change password form back Else A pop-up displayed Password have been successfully updated and the data are updated to the database and application system displayed the Admin homepage 77

94 Test Case for Change Password User Table 4.11: Test Case for Change Password User Test Case for Change Password User Step Test Procedure Expected Result Result 1. Admin clicks Application Change Password displayed change User password user form 2. Admin select which user account to change, enter new password confirm and new password field 3. Admin clicks Submit And Save Validation: If there is empty form, Application will have displayed notice: Enter password 78