Task: Model Component Flow

This task specifies the details of the Service Components which realize a Design Subsystem.

Purpose

To elaborate on one or more Artifact: Design Subsystems which were described during Task: Subsystem Design (SOA) and to provide detailed Artifact: Service Component designs.

Relationships

Roles	Main: Designer	Additional: Implementer	Assisting:
Inputs	Mandatory: Design Subsystem Service Component	Optional: Service Model	External: None
Outputs	Service Component

Main Description

Services used in an SOA based solution are realized through Artifact: Service Components which belong to a specific business function aligned subsystem. Each Service Component will have the responsibility of ensuring the QoS of the services it will realize. As an enterprise-scale asset, each Service Component qualifies for funding, governance and maintenance associated with it. Infrastructure management must be in place to ensure availability, load balancing, security, performance, versioning and overall health of the Service Component that will be responsible for implementing the functionality of a set of services and ensuring its quality of service. Functional components and technical components can be used across several Service Components.

Steps

Model Component Flow

During this activity, we identify the internal flow of control within the service component. This can be represented as a sequence or activity diagram.

ISV Consideration: The Component Internal Flow within an ISV package Component may or may not be exposed and/or configurable depending upon the package. If objects within the ISV Component are exposed and configurable, their flow may be tailored and customized to better meet the solution. However, one should be cognizant of any potential ongoing maintenance issues associated with doing so. In many cases, it will not be possible, nor even necessary, to identify the Component Internal Flow within an ISV package. In this case, the ISV Component should be considered a "black box", with only exposed and realized services documented.

Properties

Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable

More Information

Guidelines	Service Component Patterns