Data Management By Privacy Preserving In The Anonymous Database

ABSTRACT
The main aim of our project is to give confidentiality to user details in a database and we are going to show this by using a medical process and that medical DB. When a patient newly comes to a medical his information must be collected so here also we are going to do the same thing. The medical database admin (MDA) will store all the fresh information about that patient in the anonymous database. And give one user name id password to that patient to access his/her page created by that medical. When user wants to open his/her page, he/she can use that user id and password that page. In that page all doctor information will be available who all are working in that medical. By that list patient can give request to the preference doctor . then request will go to the particular doctor page. If doctor approve the particular patient appointment request. Then the patient add as his/her OWN PATIENT list and can start the treatment. Dr can store all the patient information (Treatment, medicine, status) in the anonymous database and when treatment would be finished Dr can use the complete action on his/her page then only all the information regarding that patient will to that anonymous database . Then after completion Dr will send the Patient id to the MDA. Here MDA will send approval request to the patient to send his/her details to the researchers and if patient will give the permission then only MDA will send the information to the researchers. After getting the details researcher admin will allocate maximum sub researcher to researching about that disease and treatment now the maximum sub researchers only can access the database for research and save all the researching information in anonymous database but in two ways one for user and another one for doctor. If user search about the disease in web. The user can get only limited information from the anonymous database. And also doctor also can get the particular new treatment and medical information from the anonymous database.

TABLE OF CONTENTS
CHAPTER NO. ABSTRACT LIST OF FIBURES LIST OF SYMBOLS LIST OF ABBREVIATIONS LIST OF TABLES TITLE PAGE NO. i v vii xi xii

1.

INTRODUCTION 1.1 GENERAL 1.2 OBJECTIVE 1.3 EXISTING SYSTEM 1.3.1 Literature survey 1.4 PROPOSED SYSTEM

2.

ANONYMOUS DATABASE MANAGEMENT SYSTEM IN DATABASE SYSTEM 2.1 GENERAL 2.2 PROBLEM DEFINATION 2.3 METHODOLOGIES 2.3.1 MODULES

3.

REQUIREMENTS 3.1 GENERAL 3.2 HARDWARE REQUIREMENTS 3.3 SOFTWARE REQUIREMENTS 3.4 FUNCTIONAL SPECIFICATION

3.5 NON-FUNCTIONAL SPECIFICATION

4.

DESIGN ENGINEERING 4.1 GENERAL 4.2 ACTIVITY DIAGRAM 4.3 USE CASE DIAGRAM 4.4 DATA FLOW DIAGRAM 4.5 SEQUENCE DIAGRAM 4.6 COLLABORATION DIAGRAM 4.7 CLASS DIAGRAM 4.8DEPLOYMENT DIAGRAM

5.

DEVELOPMENT TOOLS 5.1 GENERAL 5.2 FEATURES OF JAVA 5.2.1 THE JAVA FRAMEWORK
5.2.2 OBJECTIVE OF JAVA 5.2.3 COMPONETS OF JAVA FRMEWORK 5.3 FEATURES OF THE COMMON LANGUAGE RUNTIME 5.4 J2EE 5.4.1 EVALUTION OF J2EE 5.4.2 THE J2EE DATA ARCHITECTURE 5.5.3 COMPONENT CLASSES THAT MAKE UP DATA PROVIDERS

IMPLEMENTATION

6.

6.1 GENERAL 6.2 IMPLEMENTATION OF ANONYMOUS DATABASE MANAGEMENT SYSTEM IN DATABASE SYSTEM

7.

SNAPSHOTS 7.1 GENERAL 7.2 VARIOUS SNAPSHOTS

8.

SOFTWARE TESTING 8.1 GENERAL 8.2 DEVELOPING METHODOLOGIES

9.

APPLICATIONS AND FUTURE ENHANCEMENT 9.1 GENERAL 9.2 APPLICATIONS 9.3 FUTURE ENHANCEMENTS

REFERENCES

LIST OF FIGURES
FIGURE NO 2.3.1 4.2 NAME OF THE FIGURE
Module Diagram

PAGE NO.

Activity Diagram for Anonymous database Management

4.3 4.4 4.5 4.6

Use case Diagram for Anonymous database Management

Data flow diagram for Anonymous database Management

Sequence diagram for Anonymous database Management

Collaboration diagram for Anonymous database Management.

4.7 4.8

Class diagram for Anonymous database Management

Architecture Diagram for Anonymous database Management

7.1

Medical home page

7.2 7.3 7.4 7.5

Patient Registration Page

Doctor Registration page

Patient get Doctor Appointment Page

Doctor Appointment Page

LIST OF SYSMBOLS
NOTATION S.NO NAME NOTATION DESCRIPTION

Class Name
1. Class

-attribute -attribute + public -private # protected +operation +operation +operation

Represents a collection of similar entities grouped together.

Class A
2. Association

NAME

Class B

Associations represents static relationships between classes. Roles represents

Class A

Class B

the way the two classes see each other.

3.

Actor

It aggregates several classes into a single classes.

Class A
5. Aggregation

Class A

Interaction between the system and external environment

Class B

Class B

5. Relation (uses) uses Used for additional process communication. Extends relationship is used when one use case is similar to another use case but does a bit more. Communication between various use cases.

6.

Relation (extends)

extends

7.

Communication

8.

State

State of the processs.

State

9.

Initial State

Initial state of the object

10.

Final state

F inal state of the object

11.

Control flow

Represents various control flow between the states.

12.

Decision box

Represents decision making process from a constraint

13. Usecase

Usescase

Interact ion between the system and external environment.

14.

Component

Represents physical modules which is a collection of components.

Represents physical modules 15. Node which are a collection of components.

16.

Data Process/State

A circle in DFD represents a state or process which has been triggered due to some event or acion.

17.

External entity

Represents external entities such as keyboard,sensors,etc.

18.

Transition

Represents communication that occurs between processes.

19.

Object Lifeline

Represents the vertical dimensions that the object communications.

20.

Message

Message

Represents the message exchanged.

LIST OF ABBREVATION

S.NO

ABBREVATION

EXPANSION

1. 2. 3. 4.
10 11.

DB SMC MDA
DBC JVM JSP

Data Base Secure Multiparty Computation

Medical Admin Data Base Confidentiality Java Virtual Machine Java Server Page

CHAPTER 1

INTRODUCTION

1.1.

GENERAL
It is today well understood that databases represent an important asset for many applications and thus their security is crucial. Data confidentiality is particularly relevant because of the value, often not only monetary, that data have. . Criteria for evaluating the performance of the various security-control methods are identified. Security-control methods that are based on each of the four approaches are discussed, together with their performance with respect to the identified evaluation criteria.

1.2. OBJECTIVE 1. The availability of huge numbers of databases recording a large variety of information about individuals makes it possible to discover information about specific individuals by simply correlating all the available databases. 2. Although confidentiality and privacy are often used as synonyms, they are different concepts: data confidentiality is about the difficulty (or impossibility) by an unauthorized user to learn anything about data stored in the database.

1.3 EXISTING SYSTEM 1. One well-known technique is k-anonymization. Such technique protects privacy by modifying the data so that the probability of linking a given data value, for example a given disease, to a specific individual is very small. So far, the problems of data confidentiality and anonymization have been considered separately.

2. a relevant problem arises when data stored in a confidential, anonymity-preserving database need to be updated. The operation of updating such a database, e.g., by inserting a tuple containing information about a given individual.

1.3.1 LITERATURE SURVEY

1.3.1.1 Dan Boneh._ Giovanni Di Crescenzo Rafail Ostrovskyy Giuseppe Persianoz , Public Key Encryption with keyword Search. YEAR: 2005 DESCRIPTION: We study the problem of searching on data that is

