Patterns: Extended Enterprise SOA and Web Services

Chapter 2. Introduction to the Patterns for e-business 25

2.3 Patterns for e-business naming conventions

The Patterns for e-business use a standard naming convention with the objective

of making it easier for the reader to fully identify the referenced asset.

The capitalization convention is to use lower case for pattern and upper case for

the first and most significant qualifier as seen in the following example:

򐂰 Business pattern

When referencing a specific type of pattern, the higher level qualifier (business)

is not capitalized as seen in the following example:

򐂰 Self-Service business pattern

The textual notation Business pattern::Application pattern::Runtime

pattern::Product mapping is used to represent the position of an asset within the

hierarchy. Occasionally an intermediate level or the pattern type will be omitted

for brevity as seen in the following examples:

򐂰 Self-Service::Router application pattern

򐂰 Self-Service::Router runtime pattern

In addition, when it is necessary to identify variations or product instances at the

same level in the hierarchy an '=' sign will be used as seen in the following

examples:

򐂰 Self-Service::Decomposition=Integration Server runtime pattern

򐂰 Application Integration::Direct Connection=Message Connection::Product

mapping=Web services

2.4 Summary

The IBM Patterns for e-business are a collected set of proven architectures. You

can use this repository of assets to facilitate the development of Web-based

applications. Patterns for e-business help you understand and analyze complex

business problems and break them down into smaller, more manageable

functions that you can then implement.

26 Patterns: Extended Enterprise SOA and Web Services