Medicate Documentation

Medicare and Medicaid services
1. INTRODUCTION
1.1 PURPOSE: This project aims at providing medical assistance for common people who have minimal computer knowledge and need not have any medical knowledge.The main purpose of developing this system is to provide a place where several information related to medicines can be known by general public and it provides an environment where medicos from different experience levels can interact with each other.
1.2 PROJECT SCOPE: This system also provides various categories such as Ayurvedic , Allopathy, Homeopathy etc where in so that users can search according to there interest. This system also provides a forum for Junior and Senior level doctors where we can have registered and non registered users. Doctors can post queries and get responses. It is web based application. Users are free to search. Doctors are Primary Stakeholders. Feedback facility. Registration/Login facility. Open community like module is available
1.3 EXISTING SYSTEM:
Presently there is no such system where people can find the information related to any medicine or medical related information and there is no such platform that provide all kinds of treatment at one base.
ST.MARYS COLLEGE OF ENGG & TECH
1.4 PROPOSED SYSTEM:
The objective of this project is to develop a system which is useful in the above mentioned emergency situations effectively. This project involves the detailed study of the symptoms of the disease and its severity. This is not merely based on the theoretical knowledge of medicine but is performed under the esteem supervision of highly experience doctors from all the fields of medicine. This includes the symptoms, videos and also video chat between the doctor and the patients which help in diagnosing the disease. This is mainly intended to provide first-aid for the persons before they could be taken to the doctor and also helps a lot during the natural calamities where its very difficult to provide direct medical assistance to the affected people. This includes the names of the medicines for cure of common diseases. The proposed system provides various means through which lot of information related to medical can be retrieved. This system not only benefits general public but also to medical professionals.
1.5 MODULES:The project is divided into 7 subsystems each is having its own process to perform and the work of each sub system is shown as follows.
Search Module Feedback Module First aid Module Admin Module Registration Module Login Module Forum Module
SEARCH MODULE:Search module provides the information about the treatments, medicines and the symptoms. This is the main functionality in this system because of medicine index system that means, if any user wants to take a medicine regarding to his illness, he/she can free to search and take the medicine according to result where it was provided in system. This module takes the name of the medicine or a disease as input and searches for that in the database and displays the results i.e., the purpose of the medicine or the treatment that have to be followed. The perfect module would allow one to enter symptoms, and get an ordered result of the top likely illnesses in order of nearest match to the symptoms searched for. We have a search function on the homepage that will present the user with a series of dropdown boxes as search options. These search options preferably need to be based on the medical symptoms and retrieves the preferred solution. New registered users will be provided to choose an option on the home page to get information about the medication, disease and which involves detailed study of first-aid treatments.
FEEDBACK MODULE:This module welcomes the feedback from the user of the system and it indicates the necessary actions that have to be taken by the administrator. The feedback can be taken by the people from Medical backgrounds like Doctors at all levels, Medicos, Pharmacists and the people involved in Bio-Technology, etc.Here feedback option is provided in order to gather the information from various medical departments inorder to develop the various drawbacks of the present developed system and to overcome them in a better manner based on the options provided by various people regarding the site.It also provides a scope for the developer to implement various features in the site regarding various functionalities regarding to medical background. Thus, by proving feedback option the administrator come to know the user problems regarding to site or search or any functionality and thus user can send his valuable feedback to the administrator.
FIRST AID MODULE:The First aid module includes the names of the medicines for cure of common diseases. It emphasis is on the various first aid treatments in the form of text, images and videos which has to be followed in the critical situations to yield better results. Through the First-aid module users can be provided with a simple and easy way of descriptions of various kinds of treatments and their availability. The system is designed with completely automated process hence there is less user intervention. Through the First-aid module in the present system is concentrated only on that part of the health care were a common man was ought to see and can implement the same in the critical situations. This is mainly for providing the information about the medicines and thus, user can get information about the medication, disease and which involves detailed study of first-aid treatments. This module is concentrated only on that part of the health care were a common man was ought to see and can implement the same in the critical situations.
ADMIN MODULE:This module is concerned with the updates and validating the users. Here as we are dealing with the various medical issues and the first-aid treatments we need to take minimal care regarding the doctors who participate in the Forums are certified practitioners or not. Thus, in order to validate only the certified doctors we are implementing the Admin module where the role of the admin is to check whether the doctors who registers into the site are certified practitioners or not.Thus, in order to verify their identity admin need to carry out the validations and updations. Admin also carries out the updations and validations on the users and pharmacists. Here as we are dealing with the various medical issues and the first-aid treatments we need to take verify the pharmacists identity who delivers the medicines to the Users and should check whether they are certified pharmacists or not. Thus in order to validate only the registered pharmacists we are implementing the Admin module where the role of the admin is to check whether the pharmacists who registers into the site are registered or not.Thus, in o rder to verify their identity admin need to carry out the validations and updations.
REGISTRATION AND LOGIN MODULE: This is the process where user first need to login into the site to carry out the various functionalities that are provided in the site. The Registered users thus can login to execute further functionalities like forums and other features like order medicine. Here, if user is not a registered user, this is the process where user can get registered easily without any fee. Professional registrations like doctor registration or pharmacist registration may take one business day as the validating of the doctor and pharmacist is carried out by the administrator. Here in this module the pharmacist first needs to register and then login into the site. The pharmacist then with his given username identity can take the orders from the users and deliver the medicines in time. This module takes care about collecting the information about various users and depositing the same in the database. Login module verifies whether the user is intended to enter into that part of the system which requires a valid identity
FORUM MODULE:This module is responsible for conducting the online discussions for the registered users of the system and need to store the details regarding the conversations between the users. After user logins into the site, users can send their queries regarding to their health and this is an open community where user can send a query or user can send solution regarding to any query. In Forums the users can participate in discussions with the doctors regarding various medical problems and their solutions. Here Doctors give the solutions for the problems that are posted by the user accordingly. People from Medical backgrounds like Doctors at all levels, Medicos, Pharmacists and the people involved in Bio-Technology, etc. can all participate in the forums but need to get registered in the site in order to participate in the forums .Thus Forum module provides an extreme functionality to the user where he can discuss his problem and get a solution for his problem by esteem supervision of highly experience doctors from all the fields of medicine.
1.6 ADVANTAGES:
USABILITY:The system is designed with completely automated process hence there is less user intervention. Usability is the ease of use and learnability of a human-made object. The object of use can be a software application, website, book, tool, machine, process, or anything a human interacts with.
RELIABILITY:The system is more reliable because of the qualities that are inherited from the chosen platform java. The code built by using java server pages is more reliable. The ability of a system or component to perform its required functions under stated conditions for a specified period of time.
PERFORMANCE:The system exhibits high performance because it is well optimized. It uses the automatic garbage collection from java.
SUPPORTABILITY:The system is designed to be the cross platform supportable. The system is supported on a wide range of hardware and any software platform.
IMPLEMENTATION:The system is implemented in the JAVA SERVER PAGES concept.
2. LITERATURE SURVEY
2.1. About Programming Language : JAVA Topic1:Characteristics of Java: Java has become enormously popular. Javas rapid rise and wide acceptance can be traced to its design and programming features, particularly its promise that you can write a program once and run it anywhere. As stated in the Java language white paper by Sun, Java is
simple, objectoriented, distributed, interpreted, robust, secure,architecture- neutral, portable, high-performance, multithreaded, and dynamic. Implementation Technology: The J2EE platform uses a distributed multitier application model for enterpris applications. Application logic is divided into components according to function, and the various application components that make up a J2EE application are installed on different machines depending on the tier in the multitier J2EE environment to which the application component belongs. Multitier J2EE applications divided into the tiers described in the following list. .Client-tier components run on the client machine. Web-tier components run on the J2EE server. Business-tier components run on the J2EE server.
2.2. SERVLETS: INTRODUCTION OF SERVLETS: A Servlet is a Java technology based web component, managed by a container that generates dynamic content. Like other Java-based components, Servlets are platform independent Java classes that are compiled to platform neutral byte code that can be loaded dynamically into and run by a Java enabled web server. Containers, sometimes called Servlet engines, are web server extensions that provide Servlet functionality. Servlets interact with web clients via a request/response paradigm implemented by the Servlet container. The Servlet container is a part of a web server or application server that provides the network services over which requests and responses are sent, decodes MIME based requests, and formats MIME based responses. A Servlet container also contains and manages Servlets through their lifecycle. A Servlet container can be built into a host web server, or installed as an add-on component to a Web Server via that servers native extension API. A Servlet Container may place security restrictions on the environment in which a Servlet executes. In a Java TM 2 Platform, Standard Edition 1.6 (J2SETM) or Java TM 2 Platform, Enterprise Edition 5.0 (J2EE) environment, these restrictions should be placed using the permission architecture defined by the Java 2 platform. Just like an applet is a client side program, a Servlet is a server side program, written in java, that is dynamically extends the functionality of a server. Similar to the manner in which applets run inside a web browser on the client, Servlets execute inside Apache Tomcat on the server. Unlike applets, Servlets do not display a Graphical Interface to the user. A Servlet work is done behind the scenes on the server and only the Servlets processing are returned to the client.
Servlet Architecture:
2.3. My SQL MySql5.0 MySQL is Relational database Management System this program runs as a server providing multi-user access to a number of databases.It is a open source product of Sun micro systems. Platforms and Availability The production version of MySQL 5.0 is available now for Linux, Windows, Solaris, Mac OS X and a range of other operating systems.All MySQL database software is available under a dual licensing model. Developers and organizations can choose between open sources (GPL) or a commercial MySQL license, depending on their deployment requirements. End-user enterprises can also subscribe to MySQL Network, a comprehensive set of certified software and premium support services. MySQL 5.0's Enterprise Database Features: The new MySQL 5.0 combines enterprise-grade reliability and performance with advanced SQL 2003 standard-compliant features, making it the most cost-effective database solution for business-critical applications. The product's new functionality will be especially familiar to database developers and DBAs of proprietary relational database systems -- allowing IT departments to ease the integration and transition of their data, applications and skill-sets. Open Source and MySQL @ Work in Applications Key elements of open source software that make it attractive to government include: Greater interoperability Eliminates lock-in Higher level of security Lower Total Cost of Ownership (TCO) We review some of the reasons why open source software is ideally suited to Applications. We also provide examples of where open source software in general, and the MySQL open source database in particular, have enabled government organizations to develop
10
and deploy highly scalable applications at a fraction of the total cost of traditional, closed source software. WebServerComponents: Web server: application that responds to HTTP requests by returning web resources such as HTML files, images, applets, and CGI output over the Internet . Servlet container (or servlet engine): Runtime shell that invokes servlets on behalf of clients; software that runs servlets and manages them through their lifecycle (e.g., Tomcat servlet container.) 2.4. HTML INTRODUCTION TO HTML What is World Wide Web? The World Wide Web is a network of information resources. The web realize on three mechanism to make the resources readily available to the widest possible audience: 1. A Uniform name is scheme for locating resources on the web (E.g.: - URLs) 2. Protocols, for access to named resources over the web (E.g.: - http). 3. Hypertext, for easy navigation among resources (E.g.: - HTML) The ties between the three mechanisms are apparent throughout this specification.
11
Introduction to URLs: Every resource available on the web-TML document, image, video clips, program, etc. Has an address that may be an encoded by a Uniform Resource Locator, or "URL" URLs typically consist of three pieces: 1. The naming scheme of the mechanism used to access the resource. 2. The name of the machine hosting the resource. 3. The name of the resource itself, given as a path.
12
3.REQUIREMENT ANALYSIS
3.1. FUNCTIONAL REQUIREMENTS: Search: He should have minimal computer knowledge to open and use the website. When the user enters the keyword and clicks on search button, the keyword is searched in the database and all the data or records that match with the keyword are displayed and then the user has to choose the desired which is retrieved from the database. if the keyword doesnt match with any of the data in the database then a message keyword not found is displayed. Register: User has to fill the mandatory fields of registration form.When the user wants to consult a doctor or pharmacist through the website, then he should be registered. so, for that the user has to click on register then a web page of registration form gets opened and user has to enter all the details (user is allowed to enter his own user-id or password in registration form however with some constraints) and click on submit button. Then the details of the user are stored into the database and user gets a message successfully registered.If the user doesnt enter any of the mandatory fields of the registration form and clicks on submit an error message enter respective field is displayed. Login: User requires user-id and password to login.When the user enters user-id and password and clicks on login ,the user-id and password are verified with the database and if it matches with the database the user gets logged into his account else an error message invalid user-id or password is displayed.
13
Report Upload: User should be logged in into his account. To upload a report, patient has to logon to his account and click on upload to browse the report from the system and enter user-id of the doctor to whom the report has to be sent and then click on send. Then it verifies the user-id (to be sent) with the database and if it matches with the database. The report is send to that doctors account and when doctor logs on into his account can view the report and reply.
Order Medicine: User should be registered to use this feature. User has to select the pharmacist to whom order has to be done and click on order now. Then a webpage of order form gets opened. Then the user has to fill all the details and click on order. The details are sent to the pharmacist account and then the pharmacist confirms the order by sending a bill. If the user doesnt enter any of the mandatory fields of the order form and clicks on order an error message enter respective field is displayed. If any of the medicines ordered are not available with the pharmacist the same is informed to the user. Feedback: User may or may not be registered. The user using the website can leave a feedback by clicking on Leave Feedback which is stored on to the database and can be used by the admin to improve the website.
Forum: User should be registered to use this feature. Forum is between budding practitioners and senior level doctors. Here budding practitioners can post their queries which are stored onto the database and can be viewed and replied by senior level doctors and the replies are also stored on to the database which can be viewed by any user.
14
3.2. NON FUNCTIONAL REQUIREMENTS: Describe user visible aspects of the system that are not directly related with the functional behavior of system. Non functional requirements include quantative constraints, such as response time (i.e. how fast the system reacts to user command) or accuracy (i.e. how system numerical answers). 3.2.1.Performance Requirements The product shall be based on web and has to be run from a web server. The product shall take initial load time depending on the internet connection strength which also depends on the media from which the product is run. The performance shall depend upon hardware components of the client/customer.System can withstand many number of clients requested the desired service. As Mediworld is an internet application it provides direct communication with the users of the system where they can get their queries or problems resolved. 3.2.2. Safety Requirements
By incorporating a robust and proven DBMS (Sql Server 200) into the system, reliable performance and integrity of data is ensured. There must be a power back up for server requirements.
3.2.3. Security Requirements The system shall use secure sockets in all transactions that include any confidential clients information like details of the patient and his disease. The system shall automatically log out all clients after a period of inactivity. The system shall not leave any cookies on the clients computer containing the users password and any of the users confidential information. The customers web browser shall never display a customers password. The systems back-end servers shall only be accessible to authenticated administrator.
This system maintains the secrecy of user details. This is maintained by using user ids and passwords. Data confidentiality can be provided in such a way that functionalities of one user cannot be used by other user.
15
3.2.4. Software Quality Attributes: Functionality: The ability of the system to do the work for which it was intended. Performance: The response time, utilization, and throughput behavior of the system. Not to be confused with human performance or system delivery time. Security: A measure of systems ability to resist unauthorized attempts at usage or behavior modification, while still providing service to legitimate users. Availability: The measure of time that the system is up and running correctly; the length of time between failures and the length of time needed to resume operation after a failure. Usability: The ease of use and of training the end users of the system. Sub qualities: learnability, efficiency, affect, helpfulness, control. Interoperability: The ability of two or more systems to cooperate at runtime. Modifiability: The ease with which a software system can accommodate changes to its Software Portability: The ability of a system to run under different computing environments. The Environment types can be either hardware or software, but is usually a combination of the Two. Reusability: The degree to which existing applications can be reused in new applications Integrability: The ability to make the separately developed components of the system work correctly together. Testability: The ease with which software can be made to demonstrate its faults.
3.3. USECASE DIAGRAMS:

