Decomposition Clause Samples

Decomposition. Decomposition is a relation describing of what smaller parts a larger part consists and is here called “contains”, while the inverse is called “contained by”. Because of decomposition, the larger part can be considered a (decomposition) set of the smaller parts linked through decomposition and some additional unknown part as well. Similar to instantiation, a larger part can contain several smaller parts and a smaller part can also be part of several larger things. There can however be exceptions to this, depending on where the decomposition is applied. Also, the structure created through decomposition should form a directed acyclic graph, meaning that loops in decomposition are not allowed. Decomposition is generally described using the AND-inclusion type. However, variability can be achieved in some cases by also using different ones. For example, when describing products, the OR- and XOR-inclusion types can be used to denote the potential for customisability. In addition to the inclusion types the decomposition relation can also be marked as separable or inseparable. An inseparable decomposition indicates that the larger must contain the smaller, while with a separable relation the smaller part is considered optional. Having a separable contains relation to a smaller thing is the same as a contains relation to a decomposition set of XOR-inclusion type that itself contains the smaller thing and an empty set (see Figure 3).

Decomposition. 2.4.1. Overview

Decomposition. ‌ We have explored two avenues on decomposing Event-B models, here called A style and B style, respectively. The A style decomposition is based on the idea of partitioning the events into separate modules. The modules commu- nicate using a shared variable model. Hence, we have a state-based decom- position of models. The B style takes the view where an event is divided into different modules, giving rise to an event-based view. In Chapter 13 we give an overview of the methods and also present a more thorough compar- ▇▇▇▇ of the two approaches. Moreover, in Chapter 14 we discuss one special case of the A style decomposition, used in the SSF deployment study, where the possibility of decomposing an Event-B specification using modules and operation calls has been investigated.

Decomposition. 13.1. If the customer wants to cancel the order placed by MSYS, MSYS needs to be informed by the costumer within 5 days after the date of orders received. As long as the goods have not been sent to deliver within 5 days, the customer can cancel the order placed with MSYS. 13.2. Returning is possible within 5 days. If the order has already been delivered to the customer, MSYS takes the cancelled items back, only in their original, unopened and undamaged packaging. 13.3. The costs of returning the article are entirely for the account of the costumer. 13.4. If the costumer has complied with the foregoing conditions, the payment order for credit will be given to the bank of MSYS by MSYS within a week. 13.5. If the customer or any of its obligations under the agreements resulting from not, not properly or not timely to fulfil it is legally in default. MSYS then has the right to terminate the agreement without notice and unilaterally fully or partially without judicial intervention by means of a notification (by post, fax or e-mail) to the customer without MSYS is obliged to pay any compensation, without prejudice MSYS other rights. 13.6. All claims that MSYS may have or obtain in the event of termination of the agreement by the customer shall be immediately due and payable.

Decomposition. The system is divided into sub-systems : • carbornecontroller and its variable/events, • Driver and its variable/events, • Train and its variable/events, • Wayside controller and its variable/events • Track and its variable/events • Time (universal time for all sub-systems) The wayside controller is then decomposed into several zone controller (each one dealing with a part of the CBTC territory). Each ZC (Zone Controller) can communicate with the trains that are on the ZC area. A ZC can communicate with the nearby ZC.

Decomposition. Under no circumstances can Averica be held responsible for loss by decomposition when samples are handled under customary and safe laboratory conditions and consistently with Client’s concerns or instructions.

Decomposition. Formal, shared event decomposition is now used to separate the Controller model from its environment for further refinement towards implementation. The decomposed Controller model can also be converted into a Functional Mockup Unit (FMU) for simulation in a continuous representation of the landing gear environment. Chapter 4‌

Decomposition e i,l i,k i,l e e e

Decomposition. A has component of a single chemical element statement is a specialisation of a has part statement. • A Decomposition structure description is a set of has part statements. A Quantity of a single chemical element is associated with a Chemical element. This is shown in Figure 17. domain 1 * range Chemical element element of quantity Physical object Statement Class of physical object Physical object • An element of quantity statement is not a classification. This is because a member of a Chemical element, such as Iron, is a single atom, not many atoms. The magnitudes of the components can be expressed as mass, volume or amount of substance (molar) ratios. A ratio can be between a component and the whole, or between two components. The model for Mass, Volume and Amount of substance ratios is shown in Figure 18. domain * * range 1 1 numerator * value value value Amount of Substance ratio Volume ratio Mass ratio * numerator 1 * numerator Volume Amount of substance Class of physical object Physical object Statement Physical quantity Statement • The relationship between a Physical object and a Physical quantity such as a Mass, a Volume or an Amount of Substance is type, i.e. classification. This is not intuitive, but is an interpretation of the physical meaning.