<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">469072830</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180323132926.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170328e19920601xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/BF01580149</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/BF01580149</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Cooperation in aircraft design</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Alan Bond, Richard Ricci]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">We describe how aircraft are designed in a large organization. We discuss the different phases of design and interaction with the customer. We then describe the models used by each specialist department and the interactions among departments during the design process. We observe that the main design choices are refinement operations on the design. We then briefly describe how the negotiation process is controlled by an organizationally agreed sequence of commitment steps. We then describe negotiation at higher levels in the organization. What decisions are made, the compromises worked out, and the effect of these higher-level commitments on the design process. We conclude that: (1) aircraft design proceeds by thecooperation ofspecialists (specialist teams or departments); (2) each specialist has its ownmodel of the design, and may use several different models or partial models for different purposes; (3) specialists have limited ability to understand each other's models. They communicate using ashared vocabulary, but not necessarily shared technical knowledge; (4) design proceeds by successiverefinement of the models, which are coordinated and updated together; (5) the design decisions, which are acts of commitment and model refinement, arenegotiated by the specialists among themselves; (6) one way this negotiation process is organized and controlled is by the use ofcommitment steps; (7) negotiations occur at higher levels in the organization, resulting in commitments which greatly influence and constrain the design process and its organization, and which have the greatest effect on the cost of the product.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer-Verlag New York Inc, 1992</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Bond</subfield>
   <subfield code="D">Alan</subfield>
   <subfield code="u">Manufacturing Engineering Program, University of California, Los Angeles, California, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Ricci</subfield>
   <subfield code="D">Richard</subfield>
   <subfield code="u">Automation Systems, Lockheed Aeronautical Systems Company, Burbank, California, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Research in Engineering Design</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">4/2(1992-06-01), 115-130</subfield>
   <subfield code="x">0934-9839</subfield>
   <subfield code="q">4:2&lt;115</subfield>
   <subfield code="1">1992</subfield>
   <subfield code="2">4</subfield>
   <subfield code="o">163</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/BF01580149</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/BF01580149</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Bond</subfield>
   <subfield code="D">Alan</subfield>
   <subfield code="u">Manufacturing Engineering Program, University of California, Los Angeles, California, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Ricci</subfield>
   <subfield code="D">Richard</subfield>
   <subfield code="u">Automation Systems, Lockheed Aeronautical Systems Company, Burbank, California, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Research in Engineering Design</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">4/2(1992-06-01), 115-130</subfield>
   <subfield code="x">0934-9839</subfield>
   <subfield code="q">4:2&lt;115</subfield>
   <subfield code="1">1992</subfield>
   <subfield code="2">4</subfield>
   <subfield code="o">163</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
