Data Modelling Management and Governance - Desklib

This report covers the description of UML use case diagram, entity relationship diagram, logical and physical design, and SQL queries for data access and information retrieval. It provides a clear understanding of data modelling, management and governance with solved assignments, essays, dissertations and more on Desklib.

DATA MODELLING
MANAGEMENT AND
GOVERNANCE
1

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................3
MAIN BODY...................................................................................................................................3
1. UML use case diagram................................................................................................................3
Use case relationship...................................................................................................................6
Benefits of use case diagram.......................................................................................................7
2. Entity relationship diagram for school scenario..........................................................................9
Database system diagram...........................................................................................................16
3. Logical design (ERD) and physical design................................................................................18
4.SQL Queries................................................................................................................................23
CONCLUSION..............................................................................................................................28
REFERENCES..............................................................................................................................30

INTRODUCTION
Data modelling refer to the process of developing the simplified diagram of the software
system which contains the data elements and other symbols etc. and it also shows how the data
flows within the system (Liu and et.al 2020). Data modelling is all about to generating the
blueprint for the desired database system or reengineering with the legacy applications. It
comprises of the visual representation of the complete information system or to communicate the
associativity between every data point aspects. data models can be developed around the
requirement of business. There are specific data models which the user concerns with conceptual
data model, logical data model and physical data model. Where it gives the clear image about the
data entities along with its various attributes (Sawaneh and et.al 2018). Database management
system refers to the computerised data storing system where the data is available in the arranged
or organised form that can be easily retrieved and accessed. Every business has their individual
data base system where they store their business details and other critical information, for
accessing the data they are provided with particular authentication in order to protect data from
any malicious activities. Data model generally examine the structured data that keeps the
persistent data within the relational database system and it is specified within the data modelling
language.
Following report will cover the description about the UML use case diagram that will be
made for the local secondary school in Luton who is looking forward to develop the database
system that comprises of all their useful details and other information. It will cover the Entity
relationship diagram where it will also highlight the conversion of logical ERD into physical
ERD and also covers the SQL queries for data access and information retrieval.
MAIN BODY
1. UML use case diagram
Unified modelling language diagram assists in providing the visual aspects of the system,
it generally describes the quantifiable factors about the system which is discussed visually like
relationship, behaviour and its cardinality, functionality (Zhidchenko and et.al 2021). UML is
utilised as the modelling of the system that is independent of the language platform, it provides
the standard approaches for write down the system models that consists of the conceptual ideas.
It is further classified into the categories that are on the basis of the structure where it covers the
3

Class diagram, composite structural diagram, object diagram and component diagram. While
other category is behavioural diagram where it covers the state machine diagram, activity
diagram, use case diagram and sequence diagram, timing diagram. UML diagram offers the
greater flexibility as it is one of the common used and widely accepted language for the outlining
programs.
UML use case diagram refers to depicting the functionality about the system and for its
components. These diagram are most commonly used diagram in order to describe the functional
requirements about the system and its interaction with the system users (Fischer, Scholten, and
Unwin, 2019). This diagram uses the set of use cases where it also involves the actor and their
relationship, it describes the different scenarios from which the system is used, it provides the
greater level view about the system. Main purpose of use case diagram is to specify the context
of the syst4em and to capture the system essential requirement, it also validates the architecture
of system and drive the execution or deliver the test cases. For the local school case scenario, it is
provided with the details that the school wants to develop their database system where they can
store the details of their staff, students and subjects. It comprises of the aspects that are as
follows:
Actor: Actors, someone or other external hardware system who interacts with the system and
they have crucial role in the business they are similar to the user but user can play other different
roles. They generally trigger the use case and play their role towards the system to enter the input
within the system in order to get the output. Regarding the school scenario two actors are
identified as student (pupil) and staff.
Use case: System functions that is process (automated or manual), every actor is required to
associates with the use case while some of the use cases might not associates with the actors.

Communication link: Participation of the actor within the use case system is represented by the
solid link, that generally associates the use case with the actor. With the help of this actors are
connected with the use case and also indicates the communication as how actor is
communicating with the use case (Mehta and et.al 2021). Thus connector helps in specifying that
particular actor has the role within the system. For an instance for school scenario in use case
diagram it will show how pupil can access the system and can take the subjects, also shows how
staff access the system and perform their specific role within the system.
System boundary: System boundary indicates the entire system where it describes the required
documents. For the large size and complicated system every module is considered as the system
boundary.
5

Use case relationship
Use case shares the distinct type of relationship where decision regarding relationship between
the two use cases is taken by the software analysts of that particular use case diagram. Where the
relationship between the two use cases is generally consider as modelling the dependency among
the use cases (Revesz, Rashid and Tuyishime, 2019). By reusing the use case with the different
kind of relationship is effective as it decreases the efforts that is needed for constructing the
system. Some of the use case relationship are as follows:
Extend: This relationship can be used as to specify that the particular use case is extending the
behaviour of the other use case. Such type of relationship helps in disclosing the information
about the application which generally do not appears and hidden within the use case.
Include: Include relationship is found when the use case is presented as using the functionality
and other aspects of the other use case. It is depicted by the directed arrow with having the dotted
line.

Benefits of use case diagram
There are various advantages of use case diagram which assists the software developer to design
their process as per the user’s perspective. As an outcome system works more efficiently and
helps in achieving the user’s goals (Utomo,Cahyono and Tristono, 2019). There are other
benefits of use case diagram is as follows:
 This diagram is usually traceable; it provides the information about structure as well as
system behaviour.
 It assists in analysing the complete functional requirements about the system so desired
result can come out.
 Its simplicity and easy interface lead the businesses to easily commence with and use
case also compatible for the software developer to deliver end result to their end users.
 They are reusable in project and it captures all the requirements for every iteration within
a creation guidance for the programmers, within test cases and also in user
documentation.
 Use cases are also useful for the scoping and it also make easier or simpler for the project
to undertake the phased approaches for the delivery, it can be easily removes and added
from the software projects when the priorities changes (Wajszczyk and Gruszka, 2020).
 Every use case defines the one approach for system is being used but additionally use
case modelling also helps in explaining the things which are not correct. Identification of
the exception points to the successful scenario in initial phase within a project is quite
helpful and saves a lot of time by determining the appropriate requirements.
 Its major advantage is that it is written in the natural language that means it can be easily
understood as well as it gives the easier way for communication and interaction with the
users. It also helpful is managing the complexity of the large projects by simply
decomposing the issue within a different functions and can be easily specified by the
user’s perception.
7

Above is the use case of Secondary school system where the major two actors are staff and
pupil(students) who access the system. there are sort of use cases involves in the diagram where
first is about login and logout system which is accessible to both staff and student (Chauhan and
Tripathi, 2019). Pupil register to course and view the subject course, they also give exam and
accessible to view the result. On the other hand, staff manage the student attendance, and view

the student performance, they also add the subjects and takes exam also manage the student
information. It also involves the include and extended relationship for the use cases.
2. Entity relationship diagram for school scenario
Entity relationship diagram defines the interrelated things that are present in specific domain, it
is the type of structural diagram in the database designing system where it shows the relationship
between the different entities. It shows the relationship among the user, objects and other
concepts in an information technology system (Osborne, 2020). It is mostly use for designing or
debugging the relational database system, it uses the defined set of symbols like rectangles, oval
and associativity lines all have importance in ER diagram. It consists of three major things that
are entities, attributes and relationship.
Entity: Entities define as the person, object or other concept for that the data have been stored, it
is the table that are used in the database system for storing the information. It simply presented
with the help of the rectangles. It is the real world object that is distinguished from the other
objects.
Weak entity: Weak entity an entity which usually relies on the existence of the other entity, in
technical terms it can be understood as the entity which cannot be easily determined by its own
attributes. In this it takes the use of foreign key that combines with its attribute to develop the
primary key (Fatmawati and Munajat, 2018).
9

There are other types of entities that are as follows:
Independent entity: These type of entities is considering as the kernels which also understood as
the backbone of database system, they are the things on which the other tables based on
(Peleshchyshyn and et.al 2018). It has some characteristics that are as follows:
 Building block of the system
 Primary key can be simple and composite as well
 Primary key cannot be a foreign key
 They generally don’t rely on other entity for its existence
Dependent entity: It is also called as the derived entities which rely on another table for its
meaning. There are some characteristics of dependent entities is as follows:
 These entities are used for associating the two kernels together
 They are considering as to depend on two or more other tables
 In this many to many cardinality becomes the linkage tables with at least two foreign
keys.
 They also consist of other attributes
 In this foreign key determines every associated table
In this generally there are three options for the primary key, utilise the composite of the foreign
keys of the linked tables if it is unique or to develop new simple primary key.
Attributes: These are referring to the characteristics of the entities, ERD attributes also
represented as the primary key which determines the unique attribute that can easily assigned to
the other attributes as well. It involves the details of Entity which are highlighted in the
conceptual entity relationship model diagram (Roy-Hubara and Sturm, 2020). It is simply
represented in an oval shape so that user can easily identify that particular things present in an
oval shape are attributes that carries the detailed information about entities.

It further involves the concept that are key attribute and partial key attribute. Where key
attribute is uniquely identifying in every entity within an entity set it is represented by
underlining the attribute (Bjeladinovic, 2018). Key attribute also represented as the primary key
which is unique for every entity. Whereas partial key attribute is to identify the weak entity.
Composite attribute: When an attribute is generally composed of more than one attribute than
it is termed as the composite attribute. It can also be understood as the attribute that divides into
other sub parts. For an example in school case scenario it involves the attribute which is
student_address so in this address attribute can further divide in other sub attributes that are city,
street, country an state.
11

Multivalued Attribute: Attribute that involves more values for an entity, it is represented by the
double value. For an example in school case scenario staff has phone number so it can be
concluded that there are many possibilities that one staff will have more than one contact
number.
Relationship: It shows that how entities acts over each other and are linked with each other. It is
utilised to document the overall interaction among the entities. It is simply an verb for
associating and giving the useful information which cannot be discerned with the entity types
only.

There are usually three type of cardinal relationship that are one to one, one to many and
many to many.
One to one cardinality: It shows the relationship between the two entities for an example in A
and B entity where the one element of A is associated with one element of B than the
relationship is found as one to one (Hasan and et.al 2019).
One to many cardinality: This relationship in database management system is about representing
that an element of one entity is allowed to link with the many element of other entity. For
example, instances of A can be linked with many instances of Entity B, but the instances of B
can only have linked with the one instance of entity A.
Many to many cardinality: It occurs when the multiple elements in the table are linked with the
multiple records of the other table. All elements of A can linked with all elements of B and vice
versa.
Many to one cardinality: More than one element of the entity can be linked with one element of
one entity.
Benefits of ER diagram
Data requirements can be easily understood while using the Entity relationship model
which shows every detailed information about the system clearly (Syamsiah, 2022). This model
can be converted into the relational database, one of the major advantage of ER model is that it
can be easily understood and have clear information about the entities, attributes that are present
in the database system. Another benefits of ER diagram is as follows:
Conceptual simplicity: When the concept or relationship between the entities and attributes are
identified than ER diagram can be drawn quickly.
Explicit visual representation: Structure of relational database system can simply comprehend
after instructing the ER diagram.
Effectiveness in communication: In this the use of specific symbols presents the different data
which facilitates the better understanding about working of the database system after its
completion.
Easier to convert the ER diagram into other data model: ER diagram is more compatible and
offers the higher flexibility, as it can be easily convert into the other hierarchical and graphical
data model. As graphical representation of the ER diagram is more efficient and provides the
13

better understanding, as ER models provides the graphical representation about the different
entities, its attributes and relationship among the entities.
It built the conceptual design of the system also helps in creating the simpler and easy to
design for accessing the data where in ER modelling database structure can depicted as the ER
diagram.
For the school case scenario there are generally four entities that are pupil (student), staff,
course and subject. Where each entity has its different attributes which can be shown in data
dictionary table which is drawn below (Fadhil).
Data dictionary
Data dictionary refers to the collection of the names, attributes and other data elements
which can be stored in a database management, it is the centralised repository about the
metadata. Where the metadata refer to the data about data (Putra and Alfauzain, 2021). It is
beneficial that helps in easily understanding the concept so that user can easily develop the
understanding about the data. It helps in developing the complete understanding in database
design its structure and other data flow, it also helps in analysing the errors and anomalies in the
data. Main purpose of designing the data dictionary is to give the meaningful description for the
data objects.
Entities Attributes
Pupil Stu_Id, Stu_firstName, Stu_surname, Stu_address, Postcode
Staff Staff_Id, Staff_firstName, Staff_surName, Staff_mobileNo,
Staff_address
Subject Sub_Id, Sub_code, Sub_name
Course Course_id, Course_name, Course_desc
Schedule Schd_Id, day(day of schedule), time_start and time_end
Primary key: Primary key generally uniquely determines each record within a table, it consists
of the unique values and there are no null values in it. It is mandatory for the database system to
have the primary key as it helps in performing updating, inserting and other database operations.

In this case scenario from the following above tables suitable primary key are as follows: Student
Id, Staff Id, Subject ID, Schedule Id and course Id.
Foreign key: Foreign keys defines as field in one table, it also considers as the primary key in
other table. It is the set of attributes together refers to the candidate key. In School management
system foreign key attributes are course ID in subject table, Stu_Id, Staff_Id, Course_Id,. Sub_Id
in schedule table.
15

Database system diagram
Database generally a comprehensive database software program which is also termed as the
database management system. DBMS system work as an interface between the database and its
user, where the user can access the information by performing database functions, users are
allowed to easily access, update and manage the information. Many businesses always concern
with the designing of their database system that helps them to manage their critical and other
useful information in organised manner (Malik, Burney and Ahmed, 2020). Relational database
management system is commonly used DBMS interface to which many businesses are associated
with it allows to manage and update the information in a system, queries are being generated in
order to retrieve, access, update, delete the information. In which the data is mostly stores in a
table where rows which presents the records and columns that presents attributes. Tuples are also
there which represents the single record of single roe in table.
Benefits of database system
Improvised data sharing and security: This system allows the user to perform operation quickly
as to efficiently shares the data across the business. By performing better database queries
system helps in quickly accessing the accurate data (Sytnyk and Zinovieva, 2019).
Data integration: Proceeding with the database system it will provide the integrated layout of
operations by simply evaluating how processes within a segment of firm affects the other
segment.
Consistent and reliable data: Generally, inconsistency in data is found when distinct versions of
the data exits in other places in organisation., thus this problem can be easily solved with the
help of the database management system and other quality tools.
Increased productivity: Deploying the DBMS system eventually helps in increasing the
productivity as it empowers and encourage the people to spend time on these valuable activities
and strategic initiatives, there is less time in cleaning the data and manually scrubbing the lists.

Therefore, having a proper database management system, it will allow the businesses to
take better decisions, as it stores the accurate data so there is more productivity chances. System
facilitate the accurate data and other quality initiatives that assist in better decision making
process (Kraleva, Krale and Sinyagina, 2018). Thus for the secondary school system, with the
database system they will be able to store the accurate details of their staff, pupils also they will
be able to perform queries in order to retrieve data.
17

3. Logical design (ERD) and physical design
Logical ER model
Logical Entity relationship diagram refer to the detailed version of the conceptual ER
diagram. Logical ER is developed in order to enrich the conceptual design of the system by
explaining all the columns in every entity and also introduce the operational and transactional
entities (Mearaj, Maheshwari and Kaur, 2018). Although logical design is still independent to
the real database system where the system is developed and this design still allow to take other
things in consideration that is affecting the design. Entities in such type of ER diagram can be
made on the basis of the business requirements. It is possible for applying the normalisation
process generally it is up to the third normal form level.

Characteristics of logical ER model
 This diagram generally explains the data without considering the fact that how it will be
work in a physical implementation of the database system.
 It generally describes the data elements along with its relationship.
 Data architects and other business analysts develops the logical data model for
understanding their business requirements
 It is simpler diagram as compared to the physical diagram, where it is user friendly and
non-technical background people can easily understand this.
 Main purpose of logical ER is to create the technical set of rules and other data structures.
19

Above is the diagram of logical ER model for the secondary school management where it
generally shows the element as number of entities and sort of attributes in each entity (Tian and
et.al 2019). It also shows the connectivity between the tables, it is clearly seen that there is no
such primary and foreign key concept because it does not concern with the actual layout of the
system, above diagram also not shows the data type of each attributes.
Physical ER model
Physical designing generally concerns with the actual design or layout of the relational
database system. It mainly elaborates over the logical model by showing every table with its data
type and other useful or essential things (Singh, 2019). Physical ERD describe how data should
be arranged and structured within the system and related within the DBMS, it is necessary to
concern with the conventions and restrictions of the real database system where the system will
develop. It is more complicated than the logical model because it involves the data type and
other primary and foreign key concept as it is showing the actual database system. Additionally,
it is possible to make changes in physical model on the physical constraints. Characteristics of
physical data model is as follows:
 Physical data model is created by the database developers and administrators.

 It describes the proper table structure and other column name, attributes type, relationship
between entities which cannot be seen in logical designing.
 Main objective of the physical data model is to implement the real database system.
21

Comparison between logical and physical ER model
Parameters for comparison Logical database Physical database
Definition It defines the data It showcase the data
Introduced by Data architects and other
business analysts
Developers and professional
database administrators
Objectivity Concern with developing the
technical structure and map
out all the rules
Executes database
Modelling User feedback and
documentation, entity
Server model diagram

relationship diagram
4.SQL Queries
Structured query language, it is a domain specific language which is utilised in a
programming and developed for managing data, it is mainly used for the relational database
management system. It is generally utilised to perform the several operations within the database
system, there are different queries that is being performed on the records that has been stored
within the table in a system (Shichkina, Kupriyanov and Shevsky, 2018). It is a standardised
programming language that is easy to understand and implement. Today all relational database
system that are MySQL, oracle, Sybase and MS access mostly utilise the SQL language because
of its flexibility and simplicity. SQL is more popular because of some factors that are as follows:
 Users can easily access the data within the relational database system.
 Enables the users to describe the data.
 Allows users to easily manipulate and define the data.
 With this user are free to use other languages as well by using SQL modules, libraries
and other pre compilers.
 User can easily develop and drop the database and tables.
Benefits of SQL
There are a lots of SQL which is discussed below:
Commonality: One of the major advantage of SQL is that commonality of the language. It is
beneficial for most of the IT system and it is very compatible to use it with other language.
Commonality of this language makes it easier for the users who are at initial stage of their career
profession, it also helps in making the application easier that can be beneficial for the
productivity and efficiency of business.
Simplicity: This language is more popular because of its simplicity as its commands are mainly
an English phrases that can be easily understood, thus with this programmer can easily get the
point to use the language for performing different functions over the system.
23

Integration: SQL can easily integrate with other programming languages too, for an instance
other language like python and R are commonly integrated with SQL, thus it helps in
manipulating the data and managing the system appropriately.
Speed: SQL’s major advantage is that it has better ability to efficiently function with greater
operating speed. Its better speed eventually increase the retrieval of data also allows user to
quickly perform other operations at greater speed like to manipulate and store the data.
In this school case scenario create query is being used to create the tables in a system,
where it shows the all attributes type and their values which is being run on SQL server. Moving
further for testing the system performance other SQL queries are also made that are insert query
which is generally execute in order to insert the additional details in the system, and other delete,
select and where query is also used for ensuring the better functions of the school database
system. Thus with the help of this Scholl administration can easily manage their students and
other useful details and can be able to perform queries in order to update their database system.
Thus they will be able to use their information for their future use and will be able to store their
information.
Pupil
CREATE TABLE pupil(
Stu_id int primary key NOTNULL,
Stu_firstName varchar(255),
Stu_surName varchar(255),
Stu_address varchar(255),
postcode varchar(255),
);

Above is the SQL query that is generated for the Pupil table where it involves the information
that is present in the system (de Oliveira and et.al 2020). Primary key is shown on the left side of
student Id that is unique for this table, its data type is int and value is not null
Staff
CREATE TABLE Staff(
Staff_Id int primary key NOTNULL,
Staff_firstName varchar(255),
Staff_surName varchar(255),
Staff_address varchar(255),
Staff_mobileNo varchar(255),
);
Above query is generated to create the second table that is staff where staff id is identified as
primary key and its id is not null.
Subject
CREATE TABLE Subject(
Sub_Id int primary key NOTNULL,
Sub_code varchar(255),
Sub_name varchar(255),
Course_Id int Foreign key NOTNULL,
);
25

Subject table where sub id is primary key and id is not null in this table course ID is
identified as foreign key that will help in linking both tables.
Course
CREATE TABLE Course(
Course_Id int primary key NOTNULL,
Course_name varchar(255),
Course_desc varchar(255),
);
Course table which consists of limited attributes that is required for the database system, in this
primary key is course id.
Schedule
CREATE TABLE schedule(
Sch_Id int primary key NOTNULL,
time_start timestamp,
time_end timestamp,
Course_Id int foreign key NOTNULL,
Sub_Id int Foreign key NOTNULL,
Stu_id int foreign key NOTNULL,
);

Above is the SQL query that is made for creating table schedule which consists of maximum
attributes of the system. In this Sch Id is uniquely identified elements which is primary key, it
also contains the four foreign keys, in short it is working as the table from which the other tables
within the system are depended and associated with it.
INSERT query
INSERT INTO dbo.pupil (Stu_id, Stu_firstName, Stu_surName,Stu_address,postcode)
VALUES ('107','Rachel', 'green','19 southhampten street','GF15');
DELETE SQL query
DELETE FROM dbo.pupil WHERE Stu_firstName='Rachel';
27

SELECT AND WHERE query
SELECT Stu_firstName FROM dbo.pupil WHERE Stu_id='101';
CONCLUSION
From the above report it is concluded that data modelling helps in making things easier to
integrates the greater level of business process. It provides the proper synergy to the way as how

business operates and how it utilised the data for their growth and other business processes.
Database management system plays a significant role in order to store the information in proper
structure so that it can be retrieved and access easily. Relational database system allows the user
to made queries in order to perform different operations over the data, with the use of such
system organisation could easily arranged their useful information and easily perform insert,
update, delete and other operations. RDBMS provided security to the data so that accurate data
would be used in making better business decision. Above report have illustrated the range of
description about the UML Use case diagram where it covered the given scenario in diagram it
shows the two actors has been included in the diagram who are interacted with the different use
cases within the system. It also discussed the benefits of the use case diagram as how it makes all
things simpler and easier to understand.
Moving further report have discussed about the entity relationship diagram that is made on
the given school case scenario where it covers as how ER model helps in understanding the
relationship between entities and attributes within the system. In ER diagram it discuss the type
of entities and attributes or its types along with the relationship factor where it highlighted the
different one to many and other cardinalities. It also discussed the advantages of ER diagram and
its importance to the database management system. Further report has illustrated the description
about the logical and physical ER diagram and its conversion, where it covers importance of both
ER model. Report finally concluded with the description about the Structured query languages
that is made for accessing the information within the database system.
29

REFERENCES
Books and journals
Bjeladinovic, S., 2018. A fresh approach for hybrid SQL/NoSQL database design based on data
structuredness. Enterprise Information Systems. 12(8-9), pp.1202-1220.
Chauhan, N. and Tripathi, S.P., 2019. QoS aware replica control strategies for distributed real
time database management system. Wireless Personal Communications. 104(2). pp.739-
752.
de Oliveira, P.S. and et.al 2020. Efficient Match-Based Candidate Network Generation for
Keyword Queries over Relational Databases. IEEE Transactions on Knowledge and Data
Engineering.
Fadhil, A.A., Build Tool to Generate Relational Database from Class Diagram. International
Journal of Computer Applications. 975. p.8887.
Fatmawati, F. and Munajat, J., 2018. Implementasi Model Waterfall Pada Sistem Informasi
Persediaan Barang Berbasis Web (Studi Kasus: PT. Pamindo Tiga T). Jurnal Media
Informatika Budidarma. 2(2).
Fischer, M.M., Scholten, H.J. and Unwin, D., 2019. Geographic information systems, spatial
data analysis and spatial modelling: an introduction. In Spatial analytical perspectives on
GIS (pp. 3-20). Routledge.
Hasan, H. and et.al 2019. Smart contract-based approach for efficient shipment
management. Computers & Industrial Engineering. 136. pp.149-159.
Kraleva, R., Kralev, V. and Sinyagina, N., 2018. Design and Analysis of a Relational Database
for Behavioral Experiments Data Processing. International Journal of Online
Engineering. 14(2).
Liu, C. and et.al 2020. Digital twin-enabled collaborative data management for metal additive
manufacturing systems. Journal of Manufacturing Systems.
Malik, A., Burney, A. and Ahmed, F., 2020. A comparative study of unstructured data with SQL
and NO-SQL database management systems. Journal of Computer and
Communications. 8(4). pp.59-71.
Mearaj, I., Maheshwari, P. and Kaur, M.J., 2018, November. Data conversion from traditional
relational database to MongoDB using XAMPP and NoSQL. In 2018 Fifth HCT
Information Technology Trends (ITT) (pp. 94-98). IEEE.
Mehta, M.M. and et.al 2021, April. Smart Office Automation System using IOT: An efficient
database management system. In 2021 5th International Conference on Computing
Methodologies and Communication (ICCMC) (pp. 510-514). IEEE.
Osborne, J.B., 2020. A quantitative evaluation of the performance impact of Type-I
virtualization on a NewSQL relational database management system (Doctoral
dissertation, Colorado Technical University).
Peleshchyshyn, A. and et.al 2018, October. A formal approach to modeling the characteristics of
users of social networks regarding information security issues. In International
Conference of Artificial Intelligence, Medical Engineering, Education (pp. 485-494).
Springer, Cham.
Putra, D.M. and Alfauzain, A., 2021. Design Of Tracer Using Microsoft Access Unit In Medical
Record Primary Health In Padang. International Journal of Engineering, Science and
Information Technology. 1(3). pp.64-74.

Revesz, P.Z., Rashid, M.P. and Tuyishime, Y., 2019, June. The design and implementation of
AIDA: Ancient Inscription Database and Analytics system. In Proceedings of the 23rd
International Database Applications & Engineering Symposium (pp. 1-6).
Roy-Hubara, N. and Sturm, A., 2020. Design methods for the new database era: a systematic
literature review. Software and Systems Modeling. 19(2). pp.297-312.
Sawaneh, I.A. and et.al 2018. Student Dissertation Database Management System: IAMTECH
Sierra Leone as a Case Study. Science and Technology. 4(3). pp.93-99.
Shichkina, Y., Kupriyanov, M. and Shevsky, V., 2018. The application of graph theory and
adjacency lists to create parallel queries to relational databases. In Internet of Things,
Smart Spaces, and Next Generation Networks and Systems (pp. 138-149). Springer,
Cham.
Singh, H., 2019. Interfaces to query relational databases in natural language. IT
Professional. 21(1). pp.67-73.
Syamsiah, N., 2022. The Use Of E-Reservation Open-Source Software (OSS) On Web-Based
Laboratory Scheduling Information Systems In Order To Support Education Laboratory
Management. Simposium Nasional Mulitidisiplin (SinaMu). 3.
Sytnyk, N. and Zinovieva, І., 2019. Evolution of the concept of database organization in the
context of the digitalization of society.
Tian, Y. and et.al 2019. Synergistic graph and SQL analytics inside IBM Db2. Proceedings of
the VLDB Endowment. 12(12). pp.1782-1785.
Utomo, P., Cahyono, S.D. and Tristono, T., 2019, April. Selection of talented archery athletes
using weighted product method. In Journal of Physics: Conference Series (Vol. 1211, No.
1, p. 012037). IOP Publishing.
Wajszczyk, B. and Gruszka, I.M., 2020, February. Analysis of possibilities to increase the
efficiency of the relative database management system using the methods of parallel
processing. In Radioelectronic Systems Conference 2019 (Vol. 11442, pp. 385-398).
SPIE.
Zhidchenko, T.V. and et.al 2021, February. Design of energy-loaded systems using the Neo4j
graph database. In IOP Conference Series: Earth and Environmental Science (Vol. 659,
No. 1, p. 012108). IOP Publishing.
31