Commit 7dd7716f authored by Pietro Braghieri's avatar Pietro Braghieri
Browse files

Update README.md

parent d5304430
......@@ -38,11 +38,15 @@ These topics have [specifications](https://open-services.net/specifications/) ca
For the integration with our tools, we select the [Automation](https://archive.open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/index.html) specifications.
The OSLC Automation domain define resources as `Automation Plan`, `Automation Request` and `Automation Result`; they are in relationship as shown below
![](/docs/AutomationResourcesRelationship.png)
[<img src="/docs/AutomationResourcesRelationship.png" width="600">](/docs/AutomationResourcesRelationship.png)
A OSLC Service Provider based on the OSLC Automation domain has been realized.
The figure below shows the interactions between the OSCL Client ([CHESS](https://projects.eclipse.org/projects/polarsys.chess) in this example) and the Service Provider:
![](/docs/OSLC_FBK_Tool_Interactions.png)
[<img src="/docs/OSLC_FBK_Tool_Interactions.png" width="600">](/docs/OSLC_FBK_Tool_Interactions.png)
The integration and implementation of the tool chain through OSLC is realized by a web application server (i.e. [Tomcat](https://tomcat.apache.org/)) that runs the OSCL Registry (that lists the available services) and the OSLC Service Provider that interacts with the analysis tools as shown below:
[<img src="/docs/OSLC_FBK_Tool_WebApplication.png" width="600">](/docs/OSLC_FBK_Tool_WebApplication.png)
---
### Dependencies
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment