Pattern 28 (Data Transfer by Value - Outgoing)

FLASH animation of Data Transfer by Value - Incoming and Outgoing patterns

Description

The ability of a process component to pass data elements to subsequent components as values avoiding the need to have shared names or common address space with the component(s) to which it is passing them.

Example

Upon completion, the Identify Successful Applicant task passes the successful applicant name to the next task.

Motivation

Similar to Data Transfer by Value - Incoming pattern (WDP27) although in this scenario, the emphasis is on minimising the coupling between a component and the subsequent components that may receive its output data.

Overview

As for Data Transfer by Value - Incoming pattern (WDP27).

Context

There are no specific context conditions associated with this pattern.

Implementation

As for Data Transfer by Value - Incoming pattern (WDP27).

Issues

None observed.

Solutions

N/A.

Evaluation Criteria

An offering achieves full support if it has a construct that satisfies the description of the pattern. It rates as partial support if there are any limitations on the range of data elements or data values that can be passed or if the data passed action is not explicit.

Product Evaluation

To achieve a + rating (direct support) or a +/- rating (partial support) the product should satisfy the corresponding evaluation criterion of the pattern. Otherwise a - rating (no support) is assigned.

Summary of Evaluation