encrypted sing a public key system. Consider user Bob who sends email to user Alice encrypted under Alice's public key. An email gateway wants to test whether the email contains the keyword \urgent" so that it could route the email accordingly. Alice, on the other hand does not wish to give the gateway the ability to decrypt all her messages. We de_ne and construct a mechanism that enables Alice to provide a Key to the gateway that enables the gateway to test whether the word \urgent" is a keyword in the email without learning anything else about the email. We refer to this mechanism as Public Key Encryption with keyword Search. As another example, consider a mail server that stores various messages publicly encrypted for Alice by others. Using our mechanism Alice can send the mail server a key that will enable the server to identify all messages containing some speci_c keyword, but learn nothing else. We de_ne the concept of public key encryption with keyword search and give several constructions.

EXISTING:

Suppose user Alice wishes to read her email on a number of devices: laptop, desktop, pager, etc. Alice's mail gateway is supposed to route email to the appropriate device based on the keywords in the email. For example, when Bob sends email with the keyword \urgent" the mail is routed to Alice's pager. When Bob sends email with the keyword \lunch" the mail is routed to Alice's desktop for reading later. One expects each email to contain a small number of keywords. For example, all words on the subject line as well as the sender's email address could be used as keywords. The mobile people project provides this email processing capability. Now, suppose

DISADVANTAGES OF EXISTING:

Bob sends encrypted email to Alice using Alice's public key. Both the contents of the email and the keywords are encrypted. In this case the mail gateway cannot see the keywords and hence cannot make routing decisions.

As a result, the mobile people project is unable to process secure email without violating user privacy.

PROPOSED:

Our goal is to enable Alice to give the gateway the ability to test whether \urgent" is a keyword in the email, but the gateway should learn nothing else about the email. More generally, Alice should be able to specify a few keywords that the mail gateway can search for, but learn nothing else about incoming mail.

ADVANTAGES OF PROPOSED:

Mail forwarding using keyword only read the data whether urgent or what but not the data.

1.3.1.2 Rakesh Agrawa,l Alexandre Evfimievski, Ramakrishnan Srikant ,Information Sharing Across Private Databases YEAR: 2004 DESCRIPTION: Literature on information integration across databases tacitly assumes that

the data in each database can be revealed to the other databases. However, there is an increasing need for sharing information across autonomous entities in such a way that no information apart from the answer to the query is revealed. We formalize the notion of minimal information sharing across private databases, and develop protocols for intersection, equijoin, intersection

size, and equijoin size. We also show how new applications can be built using the proposed protocols.

EXISTING:

Information integration has long been an area of active database research. So far, this literature has tacitly assumed that the information in each database can be freely shared. However, there is now an increasing need for computing queries across databases belonging to autonomous entities in such a way that no more information than necessary is revealed from each database to the other databases.

DISADVANTAGES OF EXISTING : Low data accuracy Here no guarantee for accurate queries results.

PROPOSED:

We propose a new paradigm of minimal necessary information sharing across private databases. Intuitively, given a database query spanning multiple private databases, we wish to compute the answer to the query without revealing any additional information apart from the query result. We will sometimes relax this constraint to allow some minimal additional information to be revealed.

ADVANTAGES OF PROPOSED: High data accuracy. Here data retrieval based on the query and additional information. So the results are accurate.

1.3.1.3 Jingmin He and Min Wang,Cryptography and Relational Database Management Systems. YEAR: 2008 DESCRIPTION: Security is becoming one of the most urgent chal- lenges in database

research and industry, and the chal- lenge is intensifying due to the enormous popularity of ebusiness. In this paper we study database secu- rity from a cryptographic point of view. We show how to integrate modern cryptography technology into a re- lational database management system to solve some major security problems. Our study shows that cryp- tographic support is an indispensable ingredient for a modern RDBMS to provide a secure environment for storing and processing huge amount of business data.

EXISTING:

Suring the net has become part of the daily life of our society. Internet shopping has become very popular and e-business is reshaping the way we do business. In the mean time, when using all the old and new services, people are worried about the privacy and integrity of their business data. Recently, there was an attack on a popular web site which resulted in the possible stealing of the credit card numbers of several thousand customers: The safety of online commerce soured an- other blow with the disclosure that the credit card database of a health products supplier was opened to hackers for a few hours this.

DISADVANTAGES IN EXISTING: Low database security and privacy. Hackers can easily hack the data from the database.

PROPOSED:

WE PROPOSE A SYSTEM:

1. We introduce the important concept of security dictionary that can serve as the basis for many security services in a database system.

2. Based on the new concept of security dictionary, we show how to enhance the security of the current user management mechanism deployed in all RDBMSs.

3. We propose several database encryption methods and show how to do key management, again based on the security dictionary. ADVANTAGES OF PROPOSED:

By using security dictionary we can protect the data services in the database Here we encrypting datas that help us to secure the private datas.

1.3.1.4 Policy Hiding Access Control in Open Environment. Jiangtao Li Purdue University, Ninghui Li Purdue University YEAR: 2002

DESCRIPTION:

In trust management and attribute-based access control systems, access

control decisions are based on the attributes (rather than the identity) of the requester: Access is granted if Alices attributes in her certificates satisfy Bobs access control policy. In this paper, we develop a policy-hiding access control scheme that protects both sensitive attributes and sensitive policies. That is, Bob can decide whether Alices certified attribute values satisfy Bobs policy, without Bob learning any other information about Alices attribute values or Alice learning Bobs policy. To enable policy-hiding access control, we introduce the notion of certified input private policy evaluation. Our construction uses Yaos scrambled circuit protocol

and two new techniques introduced in this paper. One novel technique is constructing circuits with uniform topology that can compute arbitrary functions in a family. The other technique is committed-integer based oblivious transfer.

EXISTING:

In trust management and attribute-based access control systems access control decisions are based on attributes of clients, which are often documented by public key certificates. Each certificate associates a public key with the key holders identity and/or attributes such as employer, group membership, credit card information, birth-date, citizenship, and so on. Because these certificates are digitally signed, they can serve to introduce strangers to one another without online contact with the Certificate Authorities (CAs). As attribute information may be sensitive, the certificates that contain attribute data need protection just as other resources do. Often times, the policies for determining who can access the resources are sensitive also and need protection as well.

DRAWBACKS OF EXISTING: Anyone can access the datas from database, if one person knows another person key. Here the person data only set as a key, that makes privacy problem.

PROPOSED:

We develop a CIPPE protocol for certain families of functions that we believe are useful for expressing policies. Our solution uses Yaos scrambled circuit protocol .When a circuit is scrambled, the operation in each gate is hidden; however, the topological structure of the circuit is not. Therefore, Alice could infer some information about Bobs policy by looking at the scrambled circuit if Bob constructs the circuit in the naive way. To protect Bobs private function, we develop an efficient approach to construct circuits with uniform topology that can

compute certain functions families. To ensure that Alice can evaluate the scrambled circuit only with her attribute values as committed in her certificates, we develop an efficient and provably secure Committed-Integer based Oblivious Transfer (CIOT) protocol.

ADVANTAGES OF PROPOSED:

Here we using CIOT protocol to ensure the person private databases. High privacy of data sharing.

1.3.1.5 Security-Control Methods for Statistical Databases: A Comparative Study. NABIL R. ADAM, JOHN C. WORTMANN. YEAR: 2003

DESCRIPTION:

This paper considers the problem of providing security to statistical

