Choice of modelling languages and tools Sample Clauses

Choice of modelling languages and tools. The information model is intended to be generic, i.e. applicable for all use cases of the project. This means that the information model will need to be a high level model. The main aim is to show the relationships between different subcomponents of the architecture. For the actual implementation of the components, specialized models containing the relevant details of the specific use case will be developed. These more specialized models will be created using RDF, whereas the high level information model, presented here, is mainly done in UML. The reasoning behind this choice of different modelling languages is both pragmatic (availability of and familiarity with good UML tools) and based on architectural concerns (some software components of the Smart Vortex suite relies on RDF-based representations). Process models are mainly designed using BPML/BPMN. The value oriented process models are expressed in a syntax with concepts such as sub-process and value created by processes, as described by Penker et al. [6]. Since different modelling tools and frameworks have different strengths and weaknesses, the approach for the design of the higher level information model is to promote maximum flexibility by allowing a heterogeneous set of tools, frameworks and languages, rather than to restrict the modelling to a common framework. At the more specialized semantic model levels (described in D2.2 and D2.3), a more homogeneous framework based on RDF will be used.
AutoNDA by SimpleDocs

Related to Choice of modelling languages and tools

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION AND DISASSEMBLY You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • Notification of Modifications of Licensed Materials From time to time Publisher may add, change, or modify portions of the Licensed Materials, or migrate the Licensed Materials to other formats. When such changes, modifications, or migrations occur, the Licensor shall give notice of any such changes to Licensee as soon as is practicable, but in no event less than sixty (60) days in advance of modification. Such a notice may also be given directly by the Publisher to the Licensee. If any of the changes, modifications, or migrations renders the Licensed Materials substantially less useful to the Licensee, the Participating Institutions or their Authorized Users, the Licensee may seek to terminate this Agreement for breach pursuant to the termination provisions of this Agreement in Section XI, below.

  • Effect of Addenda, Bulletins, and Change Orders No special implication, interpretation, construction, connotation, denotation, import, or meaning shall be assigned to any provision of the Contract Documents because of changes created by the issuance of any (1) Addendum, (2) Bulletin, or (3) Change Order other than the precise meaning that the Contract Documents would have had if the provision thus created had read originally as it reads subsequent to the (1) Addendum, (2) Bulletin, or (3) Change Order by which it was created.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Technical Bulletins A Technical Bulletin (TB) will be used to explain updated processes, provisions or monitoring requirements as Florida Housing receives updates, clarification and additional guidance with respect to the CRF funds. TBs will also be used to clarify, discuss, interpret, and provide guidance for contract administration issues related to this Agreement. TBs will be posted at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/about-florida-housing/florida- housing's-coronavirus-relief-fund, and Grantee is encouraged to regularly check for TBs.

  • Technical Data For the purpose of this Agreement, "TECHNICAL DATA" shall mean all information of the Company in written, graphic or tangible form relating to any and all products which are developed, formulated and/or manufactured by the Company, as such information exists as of the Effective Date or is developed by the Company during the term hereof.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Contract Language The following language shall be included in contracts for City projects between the Consultant and any Subcontractors, vendors, and suppliers: Contractor shall not discriminate on the basis of race, gender, gender expression, gender identity, religion, national origin, ethnicity, sexual orientation, age, or disability in the solicitation, selection, hiring, or treatment of subcontractors, vendors, or suppliers. Consultant shall provide equal opportunity for Subcontractors to participate in opportunities. Consultant understands and agrees that violation of this clause shall be considered a material breach of the contract and may result in contract termination, debarment, or other sanctions.

  • Warning Language Where required, Xxxxxxxx shall provide Proposition 65 warnings on the Product’s label as follows:

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