HEALTH CARE FOR YOU 24x7 Medical Help Line

HEALTH CARE FOR YOU 24x7 Medical Help Line
CONTENTS
1. INTRODUCTION
1.1 OVERVIEW
1.2 SCOPE OF THE PROJECT
2. LITERATURE SERVEY
2.1 INTRODUCTION
2.2 JAVA
2.3 JAVA SCRIPTS
3. MODULE
3.1 CLOUD COMPUTING
3.2 DATA LOCATION
3.3 REMOTE DATA BACKUP SERVER
4. SYSTEM REQUIREMENTS AND SPECIFECATION
4.1 FUNCTIONAL REQUIREMENTS
4.2 NON-FUNCTIONAL REQUIREMENTS
4.3 HARDWARE REQUIREMENTS
4.4 SOFTWARE REQUIREMENTS
5. SYSTEM ANALYSIS
5.1 OVER VIEW
5.2 EXISTING SYSTEM
5.3 PROPOSED SYSTEM
6. SYSTEM DESIGN
6.1 SYSTEM DESIGN DEFINITION
6.2 E-R DIAGRAM
6.3 USECASE DIAGRAM
6.4 SEQUENCE DIAGRAM
6.5 ACTIVITY DIAGRAM
7. SOFTWARE TESTING
7.1 INTRODUCTION
7.2 TYPE OF TESTS
7.3 TEST CASES
8. CONCLUSION
8.1 CONCLUSION
9. USER MANUAL
10. BIBLIOGRAPHY
Govt. Science College, Hassan Science and Computer Applications Page 1

1. INTRODUCTION
1.1 OVERVIEW
The main objective of the Healthcare for you is to computerize the maintenance of the patient details and
billing section in the hospital. This system has been developed to form whole management system including
Employees, Doctors, Nurses, Patients, Bills, and Complains etc. It also includes the details about the
laboratory checkups.
Its budget is low and its needs are great, but that hasn’t deterred B.M Hospital (BMH) from
its mission to deliver the highest quality of care to its patients. With 105 employees,
including medical, administrative and support personnel, this 37-bed facility services patients
in the rural area that surrounds Magnolia, a small city in southwestern Mississippi. The
hospital also sought to make patient records available electronically, saving time for
physicians and staff. Wellness Connect uses electronic imaging to collect data and images
from various sources and places it into secure, electronic patient record folders. The stored
information can be retrieved using a Web browser from any location, but only by those with
a need to know are granted access.
1.2 SCOPE OF THE PROJECT
The proposed software product is the Healthcare for you. The system will based in any
Hospital, Clinic, Dispensary or Pathology labs in any Hospital, Clinic, Dispensary or
Pathology labs to get the information from the patients and then storing that data for future
usage .
The current system in use is a paper-based system. It is too slow and cannot provide updated
lists of patients within a reasonable timeframe. The intentions of the system are to reduce
over-time pay and increase the number of patients that can be treated accurately.
Requirements statements in this document are both functional and non-functional.

2. LITERATURE SURVEY
2.1 INTRODUCTION
Literature survey is the most important step in software development process. Before
developing the tool it is necessary to determine the time factor, economy and company
strength. Once these things are satisfied, then next step is to determine which operating
system and language can be used for developing the tool. Once the programmers start
building the tool the programmer need lot of external support. This support can be obtained
from senior programmers, from book or from website. Before building the system the above
consideration are taken into account for developing the proposed system.
Hospitals currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper form with data stores spread
throughout the hospital management infrastructure. Often information is incomplete or does
not follow management standards. Forms are often lost in transit between departments
requires a comprehensive auditing process to ensure that no vital information is lost.
Multiple copies of the same information exist in the hospital and may lead to inconsistencies
in data in various data stories.
2.2 JAVA SERVER PAGES
Introduction:
Jsp technology enables you to mix regular static html with dynamically generated content from servlets.
Separating the static html from the dynamic content provides a number of benefits over servlets alone.
Why use JSP:
Jsp is easy to learn and allows developers to quickly produce wed sites and application in an open and
standard way. Jsp is based on java, an object-oriented language. Jsp offers a robust platform for web
development.

Main reasons to Jsp:
a. Multi platform
b. Component reuse by using java beans and Ejb
c. Advantages if java
We can take one Jsp file and move it to another platform, web server or Jsp servlet engine.
JSP compared to ASP:
Jsp and Asp are fairly similar in the functionality that they provide. Jsp may have slightly higher learning
curve. Both allow embedded code in an html page, session variables Platform i.e., NT, JSP can operate on
any platform that conforms to the J2EE specification. Jsp allow component reuse by using JavaBeans and
Ejbs. Asp provides the use of Com/activeX controls.
JSP compared to servlets:
A servlet is java class that provides special server side service. It is hard to write HTML code in
servlets. In servlets you need to have lots of println statement to generate HTML.
Description:
JSP looks like html, but they get compiled into java servlets the first time they are invoked. The
resulting servlet is a combination of the html from the jsp file and embedded dynamic content specified by
the new tags. That is not to say that jsp must contain html. Some of them contain only java code; this is
particularly useful when the jsp is responsible for a particular task like maintaining application flow.
Everything in Jsp can be broken into 2 categories:
a. Elements that are processed on the server.

b. Template data or everything other than elements that the engine processing the Jsp ignores.
A Jsp page is executed by a Jsp engine
2.3 JAVA SCRIPT
Java Script is Netscape’s cross–platform, object-based scripting language for client server
application. JavaScript is mainly used as a client side scripting language. This means that JavaScript code is
written into an HTML page. When a user requests an HTML page with JavaScript in it, the script is sent to

the browser and it's up to the browser to do something with it. JavaScript can be used in other contexts than
a Web browser. Netscape created server-side JavaScript as a CGI-language that can do roughly the same as
Perl or ASP.
Fortunately most browsers can handle JavaScript nowadays, but of course some browsers do not
support some bits of script.
Types of Java Script:
a. Navigator Java Script also called client-side Java Script.
b. Live Wire Java Script also called server-side Java Script.
Using Java Script, dynamic HTML pages can be created that process user input and maintain
persistent data using special objects, files and relational databases. Browser interprets JavaScript statements
embedded in an HTML page. Netscape Navigator 2.0 and Internet Explorer 3.0 versions and later recognize
Java Script. Through JavaScript Live Connect functionally, application can access Java and CORBA
distributed-object applications. Navigator versions supports Live Connect.

3. MODULES
1. Registration/Login
2. Admin
3. Users
4. Patient
1. Registration/Login
All the users like Physician, Front Office Assistant, Lab Assistant, and Patient have to register into the
application before they can use it. The users will have to fill the required details in the registration form and
then only they can login and access the application.
2. Admin
Admin can login using his credentials. He keeps the record of all the activities in the application. He sets the
access policies for all the users of application.
3. Users
Users are Physician, Lab Assistant, and Front Office Assistant.

Physician can write the prescription for the patient and also view it. He can view the patient details.
4. Patient
Patient can login and view the history of his check ups and also view the prescription given. He can write
anything.

4. SYSTEM REQUIREMENT AND SPECIFICATION

SRS – SOFTWARE REQUIREMENT SPECIFICATION
Requirements analysis, also called requirements engineering, is the process of determining user expectations
for a new or modified product. These features, called requirements, must be quantifiable, relevant and
detailed. In software engineering, such requirements are often called functional specifications. Requirements
analysis is an important aspect of project management. Requirements analysis involves frequent
communication with system users to determine specific feature expectations, resolution of conflict or
ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature
creep and documentation of all aspects of the project development process from start to finish. Energy
should be directed towards ensuring that the final system or product conforms to client needs rather than
attempting to mold user expectations to fit the requirements. Requirements analysis is a team effort that
demands a combination of hardware, software and human factors engineering expertise as well as skills in
dealing with people.
4.1 HARDWARE REQUIREMENTS
Hardware required to develop the software is as listed below
Processer : Any Update Processer

Ram : Min 1 GB
Hard Disk : Min 100 GB
4.2 SOFTWARE REQUIREMENTS:
Operating System : Windows family

Technology : Java (1.7/1.8)
Web Technologies : Html, Html-5, JavaScript, CSS.
Web Server : Tomcat 7/8 server side Lang : J2EE
Database : My SQL5.5

5. SYSTEM ANALYSIS
5.1 EXISTING SYSTEM
Hospitals currently use a manual system for the management and maintenance of critical information.
The current system requires numerous paper form with data stores spread throughout the hospital
management infrastructure. Often information is incomplete or does not follow management standards.
Forms are often lost in transit between departments requires a comprehensive auditing process to ensure that
no vital information is lost. Multiple copies of the same information exist in the hospital and may lead to
inconsistencies in data in various data stories.
DISADVANTAGES
 Hospitals currently use a manual system for the management and maintenance of critical
information. The current system requires numerous paper forms, with data stores spread throughout
the hospital management infrastructure.
 Often information is incomplete or does not follow management standards.
 Forms are often lost in transit between departments requiring comprehensive auditing process to
ensure that no vital information is lost.
 Multiple copies of the same information exist in the hospital and may lead to inconsistencies in data
in various data stores.
5.2 PROPOSED SYSTEM
1. Patient Registration happens online when the patient walks into the hospital facility. An online
registration form is filled by the Front Office Assistant. The patient id is generated automatically buy the
system. The patient record can be accessed by authorized users of the system in various sections. example. A
LAB Assistant cannot view patient history of physicians recording. This user can only view basic contact
details and any LAB Work which has happened in the past and electronic reports.
2. For walk in patients, the physician shall pull up patient record with the patient name or phone number.
The history of visits and earlier prescription can be viewed along with the reports.
3. Physician updates the patient record for heath problem visited for, recommendation brief, selects health
condition from the master list, prescribes tests if any from the master list. In case of tests, the lab team is
notified. An appointment record is generated for the patient.

4. The bills are generated for the patient based on the Procedure(s) selected by the Physician. The bills are
sent to the health insurance company as a text file feed.
5. The masters such as Billing Code, LAB Tests, Room Charges are maintained by the
Administrator of the system.
6. The security of patient record is very important, thus all role players can view only selective information
of the patient.
7. The application generates the Number of Hours put in by the physician’s In and out time entry done by
him.
8. The system also generates turnaround time reports for servicing the patients e.g. Time of registering to
time of physician’s appointment or procedure. Identifying wait time of patients and work towards reducing
it.
ADVANTAGES OF PROPOSED SYSTEM
 Makes easy for the patients as they do not have to do many procedures manually
 The information about the patient and his prescriptions history will be stored in the database.
5.3 FEASIBILITY STUDY
Feasibility study is conducted once the problem is clearly understood. The feasibility study which is a high
level capsule version of the entire system analysis and design process. The objective is to determine whether
the proposed system is feasible or not and it helps us to the minimum expense of how to solve the problem
and to determine, if the Problem is worth solving. The following are the three important tests that have been
carried out for feasibility study.
5.5.1 Technical feasibility
In the technical feasibility study, one has to test whether the proposed system can be developed using
existing technology or not. It is planned to implement the proposed system in JSP. The project entitled is
technically feasible because of the following reasons.
 All necessary technology exists to develop the system.

 The existing system is so flexible that it can be developed further.
5.5.2 Economic feasibility
As a part of this, the costs and benefits associated with the proposed systems are to be compared. The
project is economically feasible only if tangible and intangible benefits outweigh the cost. We can say the
proposed system is feasible based on the following grounds.
 The cost of developing the full system is reasonable.

 The cost of hardware and software for the application is less.

3.3.2 Operational feasibility
The project is operationally feasible because there is sufficient support from the project management
and the users of the proposed system .Proposed system definitely does not harm and will not produce the
bad results and no problem will arise after implementation of the system.
User-friendly
Customer will use the forms for their various transaction i.e. for adding new routes, viewing the routes
details. Also the Customer wants the reports to view the various transactions based on the constraints. These
forms and reports are generated as user-friendly to the Client.
Reliability
The package wills pick-up current transactions on line. Regarding the old transactions, User will enter them
in to the system.
Security
The web server and database server should be protected from hacking, virus etc.
Availability
This software will be available always.
3.4 PROCESS MODEL USED WITH JUSTIFICATION
SDLC is nothing but Software Development Life Cycle. It is a standard which is used by software industry
to develop good software.

