Patterns Sample Clauses

Patterns. Absences and/or lateness that consistently occur (a) before and/or after scheduled days off including holidays, float holidays and vacations (b) on scheduled weekend shifts and (c) on days for which requested time off was denied and. (d) the same day of the week or month. The University retains the discretion in determining what constitutes a pattern. Disciplinary action may be taken if the absences within the rolling twelve-month attendance review period exceed the grace period, or when the above patterns have been identified. Twelve (12) hour staff members are not subject to disciplinary action for pattern absences. However, staff members who have an unscheduled weekend absence can be required to make up the weekend absence.
Patterns. No adjacent losing tickets have identical play symbols in the same locations. - No more than one winner of L.50 or above appears in a pack. - No consecutive string of losing tickets in a pack exceeds three times the overall odds of the prize structure, or seventeen consecutive losing tickets. - Four or more like play symbols do not appear on a ticket. - Losing tickets contain approximately the following quantities of pairs of play symbols Three pairs of play symbols - 40% of losing tickets Two pairs of play symbols - 40% of losing tickets One pair of play symbols - 20% of losing tickets - No ticket has more than one occurrence of three identical play symbols. - Losing tickets use the play symbols in the following approximations:
Patterns. In urban areas, columns may be finished with cast-in patterns and textures that recognize local preferences and/or historical characteristics. Phoenix Light Rail Texas Highway Patterns and Textures
Patterns. Architectural patterns describe coherent frameworks that help guide implementations that adhere to the architectural principles. California will base its statewide technical architecture on these patterns:  Service Oriented Architecture (SOA). SOA is a well understood architectural pattern that defines services implemented by service providers and utilized by service consumers. Interactions between providers and consumers of services are standardized through messaging protocols, enabling widespread interoperability among distributed systems.  Enterprise Service Bus (ESB). An ESB is an architectural pattern often used to implement SOA. It provides a mediation layer that has advantages when implementing an SOA, including translating various lower-level messaging formats so that service providers and consumers are less dependent upon specific formats, and the use of a service registry to enable late binding between service providers and consumers. These patterns improve interoperability of an SOA.  A Peer to peer services topology will be considered. This pattern specifies that there are no constraints on the connectivity allowed between service providers and consumers. This is the most flexible connectivity pattern, enabling any service consumer to connect to any service provider. Note that more constrained connection topologies (for example a hierarchical connectivity topology that forces all service consumers to connect through a specified set of network nodes) can be imposed through policy.
Patterns models and wall charts for use exclusively for demonstrating and teaching purposes in public or private educational, scientific or cultural institutions approved by the competent authorities of the importing country for the purpose of duty-free admission of these types of articles. Annex D Scientific instruments or apparatus Scientific instruments or apparatus, intended exclusively for educatio- nal purposes or pure scientific research, provided:
Patterns. Patterns jigs, tooling and moulds will be supplied on loan to the Seller where necessary, but shall be returned to the Purchaser in the same condition as originally received by the Seller from the Purchaser fair, wear and tear excluded. The Seller shall remain solely responsible to ensure that the patterns, jigs, tooling and moulds provided by the Purchaser conform to the requirements of the order and indemnifies the Purchaser against any cost, expense or damages, arising from the use of a faulty pattern by the Seller. Should patterns, jigs, tooling or moulds be returned in a damaged or incomplete condition, any repair or replacement charges will be for the Seller’s account.
Patterns. Architectural patterns describe specific system architectures, both in terms of structural organization and behaviour, which address particular needs of the system. We consider the concepts of architectural patterns and architectural styles (introduced in Section 2.2.5) to be synonymous. An example of an architectural pattern would be one that addresses a particular type of control for a system (for example, centralised control), or the use of shared resources in the SoS. The use of architecture patterns tends to be limited to software engineering, though their use has been proposed in systems engineering [Cloutier&07]. To date the use of architecture patterns in systems engineering is at its infancy, and in SoS architectural patterns is considered an important challenge [TAS&12]. Patterns tend to appear through the repeated development of software/systems/XxXx. We focus both on existing patterns from literature – and consider how they may be applied in a SoS, where the basic architectural elements of the patterns are the constituent systems of an SoS – and develop several new architectural patterns. We begin to consider those architectural patterns, which may be used at the SoS- level. For example, in this work the model-view-controller pattern [Reenskaug79] and the patterns described by Gamma et al. [Gamma et al 1995] consider paradigms relevant only to software and do not translate to SoS. As such, in this deliverable, we consider a set of patterns to include those identified in our survey of SoS examples in Section 3.2:  Centralised  Service Oriented  Publish-Subscribe  Pipes and Filters  Supply Chain  Blackboard  Infrastructure Grid  Reconfigurable Control Architecture When considering such architectural patterns, we also consider how the patterns relate to the architecture principles and SoS types outlined in Section 2 and 3. Finally, it’s not our expectation that an SoS will exhibit one pattern only. Most XxXx are capable of implementing multiple patterns at once. For example, a Publish-Subscribe pattern may be employed along with a Reconfiguration Control Architecture.
Patterns. This contract shall include all longitudinal lines. Lines shall be (6”) and (12”), dotted, skip or solid, as required herein or as specified by the engineer. The typical skip pattern is a (40 ft.) cycle made up of a (10 ft.) painted surface and a (30 ft.) space. The typical pattern for dotted lines (ET’S) is a (8 ft.) cycle made up of a (2 ft.) painted surface and a (6 ft.) space. The Project Coordinator may require other patterns.
Patterns. (a) Employees would receive a date off: in two week period in a three week period No employees shall be credited or debited a designated day off as a result of transfer The designated day off would be scheduled adjacent to the employee's day off and day of rest and predetermined on a yearly basis wherever possible. The terms and conditions of the Association will be applicable to this work week arrangement, except the following: Article Leave of Absence
Patterns. ‌ Design patterns codify “best practices” and hence are at the heart of reuse. Design patterns can be defined for different purposes. We have basically two approaches to patterns which are applicable during a refinement step (see Chapter 16). In one approach the patterns are pieces of models that can be instantiated at need. The instantiation amounts to a refinement step. The idea here is to be able to reuse proofs as the patterns are small “models” with pre-proven properties. The other approach defines refinement patterns via a dedicated language and works as a model transformer. When applying such a refinement pattern the new model is calculated from the original model. Here again the goal is to reuse proofs. In addition to these textually based design patterns, patterns are also defined on the level of UML diagrams within the UML-B work. The pattern ideas are especially used in the SAP deployment where com- munication structures between buyers and sellers in different negotiation sit- uations can be developed using patterns which code the available communica- tion structures. Moreover, the transformational approach targets especially the introduction of fault tolerance mechanisms in a design process.