A use case diagram shows a set of use cases and actors and their relationships. Use case diagrams address the static use case view of a system. These diagrams are especially important in organizing and modeling the behaviors of a system.Use case diagrams commonly contain Use cases Actors Dependency, generalization and association relationships
16
Use case diagrams for Medicare and Medicaid services system are as follows
FIG 1
17
FIG 2
18
3.4.Sequence diagram:
A sequence diagram is an interaction diagram that emphasizes the time ordering of messages. Graphically, a sequence diagram is a table that shows objects arranged along the X axis and messages, ordered in increasing time, along the Y axis. Sequence diagrams commonly contain Objects Links Messages
Sequence diagrams have two features. First, there is an object life line. An object lifeline is the vertical dashed line that represents the existence of an object over a period of time. Most objects that appear in an interaction diagram will be in existence for the duration of the interaction, so the objects are all aligned at the top of the diagram, with their life lines drawn from the top of the diagram to the bottom. Objects may be created during the interaction, their lifelines start with the receipt of the message stereotyped as create. Objects may be destroyed during the interaction, their lifelines start with the receipt of the message stereotyped as destroy. Second, there is a focus of control. The focus of control is a tall, thin rectangle that shows the period of time during which an object is performing an action, either directly or through a subordinate procedure. The top of the rectangle is aligned with the start of the action; the bottom is aligned with its completion.
19
Visitor:
FIG 3.1
20
Patient:
FIG 3.2
21
Pharmacist:
FIG 3.3
22
Admin:
FIG 3.4
23
3.5. COLLABORATION DIAGRAM: A collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages. Graphically, a collaboration diagram is a collection of vertices and arcs. A collaboration diagram emphasizes the organization of the objects that participate in an interaction. Collaboration diagrams have two features. First, there is a path, to indicate one object is linked to another. Second, there is a sequence number, to indicate the time order of a message. Visitor:
FIG 4.1
FFFFFFFF
24
Patient:
FIG 4.2
25
Pharmacist:
FIG 4.3
26
Admin:
FIG 4.4
27
3.5. Software Requirements: Operating System: Win 2000 & above Front End: Java Back End: SQL Server2000/2005
3.6. Hardware Requirements:
512 min RAM 20GB Hard Disk
28
4.ARCHITECTURE
4.1. Technical Architecture:
29
4.2. System Architecture:
30
31
5.DESIGN
5.1. Data Flow Diagram: A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be
/described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops the data flow diagrams. Each component in a DFD is labeled with a descriptive name. Process is further identified with a number that will be used for identification purpose. The development of DFDs is done in several levels. Each process in lower level diagrams can be broken down into a more detailed DFD in the next level. The lop-level diagram is often called context diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the context level diagram is exploded into other process at the first level DFD. The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is described for analyst to understand the process. Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to the modular design.A DFD is also known as a bubble Chart has the purpose of clarifying system requirements and identifying major transformations that will become programs in system design. So it is the starting point of the design to the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.
32
DFD SYMBOLS: In the DFD, there are four symbols 1. A square defines a source(originator) or destination of system data 2. An arrow identifies data flow. It is the pipeline through which the information flows 3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. 4. An open rectangle is a data store, data at rest or a temporary repository of data
Process that transforms data flow.
Source or Destination of data
Data flow
Data Store
33
CONSTRUCTING A DFD: Several rules of thumb are used in drawing DFDs: 1. Process should be named and numbered for an easy reference. representative of the process. 2. The direction of flow is from top to bottom and from left to right. Data Traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal. 3. When a process is exploded into lower level details, they are numbered. 4. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized Each name should be
A DFD typically shows the minimum contents of data store. Each data store should contain all the data elements that flow in and out. Questionnaires should contain all the data elements that flow in and out. Missing interfaces redundancies and like is then accounted for often through interviews. SAILENT FEATURES OF DFDs 1. The DFD shows flow of data, not of control loops and decision are controlled considerations do not appear on a DFD. 2. The DFD does not indicate the time factor involved in any process whether the dataflows take place daily, weekly, monthly or yearly. 3. The sequence of events is not brought out on the DFD.
TYPES OF DATA FLOW DIAGRAMS: 1. Current Physical 2. Current Logical 3. New Logical
34
4. New Physical CURRENT PHYSICAL: In Current Physical DFD proecess label include the name of people or their positions or the names of computer systems that might provide some of the overall system-processing label includes an identification of the technology used to process the data. Similarly data flows and data stores are often labels with the names of the actual physical media on which data are stored such as file folders, computer files, business forms or computer tapes.
CURRENT LOGICAL: The physical aspects at the system are removed as mush as possible so that the current system is reduced to its essence to the data and the processors that transform them regardless of actual physical form. NEW LOGICAL: This is exactly like a current logical model if the user were completely happy with he user were completely happy with the functionality of the current system but had problems with how it was implemented typically through the new logical model will differ from current logical model while having additional functions, absolute function removal and inefficient flows recognized. NEW PHYSICAL: The new physical represents only the physical implementation of the new system.
RULES GOVERNING THE DFDS: Process 1) No process can have only outputs. 2) No process can have only inputs. If an object has only inputs than it must be a sink.
35
3) A process has a verb phrase label. DATA STORE: 1) Data cannot move directly from one data store to another data store, a process must move data. 2) Data cannot move directly from an outside source to a data store, a process, which receives, must move data from the source and place the data into data store 3) A data store has a noun phrase label. SOURCE OR SINK: The origin and /or destination of data. 1) Data cannot move direly from a source to sink it must be moved by a process 2) A source and /or sink has a noun phrase land
DATA FLOW: 1) A Data Flow has only one direction of flow between symbol. It may flow in both directions between a process and a data store to show a read before an update. The later is usually indicated however by two separate arrows since these happen at different type. 2) A join in DFD means that exactly the same data comes from any of two or more different processes data store or sink to a common location. 3) A data flow cannot go directly back to the same process it leads. There must be atleast one other process that handles the data flow produce some other data flow returns the original data into the beginning process. 4) A Data flow to a data store means update ( delete or change). 5) A data Flow from a data store means retrieve or use.
A data flow has a noun phrase label more than one data flow noun phrase can appear on a single arrow as long as all of the flows on the same arrow move together as one package.
36
Data flow diagrams represent the flow of data through a system. A DFD is composed of: Data movement shown by tagged arrows. Transformation or process of data shown by named bubbles. Sources and destination of data represented by named rectangles. Static storage or data at rest denoted by an open rectangle that is named. The DFD is intended to represent information flow but it is not a flow chart and it is not intended to indicate decision-making, flow of control, loops and other procedural aspects of the system. DFD is a useful graphical tool and is applied at the earlier stages of requirements analysis. It may be further refined at preliminary design states and is used as mechanism for creating a top level structural design for software. The DFD drawn first at a preliminary level is further expanded into greater details:
The context diagram is decomposed and represented with multiple bubbles. Each of these bubbles may be decomposed further and documented as more detailed
DFDs. Context level diagram:
37
FIG 5
38
Level 1 diagram :
FIG 6
39
Database Tables:
Diseases Details:
1. Name DID Dname Cdate
2. Null? NOT NULL
3. Type Int VARCHAR2(12) Datetime
TABLE 5.1
Feedback details:
4. Name fno Description Solution Cdate
5. Null? NOT NULL
6. Type int VARCHAR2(50) VARCHAR2(max) datetime
TABLE 5.2
40
Medicine details:
7. Name medicineno Mrank Mname mcategory Mmanufacture Mside Disease Age Dosage m_composition Cdate
8. Null? NOT NULL
9. Type int VARCHAR2(50) VARCHAR2(max) Varchar2(max) Varchar2(max) Varchar2(max) Varchar2(max) Varchar2(max) Varchar2(max) Varchar2(max) Datetime
TABLE 5.3
41
Registration:
10. Name Rno Username Password fname lname Cdate
11. Null? NOT NULL
12. Type int VARCHAR2(50) VARCHAR2(max) Varchar2(max) Varchar2(max) Datetime
TABLE 5.4
Problem:
13. Name Pno Pname Problem Email Site Cdate
14. Null? NOT NULL(primary key)
15. Type int VARCHAR2(50) VARCHAR2(max) Varchar2(max) Varchar2(max) Datetime
TABLE 5.5
42
Solution:
16. Name Tsol Pno Name Problem Solution Email Cdate
17. Null? NOT NULL Foregin key
18. Type int int VARCHAR2(max) Varchar2(max) Varchar2(max) Varchar2(max) datetime
TABLE 5.6
43
Product:
19. Name Pid Did Pdisease Pname Pdosage psideeffects Page Cdate
20. Null? NOT NULL Foregin key
21. Type int int VARCHAR2(max) Varchar2(max) Varchar2(max) Varchar2(max) Varchar2(50) datetime
TABLE 5.7
5.2. Activity Diagram: Activity diagrams are one of the five diagrams in the UML for modeling the dynamic aspects of systems. An activity diagram is essentially a flowchart, showing flow of control from activity to activity. Whereas interaction diagrams emphasize the flow of control from object to object, activity diagrams emphasize the flow of control from activity to activity. An activity is an ongoing non-atomic execution within a state machine. Activities ultimately result in some action, which is made up of executable atomic computations that result in a change in state of the system or the return of a value.
44
Activity diagrams are not only important for modeling the dynamic aspects of a system, but also for constructing executable systems through forward and reverse engineering. Graphically an activity diagram is a collection of vertices and arcs
Activity diagram commonly contain Activity states and action states Transitions Objects
45
46
FIG 13
5.3. Class diagram: A class diagram shows a set of classes, interfaces, and collaborations and their relationships. A class diagram is just a special kind of diagram and shares the same common properties as do all other diagrams- a name and graphical content that are projection into a model. Class diagram commonly contain the following Classes Interfaces Collaborations Dependency, generalization, and association relationships
47
FIG 8
48
6.IMPLEMENTATION
Implementation is the stage where the theoretical design is turned into a working system. The most crucial stage in achieving a new successful system and in giving confidence on the new system for the users that it will work efficiently and effectively. The system can be implemented only after thorough testing is done and if it is found to work according to the specification. It involves careful planning, investigation of the current system and its constraints on implementation, design of methods to achieve the change over and an evaluation of change over methods a part from planning. Two major tasks of preparing the implementation are education and training of the users and testing of the system.The more complex the system being implemented, the more involved will be the systems analysis and design effort required just for implementation. The implementation phase comprises of several activities. The required hardware and software acquisition is carried out. The system may require some software to be developed. For this, programs are written and tested. The user then changes over to his new fully tested system and the old system is discontinued.
49
6.1. pseudo code: 1.SEARCH <%@ page import = "java.sql.*"%> <%@ page import = "java.lang.*"%> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title>Medicine Record</title> <% String Name = request.getParameter("T1");%> <% if (Name=="") { out.print("no record found"); } %> <% Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); String dbURL = "jdbc:odbc:op"; Connection con = DriverManager.getConnection(dbURL); Statement s=con.createStatement();
50
ResultSet rs =s.executeQuery("select * from tblmedicine where disease like'"+Name+"' ORDER BY m_rank"); %> <script language=javascript > function changecolor() { if (document.forms("ch").D1.value == 1) { document.bgColor="#4b927c" } if (document.forms("ch").D1.value == 2) { //document.forms("ch").backcolor = blue document.bgColor = "#808080" } if (document.forms("ch").D1.value == 3) { //document.forms("ch").backcolor = blue document.bgColor = "ff8080" } if (document.forms("ch").D1.value == 4)
51
{ //document.forms("ch").backcolor = blue document.bgColor = "#ffffff" } } </script> <title>New Pae 2</title> </head> <body> <div align="center"> <p align="left"><b> <fontcolor="#FFFFFF" size="2" face="Verdana"> a Medicine for Your Illness </font></b></p> <p align="right"><a href="home.html">Home</a> <a href="services.html">Log in</a>   <a href="contact.html">FeedBack</a></p> <form action="search.jsp" method="post"> <div align="right">                                    <strong><fontcolor="#993366">  Moresearch </font></strong>
size="2"
face="Verdana">Search</font><font
color="#FF8000"
52
<input type="text" name="T1" size="25"> <input type="submit" value="Go!" name="B1" style="text-decoration: underline; color: #6699FF; font-family: Tempus Sans ITC; font-weight: bold">        </div> </form> <p align="left"><font color="#996666"><em><font face="Verdana, Arial, Helvetica, sansserif"><strong>This is the detail of Your Medicine **</strong></font></em></font> <%while(rs.next()) { </p> </div> <div align="center"> <div align="right"> <div align="left"> <p></p><p></p> </div> <div align="left"> </div> </div> </div> <form method="post" name="ch">
53
<p><font color="#008080"><b><font face="Verdana" size="2">Here user can select to this page color according to him by choosing from the combo box:</font></b><select size="1" name="D1" onchange= "changecolor()"> <option value = 1>Green</option> <option value = 2>Gray</option> <option value = 3>Pink</option> <option value = 4>White</option> </select></font></p> </form> <p><em><font color="#996666"><strong><font face="Verdana, Arial, Helvetica, sansserif"></p> <tablewidth="34%",border="1",cellpadding=2,cellspacing=5align=center bordercolor=#E2F2F1> <tr> <td width="27%" bgcolor="#FFFFFF"><b> <font face="Verdana" size="2" color="#008080">Medicine Rank</font></b></td> </font> <td width="32%" bgcolor="#FFFFFF"> <font face="Verdana" size="2"><%=rs.getString("m_rank")%> </font></td> </tr> <font face="Verdana, Arial, Helvetica, sans-serif"> <tr>
54
<td width="27%" bgcolor="#FFFFFF"><b> <font face="Verdana" size="2" color="#008080">Medicine Name</font></b></td> <td width="32%" bgcolor="#FFFFFF"><font face="Verdana"
size="2"><%=rs.getString("m_name")%> </font></td> </tr> <tr> <td width="27%" bgcolor="#FFFFFF"><b> <font face="Verdana" size="2" color="#008080">Medicine Category</font></b></td> <td width="32%" bgcolor="#FFFFFF"> <font face="Verdana" size="2"><%=rs.getString("m_category")%> </font></td> </tr> <tr> <td bgcolor="#FFFFFF"><b><font face="Verdana" size="2" color="#008080">Medicine Manufacturer</font></b></td> <bgcolor="#FFFFFF"><font="Verdana" size="2"><%=rs.getString("m_manfac")%> </font></td> </tr> <tr> <td bgcolor="#FFFFFF"><b><font face="Verdana" size="2" color="#008080"> Side Effects</font></b></td> <bgcolor="#FFFFFF"><font="Verdana" size="2"><%=rs.getString("m_side")%> </font></td>
55
</tr> <tr> <td bgcolor="#FFFFFF"><b><font face="Verdana" size="2" color="#008080"> Disease</font></b></td> <bgcolor="#FFFFFF"><font="Verdana" size="2"><%=rs.getString("disease")%> </font></td> </tr> <tr> <bgcolor="#FFFFFF"><b><font="Verdana",size="2",color="#008080">Age</font></b></td> <bgcolor="#FFFFFF"><font="Verdana" size="2"><%=rs.getString("age")%></font></td> </tr> <tr> <bgcolor="#FFFFFF"><b><font="Verdana",size="2",color="#008080">Dosage</font></t> <bgcolor="#FFFFFF"><font="Verdana" size="2"> <%=rs.getString("dosage")%></font></td> </tr> <tr>
<bcolor="#FFFFFF"><font="Verdana",size="2",color="#008080"><b>M</b><strong>medicine Composition </strong></font></td> <bgcolor="#FFFFFF"><font="Verdana",size="2"> <%=rs.getString("m_composition")% ></font></td></tr>

56
</table> </div> <%%> <% s.close(); con.close(); %> </p> <font size="4" face="CommercialScript BT">*</font><font face="Bradley Hand ITC">* This data is like First-Aid Treatment of any patient. If any </font></font> </strong></font><strong> <font face="Verdana, Arial, Helvetica, sans-serif"> <fontface="BradleyHandITC"><fontcolor="#FF0000">allergy</font><font color="#996666">or </font><fontcolor="#FF0000">itching</font></font><fontcolor="#996666"><font face="Bradley Hand ITC"> contact Your Doctor </font> </body> </html>
57
2.USER REGISTRATION: <%@ page import="java.sql.*" %> <html> <head> <title>Thanks</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <% String n = request.getParameter("uname"); String un = request.getParameter("id"); String p = request.getParameter("pwd"); String g=request.getParameter("r1"); String email=request.getParameter("eid"); String adr=request.getParameter("addr"); String type="User"; Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); String dbURL = "jdbc:odbc:op"; Connection con =null; Statement s=null; int rs=0;
58
try { con = DriverManager.getConnection(dbURL); s=con.createStatement(); rs=s.executeUpdate("insert into user_reg values('"+n+"','"+un+"','"+p+"','"+g+"','"+email+"','"+adr+"') "); if(rs>=1) { int c=0; Connection cc=DriverManager.getConnection("jdbc:odbc:op"); Statement ss=cc.createStatement(); c=ss.executeUpdate("insert into ulogin values('"+un+"','"+p+"','"+type+"')"); } } catch(Exception e) { out.println(e);} %> <font face="MS Sans Serif"> <b>  </b>Your Login Id: </font><font face="Square721 Ex BT" color="#808000"><%=un%> </font>
59
<p><font face="MS Sans Serif">Your Password:</font> <font face="Square721 Ex BT" color="#808000"><%=p%></p> </font> <font face="MS Sans Serif"> <p align="center">Click Here to <a href="services.html">Login </a></p></font> </body> </html> 3.ADMIN PRODUCTS <%@ page import="java.sql.*" %> <html> <head> <title>Thanks</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <% String p_disease = request.getParameter("p_disease"); String p_name = request.getParameter("p_name"); String p_dosage = request.getParameter("p_dosage"); String p_side = request.getParameter("p_side"); String p_age = request.getParameter("p_age");
60
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); String dbURL = "jdbc:odbc:op"; Connection con =null; Statement s=null; ResultSet rs=null; try { con = DriverManager.getConnection(dbURL); s=con.createStatement(); rs=s.executeQuery("insert into tblproduct_admin (p_disease,p_name,p_dosage,p_side,p_age) values ('"+p_disease+"','"+p_name+"','"+p_dosage+"','"+p_side+"','"+p_age+"')"); } catch(Exception e) { } %> <font face="MS Sans Serif"> <b>   </b> Thank u for your valuable information.</font></body> </html>
61
4.UPLOAD REPORTS: <%@ page language="java" import="java.util.*" pageEncoding="ISO-8859-1"%> <% String path = request.getContextPath(); String basePath = request.getScheme()+"://"+request.getServerName()+":"+request.getServerPort()+path+"/"; %> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <base href="<%=basePath%>"> <title>My JSP 'index.jsp' starting page</title> <meta http-equiv="pragma" content="no-cache"> <meta http-equiv="cache-control" content="no-cache"> <meta http-equiv="expires" content="0"> <meta http-equiv="keywords" content="keyword1,keyword2,keyword3"> <meta http-equiv="description" content="This is my page"> <!-<link rel="stylesheet" type="text/css" href="styles.css"> --> </head>
62
<body> file<form method ="post" action="one.jsp"> Enter Doctor Id:<input type="text" name="dname"></input><br><br></br> <input type="file" name="file1"> <br><br></br> <input type="submit" value="upload" />[Please Upload in gif format] </form> <a href="doclist.jsp">Click to View Available Doctors</a> </body> </html> 5.ORDER MEDICINE <%@page import="java.sql.*;" %> <% try { String i=(String)session.getAttribute("pid"); String mn=request.getParameter("mdn"); // out.println(mn); String q=request.getParameter("qty"); String a=request.getParameter("area"); String n=request.getParameter("uname");
63
String p=request.getParameter("ph"); String ad=request.getParameter("addr"); //out.println(a); Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); String dbURL = "jdbc:odbc:op"; Connection c9 = DriverManager.getConnection(dbURL); Statement ss7=c9.createStatement(); //out.println("1"); //out.println("4"); //Statement sss=con.; ResultSet rt=ss7.executeQuery("select * from pharmed where medname='"+mn+"' and area='"+a+"' "); if(rt.next()) { out.println("Medicine is Available"); out.println("<br><br><br>"); Connection cw=DriverManager.getConnection("jdbc:odbc:op"); Statement s0=cw.createStatement(); int j=s0.executeUpdate("insert into ordermed values('"+n+"','"+p+"','"+ad+"','"+a+"','"+mn+"','"+q+"' )"); out.println("<a href=order.html>Click here to Order</a>"); }
64
else { out.println("Sorry Medicine is not Available"); } } catch(Exception e) { out.println(e); } %>
65
7.TESTING
Software Testing is the process used to help identify the correctness, completeness, security, and quality of developed computer software. Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a criticism or comparison that compares the state and behaviour of the product against a specification. An important point is that software testing should be distinguished from the separate discipline of Software Quality Assurance (SQA), which encompasses all business process areas, not just testing. There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following routine procedure. One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are operations the tester attempts to execute with the product, and the product answers with its behavior in reaction to the probing of the tester[citation needed]. Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product putting the product through its paces. Some of the common quality attributes include capability, reliability, efficiency, portability, maintainability, compatibility and usability. A good test is sometimes described as one which reveals an error; however, more recent thinking suggests that a good test is one which reveals information of interest to someone who matters within the project community.
66
7.1. TYPES OF TESTING Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel. White Box Testing: This type of testing ensures that All independent paths have been exercised at least once All logical decisions have been exercised on their true and false sides All loops are executed at their boundaries and within their operational bounds All internal data structures have been exercised to assure their validity.
To follow the concept of white box testing we have tested each form .we have created independently to verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their boundaries.
Basic Path Testing: Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions. The main steps in deriving test cases were: Use the design of the code and draw correspondent flow graph. Determine the Cyclomatic complexity of resultant flow graph, using formula: V (G) =E-N+2 or V (G) =P+1 or V (G) =Number of Regions
67
Where V (G) is Cyclomatic complexity, E is the number of edges, N is the number of flow graph nodes, P is the number of predicate nodes. Determine the basis of set of linearly independent paths. Unit Testing: In computer programing, unit testing is a software verification and validation method in which a programmer tests if individual units of source code are fit for use. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual function or procedure. Ideally, each test case is independent from the others: substitutes like method stubs, mock objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit tests are typically written and run by software developers to ensure that code meets its design and behaves as intended. Its implementation can vary from being very manual (pencil and paper) to being formalized as part of build automation. . Integration Testing: Integration testing (sometimes called Integration and Testing, is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. System Testing: System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner
68
design of the code or logic. As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limiting type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole. 7.2.TEST CASES In software engineering, the most common definition of a test case is a set of conditions or variables under which a tester will determine if a requirement or use case upon an application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied. In order to fully test that all the requirements of an application are met, there must be at least one test case for each requirement unless a requirement has sub requirements. In that situation, each sub requirement must have at least one test case. This is frequently done using a Traceability matrix. Some methodologies, like RUP, recommend creating at least two test cases for each requirement. One of them should perform positive testing of requirement and other should perform negative testing. Written test cases should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted. If the application is created without formal requirements, then test cases can be written based on the accepted normal operation of programs of a similar class. In some schools or testing, test cases are not written at all but the activities and results are reported after the tests have been run. What characterizes a formal, written test case is that there is a known input and an expected output, which is worked out before the test is executed. The known input should test a precondition and the expected output should test a post condition. Under special circumstances, there could be a need to run the test, produce results, and then a team of experts would evaluate if the results can be considered as a pass. This happens often on new products' performance number determination. The first test is taken as the base line for subsequent test / product release cycles. Written test cases are usually collected into Test suites.
69
A variation of test cases are most commonly used in acceptance testing. Acceptance testing is done by a group of end-users or clients of the system to ensure the developed system meets their requirements. User acceptance testing is usually differentiated by the inclusion of happy path or positive test cases.
STRUCTURE OF TEST CASE Formal, written test cases consist of three main parts with subsections Information contains general information about Test case. Identifier is unique identifier of test case for further references, for example, while describing found defect. Test case owner/creator is name of tester or test designer, who created test or is responsible for its development Version of current Test case definition Name of test case should be human-oriented title which allows to quickly understand test case purpose and scope. Identifier of requirement which is covered by test case. Also here could be identifier of use case or functional specification item. Purpose contains short description of test purpose, what functionality it checks. Dependencies
Test case activity.
Testing environment/configuration contains information about configuration of hardware or software which must be met while executing test case
Initialization describes actions, which must be performed before test case execution is started. For example, we should open some file.
70
Finalization describes actions to be done after test case is performed. For example if test case crashes database, tester should restore it before other test cases will be performed.
Actions step by step to be done to complete test. Input data description
Results.
Actual results contains a brief description of what the tester saw after the test steps has been completed. This is often replaced with a Pass/Fail. Quite often if a test case fails, reference to the defect involved should be listed in this column
Expected results contains description of what tester should see after all test steps has been completed
71
7.2.1. TEST CASE1: Login :
Test case 1: Login Test Objective: To check whether the Candidate valid or invalid.
Priority (H, L): High
Test Description: The user or doctor or the pharmacist will enter his unique id and password and will click on login button. If valid, he is navigated to next page. Requirements Verified: Yes Test Setup/Pre-Conditions: Receiver should be in connection accept state
Actions
The user will click on the login button. If he is a new user, he clicks on Registration link. Pass: Yes Problems / Issues: NIL Notes: Successfully Executed Conditions pass: No
Expected Results
valid/invalid
Fail: No
72
7.2.2. TEST CASE2: REGISTRATION
Test case 2: Registration Test Objective: Registration is successful or not.
Test Description: The user or doctor or pharmacist will be registering here by providing all his details. Requirements Verified: Yes Test Setup/Pre-Conditions: Receiver should be in connection accept state
Actions
The user will click on the submit button.
Expected Results
Registration id and password displayed Fail: No
Pass: Yes Problems / Issues: NIL
Conditions pass: No
Notes: Successfully Executed
73
TEST CASE3: SEARCH
Test case 3: Search
Test Objective: To check whether particular required medicines and treatments list is generated or not. Test Description: The user will select his choice according to his requirement.. Requirements Verified: Yes Test Setup/Pre-Conditions: Receiver should be in connection accept state
22.
Actions
23. Expected Results

list of medicines,treatments and dosages Fail: No
The user will enter a disease and click on the search button Pass: Yes Problems / Issues: NIL Notes: Successfully Executed Conditions pass: No
74
TEST CASE4: UPLOAD REPORTS
Test case 4: Upload Reports Test Objective: To check whether the reports are uploaded or not.
Test Description: The user will browse the file or scanned copy to be uploaded. Requirements Verified: Yes Test Setup/Pre-Conditions: Receiver should be in connection accept state
Actions
The user will click on the submit button..
Expected Results
The report is successfully uploaded and a report id is generated Fail: No
Pass: Yes Problems / Issues: NIL
Conditions pass: No
Notes: Successfully Executed
75
TEST CASE5: FORUMS
Test case 5: Forums Test Objective: To check whether mutual responses are generated or not. Test Description: The user or doctor will select his choice of discussion to post. Requirements Verified: Yes Test Setup/Pre-Conditions: Receiver should be in connection accept state
Actions
The user will click on submit button after entering all his views about a particular topic. Pass: Yes Problems / Issues: NIL Notes: Successfully Executed Conditions pass: No
Expected Results
The discussion to be posted and updated must be viewed Fail: No
76
8. SCREEN SHOTS
Home page:
Screen Shot 8.1 Homepage
77
SEARCH PAGE
Screen Shot 8.2 search page
This is the search page where the user,doctor,guest and the pharmacist can serch the medicines. In this page the complete information regarding manufacturer ,sideeffects, disease, age,dosage,medicine composition are provided.
78
Registrtation page
Screen Shot 8.3 Registration page
79
User registration
Screen Shot 8.4 user registration page
80
User registration acknowledgement:
Screen Shot 8.5 user registration acknowledgement page
81
Doctor registration
Screen Shot 8.6 doctor registration page
82
Doctor registration acknowledgement:
Screen Shot 8.7 doctor registeration acknowledgement page
83
Pharmacist registration
Screen Shot 8.8 pharmacist registration page
84
Latest products
Screen Shot 8.9 latest products page
85
User homepage
Screen Shot 8.10 user home page
86
Order medicine
Screen Shot 8.11 order medicine
87
Discussion forum
Screen Shot 8.12 discussion form
88
MEDICINE DETAILS ADDED BY ADMIN
Screen Shot 8.13 medicine details added by admin This is medicines update page where medicine details are added by admin where the medicines details are disease name, manufacture, side effects, dosage.
89
PATIENT CARE
Screen Shot 8.14 Patient care This page gives us the information about how the patient care is provided to the users.In this page the interactive sessions are being performed.If we want to send the problems regarding your health.The post that are posted by the users and the admin can viewed.The solutions are also viewed in this page.
90
9.CONCLUSION
Using the present system, we are able to provide a simple and easy way of descriptions of various kinds of treatments and their availability. The system is designed with completely automated process hence there is less user intervention. Presently this system is concentrated only on that part of the health care were a common man was ought to see and can implement the same in the critical situations. In future, we hope that more and even more updates to this site will make the system much useful to the world than the present.
91
10.FUTURESCOPE
This Project can be further improved so that the maintenance and usage can be made a little easier to the end user and the administrator. And also security improvements can be included according to the requirement of the user. And also we can add videos about operation fields.
92
11. BIBLIOGRAPHY
JAVA COMPLETE REFERENCE PROGRAMMING WITH JAVA SQLSERVER DATABASE ACCESS WITH JAVA SOFTWARE ENGINEERING
-----------------------
HERBERT SCHILDT BALAGURUSWAMY
------------
SIMONGIBSON
------------ ROGER S.PRESSMAN
93
94

Medicate Documentation

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Medicate Documentation

Hochgeladen von

Copyright:

Verfügbare Formate

Medicare and Medicaid services

1.3 EXISTING SYSTEM:

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

1.4 PROPOSED SYSTEM:

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

IMPLEMENTATION:The system is implemented in the JAVA SERVER PAGES concept.

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

Medicare and Medicaid services

3.3. USECASE DIAGRAMS:

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

3.6. Hardware Requirements:

512 min RAM 20GB Hard Disk

ST.MARYS COLLEGE OF ENGG & TECH

Medicare and Medicaid services

4.1. Technical Architecture:

ST.MARYS COLLEGE OF ENGG & TECH

<bcolor="#FFFFFF"><font="Verdana",size="2",color="#008080"><b>M</b><strong>medicine Composition </strong></font></td> <bgcolor="#FFFFFF"><font="Verdana",size="2"> <%=rs.getString("m_composition")% ></font></td></tr>