Thursday, October 25, 2012

Object Class Cash

This document describes the process of getting from a relational data base to an object oriented system:

https://docs.google.com/viewer?a=v&q=cache:YZ9OTnXzBu4J:journals.cluteonline.com/index.php/RBIS/article/viewFile/4470/4558+&hl=en&gl=us&pid=bl&srcid=ADGEEShEy84_x_mBiqWY9wdiu4kAPTX8MCPdoT05ZyHS0yZBq43KVKlJE_1iWKKqTEaPu2v4fO-MF8Vh0p3MTvO4ozf3hUA-P7q9sK9H78jpYgve7pIrOEwOWp__-LOE-Bk1nZd-q8wB&sig=AHIEtbSsjUJ8pOo_B0dbprS2e6FiKDgPJg

It is titled:

A Mechanism for Converting a Relational Data Base Into an Object Oriented Model.

The discussion of the Object Model in the beginning is fairly simple explanation of what it is and what it does.  What it does is make information management more efficient.

In the course of information management evolution information was put into relational data bases.  Then the object model came along and was a better method of organizing the info existing in relational data bases to a management model of the business enterprise.

The conversion from relational to object model involves mapping things in the relational model to their classes in the object model.

Account is thing in the relational model that has many pieces of information in it that are to be mapped to its object model class.  One of those things is Account Balance which in the conversion process maps to the object class called class.  Cash becomes an object entity with properties and methods to do things in response to messages to do something sent to the object Cash by other objects in the system that require something to be done by cash.  Cash knows how to do many things like take the information sent to it by the requesting object and return a new value to the message sender (new balance maybe) as well as send messages to other objects (if necessary) to do things they know how to do.

As a result of the conversion process, account balance becomes something more than a cell in a spread sheet.  It becomes an intelligent object, perhaps with subclasses and maybe even different states of being that dictate different methods that it knows how to do and requirements to pass messages on to other objects in the system to do things they know how to do, maybe even change the state of another object so it can do things that state requires with the information sent to it.

What is important here is that the business world is changing to an Object Model Management system.  It all started with an adding machine long ago that grew into card punch systems and functional programming then more intelligent relational systems and now object oriented systems with more intelligence to do things.  A more complex underlaying system but one that reduces the front end complexity to a simpler, more manageable user interface that is a more efficient means of Enterprise Management.

Banking is a Business Enterprise.  It most move along the evolutionary path of Enterprise Management technology.  Today the state of the art is the Object Model that integrates design all the way down to programming and automates much of that programming as a result of an exceptionally well constructed object model. 

Banks must concede that Money is a Super Class Object in their system, not just a number in an account in a double entry accounting system.  Money can continue to be just a number in an account depending on how the system user wants to view it but in the total system it is a thing.  Money is the central thing in a banking system.  It is what a bank creates, it is what a bank sells, it is what a bank wants and gets for what it sells.

Money is an object.  It must be managed as an object.  It is the core object in the Banking Enterprise Model.  Customer Account as the core object around which the Banking system is organized is an historical point in evolutionary progress.  It can continue to be viewed as circumstantially necessary as a most important thing but the conceptual structure object model really elevates the Object Cash as the focus of the object driving the business enterprise.

Cash does not exist as a conceptual Super Class in today's banking enterprise model.  In order for it to exist as an object the system must be built on real 100% total reserve banking with each unit value of cash having unique identifying serial number.

While bankers may resist this concept, it will increasingly become more like the position of creationism versus evolution.  The logic of the object model alone, much less politics dictate a paradigm shift in the conceptual structure of the money world.

There are two big things grinding against each other here.  One is the established concept of the banking business enterprise and the new concept based on an object oriented model.

Looks like a "Let there be blood" situation.

No comments: