| Representation Options | UML Representation:
UML 2.0 Component, stereotyped as <<Service Component>>. Note that UML 2.0 does provide a stereotype,
within the "Intermediate" profile, called <<service>>, however this is simply defined as a "A stateless,
functional component (computes a value)" which does not convey the meaning implied by this model element.
Service Components represent the realization of Services identified in the Service Model and described by the Service
Specification; however as the granularity of a service tends to be quite large a Service Component may be further
decomposed into components or coarse-grained Design
Classes within its implementation. It is likely therefore that different specific forms of service are required
for this implementation. In particular during the Task: Document Service Realization Decisions patterns are identified that use the following additional stereotypes in
addition to the use of standard component, classes and elements of the RUP Design Model:
|
Icon
|
Name
|
UML Representation
|
Description
|
|
facade
|
stereotype on Class or Component.
|
Used to denote the component acting as the facade for the implementation of the service; in general there
is one facade component for each realized Service Specification.
|
|
mediator
|
stereotype on Class or Component.
|
Used in situations where there may be one or more implementations for a given service operation, the
mediator is called by the facade to identify and call the correct implementation component.
|
|
data access
|
stereotype on Class or Component.
|
Used to denote a data access component, this component is responsible for the access and management of
persistent data for the service implementation.
|
|
