Рабочий продукт (Артефакт): Service Model

WorkProductDescriptor

The service model is a model of the core elements of a Service Oriented Architecture (SOA). The service model is used as an essential input to tasks in implementation and testing.

Назначение

The service model is an abstraction of the IT services implemented within an enterprise and supporting the development of one or more service-oriented solutions. It is used to conceive and document the design of the software services. It is a comprehensive, composite work product encompassing all services, providers, specifications, partitions, messages, collaborations, and the relationships between them.

Взаимосвязи

Роли	Ответственный: Designer	Изменен: Designer
Вход для	Обязательный: Нет	Необязательный: Perform Variation Oriented Design	Внешний: Нет
Выход из	Perform Variation Oriented Design

Свойства

Необязательный
Запланированный

Иллюстрации

Шаблоны	Service Model in UML Service Model in Word
Отчеты	Service Dependencies Service Portfolio
Примеры	Service-Oriented Architecture (SOA) Model Example

Доводка

Опции представления

UML Representation:

Model, stereotyped as <<Service Model>>.

The service model can be used for different levels of scope:

Service-scoped development where the scope of the project is to develop the service independently (as much as possible) from other services. The modeling would therefore encompass the use cases, architecture, design and implementation models as a vertical slice for the one service.
Project-scoped development where a project involves the specification of a number of services in support of a set of application requirements, in this case the scope is broadened to the application level and may involve a number of services. In effect there is a set of application level models for use cases and architecture and then a set of service specific design and implementation models.
Enterprise-scoped development, or service portfolio management, where the scope is only to capture the service specifications and logical partitioning but at an enterprise-wide scope. This allows designers and architects to make wide ranging decisions about the entire portfolio, yet separate projects are required to develop the design and implementation models for the identified services (and client applications).

For more information see the concept Service Portfolio and the activity Service Design.

Дополнительные сведения

Справочные таблицы	Service Model
Концепции	Business Process Decomposition Service Portfolio