This is a gathering place for fundamental and introductory materials which I’ve collected over time. Most were collected as the technologies were introduced as proposals for standardized schemes for systems development and programming. We still create method of the week awards for brilliance in new ways to speak new languages to computers. Success happens with standardization, not diversity of methodology. We invent computer Babel partly, to fulfill a need for invention, and we don’t know what to invent, or what to do with our time, so we sell s**t to each other to keep ourselves amused. In game theory it affirms where and how we evolved as thinking beings, and it’s useful, and should be promoted, curiosity is the mother of invention. But all free thinking is chaotic, which is where some stuff has evolved.
Core understanding of complexity can be understood, and steered, mathematically, using models. But the only models that work, completely, are closed, white box models, not black box models – which are guessing machines. Algorithms are machines. Feed them garbage, they generate garbage, GIGO. Feed them proper raw materials, data, and they generate proper, ordered products, information.
White box knowledge is what you understand about a process or thing. How it works, what it’s made of, why it behaves the way it does. If only understood from the outside, the thing is a Black Box. If understood internally, with cause and effect between inputs and outputs, the thing becomes a White Box.
The ultimate Black Box is the Unknown Unknown random event, condition, or situation which doesn’t correlate with prior knowledge or understanding. Something known to potentially exist, but for which cause and effect relational interaction with known elements can not yet be determined or understood with accuracy or precision. Effects of climate change. Life beyond Planet Earth?
White Box and Black Box are model types for understanding things in a systematic, orderly manner; and being able to correlate, and collaborate understanding and knowledge. Awareness about things happens in stages, along two axes. As diagrammed:
- X axis is the wire-frame Grey Model of the Thing which we are, or should be, concerned about, and need to monitor to ensure fulfillment of our individual and group purposes.
- Y axis defines a level of awareness and concern relative to how we go about making operational decisions about things, using a scale which works in unit and federated interaction models of Things of all scales.
EATSv5 is based on a model of understanding based on a model of concerns. Concern is a matter of degree, and consequence, conditions and circumstances. EATSv5’s modeling framework attempts to reduce all understanding of things to critical aspects of understanding, and then to correlate on the basis of fundamentals. The mission of the software system, the cyber core of EATSv5 is to provide awareness, and tools to deal with concerns. Primarily communications and idea expression tools for the planning and evaluation of architectures of interest.
The specific versions of technologies used in the attachments are often out of data, for example Java 1 or 2; but the general approach and the pattern of thinking in terms of how complex systems are simplified into parsed fundamental components need to be retained as stable frames of reference. In some cases the actual code may no longer work due to deprecation of features within languages.
This is a principle problem of automation. When automation becomes infrastructure, the problem compounds, beyond what automation has helped to create for the manufacture and maintenance of physical systems. At least in physical systems, you can follow a physical trail to discover, uncover, and resolve issues. Plumbing problems can be tracked through physical pipes with fiber optic cables, for colonoscopies and for sewer repair under streets and inside buildings. And if the problems are smaller, or more esoteric, we have microscopes and MRI’s to look at physical effects.
Information flow and physical flow are distinct and different things. Business learned that with Six Sigma techniques. Global supply and distribution chains, for both physical goods and information exchange is here for as long as the rest of humanity, you can’t undo yesterday. You can make better, and better choices today, about what happens tomorrow.
- ABM – Wiley, Joseph Bigus 2001: Constructing Intelligent Agents using Java
- Bootstrap 3
- BOTS – Miscrosoft, David Pallman, 1999
- BOTS – Que, Kate Gregory, 1995: Building Internet Apps
- Capella Studio
- HLA – Prentice Hall, Frederick Kuhl, 1999: Creating Computer Simulation Systems:
An Introduction to the High Level Architecture
- HTML 5 – Apress, Shankar
- Model Futures
- MOF – Wiley, David Marco, 2000: Building and Managing the Meta Data Repository – A Full Lifecycle Guide
- MOF – Wiley, Silverston, 2001: The Data Model Resource Book, Volume 1
- MOF – Wiley, Silverston, 2001: The Data Model Resource Book, Volume 2
- OMG – Wiley, Peter Eeles, 1998
- SF Design Patterns – Addison Wesley, Carey, 2000: IBM San Francisco Evaluator
IBM San Francisco was an experimental workstation project which consisted of “a set of Java-based licensed programs that allow application programmers to develop business applications using object-oriented frameworks. San Francisco frameworks are high-level extendable business application components that are network-enabled, secure, and scalable, and are designed to operate on most Java Virtual Machines.”
EATS, partially by direct reference, has adopted a lot of San Francisco composition and organization patterns. The RedBook provides a good overview of a federated network based on San Francisco, object-oriented pattern-based architecture.
- SIM – Academic Press, Odium, 2000
- SIM – Peters, Bossel, 1994
- UML – Wiley, Eriksson, 2004: UML 2 Toolkit
- UML – Addison Wesley, Marshall, 2000: Business Object Model
- UML – Prentice Hall, Coad, 1999: Java Modeling in Color with UML
- VRML – New Riders, Mark Pesce, 1995
- WIKI – Addison Wesley, Leuf, 2001
- WWW – Thomson, Bob Leasure, 2004
- XML – Sybex, Cagle, 2000
- XML – Wiley, Ceponkus, 1999: APPLIED XML: A TOOLKIT FOR PROGRAMMERS
- AF Glossary of Terms
- Content Developer Guide
- EATSv5 Library
- Image Gallery
- AF Images
- Concept Maps
- EATS Concept Photos Gallery
- EATS Metamodel Image Library
- Industry Standard Models Image Gallery
- Photo Index
- PNG Gallery
- AF Drupal UML 2011 07 22
- AF EATS UML 001-015
- AF EATS UML 016-029
- AF EATS UML GameRobot
- AF Eclipse UML
- AF Logger
- AF Metamodel UML
- AF Metamodel UML 001-015
- AF Metamodel UML 016-030
- AF Metamodel UML 031-045
- AF Metamodel UML 046-060
- AF Metamodel UML 061-075
- AF Metamodel UML 076-090
- AF Metamodel UML 091-105
- AF Metamodel UML 106-120
- AF Metamodel UML 121-135
- AF Metamodel UML 136-150
- AF Metamodel UML 151-165
- AF Metamodel UML 166-179
- AF POC UML 001-015
- AF POC UML 016-030
- AF POC UML 031-045
- AF POC UML 046-060
- AF POC UML 061-075
- AF POC UML 076-090
- AF POC UML 091-105
- AF POC UML 106-121
- AF V3.00 Page Style
- AF WordPress 2011 08 06
- Architecture MBF DFSS Blueprint
- Architecture MBF Program
- Architecture MBF Reusability Metrics
- Architecture UML 001-015
- Architecture UML 016-030
- Architecture UML 031-047
- CIS036B Lab02
- Viewpoint Concept: Perspective Images
- pCloud Library