Inter-Aspect Concepts Sample Clauses

Inter-Aspect Concepts. ‌ In the previous sections the concepts for each Aspect have been described, without any relations between the Aspects. Such relations are however necessary in order to describe the different elements in an integrated manner. Therefore some additional Inter-Aspect relation concepts are introduced: Concept Specialisation of Source(s)  Target(s) Description influences (influenced by) implication Procedural element  Motivating value It implies that a Procedural element leads to the change of a Motivator value. This change can be positive or negative (e.g. create or consume). Additionally it should also allow stating a quantity for the change. Through this the costs and duration of an Action can be denoted. An example would be “Action X negatively influences 500 (quantity) € (value)” to describe that performing an Action costs 500€. requires (required by) implication Procedural element  Participant template, Participant instance It implies the use of a Participant in the execution of a Procedural element. Typically this also means that the used Participant instance is blocked for the time being. Under circumstances it can still be possible to perform the Procedural element even when the Participant is not available (e.g. when it was only necessary to improve efficiency). If the same Participant instance is assigned to different procedural elements, then it means that the same reality instance (e.g. the same human, the same data set) should be reused throughout one enactment of those elements. This is not guaranteed when using Participant templates, as they represent a variability space and different reality instances fitting a template could be involved during the same enactment. Additionally the requires relation can be described similarly to the permission rules (see end of section 2.4.2). Through this access requirements can be stated on which Concept Specialisation of Source(s)  Target(s) Description the permission rules should be based. has responsible (responsible for) requires Procedural element  Liable entity template, Liable entity instance A specialisation of requires, indicating the Liable entity that is responsible for a Procedural element. The approval of the responsible is required, which can be for example verbally, in writing or by a general rule. A Procedural element should have only one assigned responsible Liable entity. has performer (performs) requires Procedural element  Participant template, Participant instance A specialisation of...
Sample 1
AutoNDA by SimpleDocs

Related to Inter-Aspect Concepts

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Creative Commons Attribution-Non-Commercial-NoDerivs License The Creative Commons Attribution Non-Commercial-NoDerivs License (CC-BY-NC-ND) permits use, distribution and reproduction in any medium, provided the original work is properly cited, is not used for commercial purposes and no modifications or adaptations are made. (see below) Use by commercial "for-profit" organizations Use of Wiley Open Access articles for commercial, promotional, or marketing purposes requires further explicit permission from Wiley and will be subject to a fee. Further details can be found on Wiley Online Library xxxx://xxxxxxx.xxxxx.xxx/WileyCDA/Section/id-410895.html Other Terms and Conditions:

  • Curriculum Development This includes the analysis and coordination of textual materials; constant review of current literature in the field, some of which are selected for the college library collection, the preparation of selective, descriptive materials such as outlines and syllabi; conferring with other faculty and administration on curricular problems; and, the attendance and participation in inter and intra-college conferences and advisory committees.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to InterGlobe. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for InterGlobe (e.g. hairpinning):

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

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