Hospice Dossier Control: 1.1.purpose of The Project

Hospice Dossier Control
CHAPTER 1
1. INTRODUCTION
1. INTRODUCTION :
Hospice Dossier Control is increasingly being viewed as a solution to customize costs

and make health advice and diagnosis possible even to remote areas. We have tried to
emulate a commercial Hospice Dossier Control program in some of its ramifications.
Hospice Dossier Control is a program to facilitate medical advice and diagnosis when
the participants are geographically isolated. It is the use of medical information exchanged
from one site to another via electronic communications for the health and education of the
patient or health-care provider and for the purpose of improving patient care. However, the
definition of Hospice Dossier Control is changing fast to incorporate greater functionality,
which is made possible by greater bandwidths and facilities like Audio and Web
conferencing.
The program aims at creating facilities for consultation, diagnosis, test recommendation
and drug prescription. A heavy emphasis is laid on making the doctor aware of the patient’s
past clinical history by updating all the patient details after every visit. The patient is also
given the flexibility to choose form a pool of experts and seek second opinion from
knowledgeable resources. The program accomplishes the task of providing a suitable
platform for patients to address their consulting needs by the dint of a single click
1.1.PURPOSE OF THE PROJECT
The current application is being designed to fulfill the day to day activities to be
done in a typical hospital environment. Right from patient enquiry till discharge of the
patient all the activities need to be automated in the web enabled application.
Bhoj Reddy Engineering College for Women

1
1.2. EXISTING SYSTEM

 Time Delay: It is inefficient to deal with voluminous data manually in the existing
system, record stored in different files. It takes lot of time to search different files.
 Redundancy: As the branches are located in different locations, same files have to be
stored at all branches which involve lot of complications and duplication works thus
causes redundancy.
 Accuracy: Since same data is compiled at different branches the possibility of
tabulating data wrong increases also data is more, validation becomes difficult. It may
result in loss of accuracy of data.
1.3. LITERATURE SURVEY
Literature survey helps to provide solutions with an easy way. And it also provides some
knowledge regarding the technology
Introduction to Java:
Initially the language was called as “oak” but it was renamed as “java” in 1995.The primary
motivation of this language was the need for a platform-
independent(i.e. architecture neutral)language. Java is a programmer’s language. Java is cohesive
and consistent.
Finally Java is to Internet Programming where c was to System Programming.
Importance of Java to the Internet:

Java has had a profound effect on the Internet. This is because; java expands the Universe
of objects that can move about freely in Cyberspace. In a network, two categories of objects are
transmitted between the server and the personal computer. They are passive information and
Dynamic active programs in the areas of Security and probability. But Java addresses these
concerns and by doing so, has opened the door to an exciting new form of program called the
Applet.

2
Java Architecture:
Java architecture provides a portable, robust, high performing environment for
development. Java provides portability by compiling the byte codes for the Java Virtual Machine,
which is then interpreted on each platform by the run-time environment. Java is a dynamic
system, able to load code when needed from a machine in the same room or across the planet.
Compilation of code:
When you compile the code, the Java compiler creates machine code (called byte
code)for a hypothetical machine called Java Virtual Machine(JVM). The JVM is supposed to
execute the byte code. The code is written and compiled for one machine and interpreted on all
machines .This machine is called Java Virtual Machine.
Compiling and interpreting java source code:
Java interpreter
Pc compiler Java Byte
code
Java
Source code Macintosh Platform
interpretermaci
compiler independen
ntosh
t
SPARC Java
Compiler interpreter(SPA
RC)
)))
FIG 3.1 JAVA ARCHITECTURE

3
In reality Java interpreter could be an Intel Pentium windows 95 or sun SPARCstation

running Solaris or Apple Macintosh running system and all could receive code from any
computer through internet and run the Applets.
Java is a powerful but lean object-oriented programming language. It has generated a lot
of excitement because it makes it possible to program for Internet by creating Applets. Programs
that can be embedded in web page. The context of an applet can be an animation with sound, an
interactive game or a ticker tape. With constantly updated stock prices. Applets can be just little
decorations to liven up web page, or they can be serious applications like Word processor or
Spreadsheet.
But Java is more than a programming language for writing Applets. It is being used more
and more for writing standalone applications as well. It is becoming so popular that many people
believe it will become standard language for both general purpose and Internet programming.
Java is simple, elegant, and powerful and easy-to-use.
Java is actually a platform consisting of 3 components:
Java Programming Language.
Java Library of Classes and Interfaces.
Java Virtual Machine
FEATURES OF JAVA:
Java is portable
One of the biggest advantages Java offers is that it is portable. An application written in
Java will run on all the major platforms. Any computer with a Java-based browser can run the
applications or Applets written in the Java-Programming-Language. A programmer no longer has
to write one program to run on a Macintosh, another program to run on a Windows-machine still
another to run on a UNIX-machine and so on. In other words, with Java developers write their
programs only once.
The Virtual Machine is what gives Java is cross platform capabilities. Rather being
compiled into machine language, which is different for each OS’s and computer architecture,

