Content deleted Content added
m Citation for for product development company Tags: Reverted Visual edit Mobile edit Mobile web edit |
m Normalize {{Multiple issues}}: Remove {{Multipleissues}} for only 1 maintenance template(s): COI |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1:
{{COI|date=January 2022}}
There is a large [[body of knowledge]] that [[designer]]s call upon and use during the [[design process]] to match the ever-increasing complexity of design problems.<ref>X.F. Zha, H. Du, Knowledge intensive collaborative design modeling and support, part I: Review, distributed models and framework, Computers in Industry 57 (2006) 39–55</ref> '''Design knowledge''' can be classified into two categories:<ref>M. Stokes, Managing Engineering Knowledge: MOKA Methodology for Knowledge Based Engineering Applications, MOKA Consortium, London,2001.</ref> '''product knowledge''' and '''design process knowledge'''.
Line 6 ⟶ 8:
==Design Process Knowledge==
'''Design process knowledge''' can be described in two levels: design activities and design rationale.<ref>X.F. Zha, R. D. Sriram, et al., Knowledge-intensive collaborative decision support for design process: hybrid decision support model and agent, Computers in Industry 59 (2008)</ref> The importance of representation for design rationale has been recognized but it is a more complex issue that extends beyond artifact function. The [[design structure matrix]] (DSM) has been used for modeling design process (activities) and some related research efforts have been conducted. For example, a web-based prototype system for modeling the
==Representation Scenarios==
|