Tactics Sample Clauses

Tactics. A tactic defines the steps of adaptation to be carried out in order to achieve the objective defined by a calling strategy. As in Stitch [28], a tactic cannot call other tactics or strategies, just rt-VIL operations or rt-VIL rules. Akin to strategies, the syntax of the tactic header follows the syntax of VIL rules, which is inspired by a combination of OCL [108] and make [132]. A tactic can have a precondition [28] and an effect specification [28] (we represent this as the post- condition of a tactic in rt-VIL). A tactic is enabled if its precondition holds. A tactic is successful, if its operations are executed successfully and its (optional) post-condition holds. So far, tactics are rather similar to VIL rules. In contrast, tactics serve as a basis for recording the QoS impact through strategies. Further, the predefined rt-VIL rule Boolean validateTactic(Configuration config) is called at the end of a (so far) successful tactic in order to validate the results of the executed operations. By default, this predefined rt-VIL rule performs runtime reasoning (on the changed variables) utilizing the runtime version of EASy- producer. This method can be overridden for other forms of validation, e.g., for traditional architecture-based adaptation. Syntax: tactic name (ParameterList) post : pre { // local variable declarations // runtime configuration changes, rule calls // alternative or iterative execution } Description of syntax: • The keyword tactic indicates on this level the declaration of a tactic. • The name allows identifying the rule for explicit rule calls or for script extension. • The parameterList specifies explicit parameters which may be used as arguments for precondition rule calls as well as within the rule body. Parameters are given in terms of types and parameter names separated by commas if more than two parameters are listed. Parameter must either be bound by the calling strategy. • The optional post-condition post specifies the expected outcome of the tactic execution in terms of a logic expression akin to the effects specification in [28]. • The optional precondition pre specifies whether the tactic is considered for execution at all (in addition to the precondition in the strategy). If neither pre- nor post-condition are given, also the separating colon can be omitted. • The body of the strategy is specified within the following curly brackets. Local variable declarations, rule calls, alternative and looped execution and, in particular, ...
Sample 1
AutoNDA by SimpleDocs
Tactics. 1. Acquire existing real estate or mortgage brokerage companies.
Sample 1

Related to Tactics

  • Strategies The ESC will seek to achieve employment stability strategies as follows: - current and multi-year strategies should be developed within the resources available. Such strategies could include, but not necessarily be limited to, planning, retraining, identifying ways of determining employees= skills, training and experience previously achieved, early retirement, voluntary exit programs, alternative assignment, secondment, employee career counselling, job sharing, job trading, job shadowing, and professional development; - discussions between the parties which explore these possible strategies would assist in the development of appropriate enhancements to Employment Stability; - data which is relevant to employment stability shall be made available to both parties.

  • Product Development Attach all requested documentation and attach additional pages as necessary. For all requirements include efforts of all Sublicensees. If not applicable, please so indicate by N/A.

  • Strategy As an organization without operational services (fuel, maintenance, etc.), and in consideration that the majority of potential issues come from boat maintenance whereby the boats are personal property, the predominant strategy will be the minimization of on-site waste. With this approach, the organization will have minimal potential impact on the environment and reduce regulatory risk. To accomplish this, requirements will be established by policy, periodic communications shall occur, and audits will be utilized to provide feedback for improvement.

  • Marketing Vendor agrees to allow TIPS to use their name and logo within the TIPS website, database, marketing materials, and advertisements unless Vendor negotiates this term to include a specific acceptable-use directive. Any use of TIPS’ name and logo or any form of publicity, inclusive of press release, regarding this Agreement by Vendor must have prior approval from TIPS which will not be unreasonably withheld. Request may be made by email to xxxx@xxxx-xxx.xxx. For marketing efforts directed to TIPS Members, Vendor must request and execute a separate Joint Marketing Disclaimer, at xxxxxxxxx@xxxx-xxx.xxx, before TIPS can release contact information for TIPS Member entities for the purpose of marketing your TIPS contract(s). Vendor must adhere to strict Marketing Requirements once a disclaimer is executed. The Joint Marketing Disclaimer is a supplemental agreement specific to joint marketing efforts and has no effect on the terms of the TIPS Vendor Agreement. Vendor agrees that any images, photos, writing, audio, clip art, music, or any other intellectual property (“Property”) or Vendor Data utilized, provided, or approved by Vendor during the course of the joint marketing efforts are either the exclusive property of Vendor, or Vendor has all necessary rights, license, and permissions to utilize said Property in the joint marketing efforts. Vendor agrees that they shall indemnify and hold harmless TIPS and its employees, officers, agents, representatives, contractors, assignees, designees, and TIPS Members from any and all claims, damages, and judgments involving infringement of patent, copyright, trade secrets, trade or services marks, and any other intellectual or intangible property rights and/or claims arising from the Vendor’s (including Vendor’s officers’, employees’, agents’, Authorized Resellers’, subcontractors’, licensees’, or invitees’) unauthorized use or distribution of Vendor Data and Property.

  • Outreach Not less than 30 days prior to the opening of bids or the selection of contractors, the Agency-Assisted Contractor or Contractor shall:

  • Processes Any employer, employee, trade union or employer’s association may at any point in time apply for an exemption from any of the provisions of this Collective Agreement. The applicant is required to complete and submit in writing with the relevant office of the Council, a fully and properly completed prescribed application for exemption form, accompanied by all relevant supporting documentation.

  • Operational All expenses for running and operating all machinery, equipments and installations comprised in the Common Areas, including elevators, diesel generator set, changeover switch, pump and other common installations including their license fees, taxes and other levies (if any) and expenses ancillary or incidental thereto and the lights of the Common Areas and the road network.

  • Personnel Information Employee shall not divulge or discuss personnel information such as salaries, bonuses, commissions and benefits relating to Employee or other employees of Employer or any of its subsidiaries with any other person except the Executive Committee and the Board of Directors of Employer.

  • Budgeting The budget set out in the Consortium Plan shall be valued in accordance with the usual accounting and management principles and practices of the respective Parties.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

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