4
Java code is compiled into Byte codes. With other languages, the program code is compiled into
a language that the computer can understand.
Java is object-oriented
The Java programming language is OBJECT-ORIENTED, which makes program design
focus on what you are dealing with, rather than on how you are going to do something. This
makes it more useful for programming in sophisticated projects, because one can break the
things into understandable components. A big benefit is that these components can then be
reused.
The class paradigm allows one to encapsulate data so that specific data values are those
using the data cannot see the function implementation. Encapsulation makes it possible to make
the changes in code without breaking other programs that use that code.
If for example, the implementation of a function is changed, the change is invisible to any
programmer who invokes that function, and does not affect his/her program, except hopefully to
improve it.
JAVA DEVELOPMENT EVNIRONMENT

To code, edit, debug and test the java programs, one needs to have a java development
environment. At the minimum this will consists of a java compiler interpreter and applet viewer
where applets can be tested.Sun’s java development kit
(JDK) latest version is 2.2 can be freely downloaded from the Internet. Java compiler is available
on DOS, Win95, WIN’NT, Solaris and MAC etc.
Data flow diagram is a graphical tool used to describe analyze the movement of data
through a system manual or automated including the processes, stores of data, and delays in the
system.

5
Servlets/JSP
INTRODUCTION
A Servlet Is a generic server extension. a Java class that can be loaded

Dynamically to expand the functionality of a server.Servlets are commonly used with web
servers. Where they can take the place CGI scripts.
A servlet is similar to proprietary server extension, except that it runs inside a Java Virtual
Machine (JVM) on the server, so it is safe and portable
Servlets operate solely within the domain of the server.
Unlike CGI and Fast CGI, which use multiple processes to handle separate program or
separate requests, separate threads within web server process handle all servlets. This means
that servlets are all efficient and scalable.
Servlets are portable; both across operating systems and also across web servers. Java
Servlets offer the best possible platform for web application development.
Servlets are used as replacement for CGI scripts on a web server, they can extend any sort of
server such as a mail server that allows servelts t extend its functionality perhaps by
performing a virus scan on all attached documents or handling mail filtering tasks.

6
Servlets provide a Java-based solution used to address the problems currently associated with
doing server-side programming including inextensible scripting solutions platform-specific
API’s and incomplete interface.
Servlets are objects that conform to a specific interface that can be plugged into a Java-based
server.Servlets are to the server-side what applets are to the server-side what applets are to
the client-side-object byte codes that can be dynamically loaded off the net. They differ form
applets in than they are faceless objects(with out graphics or a GUI component).They serve
as platform independent, dynamically loadable,plugable helper byte code objects on the
server side that can be used to dynamically extend server-side functionality.
For example an HTTP servlet can be used to generate dynamic HTML content when you
use servlets to do dynamic content you get the following advantages:
 They’re faster and cleaner then CGI scripts

 They use a standard API( the servlet API)
 They provide all the advantages of Java (run on a variety of servers without needing
to be rewritten)
A t t r a c t i v e n e s s o f S e r v l e t s:
They are many features of servlets that make them easy and attractive to tuse these
include:
 Easily configure using the GUI-based Admin tool]

 Can be Loaded and Invoked from a local disk or remotely across the network.
 Can be linked together or chained, so that on servlet can call another servlet, or
several servlets in sequence.
 Can be called dynamically from with in HTML, pages using server-side include-
tags.
7
 Are secure-even when downloading across the network, the servlet security model
and servlet and box protect your system from unfriendly behavior.,
Advantages of the servlet API
One of the great advantages of the servlet API is protocol independent. It assumes
nothing about:
 The protocol being used to transmit on the net

 How it is loaded
 The server environment it will be running in
 These quantities are important, because it allows the Servlet API to be embedded
in many different kinds of servers.There are other advantages to the servelt API as
well These include:
 It’s extensible-you can inherit all your functionality from the base classes made
available to you
 It’s simple small, and easy to use.
Features of Servlets:
 Servlets are persistent.Servlet are loaded only by the web server and can maintain
services between requests.
 Servlets are fast. Since servlets only need to be l\loaded once, they offer much
better performance over their CGI counterparts.
 Servlets are platform independent.

8
 Servlets are extensible Java is a robust, object-oriented programming language,

which easily can be extended to suit your needs.
 Servlets are secure
 Servlets are used with a variety of client.
Servlets are classes and interfaces from tow packages,javax .servlet and
javax.servlet.http.The java.servlet package contains classes t support generic, protocol-
independent servlets.The classes in the javax.servelt.http package To and HTTP specific
functionality extend these classes
Every servlet must implement the javax.servelt interface.Most servlets implement it by

extending one of two classes.javax.servlet.GenericServlet or javax.servlet.http.HttpServlet.A
protocol-independent servlet should subclass Generic-Servlet.while an Http servlet should
subclass HttpServlet, which is itself a subclass of Generic-servlet with added HTTP-specific
functionality.
Unlike a java program, a servlet does not have a main() method,Instead the server in the
process of handling requests invoke certain methods of a servlet.Each time the server
dispatches a request to a servlet, it invokes the servelts Service() method,
A generic servlet should override its service() method to handle requests as appropriate for
the servlet.The service() accepts two parameters a request object and a response object .The
request object tells the servlet about the request, while the response object is used to return a
response
InContrast.anHttp servlet usually does not override the service() method.Instead it overrides
doGet() to handle GET requests and doPost() to handle Post requests. An Http servlet can
override either or both of these modules the service() method of HttpServlet handles the

9
setup and dispatching to all the doXXX() methods.which iswhy it usually should not be
overridden
The remainders in the javax.servlet and javax.servlet.http.package are largely support

classes .The ServletRequest and ServletResponse classes in javax.servlet provide access to
generic server requests and responses while HttpServletRequest and HttpServletResponse
classes in javax.servlet provide access to generic server requests and responses while
HttpServletRequest and HttpServletResponse in javax.servlet.http provide access a HTTP
requests and responses . The javax.servlet.http provide contains an HttpSession class that
provides built-in session tracking functionality and Cookie class that allows quickly setup
and processing HttpCookies.
Loading Servlets:
Servlets can be loaded from their places. From a directory that is on the CLASSPATH. The
CLASSPATH of the JavaWebServer includes service root/classes/, which is where the system
classes reside
From the <SERVICE_ROOT/servlets/directory.This is not in the server’s classpath. A class

loader is used to create servlets form this directory.New servlets can be added-existing
servlets can be recompiled and the server will notice these changes. From a remote
location.For this a code base like http://nine.eng/classes/foo/ is required in addtion to the
servlet’s class name.Refer to the admin Gui docs on servlet section to see how to set this up.
Loading Remote Servlets

Remote servlets can be loaded by:
 Configuring the admin Tool to setup automatic loading of remote servlets.

 Selectiong up server side include tags in .html files

10
 Defining a filter chain Configuration
Invoking Servlets
A servlet invoker is a servlet that invokes the “server” method on a named servlet.If the
servlet is not loaded in the server,then the invoker first loades the servlet(either form local
disk or from the network) and the then invokes the “service” method.Also like applets,local
servlets in the server can be identified by just the class name.In other words, if a servlet name
is not absolute.it is treated as local.
A Client can Invoke Servlets in the Following Ways:
 The client can ask for a document that is served by the servlet.
 The client(browser) can invoke the servlet directly using a URL, once it has been
mapped using the SERVLET ALIASES Section of the admin GUI
 The servlet can be invoked through server side include tags.
 The servlet can be invoked by placing it in the servlets/directory
 The servlet can be invoked by using it in a filter chain
The Servlet Life Cycle:-
The Servlet life cycle is one of the most exciting features of Servlets.This life cycle is a
powerful hybrid of the life cycles used in CGI programming and lower-level NSAPI and
ISAPI programming.
The servlet life cycle allows servlet engines to address both the performance and resource
problems of CGI and the security concents of low level server API programming.

11
Servlet life cycle is highly flexible Servers hava significant leeway in how they choose to
support servlets.The only hard and fast rule is that a servlet engine must confor to the
following life cycle contact:
 Create and initialize the servlets

 Handle zero or more service from clients
 Destroy the servlet and then garbage Collects it.
It’s perfectly legal for a servlet t be loaded, created an initialzed in its own JVM,only to be
destroyed an dgarbage collected without hancdling any clientrequest or after handling just
one request
The most common and most sensible life cycle implemntations for HTTP servelts are:
Single java virtual machine and astatine persistence.
Init and Destroy:-
Just like Applets servlets can define init() and destroy() methods, A servlets
init(ServiceConfig) method is called by the server immediately after the server constructs the
servlet’s instance.Depanding on the server and its configuration, this can be at any of these
times
 When the server states

 When the servlet is first requested, just before the service() method is invoked
 At the request of the server administrator
In any case, nit() is guaranteed to be called before the servlet handles its first request

