30.01.2013 Views

6.3 Suspended Ceiling Design Process - Bilkent University

6.3 Suspended Ceiling Design Process - Bilkent University

6.3 Suspended Ceiling Design Process - Bilkent University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

parameter relationships. However, once an initial model was<br />

produced, it constituted the base for further development.<br />

2. The interviews were just as important as reading design documents,<br />

because all the knowledge was not well captured by design<br />

documents. A large amount of it existed in the designers’ heads.<br />

Interviews seem to be a good means to extract this knowledge.<br />

3. A confusion about the “really-followed” and “should-be followed”<br />

processes occurred during the data collection. The respondents<br />

sometimes tended to describe the process that they thought of as<br />

an ideal one. In these cases, the author explained to the participants<br />

that the aim of the study is to model the process as it occurred.<br />

4. The author introduced both IDEF0 and DSM models to the<br />

participants. The participants understood the IDEF0 notation easier<br />

than that of DSM. This suggests that the DSM method may be<br />

difficult to comprehend for the uninitiated.<br />

6.4.4.3 The IDEF0 Models<br />

Before building DSMs, the author produced IDEF0 models of the<br />

suspended ceiling design process. While producing the diagrams, the<br />

framework proposed in the U.S. NIST (National Institute of Standards)<br />

IDEF0 Standard (U.S. NIST, 1993) was used. Microsoft Visio Professional<br />

Edition was used as the graphical modeling tool. First, an A0 context<br />

diagram was produced for suspended ceiling life cycle (Figures 6.5, 6.6<br />

and 6.7), and then the model was detailed to reflect the design process<br />

128

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!