## The Universe of Discourse

This is another framework I often refer to. I call it the “Moffett Framework” based on James Moffett’s explanation of the “Universe of Discourse”.

I found it can be represented graphically:

Where the vertical axis is speaker and audience and the horizontal axis is time and senses. I will discuss this further in a latter post.

## Systema: Zachman Framework Abstract

The Zachman Framework I have seen diagrammed often. However, I have not found the diagrams any more enlightening than the original diagrams by John Zachman. The reason is because the diagrams referred to other diagramming conventions instead of revealing the underlying concepts being described by the diagrams. Click on the thumbnail below to view what I consider an appropriate abstraction of the Zachman Framework:

I have submitted this diagram to John Zachman and he has welcomed it.

## Twelve Dimensional Universe

In information technology there are four common components to every system: process, data, location and events. When we define the structure of these components, each is a three dimensional network. As a business system operates, each of these networks is negotiated and each creates its own three dimensional path. Any observation of the system is an intersection of the paths of the four components. It lead me to wonder why the same paradigm couldn’t be transplanted where process is energy, data is mass and location and event are the one dimensional coordinates of space and time. If so, the universe could be viewed as four three dimensional networks that we traverse in four three dimensional paths with any observation being the intersection of those four paths. The universe was twelve dimensional with the only constant being change.

This is my thought experiment for time:

1. The acceleration of everything in the universe is constantly changing

2. Therefore every photon that strikes me is of a different wavelength

3. I am not one electron nor is my source of photons one electron

4. Therefore it is impossible for every photon I observe to come from the same source electron or strike the same target electron

5. Therefore it is impossible for me to observe from a single coordinate system or observe to a single coordinate system

6. Time is not linear

7. Therefore the speed of light is not constant because it cannot be measured with precision or accuracy.

The observer never observes the same clock.

The observer never observes the same energy.

The observer never observes the same mass.

The observer never observes the same location.

Abandon statistics for a moment. Everything in the universe is unique. In fact, every atomic and subatomic particle is as unique as a snowflake.

My theory is that energy, mass, space and time are each three dimensional networks that collapse into each unique observation. The universe is twelve dimensional.

(Ex,Ey,Ez) = (mx,my,mz)(Δ(lx,ly,lz)/Δ(ex,ey,ez))2

Where E is energy, m is mass, l is location and e is event.

Give Michio Kaku a view.

## Data, Information, Knowledge and Wisdom

In the late 1960s a Harvard English professor, James Moffett, wrote a book by the title Teaching the Universe of Discourse. In it he classified four perspectives that one can take to any system. These perspectives were:

Observing: What is happening

Reporting: What happened

Generalizing: What happens

Theorizing: What may happen

The products of the perspectives have been popularly termed:

1. Data
2. Information
3. Knowledge
4. Wisdom

Understanding these four perspectives and their deliverables give us an understanding of the capabilities that each affords.

Data is the set of variables that represent any state of a system such as a business. Each time something changes in a system its state changes. It is crucial to know what the state changes are and how to measure them. In science, these are known as variables.  In databases these are known as instances.  It can also be termed “polation”.

Information is the collection of data as a system’s states change. This permits the comparison of each state. In science, these are known as the results.  In databases these are represented as tables.  It can also be termed “intrapolation.”

Knowledge is the ability to generalize what a system’s states will be given particular data and information. In science, this is known as hypothesis.  In database parlance these are known as relationships.  It can also be called “interpolation”.

Wisdom is the ability to turn exceptions into advantage—states that are missed by current data, information and knowledge. It is necessary to compare many states of one form of information to many states of another form.  The result is used for projection into the future. In science, this is known as new theory. Database modelers treat this as a many to many relationship and resolve it as an association.  It is also known as “extrapolation”.

I want to distinguish the model for a venture from the model of a business. One of the key obstacles to innovation is communicating a venture model to minds grown comfortable with a business model. First, the people we are trying to convince may not even know there is an exception. Second, the new data, information, knowledge and wisdom we advocate are all untested. We do not know if the data we advocate measures the new states. We do not know if the information will make comparison of all states possible. We do not know if our knowledge will successfully forecast the benefits of the new states. We do not know if our wisdom will be able to handle new exceptions spawned by the venture. No matter how much you analyze, ultimately the experiment has to be performed. As in science, the scale of the experiment dictates the risk.

The Classification of Exceptions

Exceptions in a system are not a one dimensional phenomena, however for the first part of this discussion I am only going to concentrate on a single dimension. This dimension has the following six categories:

1. Conceptual
2. Contextual
3. Logical
4. Physical
5. Mechanical
6. Operational

These categories descend from largest, conceptual, to smallest, operational.

Conceptual exceptions involve the failure of the business model to recognize an achievable objective. Simply put, something new can be done. A contextual exception is the failure of the business model to recognize a consumer context it can support. It can be done and it can be done for the customer base chosen. A logical exception is a failure of the business model to recognize a product or service the customer requires consistently. A physical exception is a failure of the business model to recognize an opportunity to deliver to the customer at a lower cost. A mechanical exception is not seeing how to correct a defect in the manufacture of a batch of product or in the training in the procedures of a service. An operational exception is correcting a defect in a single use of a product or service.

Dealing with exceptions in only the context of product and service is actually in many instances insufficient. There are several more facets to any business and any system. For example

• Product

• Service

• Employee

• Location

• Timing

• Need

When we look at these facets and consider them in combination with the dimension we have already discussed, suddenly a venture becomes increasingly complex. The conceptual category now begs the questions: Is the product possible? Is the service possible? Can we find the employees to make it possible? Is there a location where it is possible? Is there an appropriate time for this venture? Is there a need for the product or service of this venture? And there are still five more categories unexplored.

What we have with these two dimensions are thirty-six different types of exceptions a business model can have.

The Dip Slips

In his new book, The Dip, “marketing guru” Seth Godin attempts to use the Pareto principle to claim that the first 20 percent of the work derives 80 percent of the benefit. I think he has missed the mark entirely.

If we look at the exceptions I have detailed above in the context of the Pareto principle we can see that the first four categories, which comprise eighty percent of the work, provide only twenty percent of the benefit. The first four categories are design categories. The last two categories are development and use. It is the Mechanical and Operational categories that deliver eighty percent of the profit. Put another way, “Measure twice, cut once.” Seth Godin, has logically put the cart before the horse.

## Join In

I came across this simple explanation of joins.

## Surrogate Key Best Practice

Surrogate keys (unintelligent keys) are an excellent way to preserve the referential integrity of your database and avoid the need for cascading updates of natural keys if they are changed. However, simply using surrogate key is not always enough.

One of the most common best practices for databases designed with surrogate keys is: Any independent table with a surrogate primary key should have a corresponding natural key with uniqueness enforced. When uniqueness is not enforced duplicate rows are possible and your referential integrity is lost.

For example, consider the table below:

In the student table the primary key is a surrogate key, but uniqueness is enforced stringently by protecting the full name of the student and his birthdate as a unique composite natural key.

Another context for protecting surrogate key referential integrity is by protecting the uniqueness of foreign key combinations where uniqueness would be enforced if the table were dependent. For example consider the tables below:

Note how the enrollment table has a surrogate primary key, however uniqueness is protected by the unique natural key index on the two foreign keys.

If you use surrogate keys and natural keys together when you design your database, you will avoid the pitfalls of duplicate rows in your data.