Commit adefc88f authored by Pietro Braghieri's avatar Pietro Braghieri
Browse files


parent 3fd2dc2d
......@@ -6,14 +6,17 @@ These topics have [specifications]( ca
For the integration with our tools, we select the [Automation]( specifications.
The OSLC Automation domain define resources as `Automation Plan`, `Automation Request` and `Automation Result`; they are in relationship as shown below
[<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]( in this example) and the Service Provider:
[<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]( 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)
The analysis tool functionalities are be available by means of Automation Plans; the title attribute `<dcterms:title>` of the Automation Plan selects the tool functionality.
Supports Markdown
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