The definitions and explanations contained herein are intended exactly as the title suggests: they are things I think I know. They should, therefore, not be taken as authoritative (I am no Granddaddy, and neither is this website). Much of the material is gleaned from my collection of System Engineering manuals collected over the years, the earliest of can be dated only as “pre-1980”. Some of the manuals are variants of the Defense Systems Management College textbooks, while others are specific to individual companies or authors.
Some items are a bit speculative, but have worked well for me in the past and proven portable from one project to another. A few of the items are really just stress-relievers. Apparently, I cannot help myself in that regard.
I have, to the best of my ability, linked between definitions/explanations to mitigate the redundancy that would otherwise have eventuated. The necessary consequence of that linking is that the reader will skip around in order to gain a complete picture for many of the basic concepts1.
The list is organized alphabetically:
Footnotes- For which no apology is forth-coming.[↩]