12
The init() method is typically used to perform servlet initialization creating or loading objects
that are used by the servlet in handling of its request. In order to providing a new servlet any
information about itself and its environment, a server has to call a servelts init() method and
pass an object that implement the ServletConfig interface.
This ServletConfig object supplies a servlet with information about its initialization
parameters.These parameters are given to the servlets and are not associated with any single
request.They can specify initial values, such as where a counter should begin counting, or
default values, perhaps a template to use when not specified by the request,
The server calls a servlet’s destroy() method when the servlet is about to be unloaded. In the
destroy() method, a servlet should free any resources it has acquired that will not be garbage
collected. The destroy() method also gives a servlet a chance to write out its unsaved. cached
information or any persistent information that should be read during the next call to init().
1.4.PROPOSED SYSTEM:
Computerizing of an organization whose branches are situated at different locations and

connecting them through Intranet. This provides easy accessing of shared data and provides
communication channel between employees
 Reliability: The project performs intended function with required
precision; hence this project is very reliable.
 Feasibility: The project maintenance is very easy and modifications can be
made in the existing system in future. The project can interconnect to other groups
within the organization and also to all other branches under integrated network.

13
CHAPTER 2
2.REQUIREMENT ANALYSIS
Requirement analysis is done in order to understand the problem of the software system
is to solve. The problem could be automating an existing manual process, developing an new
automated system, or a combination of two. For large systems that have many features, and that
need to perform many different tasks, understanding the requirements of the system is a major
task.
2.1.FUNCTIONAL REQUIREMENTS:
Number of modules:
After careful analysis the system has been identified to have the following modules:
1.Administrator Module
2.Doctors Module
3.Patient Module
4.Kiosk Module
Modules:

14
The system is proposed to have the following modules along with the functional
requirements.
1. Administrator module:
Administrator regularly takes backup of all kinds of data. Administrator can view the log
information. Administrator also generates system reports. Administrator also provides online
help manual for patients.
2. Doctors module:
A doctor must register with the system. Doctor’s can manage their profiles. Doctor’s give
appointments to patients, e-prescriptions, and view patient’s history. Doctor can interact with
patient using web-cam.
3. Patient module:
A patient must register with the system. Patients can make online appointment, view their
previous health records, doctor’s prescriptions, lab reports and medical expenses. Patients can
manage their profiles. Patient can interact with doctor using web-cam. In case of any medical
error (wrong medication or lab report) patient can register a complaint. Patient’s grievance and
feedback goes to Admin he can forward it to any doctor to answer.
4. Kiosk module:
Kiosk Manager views and adjusts appointments, performs day open and close activities
and calculates his commission.
2.2. Software requirements:

Operating System : Windows
Technology : Java and J2EE
Web Technologies : Html, JavaScript, CSS
IDE : My Eclipse
Web Server : Tomcat
Database :Oracle
2.3.Hardware Requirements:
15
Hardware : Pentium
RAM : 1GB
2.4.Quality Requirement:
Reliability:
The system is more reliable because of the qualities that are inherited from the chosen platform
java.The code built by using java is more reliable.
Supportability:
The system is designed to be the cross platform supportable.
Test Cases:
All the test cases that are applied on the application should be passed thus ensuring the
efficiency of the applications.
2.5 DEPLOYMENT REQUIREMENTS:
Operating System : Windows or Linux
Software : Java 2 standard edition,
Design UML Diagrams : IBM Rational Rose

16
CHAPTER 3
3.ARCHITECTURE
3.1. SYSTEM ARCHITECTURE

 Architecture is the fundamental and unifying system structure defined in terms of system
elements, interfaces, process, constraints, and behaviors and it is the structure of components,
their relationships and the principles and the guidelines governing their evolution over time.
 A system Architecture is the link between needs analysis, project scoping and functional analysis
and the first descriptions of the system structure.
Application
JDK XML Get Data
SQLITE

17
3.2 TECHNICAL ARCHITECTURE

The technical Architecture describes the working of the application.
Administrator
Maintaining
Patient and Doctor
details Send &
Receive
reports
Receive res
Gives res to from
patients 0 Doctor
Hospice Dossier Patient

Doctor Control Channel
Send req to
Accept request Doctor
from patients
Maintain
Transaction
Manager

18
CHAPTER 4
4. DESIGN
Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first step
in the development phase for any eng
ineered product or system. The designer’s goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been specified and
analyzed, system design is the first of the three technical activities -design, code and test that is
required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where
quality is fostered in software development. Design provides us with representations of software
that can assess for quality. Design is the only way that we can accurately translate a customer’s
view into a finished software product or system. Software design serves as a foundation for all
the software engineering steps that follow. Without a strong design we risk building an unstable
system – one that will be difficult to test, one whose quality cannot be assessed until the last
stage.During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either
technical or project management perspective. From the technical point of view, design is
comprised of four activities – architectural design, data structure design, interface design and
procedural design.
System design is transition from a user oriented document to programmers or data base
personnel. The design is a solution, how to approach to the creation of a new system. This is
composed of several steps. It provides the understanding and procedural details necessary for
19
implementing the system recommended in the feasibility study. Designing goes through logical
and physical stages of development, logical design reviews the present physical system, prepare
input and output specification, details of implementation plan and prepare a logical design
walkthrough.
The database tables are designed by analyzing functions involved in the system and
format of the fields is also designed. The fields in the database tables should define their role in
the system. The unnecessary fields should be avoided because it affects the storage areas of the
system. Then in the input and output screen design, the design should be made user friendly. The
menu should be precise and compact.
UML DIAGRAMS
Unified Modeling Language(UML) is a standardized general-purpose modeling language
in the field of software engineering. It is used to specify,visualize,modify,construct and document
the artifacts of an object oriented software Intensive system under development.
GOALS OF UML
The primary goals in the design of UML are:
1. Provide users with a ready to use expensive visual modeling language so they can develop and
exchange meaningful models.
2. Provide extensibility and specialization mechanisms to extend the core concepts.
3. Be independent of particular programming languages and development processes
4. Provide formal basis for understanding the modeling language.

20
USE CASE DIAGRAM

Use Case Diagram for Administrator:

21
Use Case Diagram for Doctor:

22
Use Case Diagram for Patient:
Class diagram:

23
Sequence Diagram for Patient:

24
Sequence Diagram for Negotiating Doctors - ADMIN :

25
Sequence Diagram for Reporting Test Results:

26
Sequence Diagram for Treatment Process DOCTOR:

27
Sate Diagram for Complaint Lodging:

28
Sate Diagram for Doctor’s Negotiation:

29
Sate Diagram for Test Result Reporting:

30
4.5.Database Design: ER-Diagrams

31
 Database table is the process of producing a detailed data model of a database. The term database
design can be used to describe many different parts of design of an overall database system.
 It gives the clear picture about all the entities and their attributes and also the relation that exists
between these entities.
USER REGISTRATION:
USER LOGIN AND TRANSITION:-

32
DOCTOR LOGIN AND TRANSITION:-

33
DATA DESIGN TABLES:

34
After carefully understanding the requirements of the client the the entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of data entry
Data Dictionary:
Complicants
ColumnName DataType Size Constraints

PatientName Text 20 Null
Complication Text 20 Null
RegDate Text 20 Null
Status Text 20 Null
DateOfAvailablity Date/Time Null
Timings Text 20 Null
Doctor

DoctorName Text 20 Null
Specilization Text 20 Null
Qulification Text 20 Null
AvailableDate Date/Time Null
HospitalName Text 20 Null
Status Text 20 Null
Loginaudit

Loginid Text 20 Null
Logindate Date/Time Null
login_desc Text 20 Null

35
Logindetails

Loginname Text 20 PK
Password Text 20 Null
FirstName Text 20 Null
LastName Text 20 Null
Logintype Text 20 Null
LandLineNo Text 20 Null
RegDate Text 20 Null
Squestionid Text 20 Null
Sanswer Text 20 Null
Passmodifieddate Text 20 Null
Loginprofile

Loginid Text 20 Null
Birthdate Date/Time Null
City Text 20 Null
State Text 20 Null
Country Text 20 Null
PinNo Text 20 Null
Locale Text 20 Null
Profilemodifieddate Date/Time Null
Patient

LoginName Text 20 PK
Age Text 20 Null
Height Text 20 Null
Weight Text 20 Null

36
BloodGroup Text 20 Null

BP Text 20 Null
Sugar Text 20 Null
RegDate Date/Time Null
CHAPTER 5
5. MODULES
In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browses interface. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. The operational or generic user interface

37
The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication for the
data collection. The interfaces help the administrations with all the transactional states like Data
insertion, Data deletion and Date updation along with the extensive data search capabilities.
The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps the
ordinary users in managing their own information helps the ordinary users in managing their own
information in a customized manner as per the assisted flexibilities.
NUMBER OF MODULES
Administration:
The administration module will keep track of all expenses incurred during patient diagnosis. It
should also maintain information related to bed occupancy in hospital. Billing is the key activity
in this module
 Patients
 Doctors
 Kiosk Manager
 Administration
Patients:
 The Patients module keeps track of entire information pertaining to patient

right from the first time he comes for diagnosis.
 The diagnosis results and the cost incurred for each test will be maintained