SDLC (SPIRAL MODEL):
3.5 Stages of SDLC:
Requirement Gathering and Analysis
 Designing
 Coding
 Testing
 Deployment
3.5.1 Requirements Definition Stage and Analysis:
The requirements gathering process takes as its input the goals identified in the high-level
requirements section of the project plan. Each goal will be refined into a set of one or more requirements.
These requirements define the major functions of the intended application, define operational data areas and
reference data areas, and define the initial data entities. Major functions include critical processes to be
managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and

associated with these major functions, data areas, and data entities. Each of these definitions is termed a
Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a
requirement title and textual description.
These
requirements are
fully described in
the primary deliverables for this stage: the Requirements Document and the Requirements Traceability
Matrix (RTM). the requirements document contains complete descriptions of each requirement, including
diagrams and references to external documents as necessary. Note that detailed listings of database tables
and fields are not included in the requirements document. The title of each requirement is also placed into
the first version of the RTM, along with the title of each goal from the project plan.
3.5.2 Design Stage:
The design stage takes as its initial input the requirements identified in the approved requirements
document. For each requirement, a set of one or more design elements will be produced as a result of
interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in
detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules,
business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data
dictionary.

3.5.3 Development Stage:
The development stage takes as its primary input the design elements described in the approved
design document. For each design element, a set of one or more software artifacts will be produced.
Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting
formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of
functionally related software artifacts, and an online help system will be developed to guide users in their
interactions with the software.

The RTM will be updated to show that each developed artifact is linked to a specific design element, and
that each developed artifact has one or more corresponding test case items. At this point, the RTM is in its
final configuration. The outputs of the development stage include a fully functional set of software that
satisfies the requirements and design elements previously documented, an online help system that describes
the operation of the software, an implementation map that identifies the primary code entry points for all
major system functions, a test plan that describes the test cases to be used to validate the correctness and
completeness of the software, an updated RTM, and an updated project plan.
3.5.4 Integration & Test Stage:
During the integration and test stage, the software artifacts, online help, and test data are migrated
from the development environment to a separate test environment. At this point, all test cases are run to
verify the correctness and completeness of the software. Successful execution of the test suite confirms a
robust and complete migration capability.
During this stage, reference data is finalized for production use and production users are identified
and linked to their appropriate roles. The final reference data (or links to reference data source files) and
production user list are compiled intothe Production Initiation Plan.

The outputs of the integration and test stage include an integrated set of software, an online help
system, an implementation map, a production initiation plan that describes reference data and production
users, an acceptance plan which contains the final suite of test cases, and an updated project plan.
3.5.5Installation & Acceptance Stage
During the installation and acceptance stage, the software artifacts, online help, and initial production data
are loaded onto the production server. At this point, all test cases are run to verify the correctness and
completeness of the software. Successful execution of the test suite is a prerequisite to acceptance of the
software by the customer.
After customer personnel have verified that the initial production data load is correct and the test
suite has been executed with satisfactory results, the customer formally accepts the delivery of the software.
The primary outputs of the installation and acceptance stage include a production application, a
completed acceptance test suite, and a memorandum of customer acceptance of the software. Finally, the
PDR enters the last of the actual labor data into the project schedule and locks the project as a permanent
project record. At this point the PDR "locks" the project by archiving all software items, the implementation
map, the source code, and the documentation for future reference.
6. SYSTEM DESIGN
Systems design is the process of defining the architecture, components, modules, interfaces,
and data for a system to satisfy specified requirements. Systems design could be seen as the application
of systems theory to product development. There is some overlap with the disciplines of systems
analysis, systems architecture and systems engineering. The architectural design of a system emphasizes on
the design of the systems architecture which describes the structure, behavior, and more views of that
system.
The System Design Document describes the system requirements, operating environment, system and
subsystem architecture, files and database design, input formats, output layouts, human-machine interfaces,
detailed design, processing logic, and external interfaces.
6.1 UML DIAGRAMS DESCRIPTION:
Global Use Case Diagrams:
Identification of actors:
Actor: Actor represents the role a user plays with respect to the system. An actor interacts with, but has no
control over the use cases.
Graphical representation:

Actor <<Actor name>>
An actor is someone or something that:
Interacts with or uses the system.
 Provides input to and receives information from the system.

 Is external to the system and has no control over the use cases.
Actors are discovered by examining:
 Who directly uses the system?

 Who is responsible for maintaining the system?
 External hardware used by the system.
 Other systems that need to interact with the system.
Questions to identify actors:
 Who is using the system? Or, who is affected by the system? Or, which groups need help from the
system to perform a task?
 Who affects the system? Or, which user groups are needed by the system to perform its functions?
These functions can be both main functions and secondary functions such as administration.
 Which external hardware or systems (if any) use the system to perform tasks?
 What problems does this application solve (that is, for whom)?
 And, finally, how do users use the system (use case)? What are they doing with the system?
The actors identified in this system are:
a. System Administrator
b. Customer
c. Customer Care

Identification of use cases:
Use case: A use case can be described as a specific way of using the system from a user’s (actor’s)
perspective.
Graphical representation:
A more detailed description might characterize a use case as:
 Pattern of behavior the system exhibits

 A sequence of related transactions performed by an actor and the system
 Delivering something of value to the actor
Use cases provide a means to:
 capture system requirements

 communicate with the end users and domain experts
 test the system
Use cases are best discovered by examining the actors and defining what the actor will be able to do with
the system.
Guide lines for identifying use cases:
 For each actor, find the tasks and functions that the actor should be able to perform or that the system
needs the actor to perform. The use case should represent a course of events that leads to clear goal
 Name the use cases.
 Describe the use cases briefly by applying terms with which the user is familiar.
This makes the description less ambiguous Questions to identify use cases:
 What are the tasks of each actor?

 Will any actor create, store, change, remove or read information in the system?
 What use case will store, change, remove or read this information?
 Will any actor need to inform the system about sudden external changes?
 Does any actor need to inform about certain occurrences in the system?
 What use cases will support and maintains the system?
6.2 use case Diagram
System
Login
Admin
Registration
Set Access Policy
User
Write Data
Patient
View Data
Modify Data
Relationships in use cases:

a. Communication: The communication relationship of an actor in a use case is shown by connecting

the actor symbol to the use case symbol with a solid path. The actor is said to communicate with the
use case.
b. Uses:
A Uses relationship between the use cases is shown by generalization arrow from the use case.
c. Extends:
The extend relationship is used when we have one use case that is similar to another use case but does a bit
more. In essence it is like subclass.
6.3 SEQUENCE DIAGRAMS
A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence
what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide
essential information to determine class responsibilities and interfaces.
There are two main differences between sequence and collaboration diagrams: sequence diagrams show
time-based object interaction while collaboration diagrams show how objects associate with each other. A
sequence diagram has two dimensions: typically, vertical placement represents time and horizontal
placement represents different objects.
Object:
An object has state, behavior, and identity. The structure and behavior of similar objects are defined in their
common class. Each object in a diagram indicates some instance of a class. An object that is not named is
referred to as a class instance.
The object icon is similar to a class icon except that the name is underlined:
An object's concurrency is defined by the concurrency of its class.
Message:
A message is the communication carried between two objects that trigger an event. A message carries
information from the source focus of control to the destination focus of control. The synchronization of a

message can be modified through the message specification. Synchronization means a message where the
sending object pauses to wait for results.
Link:
A link should exist between two objects, including class utilities, only if there is a relationship between their
corresponding classes. The existence of a relationship between two classes symbolizes a path of
communication between instances of the classes: one object may send messages to another. The link is
depicted as a straight line between objects or objects and class instances in a collaboration diagram. If an
object links to itself, use the loop version of the icon.
Admin/Creator Login
Set Access Policies Store
: Admin
1 : UserId()
2 : Password()
3 : Login()
4 : AccessPolicy()
5 : Transfer()
6.4 CLASS DIAGRAM:
Identification of analysis classes:
A class is a set of objects that share a common structure and common behavior (the same attributes,
operations, relationships and semantics). A class is an abstraction of real-world items.
There are 4 approaches for identifying classes:
a. Noun phrase approach:

