Abstract
Earlier chapters describe how engineers attempt to capture design work in text. In particular, Chapter 3 shows how the germ of a design idea is often recorded in proposal documents. Within these documents, it is the technical description of the engineers’ design intent that provides a reference point for the drafting of requirements specifications. Promises need to be converted into deeds. Engineers need to revisit the proposed solution to ensure the company delivers what was promised and fulfils its contractual obligations. It may happen that, on returning to the proposed solution, engineers actually improve on the original design and find they change it radically. Whatever course they take, the fact remains that the proposal provides the impetus for writing specifications that, in turn, specify the product or products that are part of the solution.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Copyright information
© 2006 H. E. Sales
About this chapter
Cite this chapter
Sales, H.E. (2006). Engineering Specifications and Requirements. In: Professional Communication in Engineering. Palgrave Studies in Professional and Organizational Discourse. Palgrave Macmillan, London. https://doi.org/10.1057/9780230625143_5
Download citation
DOI: https://doi.org/10.1057/9780230625143_5
Publisher Name: Palgrave Macmillan, London
Print ISBN: 978-0-230-58013-8
Online ISBN: 978-0-230-62514-3
eBook Packages: Palgrave Language & Linguistics CollectionEducation (R0)