38
 Scheduling the appointments and operations will be done upon

synchronizing the availability of doctor as well as exigency of appointment
or operation.
Doctors
 The Doctors module keeps track of doctors personal information and their
available timings in hospital.
 Scheduling the appointments and operations will be done upon

synchronizing the availability of doctor as well as exigency of appointment
or operation.
Kiosk Manager:
A Medicare professional is a valid medical practitioner at a Medicare center established under

the Sanjeevini program. He performs various tests to the registered patients when they approach
the Medicare center. This can be broadly categorized under the following headings.
1. Patient profile.
2. Perform test.
3. Upload test.
1.Patient profile :The Medicare professional has access to the patient profile, his previous tests so
that he can make a right decision with regard to perform a test.
2.Perform tests: The professional is allowed to perform a test from a list of available test type.
Each test is equipped with a form which is to be filled by the professionals with test results and is
to be submitted.
3.Upload test: If the professional has to perform a test such as MRI, X-ray etc, the test report can
be uploaded using this module. A third party component is used to upload the test from browser
to the server.

39
CHAPTER 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.

40
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.
PSEUDOCODE:
<!DOCTYPE html>
<html>
<li class="active"><a href="index.html">Home</a></li>
<li class=""><a href="#about">About</a></li>

<li class=""><a href="#contact">Contact</a></li>
<li class=""><a href="adminlogin.html">Admin
Login</a></li>

41
<li class=""><a href="doctorlogin.html">Doctor

Login</a></li>
<li class=""><a href="patientlogin.html">Patient Login</a></li>

<li class=""><a href="kiosklogin.html">Kiosk Login</a></li>
<li class=""><a href="registration.html"> Register</a></li>
</ul>
</div>
</div>
</div>
</nav>
<div class="container">
<div class="row">
<div class="banner-info">
<div class="banner-logo text-center">
<h1 class="white">Welcome to
Administrator <i class="fa fa-medkit"></i></h1>
</div>
<div class="banner-text text-center">
<h3 class="white">Admin Login</h3>
<form action="adminlogin.jsp"
method="post">
<table align="center" height=200px width=200px cellspacing=10px>

42
<tr><th>UserName</th><th><input type="text" name="user" placeholder="UserName"

required/> </th></tr>
<tr><th>Password</th><th><input type="password" name="pwd" placeholder="Password"
required /></th></tr>
<tr><th><input type="submit" value="Submit" style="color:black;"/></th>
<th><input type="reset" value="Reset" style="color:black;"/></th></tr>
</table>
</form>
</div>
<div class="overlay-detail text-center">
<a href="#service"><i class="fa fa-angle-down"></i></a>
</div>
<div class="overlay-detail text-center”>
</div>
</div></div></div>
</div>
</section>
……………
CHAPTER 7
7. SCREENSHOTS
SCREEN OF HOME PAGE:

43

44
SCREEN FOR OUR SERVICES:
SCREEN FOR CONTACT DETAILS:

45
SCREEN FOR ADMIN LOGIN PAGE:

46
SCREEN FOR ADMIN FUNCTIONS:

47
SCREEN FOR DOCTOR LOGIN:

48
SCREEN OF DOCTOR HOME PAGE:

49
SCREEN FOR DOCTORS LIVE CHAT:

50
SCREEN FOR LIVE CHAT:

51
SCREEN FOR PATIENTS LOGIN:

52
SCREEN OF PATIENTS DETAILS:

53
SCREEN FOR PATIENT LIVE CHAT:

54
SCREEN FOR LIVE CHAT:

55
SCREEN OF KIOSK LOGIN PAGE:

56
SCREEN FOR KIOSK HOME PAGE:

57
SCREEN FOR APPOINTMENT DETAILS:

58
SCREEN FOR PENDING APPOINTMENT DETAILS:

59
SCREEN FOR PATIENTS REGISTRATION FORM;

60
8. SYSTEM TESTING AND IMPLEMENTATION

8.1 INTRODUCTION
Errors are relevant only after the system is in use. A system that has been put to use with
out testing can be disastrous in terns of the application
The importance of software testing and its implications cannot be overemphasized.
Software testing is a critical element of Software Quality Assurance and represents the ultimate
review of the specifications, design and coding.
8.2 TESTING OBJECTIVES:

The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,
 Testing is a process of executing a program with the intent of finding an error.
 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
But there is one thing that testing cannot do (just to quote a very famous sentence) “Testing
cannot show the absence of defects, it can only show that software defects are presents.”
As the test results are gathered and evaluated they begin to give a qualitative indication of the
reliability of the software. If severe errors are detected, the overall quality of the software is a
natural suspect. If, on the other hand, all the errors, which are encountered, are easily modifiable,
then one of the two conclusions can be made:
 The tests are inadequate to detect possibly present errors.

 The software more or less confirms to the quality and reliable standards.

