Assignment Cover Sheet

Qualification Module Number and Title

HND in Software Engineering SEC4205/Database Design Development
Student Name & No. Assessor
H.M.H.S.Thilakarathna / KDHDCSE 51-05 Induranga De Silva
Hand out date Submission Date

Assessment type Duration/Length of Weighting of Assessment

Reports 5000 Words Assessment Type 100%
4 Weeks

Learner declaration

Marks Awarded
First assessor

IV marks

Agreed grade

Signature of the assessor Date

FEEDBACK FORM
INTERNATIONAL COLLEGE OF BUSINESS & TECHNOLOGY
1
Module/Title: SEC4205/Database Design Development
Student: H.M.H.S.Thilakarathna
Assessor: Induranga De Silva
Assignment: Database Design Development

Strong features of your work:

Areas for improvement:

Marks Awarded:

2
Introduction

Sri Lanka is facing at the moment one of the difficult time periods in controlling the
spreading of New Corona Virus (COIVD-19) among the people of the country. The
government is taking all possible measures as per the health guidelines and assistance given
by the World Health Organization (WHO). In the mission of fighting against the disease the
government ministries such as ministry of health, ministry of defense and ministry of public
security is leading in the front line with the direct coordination of National Operation Centre
for Prevention of COVID-19 Outbreak (NOCPCO).
The ministry of health has decided to implement information system to extract, aggregate and
manage information related to COVID-19 pandemic within the Island. The proposed
management information system is named as Sri Lanka COVID-19 Information Management
System (SLCIMS) and it’s incorporated with a Centralized Database named Sri Lanka
COVID-19 Information (SLC19I) Database This information system going to be managed by
the head office of Ministry of Health.

Executive Summary

The majority of people and businesses utilize databases to store their personal and business
information. It is the proper method of data storage. Many individuals develop databases
using various database technologies. Databases are used for a variety of purposes. Users can
obtain solid security support from databases, and they can query for whatever information
they desire. As a result, databases are one of the most important aspects of technology

This assignment is mainly done for the Sri Lanka COVID-19 Information Management
System of the Ministry Of Health. This assignment includes all the necessary information that
the SLCIMS needed. By doing this assignment it was able to gain these following:

 Understand the database concepts and components

 Develop a logical database design.

 Implement a physical database for a given requirement

 Test and document databases

3
Table of Contents
Introduction..............................................................................................................................16
Executive Summary.................................................................................................................16
1. Data Models.........................................................................................................................19
1.1 What is data base model?..........................................................................................19
1.2 Comparison of Hierarchical, Network and Relational data model............................19
I. Hierarchical Data Model...........................................................................................19
This can be represented as:..............................................................................................20
..........................................................................................................................................20
II. Network Data Model.............................................................................................20
This can be represented as:..............................................................................................20
III. Relational Data Model...........................................................................................21
1.3 Why older data models are being replaced by new data models.................................21
2. Comparing Database Management Systems........................................................................22
2.1 MySQL...........................................................................................................................22
2.3 MS SQL Server..............................................................................................................23
2.4 Oracle.............................................................................................................................23
2.5 PostgreSQL....................................................................................................................24
3. Different Database Approaches...........................................................................................25
3.1 Top – down design method............................................................................................25
3.2 Bottom – up design method.......................................................................................26
3.3 Centralized design..........................................................................................................26
3.3 Decentralized design.................................................................................................27
3.4 Advantages of different approaches...............................................................................28
3.4 Most suitable method for this organization...............................................................29
4. ER Diagram..........................................................................................................................29
5. Relational Mapping..............................................................................................................30
5.1 Strong Entity Mapping..............................................................................................30
5.2 Weak entity Mapping.....................................................................................................31
There are no weak entity......................................................................................................31
5.3 1:1 Mapping...................................................................................................................31
Update_Center......................................................................................................................31
5.4 1: M Mapping...............................................................................................................32
5.5 Final Tables...................................................................................................................32
6. Data Dictionary....................................................................................................................34
7. POSTGRE SQL...................................................................................................................36
8. SQL queries for manipulation functions..............................................................................38

