For pt.I see ibid., vol.32, no.2, p.83-93 (1991). The authors explore the two-year Danish CIM/GEMS project in computer-integrated manufacturing (CIM) at the Technical University of Denmark to show how writing is an act of technology and knowledge representation, a vehicle of their transfer to a user community, and, if successful, an accommodation of technology to its users. They address creators and users of system documentation who need documentation for CIM implementation. The authors argue that documentation is often better for representing and explaining a CIM system than the actual system itself, and they recommend that documentation production be viewed not as a separate, end-of-project activity but as an integrated part of technical development. Planned and regular documentation production can in fact be a stimulus and aid to technical development, possibly even shortening the project life cycle.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The documentation effort undertaken by the Danish CIM/GEMS (computer-integrated manufacturing: general methods for specific solutions) project to drive, direct, and support its CIM-technology development and transfer activities is described. The project recognized that in the phases of CIM development-from planning through maintenance-the primary deliverable is not the CIM system itself, but the documentation used to describe, specify, justify, and support its development and use. As a result, the project organized itself so that it would transfer to its industry participants the information needed to build CIM systems, and not CIM technology alone. Because this information best resides in well-written and complete documentation, the CIM/GEMS project adopted a management-by-document approach, treating documentation activities as part of system development and assigning professional personnel to the task. As an archive of CIM-system development, the documents captured the project's in-progress work and the knowledge of developers who performed that work. As a deliverable, the documents were the principal means for carrying CIM knowledge and experience off-site.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>