XM Systems Engineering Breakdown Diagram: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "A Systems Engineering Breakdown Diagrams (SEBD) outlines all the components of a given GVCS technology and how they relate to one another. For each component, the Breakdown D...")
 
No edit summary
Line 1: Line 1:
A [[Systems Engineering Breakdown Diagrams]] (SEBD) outlines all the components of a given GVCS technology 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 the above options - determined by best fit to [[OSE Specifications]] - from which a prototype implementation path is determined. Successive prototypes may choose different implementation paths - depending on prototype testing results.
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 the above options - determined by best fit to [[OSE Specifications]] - from which a prototype implementation path is determined. Successive prototypes may choose different implementation paths - depending on prototype testing results.


To build a SEBD:
To build a SEBD:

Revision as of 04:38, 27 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 the above options - determined by best fit to OSE Specifications - from which a prototype implementation path is determined. 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
Retrieved from "https://wiki.opensourceecology.org/index.php?title=XM_Systems_Engineering_Breakdown_Diagram&oldid=57886"