4
9. Queries.................................................................................................................................39
9.1What is a query?............................................................................................................39
9.2 Purposes of queries......................................................................................................39
9.2.1 Queries Examples....................................................................................................40
10.Test plan..............................................................................................................................42
11. Verification and Validation, Object permission, Statement permission, Implied
permission................................................................................................................................44
11.1 Verification.................................................................................................................44
11.2 Validation....................................................................................................................44
11.4 Statement permission.................................................................................................46
2. Backup.............................................................................................................................46
4. Create query...................................................................................................................48
11.5 Implied permission.....................................................................................................48
12. Conclusion and Recommendations....................................................................................49
12.1 Conclusion...................................................................................................................49
12.2 Recommendations......................................................................................................49
12.2.1 Security.................................................................................................................49
12.2.3 Backups................................................................................................................49
13. References..........................................................................................................................50
References................................................................................................................................50
14. Gantt Chart.........................................................................................................................51
..................................................................................................................................................51

Table of Figures

Figure 1 Hierarchical Data Model............................................................................................21

Figure 2 Network Data Model.................................................................................................21
Figure 3 Relational Data Model...............................................................................................22
Figure 4 Top – down design method........................................................................................27
Figure 5 Bottom – up design method.......................................................................................27
Figure 6 Centralized design.....................................................................................................28
Figure 7 Decentralized design..................................................................................................29
Figure 8 Advantages of different approaches..........................................................................29
Figure 9 ER Diagram...............................................................................................................30
Figure 10 Registration..............................................................................................................37
Figure 11 Patient.....................................................................................................................38
Figure 12 Doctor......................................................................................................................38
Figure 13 Medical_Report.......................................................................................................38
Figure 14 Update_Center.........................................................................................................39

5
Figure 15 doctor-Administration..............................................................................................39
Figure 16 Select........................................................................................................................41
Figure 17 where........................................................................................................................41
Figure 18 insert........................................................................................................................42
Figure 19 Update......................................................................................................................42
Figure 20 Delete.......................................................................................................................43
Figure 21 Verification..............................................................................................................45
Figure 22 Validation................................................................................................................46
Figure 23 Create a new data base.............................................................................................47
Figure 24 backup 1...................................................................................................................48
Figure 25 backup 2...................................................................................................................48
Figure 26 Create Table.............................................................................................................48
Figure 27 Create query.............................................................................................................49
Figure 28 Implied permission …………………………………………
49

Table of Tables
Table 1 Comparison of Hierarchical, Network and Relational data model.............................21
Table 2 DATABASE TECHNOLOGIES................................................................................25
Table 3 Data Dictionary...........................................................................................................34
Table 4 Test plan......................................................................................................................42
Table 5 Gantt Chart..................................................................................................................51

1. Data Models

6
 1.1 What is data base model?
A "data model" is a logical linkage and data flow between diverse data components in a
digital world. It also describes how to save and retrieve data. Data models accurately express
information system needs, which are then utilized to provide the responses required to satisfy
those requirements. Data models can be used to decide what data is required and in what
format for different business operations.

Types of data models

 Hierarchical Model

 Network Model

 Entity-Relationship Model

 Relational Model

 Object-Oriented Data Model

 Object-Relational Data Model

 Flat Data Model

 Semi-Structured Data Model

 Associative Data Model

 Context Data Model

(Hiter, 2022)

1.2 Comparison of Hierarchical, Network and Relational data model

7
 I. Hierarchical Data Model

Hierarchical data models were among the first to be created. To save space, this was a file-
based model made in the shape of a tree. In this tree, child nodes might have several parents,
but each child node could only have one. A directory can contain more than one file or
directory.
This can be represented as:

Figure 1 Hierarchical Data Model

(Pedamkar, 2022)

II. Network Data Model

The network database model was developed to overcome shortcomings in the hierarchical
database architecture. This data format supports child-parent relationships, whereas the
hierarchical data structure does not. Children are referred to as members, but their parents are
referred to as owners.
This can be represented as:

8
 Figure 2 Network Data Model

(studytonight, 2022)

III. Relational Data Model

The relational data model is the most common. This straightforward methodology helps
improve data processing and storage efficiency (tutorialspoint, 2022).

Figure 3 Relational Data Model

Table 1 Comparison of Hierarchical, Network and Relational data model

Hierarchical Network Relational

A structure of data A database model that A database model to manage
organized in a tree like allows multiple records to be data as tuples grouped info
model using parent child linked to the same owner relations
relationships file
Arranges data in a tree Organizes data in a graph Arranges data in tables
similar structure structure
Represents “one to many” Represent “many to many “ Represent both “one to
relationship relationship many “ and “many to many
“ relationships

9
 Difficult to access data Easier to access data Easier to access data
Less flexible Flexible Flexible

1.3 Why older data models are being replaced by new data models.

The solution is to alter things. The business has changed, and what technology need is
continually changing. Systems and their data help the business. However, as the organization
evolves, so will the data model. Technology advances and necessitates numerous data
configurations in order to work with newer infrastructure for data management, and these
new structures of "big data" and BI necessitate diverse data structures as well. As an example,
in the beginning, the organization created a data model to model a simple accounting system
that runs on a single IBM mainframe. When they transitioned to Client-Server distributed
processing, the data had to adapt in order to give data on each tier of the architecture. So data
changes as a result of changing needs and technology. (altexsof, n.d.)

2. Comparing Database Management Systems

A database management system is required for database maintenance. MySQL, Oracle, SQL
server, and other commercial databases are widely utilized in a range of applications. The
DBMS can execute a wide range of tasks, including database construction, storage, and
retrieval, as well as data updating and table creation. It ensures the database's safety and
security. Similarly, it assures data consistency when numerous users are engaged. (Mullins,
n.d.)

2.1 MySQL

MySQL is a free open-source relational database management system. It is now a popular

alternative to SQL that is used globally.

pros cons
Data safety A few stability problems
Scalability on demand Prior experience is required.

10
 Continuous availability Transactions are not processed quickly.
Complete transactional assistance

2.3 MS SQL Server

Microsoft SQL Server is a relational database management system (relational database

management system). This product's principal job is to store and retrieve data as needed by
other applications.

Pros Cons

Possibilities for employment Features for complex performance tuning

There is plenty of internet documentation. There is no native source control support.

Developer edition for free

2.4 Oracle

The Oracle Cooperative Association designed and maintains this relational database system.
It now supports multiple data models within a single database, including document, graph,
relational, and key-value. It has recently refocused on cloud computing in its most recent
releases. Oracle's proprietary database engine can be obtained as a free or premium license.

Pros Cons
Daily workflow innovations High price
Excellent technical support and Resource-consuming
documentation
Large storage capacity A difficult learning curve

2.5 PostgreSQL

11
This widely used database management system is related to MySQL. This object-relational
database management system combines user-defined objects and table procedures to create
more complex data structures (DBMS). PostgreSQL and MySQL share some similarities. As
a result of this initiative, standards for compliance and extensibility will be strengthened. As a
result, whether it's for a single computer or a big application, it can manage any workload. It
is owned and developed by the PostgreSQL Global Development Group, and it is still
entirely open source. This database management system is compatible with Microsoft, iOS,
Android, and numerous other platforms.
Pros Cons
Scalable Documentation that is inconsistent
Custom data types can be supported. a scarcity of reporting and auditing tools
Third-party technologies that integrate
easily
Community-driven and open source

Criteria MYSQL MS SQL Server Oracle

Primary Relational dbms Relational dbms Object oriented
database model dbms
Data Schema Yes Yes Yes
License Open source Commercial Commercial
Supported C,C+ Java, C++, python, C, C++, python, java
Programing +,C#,PHP ,python, PHP… script….
Language java
Market share 32.74% 13.33% 3.63%
Type of data support char,varchar, char,varchar, Char, varchar, raw,
int,double, bit,float,decimal,
nvarchar2, date,
float,date,binary.. date, binary..
char,
Clob…
Max columns 4096 per table 1024 per row 1000 per table
Max database Unlimited 524258TB Unlimited
Max table 2TB to 16TB 524258TB Unlimited
Max rows 65535 bytes per Unlimited Unlimited
table
Security This is the most strong authentication Oracle is
synonymous with
secure and reliable and access
storing and
dbms used in protection. And also protecting the
world’s
popular web it has better
Business data.

12
 applications in password protection Oracle innovates
by proactively
including Facebook, management
building in security
twitter, word press. features.
So my sql provides
high data security.

Table 2 DATABASE TECHNOLOGIES

This comparison provides a good picture of these three database technologies. And it
demonstrates the differences between each technology, what types of data it supports, its
restrictions, the security levels of various technologies, and so on. Furthermore, it
demonstrates the types of advantages that consumers can obtain by utilizing various
technologies. (khalil, 2022) (Andrieiev,
2022).

3. Different Database Approaches

Data is saved in a computer system when using a database strategy. It is accessible through a
variety of computer applications and is organized into several charts. Data is saved in
databases that are relevant to the firm that employs it.

