Task: Identify Events and Messages
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
RolesMain: Additional: Assisting:
InputsMandatory: Optional: External:
  • None
Outputs
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 Events and Messages
During this activity, we identify the events that the component must sense and respond to when they get triggered. In-coming and out-going component messages are also specified. For services that are driven by changes to data, a data-centric view must be taken and business processes not within the scope of the service-based solution must be identified and assessed for generation of events and the supplying of data to the consumer services in the service-oriented solution. For example, a new client may be added by multiple business processes within an ISV package. In all cases, the same data may not be captured for the client depending upon the specific context of the business process. Consumer services that need to be aware of new clients through a provider service need to be able to able to handle the invocation of the new client service regardless of the business process that generates it.
Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
More Information
Guidelines

©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.