PIR MEHAR ALI SHAH

ARID AGRICULTURE UNIVERSITY

RAWALPINDI

“DIGITAL AUCTION”

(MCS)

SESSION (2017-2019)

SUPERVISED BY:
Mr. Muhammad Shafique

SUBMITTED BY:

MUHAMMAD TOUSEEF AHMAD (17-ARID-6065)

MUHAMMAD ARSLAN (17-ARID-6063)
AMIR SOHAIL (17-ARID-6054)
TALHA ALI (17-ARID-6070)

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. Touseef Ahmed

Reg.No. 17-Arid-6065

Name: M. Arslan
Reg.No. 17-Arid-6063

Name: Talha Ali

Reg.No. 17-Arid-6070

Name: Amir Sohail

Reg.No. 17-Arid-6054

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

Internal Examiner 1: ------------------------

Mrs. Hina Umbreen
Lecturer
Dept. of CS
ARID University, Barani Institute of Science Sahiwal

Internal Examiner 2: -------------------------

Miss Mehwish Malik
Lecturer
Dept. of CS
ARID University, Barani Institute of Science Sahiwal

Project Coordinator: -------------------------

Mr. Imran Shahzad
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.2 Statement of the problem:

The main problem is to save time by the patient or the organization in which they are
going to have appointment. The lab person who is acting as admin should have to
manage all the report and appointment through the admin panel and the patient have
to get appointment through the patient portal by giving the report that has been taken
by the doctor so that can be verified by the laboratory so that the assignment can be
checked. The user time of login and logout should be mentioned so that the admin
came to know at which time most of the user get active on the patient portal so that he
can be available for them for get more and more user.

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.

1.4 Application of the project:

 To increase efficiency and services to the patient through better application of
technology in daily works.

 For increasing the efficiency of the system, we used object-oriented programming

method.

 To enable the Patient to have a visual confirmation that the appointment was
accept or Not.

 To enable the patient to check the reports.

 To enable the patient to use easily due to batter Interface.

1.5 Theoretical Bases and organization:

We have described the system in the different section in this section we have provided
the detail what we are going to do and how we tackle the problem of today era and
coming sections will elaborate about the mechanism and the flow about which our
project will be go through. The system will be elaborated with design of the system
like UML diagrams. Testing will be performed in the next section that how the system
passed the test by giving the test cases. Methodologies are defined in the next section.

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.

2.1 Related Technologies:

There are different technologies which are related to do our work completed.

2.1.1 Web Based Technologies:

A web-based application is any program that is accessed over a network connection

using HTTP, rather than existing within a device’s memory. Web-based applications
often run inside a web browser. However, web-based applications also may be client-
based, where a small part of the program is downloaded to a user’s desktop, but
processing is done over the internet on an external server. Web-based applications are
also known as web Apps. Web-based applications actually encompass all the
applications that communicate with the user via HTTP. This includes light
applications like Flash games, online calculators, calendars and so on, as well as more
intensive applications such as web-based word processors and spreadsheet
applications.

2.1.2 Embedded Technology:

An embedded system is some combination of computer hardware and software, either

fixed in capability or programmable, that is designed for a specific function or for
specific functions within a larger system. Industrial machines, agricultural and process
industry devices, automobiles, medical equipment, cameras, household appliances,
airplanes, vending machines and toys as well as mobile devices are all possible
locations for an embedded system. Embedded systems are computing systems, but
can range from having no user interface (UI) -- for example, on devices in which the
embedded system is designed to perform a single task -- to complex graphical user
interfaces (GUI), such as in mobile devices. User interfaces can include buttons,
LEDs, touchscreen sensing and more. Some systems use remote user interfaces as
well.

4
2.1.3 Mobile Technology:

Mobile technology is a form of technology that is mostly used in cellular

