Information Technology Reference
In-Depth Information
7.6 Examples of Correspondences
We can demonstrate the principles involved in defining correspondences by
looking at some simple examples. They are shown here using the UML pro-
file defined for correspondences in the UML4ODP standard, which uses four
stereotypes as shown in figure 7.3. Correspondence endpoints are represented
as tag definitions, providing great flexibility to refer to any model element in
the specification.
Let us show some examples of use. First, figure 7.4a shows the correspon-
dence between the binding object and the engineering channel depicted in
figure 7.1. Another correspondence (shown in figure 7.4b) establishes the re-
lationship between the Stock DataMgmt computational object from figure 4.5
and the replica engineering objects which support it, introduced in figure 5.4.
«CorrespondenceLink»
BOChannelCorrespondence
{endPoint1 = bindingObject1
«CorrespondenceLink»
DataStockMgrReplication
{endPoint1 = Stock DataMgmt ,
endPoint2 = Stock DataMgr0 , Stock DataMgr1}
,
endPoint2 = Ch3 }
(a) A binding object and the corre-
sponding channel.
(b) A computational object and its engineering
replicas.
«CorrespondenceLink»
RepairOrderRegistration
{endPoint1 = Generate Repair Order ,
endPoint2 = registerOrder }
(c) An enterprise task and the computational
operation it uses.
FIGURE 7.4: Three examples of correspondences.
A more interesting correspondence defined for the PhoneMob system
(shown in figure 7.4c) establishes that a task defined in the enterprise view-
point is related to a specific operation signature defined in the computational
viewpoint specification. Here, the correspondence indicates that a particular
computational operation type is to be used to support the business process
step in the enterprise specification.
7.7 Tool Support for Specifying Correspondences
Usability is one of the limitations of most current UML tools. Writing large
systems specifications becomes a tedious and cumbersome task; in particular,
