Beruflich Dokumente
Kultur Dokumente
“DIGITAL AUCTION”
(MCS)
SESSION (2017-2019)
SUPERVISED BY:
Mr. Muhammad Shafique
SUBMITTED BY:
1
DECLARATION
It is declared that this is an original piece of my own work, except where otherwise
acknowledged in text and references. This work has not been submitted in any form
for another degree or diploma at any university or other institution for tertiary
education and shall not be submitted by me in future for obtaining any degree from
this or any other University or Institution.
Name: M. Arslan
Reg.No. 17-Arid-6063
July 2019
2
CERTI FI C AT E OF APP RO VAL
It is certified that the project titled “ONLINE DIAGNOSTIC LAB REPORTING
SYSTEM” carried out by M. Touseef Ahmed, Reg. No. 17-Arid-6065, M. Arslan,
Reg. No. 17-Arid-6063, Talha Ali, Reg. No. 17-Arid-6070, Amir Sohail, Reg. No.
17-Arid-6054 under the supervision of Mr Muhammad Shafique, ARID University
Barani Institute of Sciences, Sahiwal, is fully adequate, in scope and in quality, as a
final year project for the degree of Master in Information Technology
Supervisor: -------------------------
Mr. Shafiq-ur-Rehman
Lecturer
Dept. of CS
ARID University, Barani Institute of Science Sahiwal
HOD/Dean ------------------------
Prof. Dr. Khalid Husain Usmani
Dean
Dept. of CS
ARID University, Barani Institute of Science Sahiwal
3
ACKNOWLEDGMENT
It has been great pleasure for us to develop a Web Application for Online Lab
Reporting System. We have gathered enough knowledge and experience during this
project. Most importantly we would like to thank our honorable teacher and
supervisor, and also our Dean. Mr. Muhammad Khalid Hussain Usmani, Dept. of
Computer Sciences at Barani Institute Sahiwal who guided us to proper analysis of
the system and helped to develop an elegant and efficient system. It was a great
pleasure to study and work with many gifted people who influenced us in many ways.
First, we would like to thank our project supervisor Mr. Muhammad Shafiq. He
encouraged us to seek out the clearest and deepest description of theoretical ideas as
well as experimental findings. We are very grateful to him for his continuous support,
advice and guidance. Finally, we would like to convey our special thanks to our
parents and friends whom have always given us tremendous Support. Without their
love and encouragement, we would not had achieved this far.
4
ABSTRACT
This project, An Online Lab Reporting System has two parts- Patient interface and
Admin interface. Patient Panel permits a Patient to book an Appointment and Checks
the Reports Online and also download their reports and maintain record, the Patient
Update Profile. There is an admin panel by which an admin can control the whole Lab
reporting system. Admin can Manage the tests, (add test, delete test) Manage Users
(Delete Users, View Users) Manage Reports (Add reports, Remove Reports) Admin
Can update their Profile. Admin Can check the appointments history and Approve the
appointment.
Application that brings up various diagnoses working online. Here patient get an
option to register on the site and login using registered details… The system allows
patients to do the booking for various tests like CBC, Blood Glucose, KFT, and LFT.
Patient have all the facilities provided in our system which he or she have to get in the
lab by going their but we are saving the time of the patient to get appointment and
show their reports from home after approval of the appointment the admin or
authorized person of that lab will inform the user about the appointment which will be
set in the patient appointment panel and this services provide lot of time and best use
of the information technology for the patients who required in the present era.
5
1 Table of Contents
DECLARATION……………………………………………….………iii
ACKNOWLDGEMENT………………………………………………..v
ABSTRACT…………………………………...……………………….vi
TABLE OF CONTENT………………………………………………..vii
LIST OF TABLE…………………………………………………….....ix
LIST OF FIGURES…………………………………………….……….x
LIST OF ACRONYMS…………………………………………………………….. xi
Chapter 1:.............................................................................................................................1
1.1 Overview:................................................................................................................1
1.2 Statement of the problem:...............................................................................1
1.3 Purpose of the Project:.....................................................................................2
1.4 Application of the project:...............................................................................2
1.5 Theoretical Bases and organization:................................................................2
1.6 Summary:........................................................................................................3
Chapter 2:.............................................................................................................................4
2.1 Related Technologies:......................................................................................4
2.1.1 Web Based Technologies:........................................................................4
2.1.2 Embedded Technology:............................................................................4
2.1.3 Mobile Technology:.................................................................................5
2.2 Related Projects:..............................................................................................5
2.2.1 Chughtai Lab:...........................................................................................5
2.2.2 Shaukat Khanum Lab:..............................................................................6
2.3 Related Studies:...............................................................................................6
2.4 Their Limitations and Bottlenecks :................................................................6
2.5 Summary:........................................................................................................7
Chapter 3:.............................................................................................................................8
3.1 Hardware used with technical specifications..................................................8
3.2 Software(s), simulation tool(s) used................................................................8
3.2.1 HTML5:...................................................................................................8
3.2.2 Bootstrap:.................................................................................................9
6
3.2.3 jQuery:....................................................................................................11
3.2.4 PHP:.......................................................................................................12
3.2.5 Adobe Dream Viewer CC2018:.............................................................12
3.3 Summary:......................................................................................................13
Chapter 4:...........................................................................................................................14
4.1 Design of the methodology:..........................................................................18
4.1.1 Use Case Diagram:.................................................................................18
4.1.2 Sequence Diagram:................................................................................27
4.2 Analysis Procedure:.......................................................................................31
4.3 Implementation procedure.............................................................................31
4.3.1 Detail About Software:...........................................................................31
4.4 Verification of functionalities........................................................................42
4.5 Summary:......................................................................................................43
Chapter 5:...........................................................................................................................44
5.1 Objective testing............................................................................................44
5.2 Usability Testing............................................................................................44
5.3 Software Performance Testing.......................................................................44
5.4 Compatibility Testing....................................................................................44
5.5 Load Testing..................................................................................................45
5.6 Security Testing.............................................................................................45
5.7 Installation Testing........................................................................................45
5.8 Testing Plan...................................................................................................45
5.8.1 Unit Testing............................................................................................45
5.8.2 System Testing.......................................................................................45
5.8.3 Integration Testing..................................................................................46
5.8.4 User Acceptance Testing........................................................................46
5.8.5 Test Cases...............................................................................................46
5.9 Summary:......................................................................................................48
Chapter 6:.................................................................................................49
Chapter7:..................................................................................................50
7
LIST OF FIGURES
Figure 4.1: Water fall model...................................................................................................15
Figure 4.2 : Incremental Model...............................................................................................16
Figure 4.3 : Spiral Model........................................................................................................17
Figure 4.4 Agile Mode............................................................................................................17
Figure 4.5 : Adopted Methodology.........................................................................................18
Figure 4.6 : UseCase Login....................................................................................................19
Figure 4.7 : UseCase Registration...........................................................................................20
Figure 4.8 : UseCase Manage Members.................................................................................22
Figure 4.9 : Password Change................................................................................................23
Figure 4.10 : UseCase USer....................................................................................................24
Figure 4.11: UseCase Admin..................................................................................................25
Figure 4.12 : Sequence User...................................................................................................26
Figure 4.13 : Sequence Admin................................................................................................26
Figure 4.14 : ERD...................................................................................................................27
Figure 4.15 : Home Page........................................................................................................29
Figure 4.16 : Admin Login.....................................................................................................29
Figure 4.17 : Patient Registration...........................................................................................30
Figure 4.18 : Patient Login.....................................................................................................31
Figure 4.19 : Patient Report....................................................................................................31
Figure 4.20 : Contact Us.........................................................................................................32
Figure 4.21 : Check Report.....................................................................................................32
Figure 4.22 : User Dashboard.................................................................................................33
Figure 4.23 : Admin Dashboard..............................................................................................33
Figure 4.24 : User Login session............................................................................................34
Figure 4.25 : Admin Test Manage...........................................................................................34
8
LIST OF TABLES
Table 5.1(TC1).............................................................................................................47
Table 5.2(TC2).............................................................................................................47
Table 5.3(TC3).............................................................................................................47
Table 5.4(TC4 table)....................................................................................................48
9
LIST OF ACRONYMS
BIS Barani Institute of Sciences
SHW Sahiwal Campus
PHP Personal Home Page
CSS Cascading Style Sheet
OLRS Online Lab Reporting System
10
Chapter 1
INTRODUCTION
This project, An Online Lab Reporting System has two parts- Patient interface and
Admin interface. Patient Panel permits a Patient to book an Appointment and Checks
the Reports Online and also download their reports and maintain record, the Patient
Update Profile. There is an admin panel by which an admin can control the whole Lab
reporting system. Admin can Manage the tests, (add test, delete test) Manage Users
(Delete Users, View Users) Manage Reports (Add reports, Remove Reports) Admin
Can update their Profile. Admin Can check the appointments history and Approve the
appointment. The user can interact with the admin by sending the detail of the
appointment, but the admin has the authority to give them appointment according to
that.
1.1 Overview:
Admin can login through the admin login portal. Patient can be login after signing up
through the sign-up page, but the email can’t be replaceable. Patient can check the
reports that can be generated by the admin. User can add the appointment Id that can
be helpful for the searching of the reports. User can do contact with the admin or with
the organization by using the contact us form.
1
1.3 Purpose of the Project:
The main goal of the Online reporting system is that the Patient will be enabled to
watch all the reports online and get appointment online without any wasting time. The
Patient download or see the reports online and check the monthly progress of their
tests. We are giving the solution of the project in purpose that the project user be user
friendly and user can easily upload their reports on it. The main purpose of the project
is to save time by the patient by getting appointment on the portal and decrease the
rush from the laboratory who are in the lab for getting appointment the rush can be
decreased by getting appointment in the web portal. Online Reporting System will be
a web-based application which main language of programming will be PHP. Its main
aim is to simplify and improve the efficiency of the Laboratory test reporting.
To enable the Patient to have a visual confirmation that the appointment was
accept or Not.
2
1.6 Summary:
The main theme is to save time of the people in the today era and giving a efficient
system for the user so that every person can get online appointment and save the fuel
and time and the reports will be generated online. This system will exist to serve
patients, because we care about your health. Everything important for our health you
can find out here. Quickly find out your lab tests information, lab test prices, reporting
time and the sample required. You can check your lab test reports online & access
your reports from anywhere. Simply enter your invoice number and email.
3
2 Chapter 2
LITERATURE REVIEW
The literature review of the project is that.
4
2.1.3 Mobile Technology:
Chughtai Lab is one of the leading pathology labs in Pakistan. The lab was founded
by Dr A S Chughtai in 1983 as ‘Lahore Lab.’ Over a period of 33 years, the lab has
grown to a nationwide network of 7 testing locations and more than 160 collection
centers. The lab has a nationwide network with presence in more than 50 cities.
Chughtai Lab has always focused on quality in order to earn the trust of patients and
doctors. The lab uses only the latest automated and integrated instruments from
manufactures of international repute. The lab is staffed by 20 pathologists and more
than 70 BSc/MSc/MPhil lab technologists. Chughtai Lab is ISO 15189 certified, and
also participates in the College of American Pathologists external Quality Assurance
program.
5
The Chughtai Lab team has a mission to deliver accurate results, on time. More than
70% of medical decisions are based on lab tests, and that is why it is important for lab
results to be accurate and timely. The lab operates 24 hours a day, every day of the
year. The lab uses fully automated instruments on a ‘test as your go’ principle, without
any requirement for batch testing. This enables the lab to report test results quickly
without ever compromising on quality. It is because of this reputation of
uncompromising quality and quick reporting time that Chughtai Lab is the reference
lab of choice for more than 50 different hospitals and labs.
Shaukat Khanum Memorial Cancer Hospital and Research Centre has an extended
nationwide network of laboratory collection centers running under strict guidelines
and standard operating procedures to ensure provision of quality testing services to
people all over Pakistan. An advanced patient data management system is available
where test results are saved within the Hospital’s Information System, an in-house
built software system, and can be easily accessed online.
6
appropriate clinical setting. Currently used biopsy techniques (punch and incisional
wedge) are high-risk procedures with a combined diagnostic yield as low as 18%. The
need for an alternative diagnostic approach is clear, with a minimally invasive
technique capable of selectively obtaining representative tissue being ideal. Recent
experience leads us to recommend the use of an image-guided core-needle biopsy in
the diagnostic evaluation of cutaneous calciphylaxis.
7
2.5 Summary:
In literature review we can to know about the related technologies which we can used
and developed our system and the system component which we need to develop our
total system. The main thing is to get idea that can be get from the related project
which we have done or already exist in Pakistan there are two main projects which are
working on it that I have defined on it .There are lot of limitation to do that thing is to
tell people that our product is in so that why they can trust on our project that can be
awareness through our regular clients.
8
3 Chapter 3
3.2.1 HTML5:
Web languages need regular upgrades in order to stay current and solve new problems
faced by web developers. HTML5 is the latest version of HTML
We do not need to write JavaScript code to validate that is given input in Valid Email
or not.
This Tag allow a web developer to add videos in his web page through HTML5
instead of JavaScript.
TML5 is the latest evolution of the standard that defines HTML. The term represents
two different concepts. It is a new version of the language HTML, with new elements,
attributes, and behaviors, and a larger set of technologies that allows the building of
9
more diverse and powerful Web sites and applications. This set is sometimes called
HTML5 & friends and often shortened to just HTML5.
Designed to be usable by all Open Web developers, this reference page links to
numerous resources about HTML5 technologies, classified into several groups based
on their function.
Semantics: allowing you to describe more precisely what your content is.
Offline and storage: allowing webpages to store data on the client-side locally
and operate offline more efficiently.
Multimedia: making video and audio first-class citizens in the Open Web.
Device access: allowing for the usage of various input and output devices.
3.2.1.3 CSS3:
CSS3 describes how HTML elements are to be displayed on screen, paper, or in other
media CSS3 saves a lot of work. It can control the layout of multiple web pages all at
once External stylesheets are stored in CSS3 files.
CSS is used to define styles for our web pages, including the design, layout and
variations in display for different devices and screen sizes. When tags like <font>, and
color attributes were added to the HTML 3.2 specification, it started a nightmare for
web developers. Development of large websites, where fonts and color information
were added to every single page, became a long and expensive process. To solve this
problem, the World Wide Web Consortium (W3C) created CSS. CSS removed the
style formatting from the HTML page!
10
3.2.2 Bootstrap:
Bootstrap is the most popular HTML, CSS, and JavaScript framework for developing
responsive, mobile-first websites. Bootstrap 4 is the newest version of Bootstrap; with
new components, faster stylesheet and more responsiveness. Bootstrap 4 supports the
latest, stable releases of all major browsers and platforms. Bootstrap has a lot of
features. These features not only make it stand out, but they also make it more popular
even among those web designers who like to take things in a very conventional way.
It is pretty easy, to begin with. Being easy to get started with is probably the first
quality which makes Bootstrap very appealing.
Bootstrap not only offers Less files but also includes the old CSS files.
Despite the fact that Bootstrap is designed in responsive 12-column grids, layouts, and
components, it is also very easy to customize. Whether we need a fixed grid or a
responsive one, it can be made possible by making a few changes. Offsetting and
nesting of columns are also easy to do in both CPU-based and mobile-based browser
grids.
Drop-downs
Button
Navigation
11
Badges Alerts
Progress Bar
The readily available templates make it easier for inexperienced users to create a
website following a simple tutorial or demo available on the Bootstrap.
3.2.3 jQuery:
jQuery is a lightweight, "write less, do more", and JavaScript library. The purpose of
jQuery is to make it much easier to use JavaScript on our website.
jQuery takes a lot of common tasks that require many lines of JavaScript code to
accomplish and wraps them into methods that you can call with a single line of code.
jQuery also simplifies a lot of the complicated things from JavaScript, like AJAX
calls.
jQuery is a fast, small, and feature-rich JavaScript library. It makes things like HTML
document traversal and manipulation, event handling, animation, and Ajax much
simpler with an easy-to-use API that works across a multitude of browsers. With a
combination of versatility and extensibility, jQuery has changed the way that millions
of people write JavaScript.
HTML
CSS manipulation
AJAX
12
Utilities.
3.2.4 PHP:
PHP is a server scripting language, and a powerful tool for making dynamic and
interactive Web pages. PHP is a widely used, free, and efficient alternative to
competitors such as Microsoft's ASP.Net PHP files can contain text, HTML, CSS,
JavaScript, and PHP code PHP code are executed on the server, and the result is
returned to the browser as plain HTML PHP files have extension.
PHP can create, open, read, write, delete, and close files on the server
With PHP you are not limited to output HTML. You can output images, PDF files,
and even Flash movies. You can also output any text, such as XHTML and XML.
PHP is compatible with almost all servers used today (Apache, IIS, etc.)
13
3.2.5 Adobe Dream Viewer CC2018:
Adobe Dreamweaver CC is a web design and development application that uses both
a visual design surface known as Live View and a code editor with standard features
such as syntax highlighting, code completion, and code collapsing as well as more
advanced features such as real-time syntax checking and code introspection for
generating code hints to assist the user in writing code. Combined with an array of site
management tools, Dreamweaver allows for its user’s design, code and manage
websites, as well as mobile content. Dreamweaver is an Integrated Development
Environment (IDE) tool. You can live preview of changes for the frontend.
Dreamweaver is positioned as a versatile web design and development tool that
enables visualization of web content while coding.
3.3 Summary:
We have used php as server language in our project and Xamp help us to run our
website on the local server and connect database through it and the apache play as a
role of local server .There are different tools that can be used for developing so we
used sublime text or dream viewer.
14
4 Chapter 4
METHODOLOGIES
In this chapter, we will discuss that what are the existing methodologies and which
one we have chosen for implementation of this project in an effective way, also we
will discuss advantages of adopted methodology.
There are several existing methodologies that can be used to develop this application
using software development processes.
2.Waterfall Model
In the software development process, the very first model that is published from other
engineering processes that is cascaded from one phase to another is known as
Waterfall model. This model is also known as linear sequential model. In the waterfall
model, firstly all the requirements gathered. After gathering all the requirements and
analysis of all the requirements further move to next phase that is making the design
of a project and then implementation, testing and maintenance phases.
As all the next phases of this model is dependent on previous phase. All the phases
worked as a waterfall after one another. It is a documentation driven model. In this
model, feedback of the client is received at the end of the project and when the
product is delivered to the user. Hence, mistake in the product requirement
specification is discovered after delivered to the user. This is Time and cost
consuming methodology, that is why we have not used this methodology in
developing this project.
15
3.Incremental Model
4.Spiral Model
Spiral Model is developed by Barry Boehm. The main idea of this model is to avert
risk, as there is always an element of risk in development of software. For example,
key personnel may resign at a critical juncture, the manufacturer of the software
development may go bankrupt, etc. In its simplified form, the Spiral Model is
Waterfall model plus risk analysis. In this case each stage is preceded by identification
of alternatives and risk analysis and is then followed by evaluation and planning for
the next phase .If risks cannot be resolved, project is immediately terminated. This is
depicted in the following diagram.
16
Figure 4.3 : Spiral Model
5.Agile Model
Agile model is useful when there is no hope for changings in product after
deployment. It is an approach to project management that is utilized in software
development. This method assists teams in responding to the unpredictability of
constructing software. It uses incremental, iterative work sequences that are
commonly known as sprints. The ability to create and respond to change to succeed in
an uncertain and turbulent environment.
17
Adopted Methodology
Incremental model is used to develop this project, in which we divided our work in
multiple modules. All these modules are further divided into more easily managed
modules which made up the actual implementation of the requirements. Because we
will not use agile model and waterfall because waterfall model does not contain any
kind of changes in it.
18
4.1 Design of the methodology:
The design methodologies of this project are as follows.
An important part of the analysis phase is to be drawing the diagrams of Use cases.
They are used through the phase of analysis of a project to find and divide
functionality of the application. Application is separated into actors and use cases.
Actors play the role that are played by the application users. Use cases define the
application behavior when one of the actors sends any particular motivation. This type
of behavior can be described by text. It describes the motivation nature that activates
use case, the inputs and outputs to some other actors and the behavior of conversion
of inputs to the outputs. Usually the use case describes everything that can go wrong
during the detailed behavior and what will be helpful action taken by the application.
Actor: User
Pre-Condition:
1. For the member, he/she must have registered already in application by the admin.
2. User must enter correct Email address and password for login.
19
Post-Condition:
Basic Path:
2. The application verifies the correct format and valid email address and
Password.
3. If provided inputs are correct, the application displays the all other user’s
content of the application and session of particular user started.
Constraints:
Non-Functional Requirements:
2. Better performance
3. Availability
4. Robustness
Actor: Admin
20
Pre-Condition:
1. UC1
Post-Condition:
Basic Path:
Alternative Path:
Non-Functional Requirements:
1. Better response
2. Robustness
3. Reliable
21
4.1.1.3 UC3: Manage Members
Actor: Admin
Pre-Condition:
Post-Condition:
Basic Path:
2. The admin views the members’ detail and then select a particular member to
perform these activities.
22
6. Admin clicks on delete button for deleting that member or press BACK TO
DETAILS page for cancel the deleting process.
Non-Functional Requirements:
1. Better response
2. Easy to use
3. Secure
4. Availability
Actor: User
Pre-Condition:
1. UC1
Post-Condition:
23
2. User can view new password in a text field.
Basic Path:
CONSTRAINTS:
NON-FUNCTIONAL REQUIREMENTS:
2. Efficient
3. Availability
4. Secure
Whenever a small or large project has started to develop, first thing all of
programmers required is methodology. Methodology is a way of developing a project,
in which all of the programmers gather the user’s requirements, design the project,
implement it, and after all this testing and maintenance of the project, in a satisfaction
of user and according to the project requirements.
24
4.1.1.6 User Use Case:
25
4.1.2.1 Sequence for user:
26
4.1.2.3 Entity Relationship Diagram:
Each user type admin or user needs to register him or her as a user or an
admin for accessing the user’s necessary information. They also have email,
27
username and password. They can login into the system from the web using
their email and password.
Admin needs to login to the system to operate the system. Admin has an
individual or unique login email, password and a user level. Through this
email and password admin can login into the system.
Admin can update all the tests. An admin can insert a new Tests with details
and can update the test Reports information through edit option.
Admin can update all the tests. An admin can insert a new Tests with details
and can update the test Reports information through edit option.
This software describes about the online laboratory system in the given screens:
28
4.3.1.1 Home:
This page describes about the admin how admin log in himself and check the
complaints of the patients.
29
4.3.1.3 Registration:
This page describes about the registration of the patients. Patients can register them
self in this page and give details about him.
30
4.3.1.4 Patient Login:
31
4.3.1.6 Contact Us:
This page describe the detail of the laboratory i.e. contact number email address etc.
32
4.3.1.8 Patient Dashboard:
This page describes the patient dashboard.
33
4.3.1.10 User Session:
This page describe the user session i.e. admin can check about the appointments.
34
4.4 Verification of functionalities
The verification of functionalities is that:
View All the users and their login information and also delete the users.
4.5 Summary:
The system used by the user can be clearly defined by the use case diagram and the
system have the best sequence relationship with by showing in sequence diagram and
the database relationship among SQL database show the relationship of entities
among them.
35
5 Chapter 5
SYSTEM TESTING
Testing of the software ensures that either the required functionality is developed or
not? Testing has been completed in different phases at completion of every unit before
launching the next phase. Therefore, all of the functionality of the system is tested so
there is no chance of errors remaining in the system.
Our system is compatible for all user like windows, IOS and the Linux that have any
other environment the system will be work perfectly.
36
5.5 Load Testing
Load testing is carried out to know the behavior of the system under the specific
expected load. Example: The software is tested in load of 20 users accessing resources
at the same time; the system response time was good.
The software units in an application are modules and routines that are assembled and
integrated to perform a specific function. Unit testing focuses first on modules,
independently of one another, to locate errors. This enables, to detect errors in coding
and logic that are contained within each module. This testing includes entering data
and ascertaining if the value matches to the type and size supported by C#. The
various controls are tested to ensure that each performs its action as required.
To test the complete application, system testing has been used. It is beneficial to check
whether the application meets its requirements and fulfill Quality Standards.
37
5.8.3 Integration Testing
Integration testing allows the software developers to integrate all the components/
units of the application within a program and then test them in a group. Basically, this
testing level is used to catch the defects in the user interface between the functions/
modules. It is useful to determine how logically and efficiently all the units/
components are running together. Here the streaming module and encoding module
options are integrated and tested. This testing provides the assurance that the
application is well integrated functional unit with smooth transition of data.
User acceptance of an application is the key factor for the success of any application.
The application under consideration is tested for user acceptance by constantly
keeping in touch with the application users at time of developing and making changes
whenever required.
User acceptance testing (UAT) is the last phase of the software testing process. During
UAT, actual software users test the software to make sure it can handle required tasks
in real-world scenarios, according to specifications. UAT is one of the final and
critical software project procedures that must occur before newly developed software
is rolled out to the market.
Test Case No 1
38
Test ID: TC1
Test Case No 4
39
Test Description: Admin Dashboard
5.9 Summary:
Test has been performed and result are also given in the section and the result are
positive for our system by doing testing on the system and also by making the test
cases on the system.
40
Chapter 6
6.2 Summary
The results we concluded from the testing is that our website has been passed by
alpha testing and it can be launched for the user in the beta testing so that it can be
launched as a product to serve humanity to save their time and money.
6.3 Conclusion
41
6 Chapter7
REFERENCES
[1]. Solomon, D., Davey, D., Kurman, R., Moriarty, A., O'Connor, D., Prey, M., ... &
Young, N. (2002). The 2001 Bethesda System: terminology for reporting results of
cervical cytology. Jama, 287(16), 2114-2119.
[2]. McKhann, G., Drachman, D., Folstein, M., Katzman, R., Price, D., & Stadlan, E.
M. (1984). Clinical diagnosis of Alzheimer's disease: Report of the NINCDS‐ADRDA
Work Group* under the auspices of Department of Health and Human Services Task
Force on Alzheimer's Disease. Neurology, 34(7), 939-939.
[3]. Mohanty, S. K., Piccoli, A. L., Devine, L. J., Patel, A. A., William, G. C., Winters,
S. B., ... & Parwani, A. V. (2007). Synoptic tool for reporting of hematological and
lymphoid neoplasms based on World Health Organization classification and College
of American Pathologists checklist. Bmc Cancer, 7(1), 144.
[4]. Díaz-Rosario, L. A., & Kabawat, S. E. (1999). Performance of a fluid-based, thin-
layer Papanicolaou smear method in the clinical setting of an independent laboratory
and an outpatient screening population in New England. Archives of Pathology and
Laboratory Medicine, 123(9), 817-821.
[5]. Kocjan, G., Cochand‐Priollet, B., De Agustin, P. P., Bourgain, C., Chandra, A.,
Daneshbod, Y., ... & Fassina, A. (2010). Diagnostic terminology for reporting thyroid
fine needle aspiration cytology: European Federation of Cytology Societies thyroid
working party symposium, Lisbon 2009. Cytopathology, 21(2), 86-92.
[6]. Dunn, E. J., & Moga, P. J. (2010). Patient misidentification in laboratory
medicine: a qualitative analysis of 227 root cause analysis reports in the Veterans
Health Administration. Archives of pathology & laboratory medicine, 134(2), 244-
255.
[7]. Stathonikos, N., Veta, M., Huisman, A., & van Diest, P. J. (2013). Going fully
digital: Perspective of a Dutch academic pathology lab. Journal of pathology
informatics, 4.
[8]. Luthra, R., Patel, K. P., Reddy, N. G., Haghshenas, V., Routbort, M. J., Harmon,
M. A., ... & Kantarjian, H. M. (2014). Next-generation sequencing-based multigene
mutational screening for acute myeloid leukemia using MiSeq: applicability for
diagnostics and disease monitoring. Haematologica, 99(3), 465-473.
[9]. Kang, H. P., Devine, L. J., Piccoli, A. L., Seethala, R. R., Amin, W., & Parwani,
A. V. (2009). Usefulness of a synoptic data tool for reporting of head and neck
neoplasms based on the College of American Pathologists cancer
checklists. American journal of clinical pathology, 132(4), 521-530.
[10]. Cohen, I., Chase, J. S., Goldszmidt, M., Kelly, T., & Symons, J. (2004,
December). Correlating Instrumentation Data to System States: A Building Block for
Automated Diagnosis and Control. In OSDI (Vol. 4, pp. 16-16).
42
43