|
There is a large [[body of knowledge]] that designers[[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'''.
==Product Knowledge==
==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 product development process using a multi-tiered DSM is developed at MIT. However, few research endeavors have been found on design rationale.<ref>F. Pena-Mora, R.D. Sriram, R. Logcher, SHARED DRIMS: SHARED design recommendation and intent management system, in: Enabling Technologies: Infrastructure for Collaborative Enterprises, IEEE Press,1993, pp. 213–221.</ref><ref>F. Pena-Mora, R.D. Sriram, R. Logcher, Conflict mitigation system for collaborative engineering, AI EDAM—Special Issue of Concurrent Engineering 9 (2) (1995) 101–123.</ref>
==Representation Scenarios==
===On-line Knowledge===
The '''onOn-line [[knowledge representation]]''' is to capturecapturing the dynamic design knowledge in a certain format for design re-use and archive. A few research efforts have been found in this area. Blessing <ref>L.T.M. Blessing, A process-based approach to computer supported engineering design, Ph.D. Thesis, University of Twente, 1993.</ref> proposes the process-based support system (PROSUS) based on a model of the design process rather than the product. It uses a [[design matrix]] to represent the design process as a structured set of issues and activities. Together with the common product data model (CPDM), PROSUS supports the capture of all outputs of the design activity.
===Ontologies===
'''[[Ontology (information science)|Ontologies''']] are being used for product representation (e.g.<ref>L. Patil, D. Dutta, R.D. Sriram, Ontology-based exchange of product data semantics, IEEE Transactions on Automation Science and Engineering 2 (3) (2005) 213–225.</ref><ref>C. Bock, X.F. Zha, Ontological product modeling for collaborative design, NIST IR, NIST, Gaithersburg, MD, 2007</ref><ref>V.C. Liang, C. Bock, X.F. Zha, Ontological modeling platform, NIST IR, NIST, Gaithersburg, MD, 2008</ref>). Research suggests, therefore, that there is a need to provide computer support that will supply clear and complete design knowledge and also facilitate designer intervention and customization during the decision-making activities in the design process.<ref>A.M. Madni, The role of human factors in expert systems design and acceptance, Human Factors 30 (4) (1988) 395–414.</ref> For example, WebCADET <ref>P.A. Rodgers, A.P. Huxor, N.H.M. Caldwell, Design support using distributed web-based AI tools, Research in Engineering Design 11 (1999) 31–44.</ref> is a design support system that uses distributed Web-based [[AI]] tools. It uses the AI as text approach, where [[knowledge-based systems]] (KBSs) can be seen as a medium to facilitate the communication of design knowledge between designers. The system can provide support for designers when searching for design knowledge.
designers. The system can provide support for designers when searching for design knowledge.
==References==
|
