XM Systems Engineering Breakdown Diagram

A Systems Engineering Breakdown Diagrams(SEBD) or Systems Ecology Breakdown Diagram breaks up a given GVCS technology (or other project, such as FeF) into components and describes how they relate to one another.

For each component, the Breakdown Diagram should also include possible implementation paths - focusing on those paths that build on existing open source projects, on available documentation, and on other available prior art. The work of OSE is founded on determining a specific implementation path from a set of general funtional units defined by the SEBD - determined by best fit to OSE Specifications. Each component of the SEBD may be based on a wide range of industry standards. Successive prototypes may choose different implementation paths - depending on prototype testing results.

To build a SEBD:


 * 1) Break down the machine or system into components. Annotate the relationships between the different components
 * 2) Document this on a dedicated wiki page for a specific project.
 * 3) Value addition: get an information architect to improve the diagram
 * 4) Annotate the SEBD with essential notes on how it works, the physics of why it works, and other explanatory material that explains the workings to a nonspecialist
 * 5) Once a general SEBD is created, this diagram should be distilled into a Specific SEBD - which reflects the actual development path taken out of a number of different options/mechanisms available. Such selection is based on optimum adherence to OSE Specifications.