2. Our Client Dr. Mawjood Institute of Indigenous Medicine University Of Colombo

3. Our Supervisor Mr. Rasika Dayarathne

4. What is our System? Give comparative analysis about western & Indigenous Medicine

5. GAP ANALYSIS

6. No readily available reliable Medical information. Poor communication of simple medical solutions. Poor knowledge on the current medical issues. No comparison between available treatments. Lack of awareness on the new medical innovations. Absence of an active discussion forum. Current state

7. Desired state Ability to provide timely and accurate details. Ability to provide reliable medical treatments. System should achieve all it’s functional requirements. Ability to maintain databases accurately and update them time to time. Maintaining strong security.

8. Operability with minimum computer knowledge. Should support information sharing among professionals. Should have a demand to publish advertisements on the site

9. Up to date health related articles Various treatments under western & indigenous systems Details on various diagnoses Comparison discussion forum Public comment thread Question & Answer platform Our system is a public internet site Providing,

10. System Users External Users Internal Users

11. External Users Patients Researchers University Students Any other information needed parties Internal Users System Administrators Medical Specialists/ Doctors Users

12. Requirement gathering Got advises from our supervisorObserved existing similar sites.Got the public opinion.Analyzed documents

13. User Requirements Functional Requirements Non Functional Requirements

14. System should provide,  General details about diagnosis  Drugs and Treatments for diagnosis  General health details. functional requirements

15.  Facility for publish and edit health related articles  Question & Answer form  Discussion form

16. Non functional requirements System should,  User Friendly  Secure different security levels  Accurate  Reliable

17. Reports generate by the system. Log Details ReportList of registered usersList of existing articles List of Diagnoses List of Treatments Viewers Report Complete detail reports about particular diagnosis

18. Feasibility Study OperationalCulturalLegalEconomicTechnicalSchedule

19. Operational Feasibility SystemDesired Requirementsstate  Ease of reach  Demanding quality due to intense competition.  Rich composition of the medical board.  High user friendliness to overcome language barriers.

20. Economic Feasibility Software Hardware Employees Maintenance  No cost to system users.  Benefits of the system clearly outweighed the costs of development.  Most of the benefits are intangible & non monitory.  System can cover maintenance costs through advertising.

21. Technical Feasibility PHP, Apache, MySQL, Joomla  All the technologies are free & obtainable.  Technologies have the capacity to meet our requirements.  Selected technologies supports each other.

22. System Requirements System Requirements Hardware Requirements Software Requirements

23.  Visual Paradigm for UML 7.0  Net beans 6.9  XHTML  Case Cade Style Sheets  Java Script  MySQL Server

24.  PHP  Java Server Pages and Servlets  WAMP Server  Apache Tomcat Server  Net beans 6.9  Adobe Dream viewer CS4

25. Hardware Requirements Should have a high storage capacity. Should be able to handle multiple tasks.

27. System Administrator Medical Specialist External Registered User External Non- Registered User System Actors

28. External Users Registered Have login name & password Able to participate many activities in system Provide user details to the system Uses internet to access the system Do not required high technical knowledge, but computer literacy Non- Registered Can only view articles, view diagnosis and view treatments Uses internet to access the system Do not required high technical knowledge, but computer literacy

29. System Administrator Create or remove user from the system Need frequency use of the system Can change privacy policy Need high technical knowledge Medical Specialist Given access by administrator High experience and good knowledge about western & indigenous medicine Manage articles, medical information & forums Internal Users

30.  User Maintenance  Manage Medical Information  External User Registration  Manage Articles  View General Health Information  View Treatments  Ask and Answer Questions  Participating to Discussion Forums Major Use Cases

31. Main Use Case Diagram

32. Class diagram

34. Client Server architecture We will be using a Client-server architecture.

35. Why client server architecture ?  Centralization - access, resources, and data security  Scalability - any element can be upgraded  Flexibility - new technology can be easily integrated  Interoperability - all components (clients, network, servers) work together

37. Database Design  We are using a relational database management system.  Facilitates multiple access at the same time.  Centralized approach.  Avoids data redundancy

38. Treatments Table Registered Users Table Article Table Diagnosis Table