Usage: "Capability" stereotypes UML Class, Component
A Capability models the ability to act and produce an outcome that achieves a result. A Capability might
provide a service specified by a ServiceContract or ServiceInterface. The Capability can specify dependencies or internal
process to detail how that capability is provided, including dependencies on other Capabilities. Capabilities are shown
in context using a service dependencies diagram.
A Capability identifies or specifies a cohesive set of functions or capabilities that a
service provided by one or more participants might offer. Capabilities are used to
identify needed services and to organize them into catalogs in order to communicate the needs and capabilities of a
service area, whether that be business or technology focused, prior to allocating those services to particular Participants. For example, service capabilities could be organized into UML Packages
to describe capabilities in some business competency or functional area. Capabilities can have usage dependencies with
other Capabilities to show how these capabilities are related. Capabilities can realize ServiceInterfaces and so
specify how those ServiceInterfaces are supported by a Participant. Capabilities can also be organized into
architectural layers to support separation of concerns within the resulting service architecture.
|