b. Common class pattern approach.
c. Use case Driven Sequence or Collaboration approach.

d. Classes , Responsibilities and collaborators Approach
Noun Phrase Approach:
The guidelines for identifying the classes:
a. Look for nouns and noun phrases in the use cases.

b. Some classes are implicit or taken from general knowledge.
c. All classes must make sense in the application domain; Avoid computer
Implementation classes – defer them to the design stage.
d. Carefully choose and define the class names After identifying the classes we have to
eliminate the following types of classes:
 A Common class pattern approach:
The following are the patterns for finding the candidate classes:
e. Concept class.
f. Events class.
g. Organization class
h. Peoples class
i. Places class
j. Tangible things and devices class.

Admin Cloud
+UserName
+Store Data()
+Password
+role
+AccessPolicy
+Login()
+AccessPolicy()
Patient User
+Username +Username
+Password +Password
+role +Role
+key +Key
+WriteData() +Decryption()
+Encryption() +ViewData()
+Modify()

I. Use case driven approach:
We have to draw the sequence diagram or collaboration diagram. If there is need for some classes
to represent some functionality then add new classes which perform those functionalities.
II. CRC approach:
The process consists of the following steps:
k. Identify classes’ responsibilities ( and identify the classes )

l. Assign the responsibilities
m. Identify the collaborators.
Identification of responsibilities of each class:
The questions that should be answered to identify the attributes and methods of a class respectively are:
a. What information about an object should we keep track of?

b. What services must a class provide?
Identification of relationships among the classes:
Three types of relationships among the objects are:
Association: How objects are associated?
Super-sub structure: How are objects organized into super classes and sub classes?
Aggregation: What is the composition of the complex classes?
Association:
The questions that will help us to identify the associations are:
a. Is the class capable of fulfilling the required task by itself?

b. If not, what does it need?
c. From what other classes can it acquire what it needs?
Guidelines for identifying the tentative associations:

 A dependency between two or more classes may be an association. Association often corresponds to
a verb or prepositional phrase.
 A reference from one class to another is an association. Some associations are implicit or taken from
general knowledge.
Some common association patterns are:
Location association like part of, next to, contained in…..
Communication association like talk to, order to ……
We have to eliminate the unnecessary association like implementation associations, ternary or n-ary
associations and derived associations.
There are three types of aggregation relationships. They are:
Assembly:
It is constructed from its parts and an assembly-part situation physically exists.
Container:
A physical whole encompasses but is not constructed from physical parts.
Collection member:
A conceptual whole encompasses parts that may be physical or conceptual. The container and collection are
represented by hollow diamonds but composition is represented by solid diamond.
7. SOFTWARE TESTING
Testing is the debugging program is one of the most critical aspects of the computer programming
triggers, without programming that works, the system would never produce an output of which it was
designed. Testing is best performed when user development is asked to assist in identifying all errors and
bugs. The sample data are used for testing. It is not quantity but quality of the data used the matters of

testing. Testing is aimed at ensuring that the system was accurately an efficiently before live operation
commands.
8.1 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 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 probability of finding an error, if it exists.
The test is inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.
8.2 Levels of Testing:
In order to uncover present in different phases we have the concept of levels of testing.
8.3 The basic levels of Testing:
Client needs acceptance testing
Requirements system testing
Design integration testing
Code unit testing
Figure 7.1: Levels of Testing

8.3.1 Code testing:
This examines the logic of the program. For example, the logic for updating various sample data and
with the sample files and directories were tested and verified.
8.3.2 Specification Testing:
Executing this specification starting what the program should do and how it should performed under
various conditions. Test cases for various situation and combination of conditions in all the modules are
tested.
8.3.3 Unit testing:
In the unit testing we test each module individually and integrate with the overall system. Unit
testing focuses verification efforts on the smallest unit of software design in the module. This is also known
as module testing. The module of the system is tested separately. This testing is carried out during
programming stage itself. In the testing step each module is found to work satisfactorily as regard to
expected output from the module. There are some validation checks for fields also. For example the
validation check is done for varying the user input given by the user which validity of the data entered. It is
very easy to find error debut the system.
Each Module can be tested using the following two Strategies:
1. Black Box Testing

