Describing the services communications
Service interactions
Service interactions show the exchanges planned between the organization entities.
A Service Interaction represents an interaction for service purpose between entities in a specific context inside or outside a company. These entities can be enterprise org-units, applications, activities or processes, as well as external org-units. The content of this interaction is described in a service interface.Exchange terms are defined by a service interface assigned to the service interaction.
A Service Interface is a template of a contract between entities (organizational, IT …). The contract is described by available operations which can be triggered trough messages exchanged by roles (vendor, buyer..).You can define service interactions between:
• Two components of resource architecture type to represent exchanges between these entities,
• A component of resource architecture type and an IT infrastructure to represent the terms of use of the equipment resource by the organizational resource. For example, you can represent that operator hardware use is arranged by booking.
• two components of IT infrastructure type to represent the terms of use of one IT resource by another in the context of the modeled resource architecture.
• a service point and one or more resource architecture type components to represent implementation of the service within the resource architecture,
• A component of architecture use type and a request point to represent that the entity calls a resource of an external organization.
For more information on service interaction management terms, see Managing Service Interactions.
Service points
Services provided by infrastructure elements are represented by service points.
A service point is a point of exchange by which an agent offers a service to potential customers.The service id requested according to specific terms that are defined by a service interface assigned to the service point.
A Service Interface is a template of a contract between entities (organizational, IT …). The contract is described by available operations which can be triggered trough messages exchanged by roles (vendor, buyer..).The resources activated to carry out a service are connected to the service point by service interactions. If the activation of several resources is necessary, several service interactions must be created between the service point and the architecture resources.
To create a service point, see Describing Service and Request Points.
Request points
A request point is used to represent the use of an external service.
A request point is a point of exchange by which an agent requests a service from potential suppliers.The service is requested according to specific terms that are defined by a service interface assigned to the request point.
A Service Interface is a template of a contract between entities (organizational, IT …). The contract is described by available operations which can be triggered trough messages exchanged by roles (vendor, buyer..).The resources emitting a request are connected to the request point via a service interaction.
In the example, request points represent service requests made between call center operators and other organizations.
The request point creation procedure is identical to that for service points. For further details, see .For further details, see Describing Service and Request Points.