databases against disclosure of confidential information. Security-control methods suggested in the literature are classified into four general approaches: conceptual, query restriction, data perturbation, and output perturbation. Criteria for evaluating the performance of the various security-control methods are identified. Security-control methods that are based on each of the four approaches are discussed, together with their performance with respect to the identified evaluation criteria. A detailed comparative analysis of the most promising methods for protecting dynamic-online statistical databases is also presented. To date no single security-control method prevents both exact and partial disclosures. There are, however, a few perturbation-based methods that prevent exact disclosure and enable the database administrator to exercise statistical disclosure control. Some of these methods, however introduce bias into query responses or suffer from the O/l queryset- size problem (i.e., partial disclosure is possible in case of null query set or a query set of size 1). We recommend directing future research efforts toward developing new methods that prevent exact disclosure and provide statistical-disclosure control, while at the same time do not suffer from the bias problem and the O/l query-set-size problem. Furthermore, efforts directed toward

developing a bias-correction mechanism and solving the general problem of small query-set-size would help salvage a few of the current perturbation based methods.

EXISTING:

In that case, the statistical researchers are authorized to retrieve only aggregate statistics; the physicians, on the other hand, can retrieve anything from the database. Many government agencies, businesses, and nonprofit organizations need to collect, analyze, and report data about individuals in order to support their short-term and long-term planning activities. SDBs therefore contain confidential information such as income, credit ratings, type of disease, or test scores of individuals. Such data are typically stored online and analyzed using sophisticated database management systems (DBMS) and software packages. On the one hand, such database systems are expected to satisfy user requests of aggregate statistics related to non confidential and confidential attributes.

DISADVANTAGES OF EXISTING: In this existing there is no privacy and confidentiality between database owners and data users. Anyone can retrieve the data from the database and can make modifications without the knowledge of database owner.

PROPOSED:

In this paper we assume that the following elements of access control have been implemented and are effective in preventing unauthorized access to the system: Authorization of people to access the computer facility and the database system. Identification of a person seeking access to the computer facility and the database system. Authentication of the users identity and access authorization.

ADVANTAGES OF PROPOSED:

High database security Only a authorized people can access and modify the database.

1.4 PROPOSED SYSTEM

We propose two protocols solving this problem on suppression-based and generalization-based k-anonymous and confidential databases. The protocols rely on well-known cryptographic assumptions, and we provide theoretical analyses to proof their soundness and experimental results to illustrate their efficiency. In their interest to check the data that are entered in their databases do not violate privacy, and to perform such a verification without seeing any sensitive data of an individual. The modification of the anonymous database DB can be naively performed as follows: the party who is managing the database or the server simply checks whether the updated database DB is still anonymous. Under this approach, the entire tuple t has to be revealed to the party managing the database server, thus violating the privacy of the patient. Another possibility would be to make available the entire database to the patient so that the patient can verify by himself/herself if the insertion of his/her data violates his/her own privacy. This approach however, Requires making available the entire database to the patient thus violating data confidentiality. Once this anonymized record is stored in the research database, the non anonymized version of the record is removed from the system of the medical facility. Thus, the research database used by the researchers is anonymous. Suppose that certain data concerning patients are related to the use of a drug over a period of four years and certain side effects have been observed and recorded by the researchers in the research database.

ADAVANTAGES IN PROPOSED SYSTEM

1. High privacy of data which updated.

2. An approach that can be used is based on techniques for user anonymous authentication and credential verification.

CHAPTER 2
SECURE COMPUTATION OF THE ANONYMOUS DATA MANAGEMENT

2.1 GENERAL
Thus, the research database used by the researchers is anonymous. Suppose that certain data concerning patients are related to the use of a drug over a period of four years and certain side effects have been observed and recorded by the researchers in the research database. It is clear that these data (even if anonymized) need to be kept confidential and accessible only to the few researchers of the institution working on this project, until further evidence is found about the drug. If these anonymous data were to be disclosed, privacy of the patients would not be at risk; however the company manufacturing the drug may be adversely affected.

2.2 PROBLEM DEFINITION

captures the main participating parties in our application domain. We assume that the information concerning a single patient (or data provider) is stored in a single tuple, and DB is kept confidentially at the server.

