D6.1 VICINITY Integrated Prototype
This deliverable describes the integration tests of individual adapters, specifically the connection between the adapters and VICINITY. This involves running test cases and resolving any bugs that are encountered. The significance of this deliverable is establishing the use cases described in T5.2. The test cases described were instrumental in completing the use cases in a timely manner; multiple bugs were solved, resulting in improved data flow from the adapters and improved reliability in registering new cases with VICINITY.
The main points of the deliverable include making value added services available to VICINITY, ensuring the data from adapters reaches their intended targets, and closing bugs that impede the completion of the tasks from T5.2. All sites achieved functional adapters, enabling multiple VASs. Consequently, VASs were deployed on test servers, allowing for a more complete testing of features. Furthermore, the tools needed for P2P connections were enabled.
This deliverable covers the merging of aspects of multiple work packets, especially WP3, WP4 – “Client/Server Implementation” and WP1 - “Requirements Specification”. Much of the effort in the document encompasses validating the previous work on the VICINITY client/server infrastructure and the marriage of individual nodes with VICINITY proper. The work done satisfies use cases, on user experience for setting up adapters for example, outlined in documents such as D1.5.
In layman’s terms (in words that someone who is not an expert can understand), each adapter from the different sites needs to be able to be available through VICINITY and needs to communicate using VICINITY infrastructure. This implies running test cases for the different sorts of communication the adapters may use, be it node-to-node, discovering available adapters, or event subscriptions. Once adapters behave as expected when engaging with VICINITY, they can be featured in use cases, or used for further development by the pilot sites or Open Project partners.
When the adapters are all integrated with VICINITY, they will encompass the overarching integrated VICINITY prototype. That is to say, the prototype adapters will be able to provide their services over VICINITY once they are integrated. Here, “integrated” means connected to VICINITY, communicating with nodes through VICINITY, and sending and receiving legible data.
In conclusion, the highlights of the deliverable encompass the finishing touches of working adapters and node structures. Test cases were run, problems were identified and documented before being solved. The overall results include completed adapters, reliably registering events and VASs, and node to node communication.
The tests and validation of integration of components will be continuously updated each time a new version of Core Components is released, and eventually bugs will be triggered and results logged in the systems and methodology developed in this task.