Ultimately, each implemented service will be documented in a Service Profile (unless the organization chooses
to omit this for any of various reasons). A Service Profile is a readable artifact, typically stored in an
enterprise-level repository, that describes those aspects of implemented services that are needed to support
discoverability and service maintenance. Service profiles are a key element in what is known as “SOA Governance.”
At a minimum, a Service Profile contains each service's “technical service contract,” which is an artifact
created during the design stage. Since the technical service contract is often fully specified in a modeling language
(such as UML), in the extreme (minimal) case the service's model may be considered to be the Service Profile.
However, the technical service contract is not business analyst-friendly, and does not contain supplemental textual
material that may be needed to completely understand the usefulness of a given service in new contexts, such as service
level agreements and other QoS factors.
Therefore, an organization will typically associate textual information and metadata with technical service contracts,
creating “documents” (service profiles) that are stored in a specialized repository.
While the finalization of a Service Profile is a deliverable of the project's development stage, useful
textual information and metadata surfaces as early as the analysis stage, and the purpose of this (optional) step is to
begin the structured capture of this textual information, in the form of a “skeletal” Service Profile.
|