2. White Box Testing
8.4 BLACK BOX TESTING
What is Black Box Testing?
Black box testing is a software testing techniques in which functionality of the software under test
(SUT) is tested without looking at the internal code structure, implementation details and knowledge of
internal paths of the software. This type of testing is based entirely on the software requirements and
specifications.
In Black Box Testing we just focus on inputs and output of the software system without bothering about
internal knowledge of the software program.

The above Black Box can be any software system you want to test. For example : an operating
system like Windows, a website like Google ,a database like Oracle or even your own custom application.
Under Black Box Testing , you can test these applications by just focusing on the inputs and outputs without
knowing their internal code implementation.
8.4.1 Black box testing - Steps
Here are the generic steps followed to carry out any type of Black Box Testing.
 Initially requirements and specifications of the system are examined.

 Tester chooses valid inputs (positive test scenario) to check whether SUT processes them correctly.
Also some invalid inputs (negative test scenario) are chosen to verify that the SUT is able to detect
them.
 Tester determines expected outputs for all those inputs.
 Software tester constructs test cases with the selected inputs.
 The test cases are executed.
 Software tester compares the actual outputs with the expected outputs.
 Defects if any are fixed and re-tested.
8.4.2 Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones -
 Functional testing – This black box testing type is related to functional requirements of a system; it
is done by software testers.
 Non-functional testing – This type of black box testing is not related to testing of a specific
functionality, but non-functional requirements such as performance, scalability, usability.
 Regression testing – Regression testing is done after code fixes , upgrades or any other system
maintenance to check the new code has not affected the existing code.
8.5 WHITE BOX TESTING

White Box Testing is the testing of a software solution's internal coding and infrastructure.It focuses
primarily on strengthening security, the flow of inputs and outputs through the application, and improving
design and usability.White box testing is also known as clear, open, structural, and glass box testing.
It is one of two parts of the "box testing" approach of software testing. Its counter-part, blackbox testing,
involves testing from an external or end-user type perspective. On the other hand, Whitebox testing is based
on the inner workings of an application and revolves around internal testing. The term "whitebox" was used
because of the see-through box concept. The clear box or whitebox name symbolizes the ability to see
through the software's outer shell (or "box") into its inner workings. Likewise, the "black box" in "black box
testing" symbolizes not being able to see the inner workings of the software so that only the end-user
experience can be tested
What do you verify in White Box Testing ?
White box testing involves the testing of the software code for the following:
 Internal security holes

 Broken or poorly structured paths in the coding processes
 The flow of specific inputs through the code
 Expected output
 The functionality of conditional loops
 Testing of each statement, object and function on an individual basis
8.5.1 System testing:
Once the individual module testing is completed, modules are assembled and integrated to
perform as a system. The top down testing, which began from upper level to lower level module, was carried
out to check whether the entire system is performing satisfactorily.
There are three main kinds of System testing:

i. Alpha Testing
ii. Beta Testing
iii. Acceptance Testing
Alpha Testing:
This refers to the system testing that is carried out by the test team with the Organization.
Beta Testing:
This refers to the system testing that is performed by a selected group of friendly customers
Acceptance Testing:
This refers to the system testing that is performed by the customer to determine whether or not to
accept the delivery of the system.
8.5.2 Integration Testing:
Data can be lost across an interface, one module can have an adverse effort on the other sub
functions, when combined, may not produce the desired major functions. Integrated testing is the systematic
testing for constructing the uncover errors within the interface. The testing was done with sample data. The
developed system has run successfully for this sample data. The need for integrated test is to find the overall
system performance.
8.5.3 Output testing:
After performance of the validation testing, the next step is output testing. The output displayed or
generated by the system under consideration is tested by asking the user about the format required by
system.

9. CONCLUSION
To reduce the paper work and increase the efficiency of working of hospital, this project helps in
computerizing all the procedure in hospital.
Since we are entering details of the patients electronically in”Healthcare for you”, data will be secured.
Using this application we can retrieve patient’s history with a single click. Thus processing information will
be faster. It guarantees accurate maintenance of Patient details. It easily reduces the book keeping task and
thus reduces the human effort and increases accuracy speed.