61
LEVELS OF TESTING
In order to uncover the errors present in different phases we have the concept of levels of
testing. The basic levels of testing are
Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing

8.3. UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software i.e. the module.
Using the detailed design and the process specifications testing is done to uncover errors within
the boundary of the module. All modules must be successful in the unit test before the start of the
integration testing begins.
In this project “Communication Media” each service can be thought of a module. There
are so many modules like fault registration, mailing, chatting. Each module has been tested by
giving different sets of inputs (giving wrong ID and password etc)when developing the module
as well as finishing the development so that each module works without any error. The inputs are
validated when accepting from the user.
Integration Testing:
After the unit testing we have to perform integration testing. The goal here is to see if
modules can be integrated properly, the emphasis being on testing interfaces between modules.
This testing activity can be considered as testing the design and hence the emphasis on testing
module interactions
In this project ‘Communication Media’, the main system is formed by integrating all the
modules. When integrating all the modules I have checked whether the integration effects
working of any of the services by giving different combinations of inputs with which the two
services run perfectly before Integration.
62
SYSTEM TESTING
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal is to see if software meets its requirements.
Here entire ‘Communication Media’ has been tested against requirements of project and
it is checked whether all requirements of project have been satisfied or not.
ACCEPTANCE TESTING
Acceptance Test is performed with realistic data of the client to demonstrate that the
software is working satisfactorily. Testing here is focused on external behavior of the system; the
internal logic of program is not emphasized. In this project 'Hospic Dossier control’ I have
collected some data and tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an equivalence
class is exercised at once. The testing phase is an important part of software development. It is
the process of finding errors and missing operations and also a complete verification to
determine whether the objectives are met and the user requirements are satisfied.
8.4. TEST PLAN

This document describes the plan for testing the course scheduling software. All major
testing activities are specified here.
Test Units:
In this project we will perform two levels of testing Unit Testing and System Testing the
basic units to be tested are:
Fault Register module
Mail sending module
Mail receiving module
Chat module
Features to be tested:
All the functional features specified in the requirements document will be tested. No
testing is done for the performance requirements like response time.
Approach for Testing:
63
For unit testing structural testing based on the branch coverage criteria will be used. The
goal is to achieve branch coverage of more than 95%.System testing will be largely functional in
nature.

64
Test Deliverables:
The following documents are required.
Unit Test Report for each Unit
Test case specification for system testing
Test report for system testing
The test case specification for system testing has to be submitted for review before
system testing commences
Schedule and Personnel Allocation
The entire testing is performed for a period of 10 days. Test case specifications for the
system testing are produced while unit testing is going on. The number of persons allocated for
my project is one.
TEST CASE REPORT
Here we specify all the test cases that are used for system testing. The different
conditions that need to be tested along with the test cases used for testing those conditions and
the expected outputs are given. The goal is to test the different functional requirements, as
specified in the requirements document. Test cases have been selected for both valid and invalid
inputs.
SAMPLE TEST CASE REPORT

S.No Test case Condition being Expected output Actual Output
checked
1 Valid ID validity for Successful Login Successfully Logged in
registration
2 Invalid ID Validity for Login should fail Failed to login
registration
8.5. 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.
65
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.
CHAPTER 9
66
9. CONCLUSION
It has been a great pleasure for me to work on this project. This project proved good for
me as it provided practical knowledge of not only programming in web based application and no
some extent Windows Application and SQL Server, but also about all handling procedure related
with – “The e-Hospital”. It also provides knowledge about the latest technology used in
developing web enabled application and client server technology that will be great demand in
future. This will provide better opportunities and guidance in future in developing projects
independently.
BENEFITS:
The project is identified by the merits of the system offered to the user. The merits of this project
are as follows: -
 It’s a web-enabled project.
 This project offers user to enter the data through simple and interactive forms. This is very
helpful for the client to enter the desired information through so much simplicity.
 The user is mainly more concerned about the validity of the data, whatever he is entering.
There are checks on every stages of any new creation, data entry or updation so that the user
cannot enter the invalid data, which can create problems at later date.
 Sometimes the user finds in the later stages of using project that he needs to update some of
the information that he entered earlier. There are options for him by which he can update the
records. Moreover there is restriction for his that he cannot change the primary data field.
This keeps the validity of the data to longer extent.
 User is provided the option of monitoring the records he entered earlier. He can see the
desired records with the variety of options provided by him.
 From every part of the project the user is provided with the links through framing so that he
