The QA Navigation SLM Architecture
The QA Navigation SLM is not, like so many other products, a monolithic block, but a collection of independent tools, which help the user to accomplish his mission. Therefore you can choose which application you wish to use and where you want to continue to use your legacy applications.
The SLM is shipped with its source files, allowing you to change the application to meet your requirements. Its architecture of a layered set of smart software modules allows it to execute any adaptation to individual requirements with ease.
The SLM is adapted to your organisational values, project values and infrastructure settings simply by changing the relevant configuration files. The wording of the SLM can be change to use your preferred wording.
XML Data Storage
All produced data are coded as XML and stored as such. This allows it to phase in foreign data, which follow the rules of the supplied DTDs, at any time or provide export data, through using, for instance, XSLT, to convert the data into any format required. This allows to integrate the QA Navigation SLM easily into any existing application architecture.
To avoid redundancy, but provide maximal flexibility at the same time the individual documents are provided with a unique, unambiguous ID and linked amongst each other by the ID. Hypertext-like links in the non-HTML applications allow to jump to the linked document and display it with the according application.
Foreign documents can be integrated to the application in the same way.
Due to the architecture of the QA Navigation SLM applications the data can be stored centrally in a common database, or dispersed on different computer, to be merged into a common database and then distributed again. This way the data for preparing executing the test can be collected independently without the necessity to work in a common network.
The Report Manager Architecture
The implementation of the Report Manager is based on Jakarta-Tomcat as a Web server and My SQL for data storage, but is not limited to that. The JSP/Servlet part is implemented according to the J2EE standard, data access is managed through the JDBC interface, independent from the data base provider.
The Test Workbench Architecture
The Test Workbench is a .Net based fat client application, using My SQL for data storage, but not limited to that. The implementation is independant from any specific libraries, thus it can be adapted by using Visual Studio Express.