HistoryViewLinks to this page 2014 May 21 | 04:29 pm


  1. Review the Transformation scenarios from Engineering Activities Matrix

    • As a basis for discussion, Jad has reviewed the scenarios and made the following observations: From the transformation scenarios reviewed, I can identify 3 kinds of transformations:
      1. Transformations where the integration need focuses on automating the steps required to perform the transformation - control integration. typical example is the scripting of code generation of FPGA using TCL.
        • This ought to be best handled using the Automation Server.
      2. model/data transformations where the integration need focuses on transforming data from 1 tool to another - data integration. Example, migrate from a UML model to a Simulink model.
        • Given that the focus is on data, should there be better direct support for this data integration in OSLC?
      3. A specific example of the above data-focused transformation is when migrating the same type of artefacts from 1 tool to another - equivalent tool.
        • In this case, would be more reasonable to use OSLC services instead of a transformation engine?
  2. Discuss the AM transformation scenario AM transformation scenario

    • quick summary and questions - based on a reading of the scenario by Jad
      • 2 (new?) resources were defined in the scenario:
        • Entity Generator Resource - Entity Generator Resource is a resource that represents and manages a long running transformation of Entities to source code.
          • references a set of “oslc_am:EntityResource”s
        • Entity Resource - Entity Resource is a model element resource that represents an Entity. It has simple properties (name/type) and can be transformed into source code.
          • = an AM Resource? What is the relationship???
      • Scenario summary:
        • Loops through the oslc_am:EntityResource”s of a Entity Generator Resource
        • Produce a sourc file per EntityResource?
      • How do the defined resources relate to the Automation resources? (automation plan, automation request, automation result)
      • The looping through entities to produce source code - as defined in this scenario - does not seem to follow the Automation specification mechanism where a request is created to run the transformation, and producing a result.


  • An analysis of the transformation scenarios on the agenda were presented by Jad. (See agenda for the details)
  • Unclear how mature the AM transformation is. We can only speculate on the meaning of the scenario.
    • Jad will followup with Steve to see the status of the AM scenario.
  • Frederic will also try to invite someone from Mbat (AIT) that has implemented a transformation using the Automation Server & Asset Management, to present their work at the next meeting.


Rainer & Frederic, & Jad