Browse Prior Art Database

BPM Flexible Business Objects

IP.com Disclosure Number: IPCOM000236815D
Publication Date: 2014-May-16
Document File: 2 page(s) / 49K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to mix strict Business Object Templates with flexible service interfaces and database schemas in order to minimize both downtime and the production of defects when the Business Object Template is changed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 2

BPM Flexible Business Objects

Business Process Management (BPM) tools rely on strictly defined Business Objects (BO) as fundamental in BPM solutions. A Business Object is defined by a Template, which is a list of the contained parts. For example, a Person Business Object has a name, an age, and an address. User interfaces (UIs), as well as service interfaces and database schemas, are derived from the Business Object Templates.

The challenge comes when Business Object Templates have to change. These changes ripple through code, user interfaces, service interfaces, and database schemas. This introduces cost in terms of change process and downtime, and can introduce new defects. If another party is interested in consuming the Business Data, then the consequences of those problems are further aggregated.

The novel solution is to mix strict Business Object Templates with flexible service interfaces and database schemas. The solution consists of three parts:

1. Generation of semantic information based on strict Business Object Templates; the semantic information is defined using Industry Standard notation

2. Definition of agnostic service interfaces that are not dependent on Business Object Templates; strict data validation can still be enforced

3. Definitions for those agnostic database schemas that are not dependent on Business Object Templates. The semantic information generated by part (1) is used for this purpose. Strict data validation can still be enforced.

A new (second) application can be built that depends on the semantic information only, accessing the Business Data created by the first application. Service interfaces are built using Industry Standard technologies, consumable from a wide variety of applications. Different tools can generate the semantic information (e.g., custom notations, Unified Modeling Language (UML) notation, and Extensible Markup Language (XML) Schema notation). An application can discover and query th...