10. USER MANUAL


BIBLOGRAPHY
 IEEE Recommended Practice for Software Design Descriptions IEEE Std 1016-1998
 IEEE Recommended Practice for Software Requirements Specifications - IEEE Std 830- 1998
 IEEE Standard for Software Test Documentation IEEE Std 829-1998
 IEEE Guide for Software Quality Assurance Planning - IEEE Std 730.1-1995
 http://www.asp.net/learn/data-access/tutorial-16-vb.aspx
 www.gliffy.com
 http://msdn.microsoft.com/ens/library/system.security.permissions.securitypermissionattr ibute(VS.71).aspx
 http://en.wikipedia.org/wiki/Load_testing
 http://en.wikipedia.org/wiki/Unit_test
 http://www.viveo-oolobject.com/savoirfaire/ecmfinance/concepts/usine/3tiers.php
 http://en.wikipedia.org/wiki/Manual_testing

HEALTH CARE FOR YOU 24x7 Medical Help Line

Uploaded by

Document Information

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

HEALTH CARE FOR YOU 24x7 Medical Help Line

Uploaded by

Copyright:

Available Formats

HEALTH CARE FOR YOU 24x7 Medical Help Line

Govt. Science College, Hassan Science and Computer Applications Page 1

1.2 SCOPE OF THE PROJECT

Govt. Science College, Hassan Science and Computer Applications Page 2

2.2 JAVA SERVER PAGES

Why use JSP:

Govt. Science College, Hassan Science and Computer Applications Page 3

Main reasons to Jsp:

JSP compared to ASP:

JSP compared to servlets:

Everything in Jsp can be broken into 2 categories:

a. Elements that are processed on the server.

A Jsp page is executed by a Jsp engine

2.3 JAVA SCRIPT

Govt. Science College, Hassan Science and Computer Applications Page 4

Types of Java Script:

a. Navigator Java Script also called client-side Java Script.

b. Live Wire Java Script also called server-side Java Script.

Govt. Science College, Hassan Science and Computer Applications Page 5

Users are Physician, Lab Assistant, and Front Office Assistant.

Govt. Science College, Hassan Science and Computer Applications Page 6

4. SYSTEM REQUIREMENT AND SPECIFICATION

4.1 HARDWARE REQUIREMENTS

Hardware required to develop the software is as listed below

Processer : Any Update Processer

Operating System : Windows family

Govt. Science College, Hassan Science and Computer Applications Page 7

 Often information is incomplete or does not follow management standards.

5.2 PROPOSED SYSTEM

Govt. Science College, Hassan Science and Computer Applications Page 8

5.3 FEASIBILITY STUDY

5.5.1 Technical feasibility

 All necessary technology exists to develop the system.

Govt. Science College, Hassan Science and Computer Applications Page 9

 The cost of hardware and software for the application is less.

This software will be available always.

3.4 PROCESS MODEL USED WITH JUSTIFICATION

Govt. Science College, Hassan Science and Computer Applications Page 10

SDLC (SPIRAL MODEL):

3.5 Stages of SDLC:

Requirement Gathering and Analysis

3.5.1 Requirements Definition Stage and Analysis:

Govt. Science College, Hassan Science and Computer Applications Page 11

3.5.2 Design Stage:

Govt. Science College, Hassan Science and Computer Applications Page 12

3.5.3 Development Stage:

Govt. Science College, Hassan Science and Computer Applications Page 13

3.5.4 Integration & Test Stage:

Govt. Science College, Hassan Science and Computer Applications Page 14

3.5.5Installation & Acceptance Stage

6.1 UML DIAGRAMS DESCRIPTION:

Global Use Case Diagrams:

Govt. Science College, Hassan Science and Computer Applications Page 16

Actor <<Actor name>>

An actor is someone or something that:

Interacts with or uses the system.

 Provides input to and receives information from the system.

Actors are discovered by examining:

 Who directly uses the system?

Questions to identify actors:

The actors identified in this system are:

Govt. Science College, Hassan Science and Computer Applications Page 17

Identification of use cases: