Online Hospital Management System, Thesis of Project Management

Download Online Hospital Management System and more Thesis Project Management in PDF only on Docsity! Easy Physician Social By Touseef Anjum 2016-GCUF-072212 Maria Ashfaq 2016-GCUF-072179 Muhammad Rizwan 2016-GCUF-072202 Muhammad Ayub 2016-GCUF-072200 A Project Sbmitted in Partial Fulfillment of the Requirements for the Degree of BACHOLAR OF SCIENCE IN INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION TECHNOLOGY GOVERNMENT COLLEGE UNIVERSITY, FAISALABAD OCTOBER 2020 I DEDICATION We dedicate this project to Allah Almighty my creator, my strong pillar, my source of inspiration, wisdom, knowledge and understanding. He has been the source of my strength throughout this program and on His wings only have I soared. I also dedicate this work to our parents who has encouraged me all the way and whose encouragement has made sure that I give it all it takes to finish that which I have started. To my respected teachers. Thank you. My love for you all can never be quantified. Allah blesses you. I Table of Contents DEDICATION................................................................................................................................................. I DECLARATION.............................................................................................................................................. II CERTIFICATE BY THE PROJECT SUPERVISOR................................................................................................III LIST OF FIGURES........................................................................................................................................VII LIST OF TABLES.........................................................................................................................................VIII ACKNOWLEDGEMENTS............................................................................................................................... IX LIST OF ABBREVIATIONS..............................................................................................................................X ABSTRACT...................................................................................................................................................XI Chapter 1: Introduction...............................................................................................................................1 1.1 Chapter Introduction.........................................................................................................................1 1.2 Project Introduction...........................................................................................................................1 1.3 Introduction to the Software tools....................................................................................................1 1.4 Aims...................................................................................................................................................1 1.5 Objectives..........................................................................................................................................2 1.6 Clear Statement of the Problem........................................................................................................2 1.7 Solution..............................................................................................................................................2 1.8 Scope.................................................................................................................................................3 1.9 Tools and Techniques........................................................................................................................3 1.9.1 Software and Language Requirements for Website:......................................................3 1.9.2 Software and Language Requirements for Android Application:..................................3 Chapter 2: Literature Review.......................................................................................................................4 2.1 Waiting time......................................................................................................................................4 2.2 Appointment Delay............................................................................................................................4 2.3 Managing Patient's Appointment......................................................................................................5 2.4 Online Booking...................................................................................................................................5 2.5 Existing System..................................................................................................................................6 2.5.1 Determination of Problem Challenge for new practitioners...........................................6 2.5.2 Proposed System.............................................................................................................6 2.6 Patient's Appointment Time..............................................................................................................7 2.7 APPLICATION TECHNOLOGIES............................................................................................................7 IV 2.7.1 Web Server......................................................................................................................7 2.7.2 Programming Languages................................................................................................8 Chapter 3: Development Methodology.....................................................................................................11 3.1 Adopted Methodology.....................................................................................................................11 3.2 Waterfall Model...............................................................................................................................11 3.2.1 Advantages of waterfall model:....................................................................................12 3.3.2 Disadvantages of waterfall model:................................................................................12 3.3 Spiral Model.....................................................................................................................................12 3.3.1 Planning Phase..............................................................................................................12 3.3.2 Risk Analysis................................................................................................................13 3.3.3 Engineering Phase.........................................................................................................13 3.3.4 Evaluation Phase...........................................................................................................13 3.3.5 Advantages of Spiral model:.........................................................................................13 3.3.6 Disadvantages of Spiral model:....................................................................................14 3.4 Incremental Approch.......................................................................................................................14 3.5 Agile Method...................................................................................................................................14 3.6 Prototype Model:.............................................................................................................................15 3.6.1 Advantages of Prototype:..............................................................................................16 3.6.2 Disadvantages of Prototype:.........................................................................................16 3.7 Adopted Approach...........................................................................................................................17 3.7.1 Advantages of Incremental model:...............................................................................17 Chapter 4: System Design..........................................................................................................................18 4.1 System Overview.............................................................................................................................18 4.2 Functional Requirement..................................................................................................................18 4.3 Non Functional Requirement...........................................................................................................18 4.3.1 Performance Requirements:..........................................................................................18 4.3.2 Safety Requirements:....................................................................................................18 4.3.3 Security Requirements:.................................................................................................19 4.4 Hardware Requirements.................................................................................................................19 4.5 Use Cases.........................................................................................................................................19 4.5.1 Patient Use Cases..........................................................................................................21 3.5.2 Doctor Use Cases..........................................................................................................23 3.5.3 Admin Use Cases..........................................................................................................24 4.6 Class Diagram...................................................................................................................................25 V 4.7 ER Diagram.......................................................................................................................................26 4.7.1 Entity.............................................................................................................................27 4.7.2 Attributes.......................................................................................................................27 4.7.3 An Entity Set.................................................................................................................27 4.7.4 Process..........................................................................................................................27 4.7.5 Actions..........................................................................................................................27 4.8 Activity Diagram...............................................................................................................................28 4.8.1 User Management........................................................................................................29 4.8.2 Login Management......................................................................................................29 4.9 Data Flow Diagram..........................................................................................................................30 4.9.1 Data Flow......................................................................................................................31 4.10 Sequence Diagram........................................................................................................................32 4.10.1 Sequence Diagram For Login.....................................................................................33 4.10.2 Sequence Diagram for New Account Register..........................................................34 4.10.3 Sequence Diagram for Patient Manage Appointment................................................34 4.10.4 Sequence Diagram for Admin/System Logs...............................................................35 4.11 Architecture Diagram....................................................................................................................35 4.12 Application Architecture:...............................................................................................................36 Chapter 5:System Implementation............................................................................................................37 5.1 Introduction.....................................................................................................................................37 5.2 Work Schedule.................................................................................................................................37 5.2.1 Schedule........................................................................................................................37 5.2.2 Phase 1: Requirements Development...........................................................................37 5.2.3 Phase 2: Software Design.............................................................................................38 5.2.4 Phase 3: Software Implementation...............................................................................38 5.2.5 Phase 4: Software Testing.............................................................................................39 5.3 Gantt Chart......................................................................................................................................39 5.4 Screen Shots....................................................................................................................................40 5.4.1 Patient Login.................................................................................................................40 5.4.2 Admin Login.................................................................................................................40 5.4.3 Doctor Login.................................................................................................................41 5.4.4 Registration...................................................................................................................41 5.4.5 Book Appointment........................................................................................................42 5.4.6 DashBoard.....................................................................................................................43 VI ACKNOWLEDGEMENTS Firstly, we are thankful to ALLAH ALMIGHTY who blessed us with knowledge to complete this project. We truly acknowledge the cooperation and help make by Name of Mr. Hafeez, Teacher And Hafiz Saad Ullah Professor of Superior College Okara for his help and guidance throughout this project. He has been a constant source of guidance throughout the course of this project. He helped in requirement gathering and specification. TOUSEEF ANJUM 2016-GCUF-072212 MARIA ASHFAQ 2016-GCUF-072179 MUHAMMAD RIZWAN 2016-GCUF-072202 MUHAMMAD AYUB 2016-GCUF-072200 IX LIST OF ABBREVIATIONS Terminology Meaning EPS Easy Physician Social ERD Entity Relationship Diagram DBD Database Diagram DFD Data Flow Diagram IT Information Technology UI User Interface PHP Server-side scripting languages HTTP Hyper Text Transfer Protocol SQL Structure Query Language DBMS Database Management System GUI Graphical User Interface IDE Integrated Development Environment XML Extreem Markup Language XAMPP X-OS, Apache, MySQL, PHP, and Perl CSS Cascading Style Sheet Java Script Scripting Programming Language HTML Hyper Text Markup Language X ABSTRACT Easy Physician Social is a web and smartphone (Android) application that helps patients to find doctors as per required specialist over the Website. Patient will be able to Schedule an appointment. This application also provides health tips and answer of question about health problem to the user. Application will also show the reviews of patient, rating of Doctor, comments of patients. EP Social provides the search of medicine details by company and formula base. For Doctors there will be an option to create and maintain prescription of the patient along with list of all the previous prescription. Doctor will be able to search all the previous prescriptions of the particular patient so there is no need to maintain manual prescriptions. Doctor will register on the website by filling out basic personal form and will mention its days & timing of appointments. XI 1.8 Scope This system is implemented for all the individuals who want to get treated by the city practitioners. The users can participate only if they have created an account through the registration form and have provided their medical history. Once they get regist ered themselves further they would not need to update their record as it would be done automatically after each doctor’s visit. 1.9 Tools and Techniques 1.9.1 Software and Language Requirements for Website:  Languages : HTML , CSS , JAVASCRIPT , PHP  Database : MYSQL  Platform : Dreamweaver , Notepad++  Presentation tool: Power Point(2016)  Documentation tool : MS word (2016) 1.9.2 Software and Language Requirements for Android Application:  Languages : XML, JAVA  Database : SQLite  Platform : Android Studio  Presentation tool: Power Point(2016)  Documentation tool : MS word (2016) 3 Chapter 2: Literature Review 2.1 Waiting time Waiting time was also defined as the time a patient entered a clinic or service point and gets consulted by a doctor with a prescription in his hand. There are two different ways in which the waiting time has been defined in the past. At first, waiting time is the time that starts when an individual comes for the appointment and it continues until the individual gets consulted by the doctor. In the second definition, it starts when an individual comes for taking appointment and ends when he got prescribed medicine after being consulted by the doctor.With the passage of time, long waiting lines at doctor's clinics became a major problem in developing countries. In a South African health clinic, block appointment system was introduced as an experiment, in which waiting time for patients was measured for the period of one week before and after the implementation of the appointment system. During the experiment, interviews were taken from focus-group, staff, and patients and from results it was realized that acute medically ill patients with prior appointments had short waiting times as compared to the patients without appointments.It has also been stated that the appointment system has no benefit for the patients not seeing the doctor or who are taking routine repeated medication. Later it was realized that the block appointment system offers shorter waiting time only for acutely ill patients and not for others. 2.2 Appointment Delay It has been proved in the past research that there is a direct relationship between appointment delay and cancellation of the appointment. Appointment delay is defined as the time which starts when an individual request for an appointment and ends until he/ she gets consulted by the doctor. Longer appointment delays cause more appointment cancellations. So, the best way to reduce appointment cancellations or no-shows is to minimize the time gap between the appointment request and doctor's checkup/consultation time. Minimizing this gap is called open access (abbreviated as OA) or advance access policy which later became a popular practice and part of an active research also. Both positive and negative results were experienced by the researchers in their experiments. Some practitioners were in the favor of OA and highly recommended it, and on the other hand, there were some practitioners who disagreed and were against of OA implementation. 4 2.3 Managing Patient's Appointment In a health care centre, an application which is used to manage and minimize patient waiting time is called managing patient's appointment system. Some health care clinics use this kind of applications while some do not. Medical clinics who use such applications usually have shorter waiting times as compared to those medical clinics who do not use any appointment application. Patients who supposed to wait more than an hour for their medical check-up feel disgraced and unfair. Patients can evaluate the quality of any medical centre based on the waiting time they have to experience. Therefore, it has become important to consider factors like "saving time" and "minimizing idle time" while developing any patient's appointment system. Whereas according to Klassen (2002), scheduling doctor's time and patient's appointment supposed to depend on the seriousness of the case and patient's need. 2.4 Online Booking An online appointment system is a web-based system which is made up of independent components or web pages, working together for a common purpose. Such systems are available on the internet for the users to accomplish some purpose. James (1999) defined internet as a system which provides an opportunity to millions of people to get access to a large amount of stored data and get connected to each other despite distances. Increased rate of missed appointments and patient dissatisfaction pushed to recognize the need for better-quality care services. With the advancement of information technology and the sensitive situation of medical care, online appointment system emerged as an important output for efficient and timely delivery of health care services. Earlier, appointment requests were used to make through the phone call, email or fax but with the advancement of technology and internet, the trend changed towards the proper online appointment systems. According to Gruca (2004), a patient can make an appointment for a doctor either by going directly to the doctor's clinic or making a manual appointment through the phone call or sending the email. With the emergence of the internet, health care centres can connect and communicate with their patients efficiently. Therefore, many healthcare centres have started using online appointment systems. Such systems ensure efficiency and effectiveness. 5 2.7.1.1 Apache web server Apache web server is a free, open source and most popularly used software. Apache web server is used by many famous websites such as Apple, Wikipedia, and PayPal. Another reason for its popularity is that it can run on multiple operating systems such as Linux, UNIX, windows, and macOS. Another feature of Apache web server is that it can host websites which use server-side language code (Perl, PHP). Because in this project server- side implementation is done by using PHP so Apache was a good choice. 2.7.2 Programming Languages In this project, PHP was chosen as a server-side programming language and MySQL was selected as a backend database. HTML, CSS, and JavaScript were used for the client-side work. 2.7.2.1 PHP PHP is a server-side programming language commonly used to develop dynamic web pages. It is free and accessible in numerous different versions. It can be used on multiple OS such as macOS, windows, UNIX and different platforms. Because it is a scripting language so in this program code is taken after the program execution. PHP can also be used in desktop applications. One of the reasons for choosing PHP in this project is that it supports MySQL which is chosen as a database in our project. PHP programming language makes easy to present images and PDF files on HTML pages. 2.7.2.2 Client-side programming For the development and designing of web pages HTML, CSS and JavaScript languages were used. HTML for creating the web pages, CSS for styling and for adding further functionalities JavaScript was used. JavaScript JavaScript is dynamic, high-level scripting language and considered to be one of the core three technologies of the world wide web. It is considered an important part of a web application. It is used for adding functionalities and making web pages interactive. In simple words, it informs the browser about a certain activity or event that occurred and changes the web page as a response to that event, for example, a click on a button. 8 2.7.2.3 HTML Hypertext markup language (HTML) is used for creating web pages and web applications. It describes the structure of the web pages. Information from the HTML documents is sent to the web browser to render or display on the multimedia pages. Html used to describe the structure of a document by presenting a document in a heading, paragraph, image, list, links and other objects like that. Web browser presents the HTML document by using its tags. 2.7.2.4 CSS It is important to make HTML pages attractive to the users and for this purpose, developers choose colors, nice fonts, and different layouts. All this work is done by the CSS. In short, CSS is used for styling of a HTML document. It is designed in such a way that enables separation of content and presentation so that it makes easier any change of content without interfering with a design. It also enables multi web pages to share the single CSS file for styling to reduce repetition and complexity. Backend technology For this project work, MySQL was chosen as a database. 2.7.2.5 MySQL It is an open source relational database management system which aims to offer multiple user access to several databases. In simple words, a database is a collection of data which can be a list of shopping items, number of items in a shopping centre or even a vast amount of numerous data in a corporate network. To manage such kind of data, a database management system is required such as MySQL which aims to access data and perform functions like add, remove or edit data. Since MySQL is a relational database so it stores data in different tables instead of putting into a large storeroom. Storing /organizing data into tables increases the accessibility speed and flexibility. Applications which demand availability and scalability use MySQL. Because it has the capability to recover and cope with failures on the host, MySQL, operating system or the hardware that may cause downtime. Scalability refers to the ability to spread the database as well as application queries. MySQL is reliable for data security. MySQL has a good memory management system and provides multiple development interfaces (ODBC, JDBC). Since MySQL is a free open source software so anyone can download it without paying anything and make changes into the source code. For this project, MySQL was chosen because it is very easy to use and PHP's ability to work with MySQL. 9 2.7.2.6 XML XML stands for Extensible Markup Language. XML is a markup language much like HTML used to describe data. XML tags are not predefined in XML. We must define our own Tags. Xml as itself is well readable both by human and machine. Also, it is scalable and simple to develop. In Android we use xml for designing our layouts because xml is lightweight language so it doesn’t make our layout heavy. 2.7.2.7 Java Android applications are developed using the Java language. As of now, that’s really your only option for native applications. Java is a very popular programming language developed by Sun Microsystems (now owned by Oracle). Developed long after C and C++, Java incorporates many of the powerful features of those powerful languages while addressing some of their drawbacks. Still, programming languages are only as powerful as their libraries. These libraries exist to help developers build applications. Some of the Java’s important core features are:  It’s easy to learn and understand  It’s designed to be platform-independent and secure, using virtual machines  It’s object-oriented 10 3.3.2 Risk Analysis A prototype is produced at the end of the risk analysis phase. If any risk is found during the risk analysis then alternate solutions are suggested and implemented. 3.3.3 Engineering Phase In this phase software is developed, along with testing at the end of the phase. In this phase the development and testing is done. 3.3.4 Evaluation Phase This phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral. Figure 2: Spiral Model 3.3.5 Advantages of Spiral model:  High amount of risk analysis hence, avoidance of Risk is enhanced.  Good for large and mission-critical projects 13  Software is produced early in the software life cycle. 3.3.6 Disadvantages of Spiral model:  Can be a costly model to use.  Risk analysis requires highly specific expertise.  Project’s success is highly dependent on the risk analysis phase. 3.4 Incremental Approch To conquer the disadvantages of the cascade show, incremental model is utilized. In incremental model, the item is created in increases and apportioned into little pieces. These littler pieces, at that point fabricated and conveyed to customer in increases. Speedy reaction from customers. Every module is littler than contrast with entire module. Figure 3: Incremental Model 3.5 Agile Method Agile model is valuable when there is no expectation for changings in item after sending. It is a specific way to deal with venture administration that is used in programming improvement. This technique helps groups in reacting to the unusualness of building programming. It utilizes 14 incremental, iterative work successions that are regularly known as dashes. The capacity to make and react to change keeping in mind the end goal to prevail in an unverifiable and turbulent condition. This method assists teams in responding to the unpredictability of constructing software. It uses incremental, iterative work sequences that are commonly known as sprints. The ability to create and respond to change in order to succeed in an uncertain and turbulent environment. Figure 4: Agile Model 3.6 Prototype Model: The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is 15 Chapter 4: System Design 4.1 System Overview We are implementing a web-based appointment system in Pakistan for booking an online appointment and keeping an online medical history. Users can sign up online, search for the nearby doctor and book appointment while sitting at their homes by using a web browser. The Main characteristics of the system are:  Every individual either a doctor or a patient will have an independent id, name and a profile.  The user (patient) can get, change or cancel appointment time and view medical record while the doctor can make changes in his calendar and accept or reject appointment request by log in to the site and accessing his/her personal page. 4.2 Functional Requirement  Allows end-users to register,login and logout from the system.  Allows users to view doctors list according to departments as well as doctors’ specifications.  Allows users to book update and cancel their appointments.  Allow the doctors to view thenumber of patients to be attended for the day.  Allow patients to review and rate their experience with the respective doctors.  Once an appointment is booked, the system notifies the users by email 4.3 Non Functional Requirement 4.3.1 Performance Requirements:  The system need to be reliable  Web pages are loaded within few seconds  System should be efficient 4.3.2 Safety Requirements:  The details need to be maintained properly  Users must be authenticated 18  The database must be kept backed up 4.3.3 Security Requirements:  After entering the password and user id the user can access his profile  The detail of user must be safe and secure  Sharing of details 4.4 Hardware Requirements SL HARDWARE MINIMUM SYSTEM REQUIREMENT 01 Processor 2.4 GHz Processor speed 02 Memory 2 GB RAM 03 Disk Space 5GB 4.5 Use Cases An important part of the analysis phase is to drawing the diagrams of Use cases. They are used through the phase of analysis of a project to find and divide functionality of system. System is separated into actors and use cases. Actors play the role that are played by the system users. The users can be defined as pieces of hardware, humans, other computers or even other system software. The standard condition is that the users must be external to the system divided into use cases. Use cases define the system behavior when one of the actors sends any particular motivation. This type of behavior can be described by text. It describes the motivation nature that activates use case, the inputs and outputs to some other actors and the behavior of conversion of inputs to the outputs. Usually the use case describes everything that can go wrong during the detailed behavior and what will be helpful action taken by the system. 19 20 Description: Before taking any appointment or get access to his medical record the user must have to provide his username and password. Precondition: The user must have valid username and password. Basic Use-case flow: A volid username and Password must be entered by user. Use Case 3: Take Appointment Primary-actor: Patient / User Description: After Choosing a doctore user send an appointment request. Precondition: The user must be Login. Basic Use-case flow: A volid username and Password must be entered by user. Use Case 4: Logout Primary-actor: Patient / User Description: A user Will logout from the system. Precondition: The user must be Login. Basic Use-case flow: The User can Sign out from the system. 3.5.2 Doctor Use Cases Figure 9: Doctor Use Case Use Case 1: Doctor Login: Primary-actor: Doctor Description: For further function the doctor must have to provide his email adress and password. 23 Precondition: the doctor must enter the user name and password. Basic use-case flow: the doctor should provide his user name and password to login. Use Case 2: Accept or Reject a request: Primary-actor: Doctor. Description: Doctor can accept or reject any patient’s request. Precondition: The Doctor must be Sign In. Basic Use-case flow: Doctor Selects any date for accept appointment. Use Case 3: View Patient: Primary-actor: Doctor Description: doctor would be able to view the patient detailed information and his medical history. Precondition: The Doctor must be Sign in. Basic Use-case flow: After selecting the date doctor select the patient. Use Case 4: Logout Primary-actor: Doctor Description: The Doctor Will logout from the system. Precondition: The doctor must be Sign in. Basic Use-case flow: The Doctor can Sign out himself from the system. 3.5.3 Admin Use Cases Use Case 1: Admin Login: Primary-actor: Admin / Administrator Description: A User Who Process admin username and password, owns administrative rights. Precondition: username and password. 24 Figure 10: Admin Use Case Basic Use-case flow: Admin need to provide username and passowrd. Use Case 2: Manage Users: Primary-actor: Admin / Administrator Description: Admin can use his administrative rights. Precondition: A user must be log in as an admin. Basic Use-case flow: Admin Can View , Edit or Delete any user information related to doctor or patient. Use Case 3: Logout Primary-actor: Admin / Administrator Description: The Admin Will logout from the system. Precondition: The Admin must be Sign in. Basic Use-case flow: Use Sign in him self “as a admin. 4.6 Class Diagram The class diagram is chosen to explain the design phase of the system. A class diagram describes classes of the system, attributes, and operations and relationships of the classes in a better way. We can also say that class diagrams are used to justify the structure or behavior of use cases of the system. Class diagrams best explain the conceptual model of the system in terms of entities and their relationships. The class diagram looks like a shape of a rectangle, comprising three compartments stacked vertically. The first top box comprises the class name, the second middle box contains the attributes of the class and third the last box contains the methods or functions performed by that class. 25 Figure 12: ER Diagram 4.8 Activity Diagram Graphical representations of stepwise workflow of action and activities with support for iteration concurrency and choice. In the UML (Unified Modelling Language), activity diagrams are used to define the business and operational workflows of components step by step in a system. The overall flow of control is shown by activity diagram. 28 4.8.1 User Management Figure 13: Activity User Management 4.8.2 Login Management 29 Figure 14: Activity Login Management 4.9 Data Flow Diagram A data-flow diagram is a way of representing a flow of data through a process or a system (usually an information system). The DFD also provides information about the outputs and 30 Figure 17: Logon Sequence Figure 16: Sequence Diagram 4.10.1 Sequence Diagram For Login 33 Figure 18: Sequence Registration Figure 19: Sequence Diagram For Patient Manage Appointment 4.10.2 Sequence Diagram for New Account Register 4.10.3 Sequence Diagram for Patient Manage Appointment 34 Figure 20: Sequence Diagram For Admin 4.10.4 Sequence Diagram for Admin/System Logs 4.11 Architecture Diagram The Software Architecture Diagram is a crucial step for software and application developers to describe the basic software structure by separating functional areas into layers. It depicts how a typical software system might interact with its users, external systems, data sources, and services. 35 reviewed by Sir Muhammad Hafeez at mid-term and before programming Easy Physician Social. Issues • Communication: There was a clear need in this phase to clearly understand the needs. We used different ways of handling this such as asking the same question in different ways to confirm the message, writing minutes of every meeting and distributing internally for consensus and clarity. • Choice of Technologies: The decision over which technologies to use for the prototype was made after taking a number of factors into account. Discussions regarding the choice of database, development language covered the performance issues, feature-set available for each available technology and so on. Eventually, Sir Muhammad Hafeez current infrastructure environment was agreed to be the overriding decision factor. 5.2.3 Phase 2: Software Design After reviewing the users’ requirements, I’m started work on system design. System architecture, database design and test cases were determined during this phase. Additionally, a detailed design was generated at the end of requirements analysis during this phase which was to be used to develop Easy Physician Social. Issues • Choice of design pattern/design principles: I’m having strong software engineering backgrounds and related experience, differences of opinions over design patterns existed naturally. These needed to be resolved and an approach agreeable to all the parties concerned needed to be developed. 5.2.4 Phase 3: Software Implementation The Project developed the software using the detailed design created in the Design phase. The progress was monitored through meetings and use of the SharePoint server. Features were included in the software incrementally. After the first version release of Easy Physician Social, testing began and bugs discovered were documented. After releasing one version of the project, I worked on feature additions and bug fixing to be released in the subsequent version. Thus the implementation process was iterative and interacted heavily with the testing process. Issues 38 • Communication and accurate understanding of Sir Muhammad Hafeez requirements was needed to prioritize bugs discovered during the testing phase. 5.2.5 Phase 4: Software Testing Testing was performed in parallel with code development. The developer performed unit testing to ensure a functioning code prior to a release and then an exhaustive system testing was performed. Issues • Communication: A lot of interaction and meticulous documentation was needed to ensure that bugs discovered were fixed or addressed. It was also important to closely watch the scope of the project during testing and bug fixing. It is easy to overlook the scope of a project and enhance the feature set offered in the quest for the perfect application during testing. 5.3 Gantt Chart Figure 23: Gantt chart 39 5.4 Screen Shots 5.4.1 Patient Login Some of the screen shots of Login screens are as follows where administrator and user can login: Figure 24: Patient Login 5.4.2 Admin Login Figure 25: Admin Login 40 5.4.6 DashBoard Ret Oger trey eens Figure 29: DashBoard 43 Creat Sota cd 5.4.7 About us About Easy Physician Social a sass a Our Services A henith sector hased Wehsite and Andi application pmnuldes information at a central level ‘with this hea'th consulting system, net nly people vill be abia te acquire better Infrmation, hur the caverrment Fan vill he ahie fo provide nelter secvices to people. “helps the penple te fing which doctor 's avallzola where ana maka cholces accordingly. Such website and ardrolé project ideas nil give mare power ta people and make lives simpy. Ths system is implemented for all the Fulividuals whe want Wo gat lwated by Une Gly practitioners. Ine users cn participate only if they nave created an account through the Feyistralion fori and fave provided Ursir inadical history. Once they yel rey)st ered Usemselves further they would not need te update their record az it would ke done autzmatically after each doctor's visi Super Speciity Hospita) ‘Tha objectives are important to achleve the goal. T1e maln osjectves af this project ara: 4 The Fest angectve ie tr replare the current manual hile keeping system with an n-line medical patient darsbace systam. @ EPS system sllows the users the cower to bock thelr avn Apnnintments with respective enctnc= anline that herefits organ vaticns to manage a time thet Diagnostic Services Would stherwise hava bean spant answering phone, asponding to e-malis ard vcica essazes. Ths online lattarm imprnes Hesihilty of healthesce service with citerized repnrting anc security features. @ To develop 3 system tha: allows users 12 Nave control aver their apnaintment making service. @ Tn ‘aiitate the parents with real rime healthears seeding @ Te manage staff rezources nesdes for manaqina apzolntmants. To maximize operation consultation hours 1n vationt Services ‘Super Specialty Hospital services zs lealth Checkup Packages Figure 30: about Us 44 5.4.8 Contact Us Contact Us Our Address wyslclan Social system, Okara el: 0390 1224557 mail 19: 1 pega Contact Us by entering following information ame (rnsiomd) Figure 31: Contact Us 45 5.5.3 User Registration: SIGN UP Username Email Password Password ALREADY HAVE AN ACCOUNT? SIGN IN Figure 34: Sign Up 48 5.5.4 User Information: Easy Physician Social Logout Hello Rana g Details User Name: Rana Email: ranatouseef 010@gmail .com password: 1234 EDIT CHANGE PASSWORD tt = Bk Appointment My Appointment ace Figure 35: Profile 49 5.5.5 Doctor Specialist Sa aes t-]| Find doctor by health Conern () CHEST SPECIALIST oO CHILD SPECIALIST «) DENTIST C) HEART SPECIALIST *) SKIN SPECIALIST Q) krpnev spe oy LT} ry = Bk Appointment My Appointment ceil Figure 36: Doctor Appointment 50 5.5.8 Sms Permission [es Allow Easy Physician Social to send and view SMS messages? Figure 39: Sms Premission 53 Chapter 6: System Testing 6.1 Unit Testing The software units in an application are modules and routines that are assembled and integrated to perform a specific function. Unit testing centers first around modules, freely of each other, to find mistakes.This enables, to detect errors in coding and logic that are contained within each module. The different controls are tried to guarantee that each plays out its activity as required. Commonly used method is White-Box Testing method. Every time a component of the program is changed, it can be run for testing that is the biggest and famous benefit of this testing phase. Issues that are arises during this phase, allowing to be resolved as quickly as possible. Unit testing is familiar by software developers. It allows them to test their application units before move them to testers for formal testing. Module: Registration Table 1: Unit Testing for “Register”: No Test Case Expected Result Actual Result 1. Leave the email and password Warning message displayed As Expected Field Empty and press to prompt email and “Register” button. password. 2. Enter an email address that is Warning message displayed As Expected Alread y registered to the to show email address is system. already registered. 3. Enter unregistered email and Warning message displayed As Expected enter unmatched passwords. to prompt re-enter password Finally, press “Register” correctly. button. 4. Enter unregistered email and Information message As Expected enter matching passwords. Displayed to indicate Finally, press “Register” successful registration. button. Update personal detail page is re-directed. 54 Table 2: Unit Testing for Make New Appointment : Module: Make New Appointment No Test Case Expected Result Actual Result 1. Select a Doctor ID Doctor name, specialty and As Expected. Hospital name is automatically displayed. 2. Select a past date and click on Warning message displayed As Expected “Book”. to prompt for a future date. 3. Select a today date and click on Warning message displayed As Expected “Book”. to prompt for at least 7 days after today date. 4. Select a date which is 6 days Warning message displayed As Expected after today and click on to prompt for at least 7 days “Book”. after today date. 5. Select a date which is 7 days Information message As Expected after today and click on Displayed To show “Book”. successful booking. 6. Book an appointment with user Warning message displayed As Expected who has a future appointment. to decline booking, future 6.2 System Testing To test the complete application as a whole, system testing has been used. It is beneficial to check whether the application meets its requirements and fulfill Quality Standards. Table 3:systen Testing Procedure Pass/ Fail (P/F) Actual Result/Comment Basic Application Testing 55 1. Login √ 2. Registration √ 3. Update personal information √ 4. Make a New Appointment √ 5. Updating Appointment. √ 6. Making Payment. √ 7. View My Appointment √ 8. View Doctor Record √ 9. Register New Staff. √ 10. System Records. √ 11. Rate consultation √ 12. Sending notification Email. √ 13. Password Strength Checker. √ Chapter 7: Conclusion and Future Work 7.1 Conclusion We are very delighted working with this project and being able to develop a system to integrate with the need of Tourist Guide. We came to result that this website will be proved beneficial in the way that everyone can assess it because in this area everyone has the availability of website. Technology is an everlasting thing and that is why we have used it for a good reason. 7.2 Future Work This project is just a head up and this is the initial Website more Features will be launched with the better security, performance and with better suitability. This project is the dream and we want to facilitate the people who want to learn the Visiting. Our targeted area for these services is Lahore but in future we wish to expand this service to other cities. 7.3 Summery As discussed in the previous chapters the main problem that we addressed was dealing with patient, doctor and hospital document. It is the above situation that above us to techniques of developing this Easy Physician Social System to be used the Patient, Doctor and Hospital to 58 enable them to handle details on policies efficiently and effectively. The Project has implemented most of the objectives stipulated in earlier chapter. The Easy Physician Social System offers a number of benefits to the user and can capture data, store, view, add and delete the records entered the data cal also be posted information to the database. Problems Encountered during Data Collection: sensitive information released to us, few projects and books written about Online Doctor Appointment System. Problem Encountered during System Design: Limited time to finish up to work, but we are finally finished to our system design the projects. References Rahman, M. (2015). practical project on online appointment for medical services. [online] VCampus. Available at: http://vcampus.co/blogs/4844/practical-project-on-online-appointment- for-medical-services [Accessed 8 Oct. 2016]. EssayMonster.net - essays, research papers, dissertations & etc. (2016). The Appointment Automation System Computer Science. [online] Available at: http://essaymonster.net/science/76498-the-appointment-automation-system-computer- science.html [Accessed 8 Oct. 2016]. Abd Wahab, M., Hassan, N., Wali Mohd, Z. and Hanaf, H. (2009). WEB BASED INTELLIGENT APPOINTMENT SYSTEM. 1st ed. [ebook] Available at: http://eprints.uthm.edu.my/121/1/mohd_helmy_abd_wahab_2.pdf [Accessed 8 Oct. 2016]. 59 Dai, X. (2013). Online Clinic Appointment Scheduling. 1st ed. [ebook] Lehigh University. Available at: http://preserve.lehigh.edu/cgi/viewcontent.cgi?article=2467&context=etd [Accessed 8 Oct. 2016]. Improving access, responding to patients. (2016). 1st ed. [ebook] Available at: http://www.practicemanagement.org.uk/uploads/access_guide/090702__improving_access_resp onding_to_patients_final.pdf [Accessed 8 Oct. 2016]. Mike Benkovich, C. (2016). Online Appointment Scheduling Software for all business - SimplyBook.me. [online] Simplybook Free Online Appointment Scheduling Software System for Web and Mobile. Available at: https://simplybook.me/index/we-are-fit-for [Accessed 8 Oct. 2016]. 60