GLUE Space

In my last posts I started to explore GLUE to formulate a common approach to all forms of engineering:

General Process Framework with
Loose Coupling of Process Components using a
Unified Approach for
Engineering in all fields.

The GLUE Space is the complete 3-dimensional frame to support all kinds of engineering processes. The first dimension is the GLUE Disciplines which form the generic engineering value stream:

 

The second dimension is the GLUE Decks which depend on the problem space to be looked at. As an example I used a fairly standard (artificial) setup for different engineering layers on top of each other:

The third dimension is the GLUE Divisions which are the different perspectives on engineering:

The intersection of these three dimensions now builds the cuboid:

“Imagination is more important than knowledge.”,
Albert Einstein (1879 - 1955)

If I now face a methodolgy, a framework or an approach I map that against GLUE. Enterprise Architecture for me for example are all architecture activities of one enterprise:

While Enterprise Information Technology Architecture is only containing the IT part of Enterprise Architecture:

So each and every method I face i map into GLUE and know therefore the part of the engineering scope it does deliver. That allows me to know the right process interfaces (if needed also technical implemented) so that any given initative is optimally supported in the GLUE SPACE. To explain that even further I must dig into GLUE Activities, GLUE Domains and GLUE Roles next.

Feel free to comment and contact me. I am more than happy to share knowledge and experience and I will try to answer questions (if there is any), be it public or private.