Tactics. There will be many “drivers” that generate demand and desire for the Nouveau Kiskeya project and each driver will have its own implementation plan clearly outlined in the Nouveau Kiskeya Sales & Marketing Plan. They are generally described as follows: o Resort Sales & Marketing o Vacation Destination & Travel o Ecotourism o Sports Marketing (Golf / Tennis / Soccer) o Heavy Industry Trades (jobs) o Residential Ownership Opportunities o Diaspora Homecoming
Tactics. 1. Acquire existing real estate or mortgage brokerage companies.
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, ...
