Talk:OSE Systems and Processes

There's a lot to improve here of course. Most of the processes listed should eventually be split off into their own page like the Bid Process. The main thing for this page is to see how the systems fit together. I will continue to refine the capabilities and jobs sections to get a clearer understanding of who we need to look to bring on. --Marshall Smith 23:46, 23 July 2011 (CEST)

-

"Design -> Prototyping -> Test -> Documentation -> Deploy" Do you consider the design phase to be part of the documentation phase? Personally, I think it is misleading to even have a documentation phase. Documentation should pervade each step in the Research -> Design -> Prototype -> Test -> Release" process. Consider:


 * Research: collecting information and requirements needed to start a design - all captured into the wiki documentation system.
 * Design: describe what needs to be built, how it is built, and how it is assembled - done with drawings, descriptions, CAD, etc. - all very important documents.
 * Prototyping: implementing a design - capturing that sub-process in pictures and video will greatly help some one else build it later - this is also documentation.
 * Test: ideally, tests are done against a protocol that describes what is being tested and what the expected results are - the protocols and collected data are all documentation.
 * Release: part of this process is to re-work accumulated information into a form that allows the tool to be built by someone else - formal documentation is part of the release effort.

FWIW, Mjn 04:26, 24 July 2011 (CEST)
 * Thank you for your insightful suggestion. Right now documentation is being handled as it's own thing for a number of reasons but as you point out that's probably not the best way to do it. I've asked Ryan who's working on documentation right now to comment on this as well.
 * --Marshall Smith 16:46, 29 July 2011 (CEST)