XM Systems Engineering Breakdown Diagram: Difference between revisions
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
#Document this on a dedicated wiki page for a specific project. | #Document this on a dedicated wiki page for a specific project. | ||
#Value addition: get an information architect to improve the diagram | #Value addition: get an information architect to improve the diagram | ||
#Annotate the SEBD with essential notes on the physics of how it works, | |||
[[Category:XM]] | [[Category:XM]] |
Revision as of 04:15, 30 March 2012
A Systems Engineering Breakdown Diagrams(SEBD) or Systems Ecology Breakdown Diagram outlines all the components of a given GVCS technology (or other project, such as FeF per se) and 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:
- Break down the machine or system into components. Annotate the relationships between the different components
- Document this on a dedicated wiki page for a specific project.
- Value addition: get an information architect to improve the diagram
- Annotate the SEBD with essential notes on the physics of how it works,