Component Model Sample Clauses

Component Model. ‌ Our approach is based on a component model that delimits the broad out- line of what constitutes a component, exposing its necessary related technical concepts and constraints. Both, components and connectors, as well as their interaction semantics, are characterised in this component model that defines the building blocks of our systematic development approach. A component 2assert is not currently a CML keyword, but could be included as a means to provide text commands to the CML model-checker that could be included in the CML specification itself. In particular, assert P [= Q asks the model checker if the process P is refined by the process Q.
Sample 1
AutoNDA by SimpleDocs
Component Model. ‌ Our approach is based on a component model that delimits the broad out- line of what constitutes a component, exposing its necessary related technical concepts and constraints. Both, components and connectors, as well as their interaction semantics, are characterised in this component model that defines the building blocks of our systematic development approach. A component contract1, whose definition is presented below, encapsulates a component in our approach. They are defined in terms of their behaviour (represented as a CSP process), ports (represented as channels) and respective inter- faces (types). 3.1 ( Component contract) A component contract Ctr com- prises an observational behaviour B, a set of communication channels C, a set of interfaces I, and a total function R : C → I between channels and interfaces of the contract (Ctr : (B, R, I, C)), such that: • B is an I/O process as defined below; • Let c ∈ C: 1In the COMPASS project contracts are described in CML. Here, a contract is a tuple that includes a behavioural specification (originally described in CSP, but lifted here to CML), and other elements that describe the ports and their types. – outputs(c, B) = {out.x : R(c) • c.out.x }, and; – inputs(c, B) = {in.x : R(c) • c.in.x } R Intuitively, the component describes the component’s channels and their respective types. Our approach follows approaches like that of [All97b] in which component models have a higher-level granularity by complementing the syntactical in- formation of a component with behaviour. In our case, we explicitly sepa- rated inputs and outputs. The behaviour of these components are represented by I/O processes, which are CSP processes P that satisfy five conditions, which are formally presented in [Ram11]: •
Sample 1

Related to Component Model

  • Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:

  • Additional Features Additional Features are invoiced at the start of the first Contract Year following the Contract Year in which such Additional Features are activated.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Alternate Work Schedule An alternate work schedule is any work schedule where an employee is regularly scheduled to work five (5) days per week, but the employee’s regularly scheduled two (2) days off are NOT Saturday and Sunday.

  • Price Adjustments for OGS Centralized Contracts Periodic price adjustments will occur no more than twice per year on a schedule to be established solely by OGS. Pricing offered shall be fixed for the first twelve (12) months of the Contract term. Such price increases will only apply to the OGS Centralized Contracts and shall not be applied retroactively to Authorized User Agreements or any Mini-bids already submitted to an Authorized User. Price decreases may be made at any time. Additionally, some price decreases shall be calculated in accordance with Appendix B, section 17, Pricing.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Commercial Price List Reductions Where NYS Net Prices are based on a discount from Contractor’s list prices, price decreases shall take effect automatically during the Contract term and apply to Purchase Orders submitted on or after the date Contractor lowers its pricing to its customers generally or to similarly situated government customers during the Contract term; or

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Unbundled Copper Loops (UCL) 2.4.1 BellSouth shall make available Unbundled Copper Loops (UCLs). The UCL is a copper twisted pair Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters) and is not intended to support any particular telecommunications service. The UCL will be offered in two types – Designed and Non-Designed.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!