|
 |
Patterns for e-business naming conventions
Patterns for e-business naming conventions
The capitalization convention is to use lower case for pattern and upper case for the first and most significant qualifier. e.g.
Business pattern Self-Service business pattern Collaboration business pattern Information Aggregation business pattern Extended Enterprise business pattern Integration pattern Access Integration pattern (Although slightly inconsistent, keeping Integration capitalized keeps the correct focus on integration.) Application Integration pattern Composite pattern, or for a specific Composite pattern, Electronic Commerce composite pattern Application pattern, or for a specific Application pattern, Router application pattern Runtime pattern
The textual notation Business pattern::Application pattern::Runtime pattern::Product mapping is used to represent the position of an asset within the P4eb hierarchy. Occasionally an intermediate level or the pattern type will be omitted for brevity. e.g.
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. e.g.
Self-Service::Decomposition=Integration Server runtime pattern Application Integration::Direct Connection=Message Connection::Product mapping=Web services
This makes it easier for the reader to fully identify the referenced asset.
Return to the resources page.
|  |
|