communication and other related aspects. It uses a form of platform whereby many
transmitters have the ability to send data at the same time on a single channel. This
platform is called Code-division multiple access (CDMA). This platform allows many
users to make use of single frequencies because it restricts the likelihood of
interference of frequencies from two or more sources. This channel has evolved over
the years. The mobile technology is rapidly evolving; over the years, its uses are
becoming diverse and is gradually replacing some similar sources in the market that
are also used for communication e.g. post office and land lines. The mobile
technology has improved from a simple device used for phone call and messaging
into a multi-tasking device used for GPS navigation, internet browsing, gaming,
instant messaging tool etc. Professionals argue with the trend that the future of
computer technology is rest on wireless networking and mobile computing. Mobile
technology through tablet and portable computers are becoming more and more
popular

2.2 Related Projects:

There are different projects which are related to our product:

2.2.1 Chughtai Lab:

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.

2.2.2 Shaukat Khanum Lab:

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.

2.3 Related Studies:

The main thing that other are doing in our field of work related to this project is
communication gap that should be less the response should be the best because when
we were planning to do this project the main thing which we were doing is to check
that everything which we need from the user so that he/she can just upload all his/her
requirement and we will get that and give the appointment regarding to that request.

Historically, genetic evaluation has been dominated by a clinician-centric traditional

model in which a patient’s physician had the central responsibility for testing, such as
ordering the test and communicating the results. Conversely, in the direct-to-consumer
(DTC) model, consumers are more empowered because they can order their own tests,
obtain samples using home test kits, and receive the results directly from the
laboratory or company that provides the test. The DTC market has expanded
substantially, reigniting controversies over the potential implications of DTC testing
for genetic health risks.

Dermatologists are frequently consulted to assist in the diagnosis of calciphylaxis,

which requires the identification of representative histopathologic features in the

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.

Clinicians estimate kidney function to guide important medical decisions across a

wide range of settings, including assessing the safety of radiology studies, choosing
chemotherapy, and reviewing the use of common nonprescription medications such as
nonsteroidal anti-inflammatory drugs. Because direct measurement of kidney function
is infeasible at the bedside, the usual approach involves using estimating equations
that rely on serum creatinine. These equations assign a higher estimated glomerular
filtration rate (eGFR) to patients who are identified as black. Yet in some medical and
social science disciplines, a consensus has emerged that race is a social construct
rather than a biological one.1 In this Viewpoint, we argue that the use of kidney
function estimating equations that include race as a variable cause problems for
transparency and unduly restrict access to care in some cases, yet offer only modest
benefits to precision.

2.4 Their Limitations and Bottlenecks:

There are some limitations are too aware customer about online lab appointment that
they can get that facility by informing them that is not possible by now. How to
engage the customer to come to us for their regular test check up and get their reports
on time and after the report has been generated, he/she should have received a
message that they can check online about their test.

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

TOOLS AND TECHNIQUES

The tools and techniques of this project are as follows.

3.1 Hardware used with technical specifications

 PC, Mac, Android device

 High Speed Internet Connection

3.2 Software Simulation Tools:

The “Adobe Dream viewer CC 2018” and “WAMP Server” are the software that are
used in the backend for overall developing this project. Reason behind using latest
versions is that; they support latest technologies and libraries for developing this
project. For Graphical user interface, Bootstrap framework v.4.0, HTML5, CSS3,
JavaScript, JQuery and for backend implementation, PHP, MySQL, AJAX, JSON and
frameworks have been used. Rather than writing numerous lines of code, in Notepad+
+ 2017. Each object has its own properties, determining its positions, sizes, colors,
nature of its text and much more.

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

3.2.1.1 Email validation:

We do not need to write JavaScript code to validate that is given input in Valid Email
or not.

3.2.1.2 Video Tag:

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.

 Connectivity: allowing you to communicate with the server in new and

innovative ways.

 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.

 2D/3D graphics and effects: allowing a much more diverse range of

presentation options.

 Performance and integration: providing greater speed optimization and better

usage of computer hardware.

 Device access: allowing for the usage of various input and output devices.

 Styling: letting authors write more sophisticated themes.

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.

3.2.2.1 Easy to Begin:

It is pretty easy, to begin with. Being easy to get started with is probably the first
quality which makes Bootstrap very appealing.

3.2.2.2 Less as Well as CSS Files

Bootstrap not only offers Less files but also includes the old CSS files.

