C2MS12 — Rework "Introduction to Specification" into a Section Describing Expected Use

There is frequently confusion about how C2MS should be used. Normal use patterns are not described in the C2MS document, and this would be useful to add as a guide to users. This is especially true when C2MS is used in an enterprise environment, because common interpretation is critical.

The section titled: "Introduction to Specification" needs evaluation and at least some rework. This is largely written as a "how we got to here" section, but could use more C2MS-centric language. Also, this should be considered to be moved from the front matter to a numbered section, such as perhaps 5.1 (moving the existing 5.1 to 5.2), and perhaps called "System Architecture", "Guidance", "User Guide", or something like that.

If moved to a numbered section, it needs to be marked "Informative".

The idea is to communicate context for how C2MS has been created and how it is expected to be used.

One concept to make clear is that it does not require a message bus, but that is one expected use. Also, that when using message bus architecture, that more than one bus is a probable solution for many issues. For example, raw TLM might flow on one bus, MVALs on another, Replay on another.