Classification and patterns

[Bob Haugen <linkage@interaccess.com>]

Consider this a rough draft that I hope will be useful in thinking about
the uses of the BP (or now ebXML?) metamodel for classifying core
components and developing re-usable collaboration patterns.

_Classification of core components:_

Metamodel elements could be used as classifiers in several
ways, including:
* stereotypes for UML diagrams for common business objects
  related to core components;
* structural or keyword elements in repositories of core components.

Here are some ideas of how the hierarchies could look:

EconomicResourceType
    ResourceFamily
        ProductFamily
    ProductDefinition
    ServiceDefinition (meaning "work for hire")
       ServiceByTimeDefinition
       ServiceByJobDefinition
    IntellectualPropertyDefinition
    FinancialInstrumentDefinition
    ReturnableContainerDefinition

EconomicResource
    ProductInstance
        ProductLot
        SerializedProduct
        UndifferentiatedProduct
    ServiceTime
    ServiceJob
    Cash
    ReturnableContainer

EconomicContract
   LongTermContract
   Order
   DeliverySchedule

Commitment
   OrderLineItem
   RawMaterialAuthorization
   FabricationAuthorization
   JITSignal

EconomicEvent
   ProductDelivery
   ServiceDelivery
   CashPayment

_Patterns_

Collaboration patterns will be critical to consistent implementations.
Here is a starter list of potential patterns to be developed:

BusinessCollaborationPatterns
    SimpleCollaboration Patterns
       QueryResponse Pattern
       CommercialTransaction Pattern
           OfferAcceptance Pattern
       RequestResponse Pattern
       RequestConfirm Pattern
       InformationDistribution Pattern
       Notification Pattern
   LongConversation Patterns
      OrderFulfillment Pattern
      OrderFulfillmentPayment Pattern
      ContractFormation Pattern
      ContractBidding Pattern
      ContractOrder Pattern
          (Contracts can be also combined with other patterns)
      JIT Pattern
      AutomaticReplenishmentPattern
          VendorManagedInventory Pattern

Feedback welcome,
Bob Haugen