XM Systems Engineering Breakdown Diagram - Revision history

Marcin at 01:56, 9 April 2012

2012-04-09T01:56:41Z

← Older revision		Revision as of 01:56, 9 April 2012
Line 9:		Line 9:
	#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 how it works, the physics of why it works, and other explanatory material that explains the workings to a nonspecialist		#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
	#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.		#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]].

	[[Category:XM]]		[[Category:XM]]

Marcin at 01:56, 9 April 2012

2012-04-09T01:56:01Z

← Older revision		Revision as of 01:56, 9 April 2012
Line 1:		Line 1:
	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.		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:		To build a SEBD:
Line 6:		Line 8:
	#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,		#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
			#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.

	[[Category:XM]]		[[Category:XM]]

Marcin at 04:15, 30 March 2012

2012-03-30T04:15:19Z

← Older revision		Revision as of 04:15, 30 March 2012
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]]

Marcin at 00:34, 28 March 2012

2012-03-28T00:34:44Z

← Older revision		Revision as of 00:34, 28 March 2012
Line 1:		Line 1:
	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.		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:		To build a SEBD:

Marcin at 04:38, 27 March 2012

2012-03-27T04:38:36Z

← Older revision		Revision as of 04:38, 27 March 2012
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:

Marcin: 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..."

2012-03-27T04:17:46Z

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..."

New page

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.

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

[[Category:XM]]