The modification of the anonymous database DB can be naively performed as follows: the party who is managing the database or the server simply checks whether the updated database DB [ ftg is still anonymous. Under this approach, the entire tuple t has to be revealed to the party managing the database server, thus violating the privacy of the patient. Another possibility would be to make available the entire database to the patient so that the patient can verify by himself/herself if the insertion of his/her data violates his/her own privacy. This approach however, requires making available the entire database to the patient thus violating data confidentiality. the question is how to enforce authorization without requiring the parties inserting the data to disclose their identities.

2.3 METHODOLOGIES Methodologies is the process of analyzing the principles or procedure of a Progressive Anonymous Database management system. The following are the 7 modules involves in Anonymous database system. MAIN MODULES: PRIVACY PATIENT PERSONAL DATABASE MANITANACE. ANONYMOUS PATIENT DETAILS REGISTRATION. ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION. ANONYMOUS SECURE DATATRANSFER. DATABASE ALLOCATION TO RESEARCH PEOPLE. USER SEARCH WITH GENERALIZATION BASED. MEDICAL SEARCH

MODULE DESCRIPTION:

PRIVACY PATIENT PERSONAL DATABASE MANITANACE.

This is the first step what patient to do. In this module patient want to register the personal details in the medical database and get the authentication processes to go forward. In this module patient want to give the database to medical admin all the registration process are done by a medical admin. After the registration process completed patient can get the authentication code and machine generated patient id, by using this only patient can login to the medical. SUB MODULESS DOCTOR APPOINTMENT : In this module patient can get the appointment from doctor, when the doctor accept the appointment request the particular requested patient consider as a own patient of the that doctor. REQUESTS : In this module patient can see and approve the medical requests. In this module patient can see what are the request are forward by a medical, and also in this sub module only patient can approve/Decline the medical requests. MY TREATMENTS In this module patient can see what are the treatments and Statuses are doctor recommending. When the doctor update any treatments and statuses for the patient that treatment and status details are forwarded to the patient. DOCTOR APPOINTMENT REQUESTS MY TREATMENTS

ANONYMOUS PATIENT DETAILS UPDATION.

In this module authorized doctors can login into the medical. Here also all the details about the doctor are registered by the medical admin. And the medical admin give the authentication details to the particular doctor after getting the authentication details doctor can login to the medical and can start the below processes.

SUBMODULES: PATIENT DETAILS APPOINTMENTS MY PATIENTS

PATIENT DETAILS In this module doctor can see patient details what are the patients register in medical. Here only the doctor can see the patient details but cant do any modifications in that database. APPOINTMENTS In this module the particular doctor can see and approve the patient appointments. If a patient appointment request is accepted means the particular patient is consider as an own patient of the particular doctor. After the patient consider as a own patient the doctor can start the treatment process in the my patient module. MY PATIENTS In this module doctor can see the own patients. And can update today treatment and status. And also can refer the old treatment and status. When the doctor update any treatments to the patient database that will be forwarded to the particular patient.

ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION. This module is only for administrator of the medical. SUBMODULES PATIENT DETAILS DOCTORS DETAILS NEW DOCTOR REGISTRATION NEW PATIENT REGISTRATION QUERIES

PATIENT DETAILS In this module Admin can see patient details what are the patients register in medical. In this module admin only can see the patient details but cant do any modifications. DOCTORS DETAILS In this module Admin can see patient details what are the patients register in medical. In this module admin only can see the doctor details, but cant do any modifications.

NEW DOCTOR REGISTRATION In this module admin get the doctor details from the doctor than can register the new doctor. After the doctor registration the authentication details are given to the doctor. After that only the doctor can login to the medical and can start the Doctor module processes. NEW PATIENT REGISTRATION:

In this module admin collect the details from the patient and register the patient details in the anonymous database. After the registration only patient can get the authentication details from the admin, by using that only patient can login to the medical.

QUERIES In this module admin can see and response for the querys forward by patient or doctor. From this module only the requests and permissions are forwarded to the medical peoples.

ANONYMOUS SECURE DATATRANSFER

In this module research people can see the datas send by medical. And allocate research peoples to each research data. And forward the data to research people. Here also research people cant do any changes or modifications in patient database they only can use the database for reference purpose.

DATABASE ALLOCATION TO RESEARCH PEOPLE. In this module research people can get the allocated datas from the research admin. And research people can update research database what they find newly. The data published to the user or medical based on the research people updating, here we have to publish the database to user only the specific data,

USER SEARCH WITH GENERALIZATION BASED. In this module any user can get relevant information about the disease from the web which is newly updated by the research people.

MEDICAL SEARCH:

In this module medical can see the research people newly updated datas from research database.

2.3.1

MODULE DIAGRAM:

PRIVACY PATIENT PERSONAL DATABASE MANITANACE.

ANONYMOUS PATIENT DETAILS REGISTRATION.

ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION.

ANONYMOUS SECURE DATATRANSFER.

USER SEARCH WITH GENERALIZATION BASED.

2.4 CONCLUTION
In order to perform the privacy-preserving verification of the database anonymity upon the insertion, the parties use a commutative and homomorphic encryption scheme. The second protocol is aimed at generalization-based anonymous databases, and it relies on a secure set intersection protocol, such as the one found in, to support privacy-preserving updates on a generalization-based k-anonymous DB.

CHAPTER 3 REQUIREMENTS ENGINEERING

3.1 GENERAL Using this requirements the Anonymous Database Management System is used for making secured database storage system. Using Anonymous Database System for Store and retrieve patient personal databases the efficient result from storage system , this system produce the good Anonymous database management to patients.

3.2 HARDWARE REQUIREMENTS The hardware requirements may serve as the basis for a contract for the implementation of the system and should therefore be a complete and consistent specification of the whole system. They are used by software engineers as the starting point for the system design. It shouls what the system do and not how it should be implemented. PROCESSOR RAM MONITOR HARD DISK CDDRIVE KEYBOARD MOUSE : : : : : : : PENTIUM IV 2.6 GHz, Intel Core 2 Duo. 512 MB DD RAM 15 COLOR 40 GB LG 52X STANDARD 102 KEYS 3 BUTTONS

3.3 SOFTWARE REQUIREMENTS

The software requirements document is the specification of the system. It should include both a definition and a specification of requirements. It is a set of what the system should do

rather than how it should do it. The software requirements provide a basis for creating the software requirements specification. It is useful in estimating cost, planning team activities, performing tasks and tracking the teams and tracking the teams progress throughout the development activity.

FRONT END BACK END :

JSP MYSQL

3.3 FUNCTIONAL REQUIREMENTS

A functional requirement defines a function of a software-system or its component. A function is described as a set of inputs, the behavior, and outputs. The proposed system is achieved by suppression-based and generalization-based k-anonymous and confidential databases. The protocols rely on well-known cryptographic assumptions, and we provide theoretical analyses to proof their soundness and experimental results to illustrate their efficiency.

3.4 NON-FUNCTIONAL REQUIREMENTS 3.5.1 EFFICIENCY Increase in efficiency of the data request processing is the core part of mining and specifically combination of both.

3.5.2 RELIABILITY To store and retrieve the personal datas in database in the anonymous format to achieve the security and confidentiality of the personal datas.

CHAPTER 4

DESIGN ENGINEERING
4.1 GENERAL Design Engineering deals with the various UML [Unified Modeling language] diagrams for the implementation of project. Design is a meaningful engineering representation of a thing that is to be built. Software design is a process through which the requirements are translated into representation of the software. Design is the place where quality is rendered in software engineering. Design is the means to accurately translate customer requirements into finished product.

4.2 ACTIVITY DIAGRAM

Activity diagram are a loosely defined diagram to show workflows of stepwise activities and actions, with support for choice, iteration and concurrency. UML, activity diagrams can be used to describe the business and operational step-by-step workflows of components in a system. UML activity diagrams could potentially model the internal logic of a complex operation. In many ways UML activity diagrams are the object-oriented equivalent of flow charts and data flow diagrams(DFDs)from structural development.

The following Activity diagram shows how the anonymous database management system working flow.

<<page>> Admin

<<Action>> Patient & Doctor Anonymous Updation

<<page>> Patient Treatment Completion Request <<page>> Doctor Database Forward To Medical After the patient Accept

<<Action>> Validation

Success <<Page>> Patient Home Action

Success

<<Page>> Doctor Home Action

<<Page>> Medical

<<Action>> Close

Fig 4.2 Activity Diagram of Anonymous Database Management System

4.3 USE CASE A use case diagram is a type of behavioral diagram created from a Use-case analysis. The purpose of use case is to present overview of the functionality provided by the system in terms of actors, their goals and any dependencies between those use cases.

In the below diagram eleven use cases are depicted. They are used to search result using CST methods.

Level 0:

Anonymous Patient Registration

Doctor Data Registration ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION. Suppression based Dtatbase Forward Anonymous Database

Admin Query's

Fig 4.3.1Use case Diagram for Anonymous Database Management System Level 0

My Profile

ANONYMOUS PATIENT TREATMENT UPDATION

Patient Anonymous Treatment Updation

Anonymous Database

Get Patient Appointments

Fig 4.3.2Use case Diagram for Anonymous Database Management System Level 0

Get Doctor Appiontment

PRIVACY PATIENT PERSONAL DATABASE MANITANACE

My Treatments

Anonymous Database

My Status

Get Admin Querys

Fig 4.3.3Use case Diagram for Anonymous Database Management System Level 0

Get Medical Forwarded Anonymous Database

DATABASE ALLOCATION TO RESEARCH PEOPLE

DataBase Allocation

Fig 4.3.4Use case Diagram for Anonymous Database Management System Level 0

Get Secured Database

Research People Research updation in Anonymous Database Reserch Updation

Anonymous Database

Fig 4.3.5 Use case Diagram for Anonymous Database Management System Level 0

4.4 DATAFLOW DIAGRAM A data flow diagram(DFD) is a graphical representation of the flow of data through an information system. It differs from the flowchart as it shows the data flow instead of the control flow of the program. A data flow diagram can also be used for the visualization of data processing. The DFD is designed to show how a system is divided into smaller portions and to highlight the flow of data between those parts.

Patient Registration

Patient Login

Anony-mous Data Update And Retrieva l In Patient database

Medical Updating Retrieve medical data from RDB Research center updating Only authorized research people can update research datas in anonymous RDB User Retrieval User retrieve only limited data from anonymous RDB Fig 4.4 Dataflow Diagram for Anonymous Database Management System

4.5 SEQUENCE DIAGRAM

A sequence diagram in UML is a kind of interaction diagram that shows how processes operate with one another and in what order. It is a construct of a message sequence chart. Sequence diagrams are sometimes called Event-trace diagrams, event scenarios, and timing diagrams. The below diagram shows the sequence flow of the Anonymous Database Management System.

PRIVACY PATIENT PERSONAL DATABASE MANITANACE

ANONYMOUS PATIENT DETAILS UPDATION Doctor Login

ANONYMOUS DB

ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION

DATABASE ALLOCATION TO RESEARCH PEOPLE.

USER

Research Login Medical Login get patient details

get appointment insert patient treatment forward tretment completed patient database

get Treatement send tretment completed request

ubdate user and medical research data in RDB get data from RDB get data through web from RDB

Fig 4.5 Sequence Diagram for Anonymous Database Management System

4.6 COLLABORATION DIAGRAM

A collaboration diagram show the objects and relationships involved in an interaction, and the sequence of messages exchanged among the objects during the interaction. The collaboration diagram can be a decomposition of a class, class diagram , or part of a class diagram. it can be the decomposition of a use case, use case diagram, or part of a use case diagram. The collaboration diagram shows messages being sent between classes and object(instances). A diagram is created for each system operation that relates to the current development cycle(iteration).

ADMIN ANONYMOUS DATAMANAGEMENT AND UPDATION 10: send tretment completed request

8: forward tretment completed patient database DATABASE ALLOCATION TO RESEARCH PEOPLE.

ANONYMOUS PATIENT DETAILS UPDATION

6: get appointment 5: get patient details 12: get data from RDB 4: Medical Login PRIVACY PATIENT PERSONAL DATABASE MANITANACE

2: Doctor Login 7: insert patient treatment

3: Research Login 11: ubdate user and medical research data in RDB 9: get Treatement

1: 13: get data through web from RDB ANONYMO US DB USER

Fig 4.6 Collaboration Diagram for Anonymous Database Management System

4.7 CLASS DIAGRAM

A class diagram in the UML, is a type of static structure diagram that describes the structure of a system by showing the systems classes, their attributes, and the relationships between the classes. Private visibility hides information from anything outside the class partition. Public visibility allows all other classes to view the marked information. Protected visibility allows child classes to access information they inherited from a parent class.

Fig 4.7 Class Diagram for Anonymous Database Management System

4.8 ARCHITECTURE DIAGRAM

The nodes involved are admin and clients which stands as UI for the system. The deployment is performed as per the requirements of Hardware and software specified in the requirements phase.

Fig 4.8 Architecture Diagram for ANONYMOUS DATABASE MANAGEMENT SYSTEM in Database System

4.11 CONCLUTION

From the above represented various UML diagrams it makes the developer and the designer of the project to easily understand the various implementations that has been carried out in the project.

CHAPTER 5
DEVELOPMENT TOOLS 5.1 GENERAL
This chapter is about the software language and the tools used in the development of the project. The platform used here is JAVA. The Primary languages are JAVA,J2EE and J2ME. In this project J2EE is chosen for implementation.

5.2 FEATURES OF JAVA 5.2.1 THE JAVA FRAMEWORK Java is a programming language originally developed by James Gosling at Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to bytecode that can run on any Java Virtual Machine (JVM) regardless of computer architecture. Java is general-purpose, concurrent, class-based, and object-oriented, and is specifically designed to have as few implementation dependencies as possible. It is intended to let application developers "write once, run anywhere".

Java is considered by many as one of the most influential programming languages of the 20th century, and is widely used from application software to web applicationsThe java framework is a new platform independent that simplifies application development internet. Java technology's versatility, efficiency, platform portability, and security make it the ideal technology for network computing. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! 5.2.2 OBJECTIVES OF JAVA To see places of Java in Action in our daily life, explore java.com. Why Software Developers Choose Java Java has been tested, refined, extended, and proven by a dedicated community. And numbering more than 6.5 million developers, it's the largest and most active on the planet. With its versatilty, efficiency, and portability, Java has become invaluable to developers by enabling them to:

Write software on one platform and run it on virtually any other platform Create programs to run within a Web browser and Web services Develop server-side applications for online forums, stores, polls, HTML forms processing, and more

Combine applications or services using the Java language to create highly customized applications or services

Write powerful and efficient applications for mobile phones, remote processors, low-cost consumer products, and practically any other device with a digital heartbeat

Some Ways Software Developers Learn Java Today, many colleges and universities offer courses in programming for the Java platform. In addition, developers can also enhance their Java programming skills by reading Sun's java.sun.com Web site, subscribing to Java technology-focused newsletters, using the Java

Tutorial and the New to Java Programming Center, and signing up for Web, virtual, or instructor-led courses. Object Oriented To be an Object Oriented language, any language must follow at least the four characteristics. 1.Inheritance : It is the process of creating the new classes and using the behavior of the existing classes by extending them just to reuse the existing code and adding addition a features as needed. 2.Encapsulation: It is the mechanism of combining the information and providing the abstraction. 3.Polymorphism: As the name suggest one name multiple form, Polymorphism is the way of providing the different functionality by the functions having the same name based on the signatures of the methods. 4.Dynamic binding : Sometimes we don't have the knowledge of objects about their specific types while writing our code. It is the way of providing the maximum functionality to a program about the specific type at runtime.

5.2.3 JavaServer Pages - An Overview

Java Server Pages or JSP for short is Sun's solution for developing dynamic web sites. JSP provide excellent server side scripting support for creating database driven web applications. JSP enable the developers to directly insert java code into jsp file, this makes the development process very simple and its maintenance also becomes very easy. JSP pages are efficient, it loads into the web servers memory on receiving the request very first time and the subsequent calls are served within a very short period of time. In today's environment most web sites servers dynamic pages based on user request. Database is very convenient way to store the data of users and other things. JDBC provide excellent database connectivity in heterogeneous database environment. Using JSP and JDBC its very cceasy to develop database driven web application. Java is known for its characteristic of "write once, run anywhere." JSP pages are platf JavaServer Pages

JavaServer Pages (JSP) technology is the Java platform technology for delivering dynamic content to web clients in a portable, secure and well-defined way. The JavaServer Pages specification extends the Java Servlet API to provide web application developers with a robust framework for creating dynamic web content on the server using HTML, and XML templates, and Java code, which is secure, fast, and independent of server platforms. JSP has been built on top of the Servlet API and utilizes Servlet semantics. JSP has become the preferred request handler and response mechanism. Although JSP technology is going to be a powerful successor to basic Servlets, they have an evolutionary relationship and can be used in a cooperative and complementary manner. Servlets are powerful and sometimes they are a bit cumbersome when it comes to generating complex HTML. Most servlets contain a little code that handles application logic and a lot more code that handles output formatting. This can make it difficult to separate and reuse portions of the code when a different output format is needed. For these reasons, web application developers turn towards JSP as their preferred servlet environment. 5.2.4 Evolution of Web Applications Over the last few years, web server applications have evolved from static to dynamic applications. This evolution became necessary due to some deficiencies in earlier web site design. For example, to put more of business processes on the web, whether in business-toconsumer (B2C) or business-to-business (B2B) markets, conventional web site design technologies are not enough. The main issues, every developer faces when developing web applications, are: 1. Scalability - a successful site will have more users and as the number of users is increasing fastly, the web applications have to scale correspondingly. 2. Integration of data and business logic - the web is just another way to conduct business, and so it should be able to use the same middle-tier and data-access code.

3. Manageability - web sites just keep getting bigger and we need some viable mechanism to manage the ever-increasing content and its interaction with business systems. 4. Personalization - adding a personal touch to the web page becomes an essential factor to keep our customer coming back again. Knowing their preferences, allowing them to configure the information they view, remembering their past transactions or frequent search keywords are all important in providing feedback and interaction from what is otherwise a fairly one-sided conversation. Apart from these general needs for a business-oriented web site, the necessity for new technologies to create robust, dynamic and compact server-side web applications has been realized. The main characteristics of today's dynamic web server applications are as follows: 1. Serve HTML and XML, and stream data to the web client 2. Separate presentation, logic and data 3. Interface to databases, other Java applications, CORBA, directory and mail services 4. Make use of application server middleware to provide transactional support. 5. Track client sessions .

5.2.5 Benefits of JSP

One of the main reasons why the JavaServer Pages technology has evolved into what it is today and it is still evolving is the overwhelming technical need to simplify application design by separating dynamic content from static template display data. Another benefit of utilizing JSP is that it allows to more cleanly separate the roles of web application/HTML designer from a software developer. The JSP technology is blessed with a number of exciting benefits, which are chronicled as follows: 1. The JSP technology is platform independent, in its dynamic web pages, its web servers, and its underlying server components. That is, JSP pages perform perfectly without any hassle on any

platform, run on any web server, and web-enabled application server. The JSP pages can be accessed from any web server. 2. The JSP technology emphasizes the use of reusable components. These components can be combined or manipulated towards developing more purposeful components and page design. This definitely reduces development time apart from the At development time, JSPs are very different from Servlets, however, they are precompiled into Servlets at run time and executed by a JSP engine which is installed on a Web-enabled application server such as BEA WebLogic and IBM WebSphere.

5.3 Servlets
Earlier in client- server computing, each application had its own client program and it worked as a user interface and need to be installed on each user's personal computer. Most web applications use HTML/XHTML that are mostly supported by all the browsers and web pages are displayed to the client as static documents. A web page can merely displays static content and it also lets the user navigate through the content, but a web application provides a more interactive experience. Any computer running Servlets or JSP needs to have a container. A container is nothing but a piece of software responsible for loading, executing and unloading the Servlets and JSP. While servlets can be used to extend the functionality of any Java- enabled server. They are mostly used to extend web servers, and are efficient replacement for CGI scripts. CGI was one of the earliest and most prominent server side dynamic content solutions, so before going forward it is very important to know the difference between CGI and the Servlets.

5.4Java Servlets

Java Servlet is a generic server extension that means a java class can be loaded dynamically to expand the functionality of a server. Servlets are used with web servers and run inside a Java Virtual Machine (JVM) on the server so these are safe and portable. Unlike applets they do not require support for java in the web browser. Unlike CGI, servlets don't use multiple processes to handle separate request. Servets can be handled by separate threads within the same process. Servlets are also portable and platform independent. A web server is the combination of computer and the program installed on it. Web server interacts with the client through a web browser. It delivers the web pages to the client and to an application by using the web browser and he HTTP protocols respectively. The define the web server as the package of large number of programs installed on a computer connected to Internet or intranet for downloading the requested files using File Transfer Protocol, serving e-mail and building and publishing web pages. A web server works on a client server model.

5.5 Conclusion
JSP and Servlets are gaining rapid acceptance as means to provide dynamic content on the Internet. With full access to the Java platform, running from the server in a secure manner, the application possibilities are almost limitless. When JSPs are used with Enterprise JavaBeans technology, e-commerce and database resources can be further enhanced to meet an enterprise's needs for web applications providing secure transactions in an open platform. J2EE technology as a whole makes it easy to develop, deploy and use web server applications instead of mingling with other technologies such as CGI and ASP. There are many tools for facilitating quick web software development and to easily convert existing server-side technologies to JSP and Servlets.

CHAPTER 6
IMPLEMENTATION 6.1 GENERAL This chapter describes the implementation of searched based application. It deals with the source code for main viewpoint for Anonymous Database Management. 6.2 IMPLEMENTAION OF ANONYMOUS DATABASE MANAGEMENT SYSTEM IN DATABASE SYSTEM
<%@page contentType="text/html" pageEncoding="UTF-8"%> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html><head><title>Medical Center</title> <meta http-equiv="Content-Type" content="text/html; charset=windows-1250"> <!-- ImageReady Preload Script (index.psd) --> <script type="text/javascript"> <!-function newImage(arg) { if (document.images) { rslt = new Image(); rslt.src = arg; return rslt; } } function changeImages() { if (document.images && (preloadFlag == true)) { for (var i=0; i<changeImages.arguments.length; i+=2) { document[changeImages.arguments[i]].src = changeImages.arguments[i+1]; } } } var preloadFlag = false; function preloadImages() { if (document.images) { home_over = newImage("images/home-over.jpg");

about_over = newImage("images/about-over.jpg"); services_over = newImage("images/services-over.jpg"); news_over = newImage("images/news-over.jpg"); contact_over = newImage("images/contact-over.jpg"); preloadFlag = true; } } // --> </script><!-- End Preload Script --> <link href="css/styles.css" rel="stylesheet" type="text/css"> </head> <body leftmargin="0" topmargin="0" onload="preloadImages();" style="background-color: rgb(255, 255, 255);" marginheight="0" marginwidth="0"> <center> <!-- ImageReady Slices (index.psd) --> <table class="frame" border="0" cellpadding="0" cellspacing="0" width="775"> <tbody> <tr> <td colspan="2" rowspan="5"> <img src="images/m1.jpg" alt="" height="272" width="205"></td> <td colspan="13"> <img src="images/m4.jpg" alt="" height="19" width="570"></td> <td> <img src="images/spacer.gif" alt="" height="19" width="1"></td> </tr> <tr> <td colspan="3"> <a href="#" onmouseover="window.status='home'; changeImages('home', 'images/home-over.jpg'); return true;" onmouseout="window.status=''; changeImages('home', 'images/home.jpg'); return true;"> <img name="home" src="images/home.jpg" alt="home" border="0" height="53" width="106"></a></td> <td> <a href="#" onmouseover="window.status='about'; changeImages('about', 'images/aboutover.jpg'); return true;" onmouseout="window.status=''; changeImages('about', 'images/about.jpg'); return true;"> <img name="about" src="images/about.jpg" alt="about" border="0" height="53" width="119"></a></td> <td colspan="3"> <a href="#" onmouseover="window.status='services'; changeImages('services', 'images/services-over.jpg'); return true;" onmouseout="window.status=''; changeImages('services', 'images/services.jpg'); return true;"> <img name="services" src="images/services.jpg" alt="services" border="0" height="53" width="105"></a></td> <td> <a href="#" onmouseover="window.status='news'; changeImages('news', 'images/newsover.jpg'); return true;" onmouseout="window.status=''; changeImages('news', 'images/news.jpg'); return true;"> <img name="news" src="images/news.jpg" alt="news" border="0" height="53" width="84"></a></td>

<td colspan="4"> <a href="#" onmouseover="window.status='contact'; changeImages('contact', 'images/contact-over.jpg'); return true;" onmouseout="window.status=''; changeImages('contact', 'images/contact.jpg'); return true;"> <img name="contact" src="images/contact.jpg" alt="contact" border="0" height="53" width="137"></a></td> <td> <img src="images/m5.jpg" alt="" height="53" width="19"></td> <td> <img src="images/spacer.gif" alt="" height="53" width="1"></td> </tr> <tr> <td colspan="5" rowspan="2"> <img src="images/m2.jpg" alt="" height="154" width="256"></td> <td colspan="8"> <img src="images/m6.jpg" alt="" height="38" width="314"></td> <td> <img src="images/spacer.gif" alt="" height="38" width="1"></td> </tr> <tr> <td colspan="4" align="left" background="images/b_wel.jpg" height="116" valign="top" width="242"> <p><span class="text1">WELCOME TO OUR CENTER </span><br> consetetur sadipscing elitr, sed diam nonumy eirmod<br> <br> invidunt ut labore Lorem ipsum dolor sit amet, conseter sadipscing elitr, sed diam Lorem ipsum dolor sit amet <a href="#">take tour now...</a></p> </td> <td colspan="4" align="left" valign="top"> <img src="images/m7.jpg" alt="" height="116" width="72"></td> <td> <img src="images/spacer.gif" alt="" height="116" width="1"></td> </tr> <tr> <td colspan="2"> <img src="images/m3.jpg" alt="" height="46" width="54"></td> <td colspan="4" rowspan="4"> <img src="images/exp1.jpg" alt="" height="160" width="225"></td> <td colspan="4" rowspan="2" align="left" valign="top"> <img src="images/exp2.jpg" alt="" height="59" width="241"></td> <td rowspan="14"> <img src="images/spacer.gif" alt="" height="410" width="24"></td> <td colspan="2" rowspan="16"> <img src="images/m8.jpg" alt="" height="454" width="26"></td> <td> <img src="images/spacer.gif" alt="" height="46" width="1"></td> </tr> <tr> <td colspan="3" rowspan="2" align="center"> <span class="maintext">OUR SERVICES</span>

</td> <td rowspan="15"> <img src="images/m9.jpg" alt="" height="408" width="41"></td>

<td> <img src="images/spacer.gif" alt="" height="13" width="1"></td> </tr> <tr> <td colspan="4" rowspan="2" align="left" height="101" valign="top" width="241"><span class="text2">Lorem Ipsum</span> consetetur sadipscing elitr, sed diam nonumy eirmod tempor i<br> <br> nvidunt ut labore Lorem ipsum dolor sit amet, conseter sadipscing elitr, sed diam Lorem ipsum dolor sit amet</td> <td> <img src="images/spacer.gif" alt="" height="44" width="1"></td> </tr> <tr> <td rowspan="9"> <img src="images/spacer.gif" alt="" height="269" width="37"></td> <td colspan="2" rowspan="5" style="padding-right: 10px;" align="left" height="149" valign="top" width="181"> <br> <br> <img src="images/dot.jpg" alt="" height="10" width="10">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="U_Login.jsp"><span class="logintext">Patient Login</span></a><br> <br> <img src="images/dot.jpg" alt="" height="10" width="10">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="D_Login.jsp"><span class="logintext">Doctor's Login</span></a><br> <br> <img src="images/dot.jpg" alt="" height="10" width="10">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="M_Login.jsp"><span class="logintext">Medical Admin Use</span></a><br> <br> <img src="images/dot.jpg" alt="" height="10" width="10">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="Research_Login.jsp"><span class="logintext">Research Center</span></a><br> <br> <td> <img src="images/spacer.gif" alt="" height="57" width="1"></td> </tr> <tr> <td rowspan="2" align="left" valign="top"> <img src="images/exp3.jpg" alt="" height="53" width="52"></td> <td colspan="7" align="left" height="18" valign="top" width="414"><a href="#" class="a">invidunt ut labore Lorem conseter dolor sit amet, sed elitr, sed diam Lorem ipsum dolor sit </a></td> <td> <img src="images/spacer.gif" alt="" height="18" width="1"></td> </tr> <tr> <td colspan="7" align="left" height="35" valign="top" width="414"><a href="#" class="a">Sed diam nonumy eirmod tempor invidunt ut labore

Lorem conseter invidunt ut labor</a></td> <td> <img src="images/spacer.gif" alt="" height="35" width="1"></td> </tr> <tr> <td colspan="4" rowspan="4" align="left" valign="top"> <img src="images/nt1.jpg" alt="" height="136" width="225"></td> <td colspan="4" align="left" valign="top"> <img src="images/nt2.jpg" alt="" height="37" width="241"></td> <td> <img src="images/spacer.gif" alt="" height="37" width="1"></td> </tr> <tr> <td colspan="4" rowspan="3" align="left" height="99" valign="top" width="241"><span class="text2">Lorem Ipsum</span> consetetur sadipscing elitr, sed diam nonumy eirmod tempor <br> <br> invidunt ut labore Lorem ipsum dolor sit amet, conseter sadipscing elitr, sed diam Lorem ipsum dolor sit amet</td> <td> <img src="images/spacer.gif" alt="" height="2" width="1"></td> </tr> <tr> <td colspan="2" align="left" valign="top"> <img src="images/sup1.jpg" alt="" height="32" width="181"></td> <td> <img src="images/spacer.gif" alt="" height="32" width="1"></td> </tr> <tr> <td colspan="2" rowspan="3" align="left" height="88" valign="top" width="181"><span class="text2">Lorem Ipsum</span> consetetur sadipscing elitr, sed diam nonumy eirmod tempor<br> <br> invidunt ut labore Lorem ipsum dolor sit amet, conseter sadipscing elitr, sed diam Lorem ipsum dolor sit amet</td> <td> <img src="images/spacer.gif" alt="" height="65" width="1"></td> </tr> <tr> <td rowspan="4" align="left" valign="top"> <img src="images/nt3.jpg" alt="" height="61" width="52"></td> <td colspan="7" align="left" height="17" valign="top" width="414"><a href="#" class="a">invidunt ut labore Lorem conseter dolor sit amet, sed elitr, sed diam Lorem ipsum dolor sit </a></td> <td> <img src="images/spacer.gif" alt="" height="17" width="1"></td> </tr> <tr> <td colspan="7" rowspan="3" align="left" height="44" valign="top" width="414"><a href="#" class="a">Sed diam nonumy eirmod tempor invidunt ut labore Lorem conseter invidunt ut labor</a></td> <td> <img src="images/spacer.gif" alt="" height="6" width="1"></td>

</tr> <tr> <td colspan="3"> <img src="images/m10.jpg" alt="" height="31" width="218"></td> <td> <img src="images/spacer.gif" alt="" height="31" width="1"></td> </tr> <tr> <td colspan="3" rowspan="3" class="text3" align="center" bgcolor="#e2e3e7" height="51" valign="middle" width="218">Copyright Your Company Name<br> Designed by TemplateYes - <a href="http://www.templateyes.com/html-templates.htm" target="_blank">Free Web Templates</a><br> Supported by <a href="http://www.hosting24.com/" target="_blank">Hosting24.com</a> </td> <td> <img src="images/spacer.gif" alt="" height="7" width="1"></td> </tr> <tr> <td colspan="9" align="center" bgcolor="#e2e3e7" valign="middle"> <img src="images/m11.jpg" alt="" height="3" width="490"></td> <td> <img src="images/spacer.gif" alt="" height="3" width="1"></td> </tr> <tr> <td colspan="9" class="text3" align="center" bgcolor="#e2e3e7" height="41" valign="middle" width="490"><a href="#">Home</a> | <a href="#">About</a> | <a href="#">Services</a> | <a href="#">Treatments</a> | <a href="#">News</a> | <a href="#">Support</a> | <a href="#">Contact</a></td> <td> <img src="images/spacer.gif" alt="" height="41" width="1"></td> </tr> <tr> <td> <img src="images/spacer.gif" alt="" height="1" width="37"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="168"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="13"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="41"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="52"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="119"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="31"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="23"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="51"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="84"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="84"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="22"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="24"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="7"></td> <td> <img src="images/spacer.gif" alt="" height="1" width="19"></td> <td></td> </tr> </tbody> </table>

<!-- End ImageReady Slices --> </center> </body></html>

6.2 Medical Admin Home:

<%@page contentType="text/html" pageEncoding="UTF-8"%> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"[]> <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US" xml:lang="en"> <head> <!-Created by Artisteer v3.0.0.39952 Base template (without user's data) checked by http://validator.w3.org : "This page is valid XHTML 1.0 Transitional" --> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>New Page</title> <meta name="description" content="Description" /> <meta name="keywords" content="Keywords" />

<link rel="stylesheet" href="style.css" type="text/css" media="screen" />

<!--[if IE 6]><link rel="stylesheet" href="style.ie6.css" type="text/css" media="screen" /><![endif]--> <!--[if IE 7]><link rel="stylesheet" href="style.ie7.css" type="text/css" media="screen" /><![endif]--> <script type="text/javascript" src="jquery.js"></script> <script type="text/javascript" src="script.js"></script> </head> <body> <div id="art-main"> <div class="art-sheet"> <div class="art-sheet-tl"></div> <div class="art-sheet-tr"></div> <div class="art-sheet-bl"></div> <div class="art-sheet-br"></div> <div class="art-sheet-tc"></div> <div class="art-sheet-bc"></div> <div class="art-sheet-cl"></div> <div class="art-sheet-cr"></div> <div class="art-sheet-cc"></div> <div class="art-sheet-body"> <div class="art-header">

<div class="art-header-clip"> <div class="art-header-png"></div> <div class="art-header-jpeg"></div> </div> <div class="art-headerobject"></div> <div class="art-logo"> <h1 class="art-logo-name">Kasi Kuppan Medical Home</h1> <h2 class="art-logo-text">We Take Care Of You</h2> </div> </div> <div class="cleared reset-box"></div> <div class="art-nav"> <div class="art-nav-l"></div> <div class="art-nav-r"></div> <div class="art-nav-outer"> <ul class="art-hmenu"> <li> <a href="M_Home.jsp" class="active"><span class="l"></span><span class="r"></span><span class="t">Home</span></a> </li> <li> <a href="D_Register.jsp"><span class="l"></span><span class="r"></span><span class="t">New Doctor Register</span></a> </li> <li> <a href="U_Register.jsp"><span class="l"></span><span class="r"></span><span class="t">patient - registration</span></a> </li> <li> <a href="M_Patient_Details.jsp"><span class="l"></span><span class="r"></span><span class="t">Patient Details</span></a> </li> <li> <a href="M_Doctor_Details.jsp"><span class="l"></span><span class="r"></span><span class="t">Doctor's Details</span></a> </li> <li> <a href="M_D_Doc_Query.jsp"><span class="r"></span><span class="t">QUERIES</span></a> </li> <li> <a href="M_Login.jsp"><span class="r"></span><span class="t">SIGN OUT</span></a> </li> class="l"></span><span class="l"></span><span

</ul> </div> </div> <div class="cleared reset-box"></div> <div class="art-content-layout"> <div class="art-content-layout-row"> <div class="art-layout-cell art-content"> <div class="art-post"> <div class="art-post-body"> <div class="art-post-inner art-article"> <h2 class="art-postheader"> </h2> <div class="cleared"></div> </div> <div class="art-postcontent"> <table align="right"> <tr> <td colspan="3" class="welcometext1">Welcome Admin</span> </tr> </table>

align="right"><span

<p><img src="images1/doctors_main.jpg" alt="an image" style="float:left" /> <table align="left"> <tr> <td><span class="text2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ABOUT US</span><span class="text4"><br> <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Hi welcome to our Hospital Home in our hospital we are <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;maintain our patient as a home member but not a people <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;invidunt ut labore Lorem ipsum dolor sit amet, <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;conseter sadipscing &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;elitr, sed diam Lorem ipsum dolor <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sit amet <br> <br> <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;invidunt ut labore Lorem ipsum dolor sit amet, <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;conseter sadipscing elitr, sed diam Lorem ipsum dolor <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;sit amet

</span> <span class="text2"><p> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;OUR OTHER SERVICES </p></span> <span class="text4"> <li>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ECG Department</li> <li> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24 hrs ICU Facility</li> <li> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;24 hrs Ambulance Service</li> <li> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Experienced Doctors..</li> </span> </td> </tr> </table>

</div> <div class="cleared"></div> </div> <div class="cleared"></div> </div> </div>

</div> </div> </div> </div> </div> </body> </html>

CHAPTER 7 SNAPSHOTS
7.1 GENERAL
Snapshot is nothing but every moment of the application while running. It gives the clear elaborated of application. It will be useful for the new user to understand for the future steps. 7.2VARIOUS SNAPSHOTS 7.2.1 MAIN PAGE Purpose: This is the home page for Medical To choose the Category

Fig 7.1 Medical Main Page

7.2.2 PATIENT REGISTRATION PAGE

P urpose: This option is to enable a new Patient to register in medical. Description: During the process of submitting the registration form, patient submits his basic identification information and also general information.

Fig 7.2 Patient Registration Page

7.2.3 DOCTOR REGISTRATION PAGE

Purpose : This option is to enable a doctor to register his/her basic information in medical.

Fig 7.3 Doctor Register Page

7.2.4 PATIENT DOCTOR APPOINTMENT PAGE

Fig 7.4 Patient doctor get appointment page

7.2.5 DOCTOR APPOINTMENT APPROVAL PAGE

Fig 7.5 Doctor Appointment Page

CHAPTER 8
SOFTWARE TESTING 8.1 GENERAL
The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement.

8.2 DEVELOPING METHODOLOGIES

The test process is initiated by developing a comprehensive plan to test the general functionality and special features on a variety of platform combinations. Strict quality control procedures are used. The process verifies that the application meets the requirements specified in the system requirements document and is bug free. The following are the considerations used to develop the framework from developing the testing methodologies.

8.3 Types of Tests 8.3.1 Unit testing

Unit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program input produce valid outputs. All decision branches and internal code flow should be validated. It is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform basic tests at component level and test a specific business process, application, and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and expected results.

8.3.2 Functional test

Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items: Valid Input Invalid Input Functions Output : identified classes of valid input must be accepted. : identified classes of invalid input must be rejected. : identified functions must be exercised. : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

8.3.3 System Test

System testing ensures that the entire integrated software system meets requirements. It tests a configuration to ensure known and predictable results. An example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points.

8.3.4 Performance Test

The Performance test ensures that the output be produced within the time limits,and the time taken by the system for compiling, giving response to the users and request being send to the system for to retrieve the results.

8.3.5 Integration Testing

Software integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or one step up software applications at the company level interact without error.

8.3.6 Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant participation by the end user. It also ensures that the system meets the functional requirements.

Acceptance testing for Data Synchronization: The Acknowledgements will be received by the Sender Node after the Packets are received by the Destination Node The Route add operation is done only when there is a Route request in need The Status of Nodes information is done automatically in the Cache Updation process 8.2.7 Build the test plan Any project can be divided into units that can be further performed for detailed processing. Then a testing strategy for each of this unit is carried out. Unit testing helps to identity the possible bugs in the individual component, so the component that has bugs can be identified and can be rectified from errors.

CHAPTER 9
APPLICATION 9.1 GENERAL
In this paper we propose a secured Anonymous database management system. we have presented two secure protocols for privately checking whether a k-anonymous database retains its anonymity once a new tuple is being inserted to it. Since the proposed protocols ensure the updated database remains k-anonymous, the results returned from a users (or a medical researchers) query are also k-anonymous. Thus, the patient or the data providers privacy cannot be violated from any query.

9.2 APPLICATION Anonymous database Management system is used to maintain the patient database in the anonymous format. It also very easy to retrieve the accurate data from anonymous database, here all the information about the patient are maintained securely and also here we achieve the confidentiality for the datas stored in the database. Concerning the actual execution of the database update, once the system has verified that the users tuple can be safely inserted to the database without compromising k-anonymity, the user is required to send to the Private Updater the non-anonymous attributes values to be stored in the k-anonymous database as well.

9.3 FUTIRE ENHANCEMENTS

1. Devising private update techniques to database systems that supports notions of anonymity different than k-anonymity. 2. Dealing with the case of malicious parties by the introduction of an untrusted, no colluding third party. 3. Implementing a real-world anonymous database system. 4. Improving the efficiency of protocols, in terms of number of messages exchanged and in terms of their sizes, as well.

REFERENCES
1. D. Boneh, G. di Crescenzo, R. Ostrowsky, and G. Persiano, Public Key Encryption with Keyword Search, Proc. Eurocrypt Conf., 2004. 2. R. Agrawal, A. Evfimievski, and R. Srikant, Information Sharing across Private Databases, Proc. ACM SIGMOD Intl Conf. Management of Data, 2003. 3. U. Feige, J. Kilian, and M. Naor, A Minimal Model for Secure Computation, Proc. ACM Symp. Theory of Computing (STOC), 1994. 4. J. Li, N. Li, and W. Winsborough, Policy-Hiding Access Control in Open Environment, Proc. ACM Conf. Computer and Comm. Security (CCS), 2005. 5. J. Li, B.C. Ooi, and W. Wang, Anonymizing Streaming Data for Privacy Protection, Proc. IEEE Intl Conf. Database Eng. (ICDE), 2008.