3.2.2.3 Easily Customizable

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.

3.2.2.4 Responsive Utility Classes

Another prominent feature of Bootstrap is its responsive utility classes. Using

responsive utility classes, a particular piece of content can be made to appear or hide
only on devices depending on the size of the screen being used. This feature is
extremely helpful for designers who want to make a mobile and tablet-friendly
version of their websites.

3.2.2.5 Components of Bootstrap

Some of the components that come pre-styled in Bootstrap are:

 Drop-downs

 Button

 Navigation

11
  Badges Alerts

 Progress Bar

3.2.2.6 Drop-Down Component Menu

The drop-down component menu is a responsive additive feature of a website. To

include it in a website, a lot of different plugins, mostly Java-based, are tested. But,
via Bootstrap and its easy customizing options, this can easily be done in a matter of
minutes.

3.2.2.7 Bootstrap Templates

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.

The jQuery library contains the following features:

 HTML

 CSS manipulation

 HTML event methods

 Effects and animations

 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.

3.2.4.1 What Can PHP Do:

PHP can do the following process.

 PHP can generate dynamic page content

 PHP can create, open, read, write, delete, and close files on the server

 PHP can collect form data

 PHP can send and receive cookies

 PHP can add, delete, modify data in your database

 PHP can be used to control user-access

 PHP can encrypt data.

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.

3.2.4.2 Why PHP:

PHP can use for the following process.

 PHP runs on various platforms (Windows, Linux, Unix, Mac OS X, etc.)

 PHP is compatible with almost all servers used today (Apache, IIS, etc.)

 PHP supports a wide range of databases

 PHP is free. Download it from the official PHP resource: www.php.net

 PHP is easy to learn and runs efficiently on the server side

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.

1.Proposed Application Architecture

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.

The waterfall model is further described in the following diagram:

Figure 4.1: Water fall model

15
3.Incremental Model

To overcome the drawbacks of the waterfall model, incremental model is used. In

incremental model, the product is developed in increments and partitioned into
smaller pieces. These smaller pieces, then built and delivered to client in increments.
Quick response from clients. Each module is smaller than compare to whole module.

Figure 4.2 : 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.

Figure 4.4 : Agile Mode

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.

Reason behind using this model is:

 It is easy to test and debug the product during iterations.

 Software released in increments over time is more likely to satisfy changing

user requirements than if it were planned as a single overall release at the end
of the same period.

Figure 4.5 : Adopted Methodology

18
4.1 Design of the methodology:
The design methodologies of this project are as follows.

4.1.1 Use Case Diagram:

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.

Some of the use cases are as follows:

4.1.1.1 UC1: Login

This figure shows the user login.

Actor: User

Figure 4.6 : UseCase Login

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:

User can access to application’s main features.

Basic Path:

1. Enter Email-Address and password for login.

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:

1. If provided email address and password are incorrect or invalid, application

redirect to main page.

Non-Functional Requirements:

1. Short Response Time

2. Better performance

3. Availability

4. Robustness

4.1.1.2 UC2: Register Member

This figure shows the registration of the members.

Actor: Admin

Figure 4.7 : UseCase Registration

20
Pre-Condition:

1. UC1

2. The admin must provide complete mandatory details of a member.

Post-Condition:

1. User Account should be created successfully.

2. Member particular folder is created in project directory.

Basic Path:

1. The admin should be logged in to the application to perform this activity.

2. The admin enters user information.

3. The admin clicks on Create Account button.

4. The application verifies the valid entered inputs.

5. After verifying provided information; the application will generate the

member account detail file.

Alternative Path:

1. On wrong entries of mandatory fields, the application displays particular

message for invalid entry or required fields.

Non-Functional Requirements:

1. Better response

2. Robustness

3. Reliable

21
4.1.1.3 UC3: Manage Members

This figure shows the managing of the users.

Actor: Admin

Figure 4.8 : UseCase Manage Members

Pre-Condition:

1. UC1 & UC2

2. The member’s detail is required.

Post-Condition:

1. The member information should be edited and deleted.

Basic Path:

1. The admin should be logged in to the application to perform this activity.

2. The admin views the members’ detail and then select a particular member to
perform these activities.

3. Update information of specific member by entering updated information and

click on update button.

4. The application verifies the valid entered inputs and updated.

5. For deleting information of specific member, applications display the message

of confirmation.

22
 6. Admin clicks on delete button for deleting that member or press BACK TO
DETAILS page for cancel the deleting process.

7. The application commits changes to the database.

Non-Functional Requirements:

1. Better response

2. Easy to use

3. Secure

4. Availability

5. Short response time.

4.1.1.4 UC4: Change Password

This figure shows the changing of the passwords.

Actor: User

Figure 4.9 : Password Change

Pre-Condition:

1. UC1

Post-Condition:

1. Password must be updated into the database.

23
 2. User can view new password in a text field.

Basic Path:

1. User select change password menu from sidebar menu list.

2. User enters new password to update old password.

3. The application verifies and updated into database.

4. Click on Logout to check whether the password has changed or not.

CONSTRAINTS:

1. User must enter valid inputs for password.

NON-FUNCTIONAL REQUIREMENTS:

1. Short response time.

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.

4.1.1.5 Admin Use Case:

This figure shows the admin use case diagram.

Figure 4.10 : UseCase User

24
4.1.1.6 User Use Case:

This figure shows the users use case diagram.

Figure 4.11: UseCase Admin

4.1.2 Sequence Diagram:

Sequence diagram uses concept of a Message-Sequence-Chart. It shows interactions

of objects in a sequence of time. It shows the classes and objects involved in the
scenario and the message sequence between the objects which is desired to carry out
the functionality of a given scenario. Sequence diagrams are usually related with the
understanding of use case in the logical View of the system which is under
development. “Sequence diagrams are sometimes called event diagrams, timing
diagrams, event scenarios”.

A parallel vertical line on sequence diagram is called lifeline. Different objects or

processes that live simultaneously, and, on horizontal arrows, the messages
exchanged, in the order in which processes occur. This allows some specification of
some simple runtime scenarios in a graphical pattern.

25
4.1.2.1 Sequence for user:

This shows the sequence working process.

Figure 4.12 : Sequence User

4.1.2.2 Sequence for admin:

This shows the working sequence of the admin.

Figure 4.13 : Sequence Admin

26
4.1.2.3 Entity Relationship Diagram:

This shows the E.R Diagram of the project.

Figure 4.14 : ERD

4.2 Analysis Procedure:

Development of web-based systems requires analysis of the process to be digitized in
order to enable a correct system, a system that functions as required and to assist the
potential users of the system understand the general functionality of the system. The
analysis specifies the system's objectives and constraints to which designers have to
comply. The purpose of doing analysis is to transform the system’s major inputs into
structured specification. This has mainly two requirement section- Admin section and
User section.

 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 delete user from user panel.

 Users can appointment for a test present in tests list.

 User Update their Password.

 User can see their Tests reports.

 Users can edit their profiles.

 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 delete user from user panel.

 Users can appointment for a test present in tests list.

 User Update their Password.

 User can see their Tests reports.

 Users can edit their profiles.

4.3 Implementation procedure:

In this procedure we discuss about the different work of the project.

4.3.1 Detail About Software:

This software describes about the online laboratory system in the given screens:

28
4.3.1.1 Home:

The home page describes the front-end of the project.

Figure 4.15 : Home Page

4.3.1.2 Admin Login :

This page describes about the admin how admin log in himself and check the
complaints of the patients.

Figure 4.16 : Admin Login

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.

Figure 4.17 : Patient Registration

30
4.3.1.4 Patient Login:

Patient can login in this page.

Figure 4.18 : Patient Login

4.3.1.5 Patient Report:

Patient can check his report in this.

Figure 4.19 : Patient Report

31
4.3.1.6 Contact Us:

This page describe the detail of the laboratory i.e. contact number email address etc.

Figure 4.20 : Contact Us

4.3.1.7 Profile Updation:

This page describe about the updating the profile.

Figure 4.21 : Check Report

