Remember, as stated in the previous section, a design relationship diagram
does not depict aggregated service structures. To be able to view the service structural perspective
always refers to the analysis proposition diagram.
SERVICE CARDINALITY
A service typically communicates and exchanges messages with consumers and peer services to
provide business and technical solutions. These activities, which engage multiple assets to provide
organizational remedies, are regarded as a collaborative aspect of service-oriented design. In other
words, to attain effective solutions, service interaction is needed.
To accomplish a given transaction, a service may need to exchange messages with more
than one consumer or with multiple peer services. That is, to fulfill a required transaction, a
service may need to have several associations with internal or external service-oriented assets.
This is referred to as service cardinality to denote the multiplicity of the service relationship.
It is time now to discuss the most rudimentary service cardinality formations that typically
identify the number of interfaces a service would have to maintain while exchanging messages
with its consuming and peer-partners. The cardinality aspect of services is explained in the sections
that follow.
ONE-TO-ONE. The one-to-one cardinality relationship is formed when an atomic service, a
composite service, or a service cluster exchanges messages with a single consumer or service.
Pages:
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424