Systems Engineering Breakdown Diagrams: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
A Systems engineering breakdown diagram defines the components of a given technology and how they are related. The purpose of this diagram is to break down complex devices into bite-size components that can then be tackled effectively by loosely-allied developers in the presence of limited attention span on the part of the developers. This has the potential to leverage valuable contributions from a wide array of developers, within a limited time budget of the developers. | A Systems engineering breakdown diagram defines the components of a given technology and how they are related. The relationships are defined by the [[XM Interface Definition]]. The purpose of this diagram is to break down complex devices into bite-size components that can then be tackled effectively by loosely-allied developers in the presence of limited attention span on the part of the developers. This has the potential to leverage valuable contributions from a wide array of developers, within a limited time budget of the developers. | ||
For the particular needs of the [[GVCS Development Template]], the Systems Engineering Breakdown Diagram focuses on identifying instantiation routes with a maximum amount of open source prior art. Building upon open source knowhow leverages the potential of open source development for rapid, agile development of GVCS technologies. | For the particular needs of the [[GVCS Development Template]], the Systems Engineering Breakdown Diagram focuses on identifying instantiation routes with a maximum amount of open source prior art. Building upon open source knowhow leverages the potential of open source development for rapid, agile development of GVCS technologies. | ||
Revision as of 03:41, 12 March 2012
Introduction
A Systems engineering breakdown diagram defines the components of a given technology and how they are related. The relationships are defined by the XM Interface Definition. The purpose of this diagram is to break down complex devices into bite-size components that can then be tackled effectively by loosely-allied developers in the presence of limited attention span on the part of the developers. This has the potential to leverage valuable contributions from a wide array of developers, within a limited time budget of the developers.
For the particular needs of the GVCS Development Template, the Systems Engineering Breakdown Diagram focuses on identifying instantiation routes with a maximum amount of open source prior art. Building upon open source knowhow leverages the potential of open source development for rapid, agile development of GVCS technologies.
Examples
Some examples of Breakdown Diagrams already found within the project are:
- Open Capitalist Platform - founding theory of Project Breakdown focusing on cost reduction of development - [1]
- Open Source Technology Pattern Language for electromechanical devices
- Industrial Robot - [2]
- Modern Steam Engine - [3]