32
4.3.1.8 Patient Dashboard:
This page describes the patient dashboard.

Figure 4.22 : User Dashboard

4.3.1.9 Admin Dashboard:

This page describes the admin dashboard.

Figure 4.23 : Admin Dashboard

33
4.3.1.10 User Session:
This page describe the user session i.e. admin can check about the appointments.

Figure 4.24 : User Login session

4.3.1.11 Admin Manage Test:

In this page admin can manage or updated the test and there rates too.

Figure 4.25 : Admin Test Manage

34
4.4 Verification of functionalities
The verification of functionalities is that:

 Register: user need to sign up first into the site

 User book an appointment.

 Update their account.

 Checks the appointment history.

 User can see their reports and download.

 Admin can check Appointment history.

 Update the status of the Appointment.

 View All the users and their login information and also delete the users.

 Admin can add the tests and delete the tests.

 Admin Update their Profile.

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.

5.1 Objective testing

While we were doing testing as an objective testing most of the goals are achieved
which we need to be covered in this system and the objective testing of the lab has
been covered by us in this system.

5.2 Usability Testing

Our system is easy to use and most understandable by most of the person who used it
as in the alpha testing phase and the system is ready to interact with all type of users
to use it by using the perfect user interface which we have provided in it.

5.3 Software Performance Testing

Our system performance is according to what we need because the report that have
been the most probably issue will be covered by high speed internet connection that
we have provided and test it and that has been generated the accurate result of the
upload the report and the get appointment.

5.4 Compatibility Testing

Compatibility testing is carried out to check the compatibility of the software on
different platform. Example: The software can run on any latest up to date browser
available on any OS e.g. Google Chrome, Safari etc.

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.

5.6 Security Testing

Security testing is carried out to disclose the weakness in the software.

5.7 Installation Testing

Installation testing is carried out to install the software like xampp and using the
sublime tool.

5.8 Testing Plan

A process of performing as application or program with the intention of finding errors
and whether the application is fulfilling user needs.

5.8.1 Unit Testing

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.

Commonly used method is White-Box Testing method. Every time a component of

the program is changed, it can be run for testing that is the biggest and famous benefit
of this testing phase. Issues that are arises during this phase, allowing to be resolved
as quickly as possible. Unit testing is familiar by software developers. It allows them
to test their application units before moving them to testers for formal testing.

5.8.2 System Testing

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.

5.8.4 User Acceptance Testing

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.

5.8.5 Test Cases

Test Case No 1

Software: Online Lab Reporting System

Test Description: Admin Login

Testing Environment: Alpha Testing

Software: Online Lab Reporting System

38
 Test ID: TC1

Table 5.1 :TC1

Preconditions Admin must be registered

Actions Admin will give username password

Expected Result Should be login

Test Case No 2

Test Description: Patient Login

Testing Environment: Alpha Testing

Test ID: TC2

Table 5.2 : TC2

Preconditions Patient must be signing in

Actions Patient will give username and password
Expected Results Patient should login
Result Login Success Full
Test Case No 0033

Software: Online Lab Reporting System

User will have to access the dashboard

Test ID:TC3
Actions User will check dashboard components
Table 5.3 : TC3
Expected Results All the component should have word properly
Result Working accurately

Test Description: User Dashboard testing

Testing Environment: Alpha Testing

Test Case No 4

Software: Online Lab Reporting System

39
 Test Description: Admin Dashboard

Testing Environment: Alpha Testing

Test ID: TC4

Table 5.4 : TC4 table

Preconditions Admin should have login

Actions Admin will check all the components of dashboard
Expected Results Component should work properly
Result Working properly

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

RESULT AND CONCLUSION

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.

6.1 Presentation of the findings

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.

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

In next our first preference is the ONLINE DIAGNOSTIC LAB REPORTING

SYSTEM is to develop the Android Application. The next thing which we intend to
embed this system to IOT (Internet of Things) as well as Cloud Computing
technology. Through this we can use this application over single network and may
resolve many validation restrictions and can improve the functionality i.e. security,
speed, no data loss and etc.

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