...

...

Deployment And Run Time View

The Deployment and Run Time View (see Figure 1shown in the architectural infrastructure diagram) comprises implementable specifications (which represent the key semantics), a configuration of enabling systems and contracts, and a run time view of systems interacting with each other to fulfill their contracts. Artifacts from this view are used in the ECCF to assess compliance. Each implementation of a service is expected to state it's level of conformance with the implementation independent specification of that service as expressed as RM/ODP enterprise/information/computation artifacts, such as Enterprise Metamodel - ITU-T Rec. X. 906 | ISO/IEC 19793 Use of UML for ODP system specifications. The closer the asserted level of conformance the higher the degree of semantic interoperability should be. Implementation viewpoint artifacts and functionalities are critical to empirically verifying that the expected level of interoperability has been achieved.

...

Figure 5: The Deployment and Run Time view. This is a static view of the components involved.

The following are shown within Implementation.

• Specifications
  • Roles and Information
  • Behavior and Conformance Point
• Run Time
  • Contract Context
  • Liaison
  • Enabled Behavior
• Configuration
  • Systems
  • Contracts

The Implementation is the instantiation of the configuration of systems with a particular objective(s) whose validity is subject to verification.

...

Figure 2: A time graph representing the states of a contract. A contract may be instantiated multiple
times with different liaisons.

...

Enabled behavior occurs between Establishing behavior and Terminating behavior, over the Period of liaison and the Period during which context exists