Project Development Template: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
Our experience has shown this procedure to be effective in product development. | Our experience has shown this procedure to be effective in product development. | ||
#'''Product Specification and Design Rationale''' - called Specification - see [[Specifications Specification]]. Clarity on this point is crucial | #'''Product Specification and Design Rationale''' - also called '''Specification''' - see [[Specifications Specification]]. Clarity on this point is crucial, as this is a translation of [[OSE Specifications]] into an actual product design. This is the conversion of high level OSE Specification into specific design parameters. This specification needs to be sufficiently specific to allow any designer to create a full physical design. The mark of a successful Specification is that it is degenerate - | ||
# | # | ||
[[Category:Recruiting]] | [[Category:Recruiting]] | ||
[[Category:Standards]] | [[Category:Standards]] | ||
Revision as of 20:03, 18 February 2012
This build on former work at the
and blog posts from
The latest iteration of the development method is summarized in the roles of the Projects Director
Main Steps of Project Development
Our experience has shown this procedure to be effective in product development.
- Product Specification and Design Rationale - also called Specification - see Specifications Specification. Clarity on this point is crucial, as this is a translation of OSE Specifications into an actual product design. This is the conversion of high level OSE Specification into specific design parameters. This specification needs to be sufficiently specific to allow any designer to create a full physical design. The mark of a successful Specification is that it is degenerate -