Browse Prior Art Database

Methodology for mapping Business Object Model to COBOL model

IP.com Disclosure Number: IPCOM000208878D
Publication Date: 2011-Jul-21
Document File: 9 page(s) / 153K

Publishing Venue

The IP.com Prior Art Database

Abstract

Modern business rules are developed against a Object-Oriented Business Object Model(BOM). In an effort to deploy the business rule as native COBOL applications, BOM to COBOL mapping is needed for its execution on mainframe. To achieve this, this solution chooses to generate COBOL copybook from BOM and apply COBOL rule application generation against this copybook structures. With this capability, business rules design is purely based on business model and rules can be deployed on different platform, especially on COBOL. The solution also opens another direction for COBOL legacy system modernization by generating COBOL code from an existing modern rule application.

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

Page 01 of 9

Methodology for mapping Business Object Model to COBOL model

1. Background

The Business Rules Management Systems (BRMS) are software applications used to define, deploy and execute variety and complexity of decision logic that is used by operational systems. This decision logic also referred as to business rules includes policies, requirements, and conditional statements that are used to determine the policy actions that take place in applications and systems.

In a BRMS, the business rules are constructed with business terms and vocabularies described in an object model, often called a Business Object Model (BOM). The following drawing illustrates a BOM written for an application domain (loan approval), and the business rules which can be written on the BOM.

(This page contains 00 pictures or other non-text object)

At runtime environment, the business rules are mapped to executable programming language, often called Execution Object Model (XOM). A typical XOM mapping is implemented by an Object-Oriented language, for instance Java.

There is existing solution to provide mainframe customers the capability to author and manage rules against COBOL data structures (called COBOL copybook), and to deploy these rules as native COBOL rule applications. Such a tool can create a BOM a COBOL copybook which also constrains that the BOM can only be started from an existing COBOL copybook.

However, many modern business rules are developed against a BOM based on Object-Oriented XOM (like java). In an effort to deploy the business rule as native COBOL applications,

we choose to generate COBOL

we need to create the BOM to COBOL mapping for its execution on mainframe. To achieve this,

copybook from BOM and apply COBOL rule application generation against this copybook structures.

1



Page 02 of 9

Such a solution is a new way of creating BOM to COBOL mapping with Top-Down direction. With this capability, customer can design business rules purely based on business model and choose to deploy rules on different platform, especially on COBOL. The solution is a successful synthesis of 2 aspects:

A. Improve BRMS cross-platform deployment competency on mainframe

B. Open another direction for the COBOL legacy system modernization by generating COBOL code from an existing modern application (rule application).

2. Main Ideas

The invention is consists of two core ideas as below:
1. An instance based Top-Down direction to establish BOM to COBOL mapping by generating COBOL copybook.
2. Apply the COBOL code generation logic from business rules against the generated COBOL copybook.

For point #1, there is existing solution to create BOM from COBOL copybook. This is a Bottom-Up direction (COBOL -> BOM) and assumed that one BOM class can only appear once in the data structure tree.

COBOL is a flat-structured language and has no class type and instance concept. With above assumption, it is easy to create COBOL to BOM mapping while it limit the capacity to map arbitrary B...