How does an organization actually set about developing software ?

Question

At first sight it is a straightforward exercise. A number of modules will be linked and become a baseline. There is a "rachet", "no-return" mechanism so quality is not allowed to fall off. So far so good.

Won't there be lots of undocumented communications, which tend to destroy the project ? As an example, someone asks for a paperless office. By itself the idea might be good. But there can be hundreds of such requests.

Also, offers to assist may be undocumented.

Answer 1

Control the delivery mechanism and only deliver those items that can be reproduced by a configuration management segment of the organization.  In that way there is no magic/mystery about the source code.  The source code can be reviewed at any time.

Answer 2

Here's something from this link.  Try if this helps.  /rhy

http://www.embedded.com/shared/printable...