ABSTRACT

In the current digital era, personal data storage on public platforms is a major cause of
concern with severe security and privacy This is true especially in e-health data management
since patient's health data must be managed following a slew of established standards. The
Cloud Service Providers (CSPs) primarily provide computing and storage resources.
However, data security in the cloud is still a major concern. In several instances, Block chain
technology rescues the CSPs by providing the robust security to the underlying data by
encrypting data using the unique and secret keys. Each network user in Block chain has its
own unique and secret keys to protect the data. However, Block chain technology suffers in
high workload scenarios. To overcome e-healthcare records privacy issues in a third-party
cloud, we designed a Patient's Healthcare Records Management System (PRMS) that focuses.
A of PRMS is carried out on different third-party clouds to validate. The proposed PRMS is
compared to the Secure and Robust Healthcare-Based Block chain (SRHB) approach using a
database.

I
 TABLE OF CONTENTS

CHAPTER NO. CONTENT PAGE NOS

ABSTRACT I
LIST OF FIGURES IV
LIST OF SYMBOLS V – VI
LIST OF ABBREVITIONS VII

1. CHAPTER 1: INTRODUCTION (1-6)

1.1 GENERAL 1
1.2 OBJECTIVE 2
1.3 SCOPE OF THE PROJECT 2
1.4 EXISTING SYSTEM 2
1.4.1 EXISTING SYSTEM DISADVANTAGES 2
1.5 LITERATURE SURVEY 3-5
1.6 PROPOSED SYSTEM 6
1.6.1 ADVANTAGES IN PROPOSED SYSTEM 6

2. CHAPTER 2: PROJECT DESCRIPTION (7-20)

2.1 GENERAL 7
2.2 METHODOLOGIES 7
2.2.1 MODULES NAME 7
2.3 MODULES EXPLAINATION & DIAGRAMS 7
2.3.1 USER INTERFACE DESIGN 7-8
2.3.2 DOCTOR 8
2.3.3 PATIENT 9
2.3.4 HOSPITAL 10
2.3.5 RELATIVE 11
2.4 GIVEN INPUT EXPECTED OUTPUT 12
2.5 TECHNIQUE USED OR ALGORITHM USED 13
2.5.1 PROPOSED ALGORITHM 13-15
2.5.2 EXISTING ALGORITHM 16

3. CHAPTER 3: REQUIREMENTS ENGINEERING (17-31)

3.1 GENERAL 17
3.2 HARDWARE REQUIREMENTS 17
3.3 SOFTWARE REQUIREMENTS 17
3.3.1 FEATURES OF JAVA 17-19
3.3.2 THE JAVA FRAMEWORK 19
3.3.3 OBJECTIVE OF JAVA 20
3.3.4 JAVA SERVER PAGE - AN OVERVIEW 20-21
3.3.5 EVOLUTION OF WEB APPLICATIONS 21
3.4 FUNCTIONAL REQUIREMENTS 22-25
3.5 NON-FUNCTIONAL REQUIREMENTS 25-28
3.6 DOMAIN REQUIREMENTS 29-31

II
4. CHAPTER 4: SYSTEM DESIGN (32-51)
4.1 GENERAL 32
4.2 SYSTEM ARCHETECTURE 32-33
4.3 UML 33-34
4.3.1 USE CASE DIAGRAM 35
4.3.2 CLASS DIAGRAM 36-38
4.3.3 OBJECT DIAGRAM 38-39
4.3.4 COMPONENT DIAGRAM 40-41
4.3.5 DEPLOYMENT DIAGRAM 42
4.3.6 SEQUENCED DIAGRAM 43
4.3.7 COLLABARATION DIAGRAM 44
4.3.8 STATE DIAGRAM 45
4.3.9 ACTIVITY DIAGRAM 46-47
4.4 DATA FLOW DIAGRAM 48
4.5 ER DIAGRAM 49
4.6 GUI DESIGN 50
4.6.1 Components of GUI 50-51
4.6.2 Features of GUI 51

5. CHAPTER 5: IMPLEMENTATION (52-59)

5.1 GENERAL 52
5.2 IMPLEMENTATION 52-59

6. CHAPTER 6: SNAPSHORTS (60-64)

6.1 GENERAL 60
6.2 OUTPUT SNAPSHORTS 60-64

7. CHAPTER 7: SOFTWARE TESTING (65-)

7.1 GENERAL 65
7.2 DEVELOPING METHODOLOGIES 65
7.3 TEST STRATEGY 65
7.3.1 LEVELS OF TESTING 65
7.3.2 TYPES OF TESTING 66
7.3.3 TEST CASE TYPE – GUI 67
7.3.4 TEST DESIGN TECHNIQUES 68
7.3.5 TEST ENVIRONMENT 68
7.4 ACCEPTANCE CRITERIA 68
7.4.1 ACCEPTANCE TESTING 68
7.5 BUILD THE TEST PLAN 69

8. CHAPTER 8: CONCLUSION AND REFERENCES (70-71)

8.1 CONCLUSION 70
8.2 FUTURE ENHANCEMENT 70
8.3 REFERENCES 70-71

III
 LIST OF FIGURES

FIGURE NO NAME OF THE FIGURE PAGE NO.

2.3 Module Diagram 7 TO 11
4.2 System Architecture 32
4.3.1 Use Case Diagram 35
4.3.2 Class Diagram 36
4.3.3 Object diagram 38
4.3.4 Component diagram 40
4.3.5 Deployment Diagram 42
4.3.6 Sequence Diagram 43
4.3.7 Collaboration Diagram 44
4.3.8 State diagram 45
4.3.9 Activity diagram 46
4.4 Data Flow Diagram 48
4.5 ER Diagram 49

IV
 LIST OF SYSMBOLS

NOTATION NOTATION DESCRIPTION

S.N
NAME
O
1. Class Represents a
collection of similar
Class name entities grouped
together.

-attribute

-attribute

2. Association Associations
represents static
relationships between
NAME Class B classes. Roles
Class A represents the way the
two classes see each
other.
Class A Class B

3. Actor It aggregates several

classes into a single
class.

4. Aggregation
Class A Class A
Interaction between
the system and
external environment

Class B Class B

5. Relation (uses) uses Used for additional

process
communication
6. Relation (extends) Extends relationship is
used when one use
extends case is similar to
another use case but
does a bit more.
7. Communication Communication
between various use

V
 cases.
8. State State of the process
State

9. Initial State Initial state of the

object
10. Final State Final state of the
object

11. Control Flow Represents various

control flow between
the states
12. Decision Box Represents decision
making process from a
constraint

13. Use Case Interact ion between

the system and
external environment.
14. Component Represents physical
modules which is a
collection of
components

15. Node Represents physical

modules which are a
collection of
components

16. Data Process/State A circle in DFD

represents a state or
process which has
been triggered due to
some event or action.
17. External Entity Represents external
entities such as
keyboard, sensors, etc.
18. Transition Represents
communication that
occurs between
processes.
19. Object Lifeline Represents the vertical
dimensions that the
object
communications.
20. Message Message Represents the
message exchanged.

VI
 LIST OF ABBREVATION

S.NO ABBREVATION EXPANSION

1. CB Collective Behavior
2. DB Database

3. JRE Java Runtime Environment

4. JSP Java Server Page
5. JVM Java Virtual Machine
6. JRE Java Runtime Environment
7. SD Social Dimension
8. SSD Sparse Social Dimension

VII