can go from one option of the project to other as per the requirement. This is bound to be
simple and very friendly as per the user is concerned. That is, we can sat that the project is
user friendly which is one of the primary concerns of any good project.

67
 Data storage and retrieval will become faster and easier to maintain because data is stored in
a systematic manner and in a single database.
 Decision making process would be greatly enhanced because of faster processing of
information since data collection from information available on computer takes much less
time then manual system.
 Allocating of sample results becomes much faster because at a time the user can see the
records of last years.
 Easier and faster data transfer through latest technology associated with the computer and
communication.
 Through these features it will increase the efficiency, accuracy and transparency,
LIMITATIONS:
 The size of the database increases day-by-day, increasing the load on the database back up
and data maintenance activity.
 Training for simple computer operations is necessary for the users working on the system.

68
CHAPTER 10
10. FUTURE IMPROVEMENT
 Online payments option can be included in future.

 Integrated ambulance service will be included in future
 Integrated pharmacy out let management can in included in future
 Employee management, their leaves and salaries information will be included in future.

69
11. BIBLIOGRAPHY
R e f e r e n c e s f o r t h e P r o j e c t D e v e l o p m e n t We r e Ta k e n F r o m t h e f o l l o w i n g
B o o k s a n d We b S i t e s .
JAVA Technologies
JAVA Complete Reference
Java Script Programming by Yehuda Shiran
Mastering JAVA Security
JAVA2 Networking by Pistoria
JAVA Security by Scotl oaks
Head First EJB Sierra Bates
J2EE Professional by Shadab siddiqui
JAVA server pages by Larne Pekowsley
JAVA Server pages by Nick Todd
HTML
HTML Black Book by Holzner
JDBC
Java Database Programming with JDBC by Patel moss.

Software Engineering by Roger Pressman

70

71

Hospice Dossier Control: 1.1.purpose of The Project

Uploaded by

Copyright:

Available Formats

Hospice Dossier Control: 1.1.purpose of The Project

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hospice Dossier Control: 1.1.purpose of The Project

Uploaded by

Copyright:

Available Formats

Hospice Dossier Control

Hospice Dossier Control is increasingly being viewed as a solution to customize costs

1.1.PURPOSE OF THE PROJECT

Bhoj Reddy Engineering College for Women

1.2. EXISTING SYSTEM

Importance of Java to the Internet:

Bhoj Reddy Engineering College for Women

FIG 3.1 JAVA ARCHITECTURE

In reality Java interpreter could be an Intel Pentium windows 95 or sun SPARCstation

Bhoj Reddy Engineering College for Women

JAVA DEVELOPMENT EVNIRONMENT

Bhoj Reddy Engineering College for Women

A Servlet Is a generic server extension. a Java class that can be loaded

Servlets operate solely within the domain of the server.

Bhoj Reddy Engineering College for Women

 They’re faster and cleaner then CGI scripts

 Easily configure using the GUI-based Admin tool]

Advantages of the servlet API

 The protocol being used to transmit on the net

Bhoj Reddy Engineering College for Women

 Servlets are extensible Java is a robust, object-oriented programming language,

Every servlet must implement the javax.servelt interface.Most servlets implement it by

Bhoj Reddy Engineering College for Women

The remainders in the javax.servlet and javax.servlet.http.package are largely support

From the <SERVICE_ROOT/servlets/directory.This is not in the server’s classpath. A class

Loading Remote Servlets

 Configuring the admin Tool to setup automatic loading of remote servlets.

Bhoj Reddy Engineering College for Women

 Defining a filter chain Configuration

A Client can Invoke Servlets in the Following Ways:

The Servlet Life Cycle:-

Bhoj Reddy Engineering College for Women

 Create and initialize the servlets

Single java virtual machine and astatine persistence.

Init and Destroy:-

 When the server states

Bhoj Reddy Engineering College for Women

Computerizing of an organization whose branches are situated at different locations and

Bhoj Reddy Engineering College for Women

Bhoj Reddy Engineering College for Women

2.2. Software requirements:

Bhoj Reddy Engineering College for Women

3.1. SYSTEM ARCHITECTURE

Bhoj Reddy Engineering College for Women

3.2 TECHNICAL ARCHITECTURE

Hospice Dossier Patient

Bhoj Reddy Engineering College for Women

Bhoj Reddy Engineering College for Women

USE CASE DIAGRAM

Bhoj Reddy Engineering College for Women

Use Case Diagram for Doctor:

Bhoj Reddy Engineering College for Women

Use Case Diagram for Patient:

Bhoj Reddy Engineering College for Women

Sequence Diagram for Patient:

Bhoj Reddy Engineering College for Women

Sequence Diagram for Negotiating Doctors - ADMIN :

Bhoj Reddy Engineering College for Women