The Data Model Resource Book, Volume 3: Universal Patterns for Data Modeling

Silverston c06.tex V2 - 11/21/2008 3:09am Page 279

Level 4 Status Pattern 279

model that when implemented could have performance implications

because searches for available statuses would always have to be filtered

by the particular type of status that is needed at the time (for example,

order status, shipment status, and so on). Although performance consid-

erations are not really a p art of data modeling, some would argue that

it is a consideration to look downstream and make sure that the data

model can be practically implemented. If this pattern is implemented

correctly in a robust physical architecture, you should have no issues

with performance .

Synopsis

In this section we d escribed the Level 4 Status Pattern that is an even more

flexible ‘‘plug-and-play’’ pattern and that can be used by an enterprise to

automatically connect new entities that need statuses to a very comprehensive

status data model structure.

The pattern uses an ‘‘interface’’-like entity called STATUS APPLICATION,

to which any new or existing entity can attach. STATUS TYPE already supports

the different types of statuses an entity may need, so by connecting to STATUS

APPLICATION, any entity can gain access to a complete set of statuses as well

as a comprehensive data structure that accounts for initial and future needs.

This approach has many advantages. It helps enterprises provide a consistent

approach across all status types, ...