作業: Identify Technical Components
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 Technical Components

Technical, or Infrastructure, components serve to make available horizontal platform capabilities; that is the capabilities they provide are not specific to the business domain but cut across business domains. These technical services are frequently provided by middleware products including operating systems and are used either directly by the service component or by the functional components on which they rely.

Example

In completing the Rent-a-Car component model (see functional component step above) we include two technical components into the model, one for the Reservation to log the completion of a reservation request and one to denote that the Vehicle and Location components rely on EJB Services to persist their business data.

Alternatively you can use a tabular format in expressing the required components and their relationship to the services previously identified, as shown in the figure below.



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