Systems Engineering Breakdown Diagrams: Difference between revisions
Jump to navigation
Jump to search
(Created page with "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 b...") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
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 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. | |||
Revision as of 23:12, 30 May 2011
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.
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.