Shared Variable Decomposition Sample Clauses

Shared Variable Decomposition. The idea of decomposition is to split a large model into smaller sub-models which can be handled more comfortably than the whole: one should be able to refine these sub- models independently. More precisely, if one starts from an initial (large) model, say M, decomposition allows us to separate this model into several sub-models M1 Mi. These sub-models can then be refined independently yielding N1 Ni. The correctness of the decomposition technique guarantees that the model N, obtained by re-composing N1 Ni, is a refinement of the original model M. This process is illustrated in the following diagram: Decomposition M → 8< M1 Refinement Re-composition → : Mi · · · N = 1 Ni → N → ;
AutoNDA by SimpleDocs
Shared Variable Decomposition. ‌ Developing an event model by successive refinements usually starts with very few events (sometimes even a single event) and with a very few state xxxx- xxxxx. On the contrary, it usually ends up with a last refinement step dealing with many events and many variables. This is because one of the most im- portant mechanisms of the Event-B approach consists in introducing new events during refinement steps. The refinement mechanism is also used at the same time to significantly enlarge the number of state variables. At some point, we might have so many events and so many state xxxx- xxxxx that the refinement process might become quite heavy. And we may also figure out that the refinement steps we are trying to undertake are not involving no longer the totality of our system (as was the case at the begin- ning of the development), only a few variables and events are concerned, the others playing a passive role only. The idea of model decomposition is thus clearly very attractive: it con- sists of cutting a large event system into smaller pieces which can be handled more comfortably than the whole. More precisely, each piece should be able to be refined independently of the others. But, of course, the constraint that must be satisfied by this decomposition is that such independently refined pieces could always (in principle) be easily re-composed. This re-composition process should then result in a system which could have been obtained di- rectly without the decomposition, which thus appears to be just a kind of “divide-and-conquer” artefact. But this is clearly not the only interesting methodological outcome of decomposition. It also allows us to build up the architecture of our future system by dividing it into independent components with well defined rela- tionships. Decomposing an event model M is defined as follows:

Related to Shared Variable Decomposition

  • Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • Unbundled Network Element Combinations 4.1 For purposes of this Section, references to “Currently Combined” Network Elements shall mean that the particular Network Elements requested by NewPhone are in fact already combined by BellSouth in the BellSouth network. References to “

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

  • 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.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Contractor Changes The Contractor shall notify DAS in writing no later than ten (10) Days from the effective date of any change in:

  • FABRICATION Making up data or results and recording or reporting them.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

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