Page History
Scrollbar | ||
---|---|---|
|
Section | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
caBIG® Semantic Infrastructure - Overview
...
|
The Contract Design Infrastructure (see Figure 1) is part of the RM-ODP Enterprise viewpoint and comprises the means of capturing the logical components of a contract. Currently these logical components are captured implicitly in code and in the design of applications. Certainly some fully specified contracts deserve to be captured, preserved, and reused where possible. However, capturing other contract components (and optionally realizing them) should be in scope for an enterprise such as CBIIT given its mission. The RM-ODP Enterprise viewpoint metamodel indicates that that a Community specifies Contract(s) to fulfill specific Objective(s). The Contract is specified by particular Behaviors that are required in order to fulfill the Objective and includes the Policies that pertain to fulfillment of the Contract. An example of capturing contract components and realizing them is the implementation of a durable service that is specified sufficiently to allow clients to consume them at run time without an early explicit binding. Other examples are discussed below.
...