Deployment Model

This model shows a static view of the run-time configuration and the main components that run on those nodes. The first of them is Web Container where SEOR Web Services are deployed providing a full video conference functionality [1]. The second node is an OSGI container composed of two different kinds of bundles; the consuming type interacts with the Web Services making requests and handling the responses, and the second type is in charge of orchestrating and managing the data provided by the ones before. The third node is a simple Database server used by the SEOR web services. The diagram below depicts the system overview described before.

Component Model

The model shows the dependencies among the main software components which are basically he OSGI bundles mentioned in the previous section. On the left side of the diagram are shown all the consuming bundles. Each one performs a specific Web Service consumption providing the data obtained to the orchestrating bundles, which are on the right side. OSOTrigger looks for devices and request permission to an extern entity meanwhile OSO carries on the full video conference establishment.

File:Component diagram.png

Class Model

The class model describes the entities represented by classes, their relationships and the overall hierarchy. The main classes are OSOTriggerImpl and OSOImpl which interact with the others using the each corresponding interface. Launcher access to OSOTrigger to start up the system and the “PortTypeProxy” classes contain the WS stubs and bindings.

Bundle Structure

All bundles implemented are structured in three packages:

• In the “Bundle Name” package is defined the activator class, which registers the interface reference so others bundles can get the exported object and run the service.
• The “Service” package contains the interface with the methods exposed. It’s the service itself.
• The “Impl” package comprises the classes that implement the service.

Impl is an inner package of Service so when the Manifest file exports the interface, the service implementation remains hidden.