-
Key: UCM-48
-
Status: closed
-
Source: THALES ( Thomas Vergnaud)
-
Summary:
Technical policy definitions specify to what kind of element they apply: only components, ports of components, or either case. There is then two metaclasses ComponentTechnicalPolicy and ComponentPortTechnicalPolicy to distinguish between the two situations. This approach creates two problems:
1- it is impossible to specify that a technical policy is meant to apply to all the interaction points of a component (both ports and policies that have port elements)
2- it is impossible to make a ComponentPortTechnicalPolicy manage the interactions between the component and one of its policies -
Reported: UCM 1.0b1 — Fri, 17 Mar 2017 15:58 GMT
-
Disposition: Resolved — UCM 1.0
-
Disposition Summary:
Merge component technical policy and component port technical policy
Define three values for policy applicability: on_component_only (for services), on_some_ports (for interceptors) and on_all_ports (for interceptors that have to intercept all ports). The later value is useful for policies that control the component execution and thus have to intercept all communications. Classes ComponentTechnicalPolicy and ComponentPortTechnicalPolicy can be merged into a unique class TechnicalPolicy, which is simpler.
-
Updated: Mon, 16 Oct 2017 15:14 GMT
-
Attachments:
- ucm_atomic_component_implementations.SVG 20 kB ()
- ucm_component_technical_policies.SVG 24 kB ()