作業: Identify Service Component
This task extends the traditional RUP subsystem design with details specific to a SOA solution, especially where subsystems were identified from business analysis models. Once we make the transition from the business domain to the IT domain, we map identified functional areas defined by the former to subsystems, their IT counterparts.
目的

To link the business models to their IT counterparts we perform the following:

  • Identify the relationship between Functional Areas (概念: Functional Area Analysis) in the 構件: Business Analysis Model to corresponding 構件: 設計子系統.
  • To define the behaviors specified in the subsystem's interfaces in terms of collaborations of contained design elements and external subsystems/interfaces.
  • To document the internal structure of the subsystem, in terms of 構件: Service Components that realize the Subsystem.
  • To define realizations between the subsystem's interfaces and contained components and classes.
  • To determine the dependencies upon other subsystems.
關係
主要說明

We begin with the determination and documentation of the dependencies between subsystems that correspond to the functional areas that have been identified during 作業: Functional Area Analysis. Usually a functional area will correspond to a single subsystem; that is, the simplifying assumption that has been found to be accurate in many, if not most cases. If we decide to map a functional area to several subsystems, that can also be feasible and valid; but usually means the domain decomposition did not go deep enough and the functional areas are not granular enough.

步驟
Identify Service Component

Subsystems, in and of themselves, are not IT assets and not deployable into the IT infrastructure; they provide a bridge between the business and IT perspectives. Each subsystem is realized by one or more Service Components where a Service Component is an enterprise-scale asset (a managed software element with guaranteed availability, load balancing, security, performance, and versioning). The Service Component is in turn realized by multiple Functional and Technical Components according to the diagram below.

Generally each service assigned to a Subsystem will result in a Service Component; Functional and Technical Components may be shared between Service Components within the same subsystem.

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