Re: Developments in the review cycle

[Gene Kim-Eng <techwr -at- genek -dot- com>]

If you're documenting hardware, there's usually a lot more that dictates 
the content than some developer or product manager's predictions of how 
the end product will be used. Failure mode analysis, safety reviews, 
reliability testing, etc., all produce content that needs to be 
documented somewhere, though not necessarily in what ships with the 
product. And once the development gets beyond a certain point, 
additional changes mean that all that analysis, review and testing needs 
to be thrown out and done all over again. And then there's all the stuff 
in the production pipeline that would have to be reworked or scrapped.

So yes, it certainly is possible to reach a point where "no more 
development is possible" if you expect to actually make any money on 
what you're developing.

I have never worked on a HW project where documentation development 
ended up being the critical path to product release. Not that it's 
impossible, but you'd almost have to try to make it happen.

SW, of course is an entirely different kettle of fish. There it's almost 
SOP.

Gene Kim-Eng


On 4/11/2016 6:03 PM, Keith Hood wrote: