Middleware Project. Development of a common API between SL and ST divisions. Minutes of the meeting held on Friday, August 11th

Some aspects of the collaboration were discussed in the first place. ST highlighted the point that they do not have resources available to develop the API, but they are very interested in participating in the design.

The project team agreed that the first point to be treated in the meeting should be the User Requirements.

Following is the first draft of the User Requirements that the API shall accomplish. The requirements are grouped following the ESA PSS 05 standards. All the categories are listed, even when there are no requirements in the category. This will allow the group to complete them in the future.

Capability Requirements

Capacity

· The API shall publish/subscribe data to subjects. These subjects shall be defined following a hierarchical structure.

· The user should have the possibility to publish/subscribe any subject in this hierarchical structure. The API shall publish/subscribe automatically all the subjects below this subject. If the root subject is chosen, the full set of subjects shall be used. If a final subject is chosen, only this subject shall be used.

· The user shall be able to send and receive any type of data

· Two subscription methods must be implemented:

· Method 1. A client subscribing a subject will receive data only if the data change.

· Method 2. A client subscribing a subject will receive immediately the value of all the data belonging to the subject.

· Only the client that asks for a particular data will receive it.

· Every data diffused by the API will have a timestamp. This timestamp shall be the time when the data were acquired.

· (TO BE CONFIRMED) The API shall have the possibility to filter non-desired data (data filtering).

Speed

· (TO BE CONFIRMED) The API shall be able to send data at the ratio of ?

Accuracy

No particular requirements

Constraint Requirements

Communication interfaces

No particular requirements

Hardware interfaces

No particular requirements

Software interfaces

No particular requirements

Human computer interaction

No particular requirements

Adaptability

· The API shall not be related to any particular MOM. It should be possible to change the MOM without any major change.

Availability

No particular requirements

Portability

No particular requirements

Security

· The API shall not implement any security check. If this is necessary, it must be the application using the API that should do it.

Safety

· The subjects that are used to publish/subscribe data shall be controlled; this means only registered subject shall be authorised.

· (TO BE CONFIRMED) The API shall have the possibility to send data using a secure connection (guaranteed message delivery).

· (TO BE CONFIRMED) The API shall have the possibility to send data using a durable subject.

Standards

No particular requirements

Resources

No particular requirements

Timescales

No particular requirements