作業: Document Service State-Management Decisions
This task defines and specifies the services and structure of a service-oriented solution in terms of collaborations of contained design elements and external subsystems/interfaces.
目的
  • To define the services and structure of a service-oriented solution in terms of collaborations of contained design elements and external subsystems/interfaces.
  • To analyze the service for commonality and variability (see 準則: Variability Analysis).
  • To document the specification of services.
  • To determine the dependencies and the communication between services.
關係
主要說明
This task refines the set of 構件: Service Specifications identified and qualified during 活動: Existing Asset Analysis and provides additional structure and detail. This design-level detail includes the interface, message and composition of services and the allocation of services to providers.
步驟
Document State-Management Requirements

Although individual services are considered stateless, compositions often have requirements to maintain state information across the invocation of the composed services. The choreographer of the services is often responsible for the management of state. Alternatively, a component that implements and realizes multiple related services or operations on services may need to maintain state between invocations for performance reasons.

State Management in SOA environment can be considered to fall into three main categories:

  • Transaction State - where a service has an open transaction during a conversation with a client.
  • Security State - where a security context is held open during a conversation with a client.
  • Functional State - where the conversation with a client involves a number of related operations.

For more information see the 準則: State Management for Services.

內容
多次出現的項目
事件驅動
持續進行中
選用
規劃
可重複的
詳細資訊