Sunday, July 29, 2012

Transprency

Transparency is a good thing.  You don't need to know the details of the system in order to use it.

A computer, the Internet, television or an automobile or airplane for example.  You can know all the details if you want to know but all most want to do is use it.  They are end users of the system.  They do things with what the system provides.

The banking system is a fraud but it is also transparent.  You can learn about it it, how it operates and why it is a fraud.  It is not easy to learn about it and opinions of knowledgeable people vary as to how it operates and why it is a fraud.....or not depending on who you believe and how much. 

The results of the fraud are apparent.  The cause is not easy to see. One of the principal things that would control the fraud is enforcement of the law by regulators who have agreed not to look at the transparency and politicians that reduce the number of regulators so there are fewer to look.  Regulators look at what the system does but base findings on what the law is regarding what the system is allowed to do or not do. 

Focus on what a system does simply presents the system from the viewpoint, generally uninformed, of the user.  Working upward through a functional hierarchy  through everything the system does to the core functional things it does is confusing, it is the easiest way to confuse and divert understanding of the system.  At the top, the point from which the entire system descends, is an object model that presents the principal objects in the system, how they relate, what their attributes are and what methods they know as the fundamental Class Object in an object oriented high level abstract concept of the system.  The object model at the top is the real basis for the system design and extension to do all the functional things the system does.  All the top Class Objects have methods that they use to do things, functional things. 

Our Constitution is a high level abstract object model for our country.  It does not say much about what the system does, it presents the basic Class Objects their attributes and what the objects in the Class inherit as members of the class and the methods they have to do things.  They are system users.  They naturally focus on processes and procedures that are built on the fundamental object model.

If anyone wants to understand banks and money they have to start with a high level abstract object model of what money is.  Nothing presents the model except people who think they know what it is, which are few. Most who think they know what money is really only know what money does.  Focus only on what money does clouds the transparency of what money is as an object and what are its attributes.

This is like a chicken and egg thing.  Which comes first in the planning design? Knowledge, of course about all aspects the total problem domain.  However when the top level design plan starts it is the top class objects that are identified in the problem domain.  Then their properties are established then their functions are identified.

Objects come first.  Then there is a dance between objects passing messages to other objects to do things.  The things that they can do are designed into the system.  It used to be that functional processes were separate programs all with functional statements in their processing programs that were verbs that did things. 

Unified Modeling Language is the object oriented method of design for high level system modeling.  There are experts in this method.  Certainly at least one of these experts must see that the money system has to be redesigned using the methodology.  Technology has often provided the solutions to problems in the past.  UML is the technology of the information age that can solve the problems related to money today.

UML and an open source transparent money system founded on what money is as an object.

No comments: