Merge Workflow: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The key to successful management of large scale, global, open development collaboration - hardware or software - is Modular Breakdown.") |
No edit summary |
||
| Line 1: | Line 1: | ||
The key to successful management of large scale, global, open development collaboration - hardware or software - is [[Modular Breakdown]]. | The key to successful management of large scale, global, open development collaboration - hardware or software - is [[Modular Breakdown]] of complex projects into small parts. | ||
For the case of hardware designs - modular breakdown means that we break machines and product systems down to their smallest components. | |||
Tracking any development effectively, and collaborating on a large scale - requires that each component is distinguished from the overall product - such that it can be developed independently and in parallel with many other components. | |||
Thus, parallel development can exist on the level of an overall product, its module, and its sub-modules or components. | |||
To document products and components, we use [[Part Libraries]]. | |||
Revision as of 20:56, 27 October 2019
The key to successful management of large scale, global, open development collaboration - hardware or software - is Modular Breakdown of complex projects into small parts.
For the case of hardware designs - modular breakdown means that we break machines and product systems down to their smallest components.
Tracking any development effectively, and collaborating on a large scale - requires that each component is distinguished from the overall product - such that it can be developed independently and in parallel with many other components.
Thus, parallel development can exist on the level of an overall product, its module, and its sub-modules or components.
To document products and components, we use Part Libraries.