A Four Level approach to handle User changes to Codes

The Challenge of User Code Editing

Many programs have code systems in which various letters, acronyms, numbers or abbreviations have meanings. The most common example I can think of is the codes for the States of the United States. Each state has a two letter code. This approach is used for a lot of things in business programming for various options, many of which have source coded written around them in an OO/RDB system. The challenge is that if you have a UI where a user can change, delete or add to these codes, you need to write or change code sometimes in order to meet the needs associated with the new or changed codes. To set up a UI to a user can manage these codes you need to go two levels higher and use these levels to handle the source code challenge.

Code/letter maintenance affects source code

In brief here is how to do this with information oriented systems:
– can’t easily do this with a UI unless you have the following two items involved:
endemes for the codes
– ontologies for the coordination

Layered Systems vs Leveled Systems

In order to meet this challenge, you need to move from layered systems to a leveled system. The difference between a layered system and a leveled system is that a leveled system handles a program in larger sections, i.e. lower granularity than a layered system. In addition, a leveled system levels can access all those below that level, and layered systems have barriers between layers. Another difference is that each level can have layers. Another difference is that you build a framework at each level. A layered system generally has only one framework, i.e. ASP.MVC. Layered system I am proposing has four levels rather than the standard two level systems we mostly build. The standard two level systems have an OO level and an RDB level. They have UI and middle tier and back end layers. Four level systems have four levels – Ontologies, Endemes, Object orientation, and relational database.

Four-Level Systems for Code Handling

The ontologies level handles where the various pieces of the program source code are that are related to the code to be changed,
the endemes level handles what the new codes mean or could mean and whether new source code needs to be added. The object oriented level handles the implementation of the codes. The relational database level handles storing the codes and their meanings in a form that the endemes and ontologies levels can used to manage toe object oriented level.

High level business users really should be able to modify the codes they work with. This is how to do it.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s