Page 102 - ASBIRES-2017_Preceedings

Madusanka & Nagahamulla
2 LITERATURE REVIEW AND
PROBLEM SPECIFICATION
2.1 Issues with the Current System
In the current system (before adding this
modification to the system) users cannot
save queries and mutations for future use. If
they want to get result for specific query or
mutation they have to always type that
query/mutation. This issue is tolerable
during the development stage when the
number of queries/mutations to run are less.
But during the testing phase users have to
test a large number of features continuously.
Therefore, they have to type the same
queries and mutations again and again
which leads to high time wastage.
Also, when new developers start
working in projects they have to walk
through these queries and mutilation to get
an idea about the work they have to do.
Therefore, they must learn descriptions
about query and mutations and where to use
these details. Furthermore, when the
developers need to share queries and
mutation they have to save them manually
or use separate systems. This can lead to
time wastage.
2.2 Solution by Proposed System
As a solution to the above problems we
propose to include a save feature to the
existing system, using which the user can
save quires and mutations. These queries and
mutations can be reused so the unnecessary
typing will be reduced resulting in reduced
time wastage.
Also, user can easily access saved details
increasing the efficiency of the software
development process. When users save
queries and mutations they can enter
description about them. Using these
descriptions even a new developer can easily
get idea about the quires and mutations.
Another advantage of this proposed
system is that the developers can share
saved quires and mutation. When one
developer saves a query/mutation, it is saved
in a server and the others can use that. As a
lot of companies use GraphQL for their
92
software development, they can also use this
proposed system because this system act as
modification for existing system.
2.3 Existing Similar Systems
MySQL provides similar facilities for
their query editor area.User can save queries
as bookmarks, and can access them. These
bookmarks are valid for specific database
and specific tables only.
3 METHODOLOGY
3.1 Overview of the System Architecture
This prospered system is a modification
of the existing system. User can see the
modification on the same system but it acts
as a separate system because it is easy to
update, maintain, do modification and add
new features easily. To enable these two
systems to work as one system NGINX is
used. NGINX is a free, open-source, high-
performance HTTP server and reverse proxy,
as well as an IMAP/POP3 proxy server.
NGINX is known for its high performance,
stability, rich feature set, and simple and low
resource consumption. Using Nginx helped
to connect separate servers. Therefore,
modified system can easily interrogate to
system. Therefore, even if the new
modification part fails the original system
can work without affecting the system, so
that the software development process is not
affected. The architecture of the proposed
system is described in Figure 1.
Figure 1: System architecture