@@ -25,6 +25,12 @@ This approach enables the references of attributes as a node in an AST and every
If there is a reference attribute stored in an AST, it represents a direct connection from an any node that is freely distant (non-local) and to itself. The value of the referred node is directly usable in the referring node without accessing any other nodes in the AST. An example of an AST in RAG compared to a traditional AST without RAG is shown in Figure 2.1. \\
Such features of RAG represent advantages over AG, largely in efficiency. It is not necessary to duplicate a same value of a node to another node and semantic functions in a complex data structure can be split into smaller functions which are completely describable in RAG. Consequently, RAG can extend existing grammars and give them more functionalities.
\caption{Architecture of JastAdd}\label{fig:jastadd}
\end{figure}
%JastAdd
An extensible system producing language-based compilers and tools is called, JastAdd. It enables to generate modules and tools based on RAG, where properties of AST to be programmed declaratively. There are already several tools implemented and extended with JastAdd (e.g. ExtendJ, JModelica.org, abc, Soot, McLab, Palacom, etc.(a)) \\
Generally, JastAdd needs two input data to generate classes written in Java. One input data is a file in ast file where AST nodes are described. With this input a class for every non-terminal node is generated and constructed using defined attributes. Other input data is one of more declarative definitions of corresponding attributes and methods. A graphical model of JastAdd is described in Figure 2.2\\
...
...
@@ -55,13 +61,8 @@ aspect Printing{
\end{lstlisting}
%Research questions
With the RAG-based tool generator system, JastAdd, there are two questions this work tries to clarify about automated testing of OpenAPI interfaces. These are following: \\ (i) How can OpenAPI specifications be described in RAG? \\ (ii) Which and how much efficiency can RAGs produce by using them while automated testing of OpenAPI interfaces?
%With the RAG-based tool generator system, JastAdd, there are two questions this work tries to clarify about automated testing of OpenAPI interfaces. These are following: \\ (i) How can OpenAPI specifications be described in RAG? \\ (ii) Which and how much efficiency can RAGs produce by using them while automated testing of OpenAPI interfaces?
