Strategic Product Ecology Deployment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
=Rapid Mechanical Package Deployment= | =Rapid Mechanical Package Deployment= | ||
<html><img src="https://docs.google.com/drawings/pub?id=1B2KvJGqnMVFZWWPVsondRMWz7jLmpEFl7uNLmR0szH8&w=480&h=360"></html> | |||
Using [[GVCS_Interface_Design_Standards]] and [[GVCS_Modularity_Pattern_Language]], we can propose the following [[Module-Based Development]] consistent with [[Test Driven Development]] and consistent with uniform [[Interface Design]]. This concept relies on a module focus instead of machine focus - thereby facilitating product ecology deployment rather than the development of a specific machine. | Using [[GVCS_Interface_Design_Standards]] and [[GVCS_Modularity_Pattern_Language]], we can propose the following [[Module-Based Development]] consistent with [[Test Driven Development]] and consistent with uniform [[Interface Design]]. This concept relies on a module focus instead of machine focus - thereby facilitating product ecology deployment rather than the development of a specific machine. | ||
Revision as of 23:45, 26 October 2012
Rapid Mechanical Package Deployment
Using GVCS_Interface_Design_Standards and GVCS_Modularity_Pattern_Language, we can propose the following Module-Based Development consistent with Test Driven Development and consistent with uniform Interface Design. This concept relies on a module focus instead of machine focus - thereby facilitating product ecology deployment rather than the development of a specific machine.