UploadSign inJoin

Mini Project Patholab

Uploaded by Kumar Manish
PathologySystemSoftwareFeasibility StudyClinical Pathology
31
5.4K views
3.8/5 score
Embed
View More
Copyright: Attribution Non-Commercial (BY-NC)
Download as DOC, PDF, TXT or read online from Scribd
Flag for inappropriate content

Documents Similar To Mini Project Patholab

Mcs 044 Mini Projects Synopsis

by sajilbabu

Laboratory Business Plan- 3rd Sem

 by Siddharth Singh

Hospital Management System - Synopsis and Project Report

by anandsinghvishen

Documents About Pathology

Necropsy- Killer Whale Kanduke

by The Orca Project Corp

 tmp512B.tmp

by Frontiers

As 4700.2-2004 Implementation of Health Level Seven (HL7) Version 2.3.1

Pathology Orders and Results

by SAI Global - APAC

More From Kumar Manish

cs

by Kumar Manish

 m03L05

by Kumar Manish

Daa Question Bank

by Kumar Manish

of 53
1

were observed.
In addition, logic
and boundary
conditions for
inputand output
data was also
checked. The
interface
between this
modeland others
was also checked
for correctness.
W
hile collecting
the inputdata for
testing the
program module
it was kept in
mind that
inputdata must
be from the all
classes, so the
entire condition
of theprogram
could be
checked. In the
testing the role
of the user is
alsovery
important since
they understand
the full range of
data
andcondition that
might occur in
the system. So a
wide range of
data
wascollected
from the user to
test the program
thoroughly. The
actualevaluation
of any system
can occur along
any of the
followingdimens
ions.
Integration and
system
T
esting
W
hen the
individual
program
modules were
working
properly,
wecombined the
module into a
working system.
This integration
isplanned and
coordinated so
that when an
errors occurs, we
have anidea of
what caused it.
Integration is the
process of
verifying that
thecomponents
of the system
work together.
For testing, the
entiresystem was
viewed as a
hierarchy of
modules.
W
e began with
thehighest level
of design and
worked down.
The next
modules to
betested are
those that call
the previously
tested are those
that call
thepreviously
tested modules.
F
unction
T
est
Once we were
sure that
information is
passed among
modulesaccordin
g to the design
prescription we
tested the system
to assurewhether
the function
described the
requirement
specification
wereactually
performed by the
integrated
system.
Acceptance
T
est
W
hen the function
test was
completed, we
involved the user
to makesure that
the system
worked
according to
users exception.
Thus theuser did
final acceptance
test.
Installation
T
est
W
hen acceptance
test was
completed, the
acceptance
system
wasinstalled in
the environment
in which it
would be used
and a
finalinstallation
test was
performed to
make sure that
the system
functionas it
should.
Implement
ation &
Maintenan
ce
The term
implementation
signifies all
those activities
that thetake place
to convert from
old system to the
new. Conversion
is oneaspect of
implementation.
The other aspects
are post
implementationr
eview and
software
maintenance.Bas
ically there are
three types of
implementation1
.
Training2.

Conversion3.

Post
implementation
T
raining
Even well
designed and
technically
elegant system
can succeedor
fail because of
the way they are
operated and
used. Therefore,
thequality of
training received
by the personnel
involved with
the systemin
various
capacities helps
or hinders and
may even
prevent
thesuccessful
implementation
of an
information
system. Those
who will
beassociated
with or affected
by the system
must know in
detail whattheir
roles will be,
they can use the
system and what
the system willor
will not do. Both
system operators
and users need
training.Training
system
operatorsMany
systems depend
on the computer
center personnel,
whoare
responsible for
keeping the
equipment
running as well
as forproviding
the necessary
support service.
Their training
must ensurethat
they are able to
handle all
possible
operations, both
routine
andextraordinary
. Operator
training must
involve the data
entrypersonnel.
Since the system
in commercial
tax is a new one
so, thetraining
personnel have
been given first
hand idea of how
to use andhandle
the equipments
properly. They
have also been
familiarized
withthe
operational
activities of the
system e.g.,
proper
shutdown,mainte
nance, common
malfunction and
their remedies.It
also involves
familiarization
with run
procedures,
whichinvolves
working through
the sequence of
activities needed
to use anew
system on
ongoing basis.
These
procedures allow
the
computeroperato
rs to become
familiar with the
actions they need
to take, andwhen
these actions
occur. In
addition, they are
also informed
that howlong
applications will
run under normal
condition. This
information
isimportant both
to enable users to
plan work
activities and to
identifysystem
that run longer or
shorter then
expected a sign
that
typicallyindicate
s problems with
the run.
U
ser
T
raining
During user
training special
emphasis has
been given
onequipment use
i.e., how to
operate the
equipment. In it
users havebeen
the idea of
troubleshooting
the system,
determining
whether
aproblem that
arises is caused
by the equipment
or software or
bysomething
they have done
in using the
system. A
troubleshootingg
uide has also
been provided to
users in case of
emergency
handling.Data-
handling
activities
receiving the
most attention in
usertraining are
adding data,
editing data,
formulating
enquiries
anddeleting
records of data.
Conversion
Conversion is
the process of
changing from
old system to
newsystem. Here
phase in method
has been adopted
because it is
notpossible to
install a new
system
throughout an
organization all
atonce. The
conversion of
files, training of
personnel or
arrival
of equipment
may force the
staging of the
implementation
over a periodof
time, ranging
from weeks to
months.Conversi
on planThe
conversion plan
includes a
description of all
the activities
of that must
occur to
implement the
new system and
put it
intooperation. It
defines the
persons
responsible for
each activity
andincludes a
timetable
indicating when
each activity will
occur.
Maintenance
The maintenance
part basically
concerned with
the
modificationthat
are made to a
MIS of Doctors
system in initial
release.Maintena
nce used to be
viewed as merely
bug fixing, and it
wasdistressing to
discover that so
much effort was
being spent on
fixingdefects and
rectifying
defects.The
majority of time
spent on
maintenance of
ESCHPD
systemis in fact
spent on
enhancing the
system with
more
information
andinterface that
were not in the
original
specification or
were stated
incorrectly
there.There is a
general
perception that
maintenance is
indeed not
theproper word
to use with
software because
maintenance
refers to unkeep
of the product in
response to the
gradual
deterioration of
partsdue to
extended use of
the product. For
example,
transmissions
areoiled and air
filters are dusted
and periodically
changed. To use
theword
maintenance
with software
gives the wrong
connotation
becausesoftware
doesnt wear
out.
Unfortunately,
however the term
is used sowidely
that we will
continue using it.
Conclusion
Using Powerful
development
tools like Java
and MS-Access
theproject titled
Pathology Lab
has been
developed
successfully.
Everypossible
validation is
applied to the
various controls
used in the
forms.The
system
developed
provides is
applied to the
various controls
usedin the forms.
The system
developed
provides a high
degree
of accuracy and
user friendliness.
The back end
MS-Access
providesflexibilit
y for dealing
with the
data.Since the
Pathology Lab
is a part of
Hospital
managementsyst
em, we use Java
as a development
platform.
Obviously it is
menudriven
program and
there is
flexibility of
using MS-
Access or
SQLServer at
backend. But due
to much
flexibility our
project suggested
touse MS-Access
as backend.

It generates test
reports; provide
prescription
details
includingvarious
tests, prescribed
to patient and
doctor. The
system
alsoprovides the
facility of
backup as per the
requirement.
W
hen we started
our project our
first objective
was to find sucha
control which
was very fast and
also provided the
flexibility of
Testreport for
they can be
easily exported
and printed.The
control on which
we did our
reporting work
has a very
largescope we it
also facilitate
some extra
features with
their kin
builtfunctions.
But at some
places we faced
some unusual
problems.Overall
, it has been a
nice experience
to work on Java
and MS-Access
in the same
project.
B
ibliography
B
ooks name
Author Publisher
The complete
ReferenceJava2
Herbert Schildt
TMHJava 2
Beginning Ivor
Horton
Dreamtech
PressCore Java
2-Vol II Cornell,
HorstmannJava 6
Programming
BlackBook-
Dreamtech
PressAn
Integrated
approach
tosoftware
EngineeringPank
aj Jalote
NarosaPublicatio
nsIntroduction to
Database Bipin
C. Desai
GalgotiaPublicat
ionsRelational
Database System
C.J. Date
Addison
W
esleyDatabase
ManagementSyst
emMajumdar
& Bhattacharya
Documents Similar To Mini Project Patholab

Mcs 044 Mini Projects Synopsis