Model Exchange Sample Clauses

Model Exchange. Procedures During the second year of the project, support for models exchange between different tools has been developed by the tool supplier partners of the MAENAD project. The developed features provide means to transform a model described in a proprietary XML format to a “standardized” XML format (EAXML) and re-import it back. Each tool supplier adopts a different solution, based on intermediate transformation steps, and provide user friendly interface to hide the complexities of the process. EAST-ADL XML file can be generated natively by the tools starting from any Hardware Architecture model. The generated EAXML file reflects the original structure preserving hierarchy, package structure and the type-prototype pattern. One solution adopted involves the use of XLST language and the related processor. The XSLT is a XML-based language used for the transformation of XML documents. The XSLT processor takes one or more XML source document and one or more XSLT style sheet modules. The XSLT processor apply the rules, instructions and directives provided through the XSLT style sheet modules, and generate a new output document based on the contents of the existing ones, leaving the original files unchanged. In this context, the EAXML import is achieved through an external tool (EAXML processor) that takes as inputs the EAXML file and an XSLT transformation script (EAST_ADL_import.xslt) and generate a file format natively supported by the tool. The following picture explain the export/import transformation path Figure 5-40. export/import transformation path for EAXML file through XSLT processor. A second approach relies on the use of ATL (Atlas Model Transformation language). The source model, expressed using a proprietary XML format, is processed together with the source meta-model and the target meta-model by the ATL processor. Figure 5-41. import/export transformation path through ATL. Evaluation Results Import/export functionalities have been tested on a subset of the “Propulsion” subsystem. The EAXML generator has been activated using the launcher button on the main MetaEdit+ toolbar As result, the embedded EAXML generator has created the EAXML file starting from the input model. Figure 5-42. Transformation of HDA propulsion subsystem to EAXML format.
Sample 1
AutoNDA by SimpleDocs
Model Exchange. The MAENAD Workbench heavily relies on tools and plugin from different tool vendors and institutions. Support for a neutral data exchange format is recommended to grant interoperability between tools and achieve a higher acceptance of the project outputs. An XML-based exchange format (EAXML), allows tools to exchange EAST-ADL models between UML2 tools and an AUTOSAR-compliant XML format. The schema for the EAXML exchange format is automatically generated from the EAST-ADL meta-model. At the present, activities on this field are planned by the different tool chain participants to support import/export capabilities to EAXML exchange format Key points for the analysis Bidirectional and consistent exchange of information between tools that belong to different tools provider. Analysis strategies ITEM Evaluation Steps Model Exchange between MetaEdit+ and Papyrus development environments 1.a: Export of an existing Use Case model to EAXML from MetaEdit+ 1.b: import the EAXML file in Papyrus. 1.c: Changes of some trait of the imported model in the Papyrus environment 1.d: Export of the modified model to EAXML from Papyrus 1.e:import the EAXML file in MetaEdit+ 2.a: Export of an existing Use Case model to EAXML from Papyrus 2.b: import the EAXML file in MetaEdit+. 2.c: Changes of some trait of the imported model in the MetaEdit+ environment 2.d: Export of the modified model to EAXML from MetaEdit+ 2.e:import the EAXML file in Papyrus Evaluation: consistency check between the models in the two different development environment, absence of loss information, changes on the model shall be correctly reflected in the two environments
Sample 1

Related to Model Exchange

  • Shift Exchange The Employer and the Union agree that shift exchanges are a useful process to allow employees more flexibility and improved work/life balance. Employees within an institution who have the same job classification will be allowed to exchange full shifts for positions in which they are qualified. The shift exchange process will not be used to circumvent the bid system or the supervisory chain of command. Shift exchanges will be in accordance with the following:

  • Shift Exchanges In no event shall any overtime be payable as a result of employees voluntarily exchanging shifts.

  • Data Exchange Each Party shall furnish to the other Party real-time and forecasted data as required by ERCOT Requirements. The Parties will cooperate with one another in the analysis of disturbances to either the Plant or the TSP’s System by gathering and providing access to any information relating to any disturbance, including information from oscillography, protective relay targets, breaker operations, and sequence of events records.

  • Trunk Data Exchange 65.9.1 Each Party agrees to service trunk groups to the blocking criteria in Section 64.3.4 in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty- one (21) Day study period. The Parties agree that twenty-one (21) Days is the study period duration objective unless mutually agreed otherwise. The study period will not include a holiday.

  • Currency Exchange All payments under this Agreement shall be payable, in full, in Dollars, regardless of the country(ies) in which sales are made. For the purposes of computing Net Sales of Licensed Products that are sold in a currency other than Dollars, such currency shall be converted into Dollars as calculated at the rate of exchange for the pertinent quarter or year to date, as the case may be, as used by Celgene in producing its quarterly and annual accounts, as confirmed by their respective auditors.

  • Trading With respect to the securities and other investments to be purchased or sold for the Fund, Subadviser shall place orders with or through such persons, brokers, dealers, or futures commission merchants (including, but not limited to, broker-dealers that are affiliated with AEFC or Subadviser) selected by Subadviser; provided, however, that such orders shall be consistent with the brokerage policy set forth in the Fund's Prospectus and SAI, or approved by the Board; conform with federal securities laws; and be consistent with securing the most favorable price and efficient execution. Within the framework of this policy, Subadviser may consider the research, investment information, and other services provided by, and the financial responsibility of, brokers, dealers, or futures commission merchants who may effect, or be a party to, any such transaction or other transactions to which Subadviser's other clients may be a party.

  • Open Market Purchases Failure of the Contractor to Perform within the time specified in the Contract, or failure to replace rejected or substandard Goods or fulfill unperformed Services when so requested and as the Contract provides or allows, constitutes a breach of the Contract and as a remedy for such breach, such failure shall constitute authority for DAS, if it deems it to be necessary or appropriate in its sole discretion, to Terminate the Contract and/or to purchase on the open market, Goods or Services to replace those which have been rejected, not delivered, or not Performed. The Client Agency shall invoice the Contractor for all such purchases to the extent that they exceed the costs and expenses in Exhibit B and the Contractor shall pay the Client Agency’s invoice immediately after receiving the invoice. If DAS does not Terminate the Contract, the Client Agency will deduct such open market purchases from the Contract quantities. However, if the Client Agency deems it to be in the best interest of the State, the Client Agency may accept and use the Goods or Services delivered which are substandard in quality, subject to an adjustment in price to be determined by the Client Agency.

  • CLEC (Competitive Local Exchange Carrier Any Local Exchange Carrier other than Frontier that is operating as a Local Exchange Carrier in the territory in which Frontier operates as an ILEC in the Commonwealth of Pennsylvania. Onvoy is or shortly will become a CLEC.

  • Quotation The Company will use its best efforts to include, subject to notice of issuance, the Common Shares on the Nasdaq National Market.

  • Voluntary Shift Exchange When operational requirements permit, employees may exchange shifts among themselves provided that:

Time is Money Join Law Insider Premium to draft better contracts faster.