[use-case] #2 - eBusiness Industry Dictionary: BP catalogues

["David RR Webber" <david@drrw.info>]

Re-send as HTML

Title: untitled

ID:  2

Title

• eBusiness Industry Dictionary: BP catalogue

Description

The ebXML architecture calls for a registry of re-usable business process definitions that can be used to configure ebusiness interactions dynamically with software.

Industry groups such as OAGi, RosettaNet and STEP have developed dictionaries using a variety of tools such as HTML and spreadsheets to manage their own sets of business processes (BODs, PIPs, etc) in a manual way.

Today ebXML has available CPA with BPSS and associated transaction handling instructions such as XSD schema and CAM template scripts to provide the physical implementation.

By defining semantics for BP catalogue entries in Registry we can provide a consistent way to package a BP definition, including all the necessary components (CPA, BPSS, Transactions, Context use rules) so that industry groups can quickly build re-usable dictionaries of BP catalogues. Linkage can be provided to OWL and topic maps so that re-use and discovery can be enhanced. A further goal is so that application implementers can reliably download and install BP catalogue definitions into their systems to configure them and provide directives for the runtime systems.

Actors

• business process analyst

Priority (Low, Medium, High)

• medium

Pre-conditions

• None

Post-conditions

• None

Basic Flow

1. analyst #1 assembles a collection of BP components, such as CPA, BPSS, business transaction definitions, and context mechanism details and publishes as a semantic object in XML to registry
2. analyst #1 assigns classification and taxonomy to BP catalogue entry
3. analyst #2 queries and retrieves BP catalogue entry based on industry search criteria
4. analyst #2 uses browse and drill down to locate specific BP catalogue item meeting industry criteria

Alternative flows

1. machine process retrieves semanticdetails of BP catalogue entry as XML and then automatically configures ebXML components accordingly (CPA - directs ebMS, BPSS - directs BP engine, et al).
2. referencing is done either via direct external key value look up and using REST interface or direct UUID referencing.
3. machine process scans registry for matching industry BP catalogue entries and produces catalogue of same as human readable report

Exceptions

• None

Includes Use Cases

• None

Special Requirements

• None

Assumptions

• Industry analyst creates BP catalogue content using domain expertise.
• BP catalogue details and associated objects (CPA, BPSS, XSD, context configuration) may be spread across multiple registries that may or may not be federated

Use Case Relationships

• None

Issues

• None