3.1 Top – down design method

Top-down design begins with the broad and works its way down to the specifics. Begin with
a general idea of what the system requires and work your way down to additional information
about how the system will function. During this operation, several entity types and their
attributes are recognized.

13
 Figure 4 Top – down design method

III.2 Bottom – up design method

This strategy is the inverse of the top-down method. It signifies that this strategy works from
specialized to universal. In this section, first identify the things and then group them together.
In other words, it first identifies the qualities and then assigns them to entities.

Figure 5 Bottom – up design method

III.3 Centralized design

Centralized design is most effective when the data component is made of a relatively small
number of objects and procedures. The concept can be carried out and reflected in a simple
database. A centralized design for a simple or small database can be implemented
successfully by a single database administrator or a small design team.

14
 Figure 6 Centralized design

III.4 Decentralized design

Decentralized design may be the best solution when the data component of the system
includes a large number of entities and extensive relationships on which sophisticated
operations are performed. This strategy is likely to be used if the problem is spread across
numerous operational sites and the elements are a subset of the entire data set.

15
 Figure 7 Decentralized design

3.4 Advantages of different approaches.

Top-down method Bottom-up method

Breaking the problem into parts helps User can replace many manual
clarify what needed to be done. processes with early automation.
Parts of the solutions may turn out to be User can implement password
reusable. management for a large number of
users.
Provides relatively quick Users do not have to develop custom
implementation and payback. adapters in the early phases.
At each step of refinement, the new parts The calculations can be designed to be
become less complicated and, therefore, additional
easier to figure out.

Figure 8 Advantages of different approaches.

(databasemanagement, n.d.)

III.5 Most suitable method for this organization

This organization must choose the better of the two techniques. The top-down approach is
best suited to this company. Because the user can grasp the system quickly and effortlessly.
And decisions can be made and implemented rapidly. In addition, the user can gain a good
understanding of management and various levels of hierarchy. Top-down approaches are less
risky for projects. This model relies on the executive level to decide how to prioritize,
manage, and carry out daily processes. These ideas, which are mentioned above, give a clear
picture about the top-down strategy and illustrate that this approach is quite good for this
company.

16
4. ER Diagram

Figure 9 ER Diagram

5. Relational Mapping

5.1Strong Entity Mapping

Registration_Department

RID Reasons Ward Date

Patient

PID Fname Lname DOB Age Gender

17
Doctor

DID Fname Lname DOB Age Gender Specialization

Medical_Report

MID Date Drugs

Update_Center

UID Description Date

Administration

AID Confirmed_ Recoverd Suspected_ Death_ Date

Case _ Case Case
Case

5.2 Weak entity Mapping.

There are no weak entity

5.3 1:1 Mapping

Administration

AI Confirmed_ Recoverd Suspected_ Death_ Date UID

D Case _ Case Case
Case

Update_Center

Patient

PID Fname Lname DOB Age Gender RID

18
 Registration Department

Medical_Report

MID Date Drugs RID UID

Registration Department Update_Center

Update_Center

UID Description Date MID

Medical_Report

Administration

AI Confirmed_ Recoverd Suspected_ Death_ Date UID

D Case _ Case Case
Case

Update_Center

5.4 1: M Mapping

Patient

PID DID Fname Lname DOB Age Gender

Doctor

Medical_Report

MID DID Drugs Date Descriptio

n

19
 Doctor

5.4 M: M Mapping

There are no M:M relationship

5.5 Final Tables

Registration_Department

RID Reasons Ward Date

Patient

PID RID DID Fname Lname DOB Age Gender

Registration Department Doctor

Doctor

DID Fname Lname DOB Age Gender Specialization

Medical_Report

MID RID DID Date Drugs Description

Registration Department Doctor

Update_Center

UID Description Date MID

20
 Medical Report
Administration

AID UID Confirme Recoverd Suspected_ Death_

d _Case Case Case
_Case

Update_Center

6. Data Dictionary
Table 3 Data Dictionary

Table Field Name Data Type- Constraint Description

Length

Patient PID Varchar (15) Primary Key ID Number of

the patient

Fname Varchar (10) Not Null First Name of

the patient
Not Null
Lname Varchar (10) Last Name of
the patient
Not Null
Age Int Age of the
patient
Not Null
Gender Varchar (7) Gender of the
patient
Not Null
Address Varchar (35) Address of
the patient

RID Varchar (10) Foreign Key Registration

ID of the
patient

DID Varchar (10) Foreign Key ID of the

Doctor

Doctor DID Varchar (10) Primary Key ID of the

Doctor

21
 Fname Varchar (10) Not Null First Name of
the Doctor

Lname Varchar (10) Not Null Last Name of

the Doctor

Age Int Not Null Age of the

Doctor

Gender Varchar (7) Not Null Gender of the

Doctor

Specialist Varchar (15) Not Null Specialization

of the Doctor

Registration RID Varchar (10) Primary Key Registration ID

of the patient

Date Date Not Null Admitted Date

Ward Int Not Null Admitted Ward

Number

Reason Varchar (50) Not Null Reason for

Admit

Medical MID Varchar (10) Primary Key Medical

Report Report Number

Date Date Not Null Report released

date

Drugs Varchar (50) Not Null Medications

approved by
Doctor

Description Text Not Null Description

about corona
patients

RID Varchar (10) Foreign Key Registration ID

of the patient

DID Varchar (10) Foreign Key ID of the

Doctor

22
Administration A_ID Varchar (10) Primary Key ID of the
Administration

Confirmed_ Int Not Null Number of

Confirmed
Cases
Cases

Deaths_Case Int Not Null Number of

Deaths

Recovered_ Int Not Null Number of

Recovered
Cases
Cases

Suspect_Cases Int Not Null Number of

Patients Suspect
Cases

Date Date Not Null Reported Date

UID Varchar (10) Foreign Key Medical Report

Number

7. POSTGRE SQL

23
 Figure 10 Registration

Figure 11 Patient

Figure 12 Doctor

24
 Figure 13 Medical_Report

Figure 14 Update_Center

Figure 15 doctor-Administration

8. SQL queries for manipulation functions

 SELECT: Retrieves data rows.

 INSERT: Insert new data rows into the database.

 UPDATE: Replace existing database values with new values.

25
  DELETE: Removes data rows from the database.

Function Query Result

Select SELECT * FROM "Patient" Successfully run.
Total query runtime:
131 msec. 2 rows
affected.

Insert INSERT INTO "Registration" INSERT 0 1 Query

VALUES('R03',1,'Headache','2022 returned successfully

in 112 msec.
-10-23');
Update UPDATE "Registration" UPDATE 1 Query

SET "rid"='R04' returned successfully

in 156 msec.
WHERE "rid" ='R03'
Delete DELETE FROM "Registration" DELETE 1 Query

WHERE rid='R04'; returned successfully

in 116 msec.

9. Queries.

9.1What is a query?

A query is a request for data or information from a database table or group of tables. This
data can be generated as SQL results or as pictorials. (janbasktraining, 2022)

9.2 Purposes of queries.

The usage of queries enables for the discovery of specific data by filtering it according to
one's own preferences and criteria. Queries can be used to calculate or summarize data, as
well as to automate data management activities. Querying can also be used to update or delete
data. It allows for the selection of data and its return from the database to an application. The

26
query's results are stored in a result table, also known as a results table, in the result set. The
SELECT statement has three subcategories: FROM, WHERE, and ORDER BY. In addition
to grouping and aggregating data, the SQL SELECT query can summarize or analyze data. A
subquery and a join can also be utilized to extract unique data.

9.2.1 Queries Examples.

Select

SELECT * FROM "Patient"

Figure 16 Select

This query returns all of the information in a given table.

Where

SELECT * FROM "Administration" where pid='P01'

Figure 17 where

This query is used to retrieve a specific detail from a table. You may also acquire the needed
value of a column by changing select * to select (column name).

Insert

INSERT INTO "Registration"

27
VALUES('R03',1,'fever','2022-10-23');

This statement allows the user to add new values to the table.

Figure 18 insert

If the output shows "INSERT 0 1," the command was successful.

Update

UPDATE "Registration"
SET "rid"='R04'
WHERE "rid" ='R03'

A query user can change the value of a table by using update.

28
 Figure 19 Update

If the output is "UPDATE 1," the command was successful.

DELETE

DELETE FROM "Registration"

WHERE rid='R04';

The user can erase undesired data by executing this query.

Figure 20 Delete

If the output is "DELETE 1," the command was successful.

10.Test plan.
Table 4 Test plan

Test case Purpose Test data Command Expec Actual Com

no. t output ment
outpu s
t
1 Check Reinsert pk INSERT INTO Violat duplica Succe
Primary key ‘P2’ of Patient "Patient" ion of te key ss
table VALUES('P02',' PK value
MAHENDRA','B violate
UDDIKA',25,'MA s
LE','THIBATUW unique
AWA constra
TENNA','R02', int
'D1) "Patien
t_pkey
"
2 Check Create fk INSERT INTO Error duplica Succe
Foreign key constraint in "Patient" messa te key ss
Patient table VALUES('P4','K ge value
using same fk UMARAEKANA violate
constraint in YAKE',24,'MALE s
Registation ','THIBATUWA unique
WA constra

29
 TENNA','R01','D int
01') "rid_id
"
3 Check Data Insert varchar INSERT INTO Error duplica Succe
type type data to a "Patient" messa te key ss
int data type VALUES(1,'MA ge value
column HENDRA','BUD violate
DIKA',25,'MALE' s
,'THIBATUWAW unique
A TENNA','R02') constra
int
"rid_id
"
4 Check Data Insert more INSERT INTO Error value Succe
size than given "Patient" messa too ss
value to a VALUES('P03','K ge long
varchar data ASUN','FERNAD for
type column O',25,'MALE','TH type
IBATUWAWA charact
TENNA','R2') er
varyin
g(10)
5 Update a Update a data UPDATE Updat UPDA Succe
data in Registration "Registration" e TE 1 ss
column SET "rid"='R04' succes Query
WHERE "rid" sfully returne
='R3' d
succes
sfully
in 111
msec.
6 Delete a Delete a data DELETE FROM Delete DELE Succe
data in Registration "Registration" succes TE 1 ss
column WHERE sfully
rid='R04'; Query
returne
d
succes
sfully
in 88
msec.
7 Drop a table Drop the table DROP TABLE Error cannot Succe
Registration "Registration" messa drop ss
which pk is ge table
reference as a "Regist
fk in another ration"
table becaus
e other
objects
depend

30
 on it.
8 Drop a table Drop the table DROP TABLE Delete DROP Succe
complain_actio "Administration" the TABL ss
n which hasn’t table E
a pk reference Query
as a fk in returne
another table d
succes
sfully
in 190
msec.

11. Verification and Validation, Object

permission, Statement permission, Implied
permission

11.1 Verification

Verification is the process of ensuring that a database meets its objectives without flaws. It is
the process of determining whether or not the product being developed is correct. It
determines whether the developed product meets the needs of users. Static testing is what
verification entails.

Figure 21 Verification

"select * from branch where pid='P01" is an example query." It also gives the proper answer.
It means that this database produces accurate results. And this is the database verification.

11.2 Validation
Validation is the process of assessing whether a data element has the correct format. The
process of ensuring that the product developers are developing the correct one. It is a
comparison of the actual product to the expected one.

31
 Figure 22 Validation

The name of this sample table is Patient, and the primary key 'P01' is repeated. It is not a
legitimate database entry. To add more data to the primary key column, the user must enter a
different value. In a database, this is known as validation.
(advanced-ict, 2022)

11.3 Object permission

An object permission defines a capability associated to a single object, such as a database or a

table. Object permissions are assigned to specific groups, roles, or people.

Example: 1. Select
SELECT * FROM "Patient"
This query returns all of the information in a given table.
2. Insert

INSERT INTO "Registration"

VALUES ('R03', 1,'fever','2022-10-23');
This statement allows the user to add new values to the table.

3. Update
UPDATE "Registration"
SET "rid"='R04'

32
WHERE "rid" ='R03'
The query user can change the value of a table by using update.

4. Delete
DELETE FROM "Registration"
WHERE rid='R04';
The user can erase undesired data by executing this query.

11.4 Statement permission

Statement permissions enable a database user, database role, or Windows user or group to
execute numerous operations like as creating databases, creating objects, and backing up the
database.

1. Create a new database

Figure 23 Create a new data base

After creating a new database, it will appear in the databases category of the object explorer pane.
This is depicted in the image as a demonstration.

33
2. Backup

Figure 24 backup

PostgreSQL includes the pg dump program to assist with database backups. It creates a
database file with SQL commands that can be simply recovered in the future.

This is depicted in the image as a demonstration.

3. Create Table

The CREATE TABLE statement in PostgreSQL is used to create a new table in any of the
supplied databases.

Figure 25 Create Table

This is done as a show in the figure.

34
4. Create query

A query is any command that is used to retrieve information from a table.

Figure 26 Create query

Can navigate to it by clicking on the query tool.

This is done as a show in the figure.

11.5 Implied permission

Members of fixed roles and database object owners have access to additional features and
functionalities in addition to the standard statement and object permissions. Implied,
preconfigured, and implicit permissions are all phrases used to denote different types of
rights.
For instance, having full access to the database. The owner of the "SLCIMS Database" in the
figure below is "postgres."

35
 Figure 27 Implied permission (flylib, 2022)

12. Conclusion and Recommendations

12.1 Conclusion
The Ministry of Health now has a good database for this Sri Lanka COVID-19 Information
(SLCIMS) Database. This database contains information on patients, registration, doctor
administration, and other topics. This database will assist them in locating the records they
want. The mapping task demonstrates how these categories are related to one another. The
Administration Department can search the data in this database using the appropriate queries
that are indicated above, which will assist them in finding the data that they require. The
Ministry of Health employs a database administrator, who is assigned specific database and
server tasks. This document makes reference to them. If the Administration wants to edit or
update the database, the database administrator can do so.

12.2 Recommendations

This database is critical for this company now and in the future. As a result, this database
requires some suggestions.

36
12.2.1 Security

As a result, database security should be a key focus. A lack of security will endanger the
database and data. This organization will need a good server to run this data. They can obtain
a substantial security advantage if they run this server through the server.

12.2.3 Backups

In the event of a calamity, backups allow them to restore the database. Backups must be kept
in their departments and with a few confidential people or firms.

13. References

References
advanced-ict, 2022. Validation. [Online]
Available at: https://www.advanced-ict.info/databases/validation.html
[Accessed 22 October 2022].
altexsof, n.d. Comparing Database Management Systems: MySQL, PostgreSQL, MSSQL
Server, MongoDB, Elasticsearch and others. [Online]
Available at: https://www.altexsoft.com/blog/business/comparing-database-management-
systems-mysql-postgresql-mssql-server-mongodb-elasticsearch-and-others/
[Accessed 21 October 2022].
Andrieiev, S., 2020. SQL Server vs MySQL vs Postgresql. [Online]
Available at: https://jelvix.medium.com/sql-server-vs-mysql-vs-postgresql-which-one-is-the-
best-abfa830d7569
[Accessed 21 October 2022].
databasemanagement, n.d. Database Design Strategies. [Online]
Available at: https://databasemanagement.fandom.com/wiki/Database_Design_Strategies#
[Accessed 21 octocber 2022].
flylib, 2022. Types of Permissions. [Online]
Available at: https://flylib.com/books/en/2.908.1.63/1/
[Accessed 22 October 2022].
Hiter, S., 2021. What is Data Modeling?. [Online]
Available at: https://www.datamation.com/big-data/what-is-data-modeling/
[Accessed 04 August 2021].

37
janbasktraining, 2022. The Types Of Database Query And How To Use Them. [Online]
Available at: https://www.janbasktraining.com/blog/database-query/
[Accessed 22 October 2022].
khalil, M., 2022. SQL Server, PostgreSQL, MySQL... what's the difference?. [Online]
Available at: https://www.datacamp.com/community/blog/sql-differences
[Accessed 21 October 2022].
Mullins, C. S., n.d. database management system (DBMS). [Online]
Available at: https://searchsqlserver.techtarget.com/definition/database-management-system
[Accessed 21 October 2022].
Pedamkar, P., 2022. Hierarchical Database Model. [Online]
Available at: https://www.educba.com/hierarchical-database-model/
[Accessed 20 October 2022].
studytonight, 2022. DBMS Database Models. [Online]
Available at: https://www.studytonight.com/dbms/database-model.php
[Accessed 20 October 2022].
tutorialspoint, 2022. Relation Data Model. [Online]
Available at: https://www.tutorialspoint.com/dbms/relational_data_model.htm
[Accessed 21 October 2022].

14. Gantt Chart

October
Task Name Start Date End Date
17 18 19 20 21 22 23 24 25
Task 1,2,3 17/10/2022 18/10/2022

Task 4,5 19/10/2022 20/10/2021

Task 6,7,8 21/10/2022 22/10/2022
Task 9,10,11 23/10/2022 24/10/2022

Task 12 24/10/2022 25/10/2022

Table 5 Gantt Chart

38