Content deleted Content added
No edit summary |
No edit summary |
||
Line 1:
There is a large body of knowledge that designers 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''' has been fairly studied and a number of modeling techniques have been
Line 9:
designs. Based on these techniques, a design repository project
at NIST attempts to model three fundamental facets of an
artifact representation <ref>
(form), an indication of the overall effect that the artifact
creates (function), and a causal account of the operation of the
Line 15:
development of the basic foundations of the next generation of
CAD systems suggested a core representation for design
information called the '''NIST core product model''' (CPM) <ref>
a set of derived models defined as extensions of the CPM (e.g.
<ref>X.F. Zha, R.D. Sriram, Feature-based component model for design of embedded system, in: B. Gopalakrishnan (Ed.), Intelligent Systems in Design and Manufacturing, Proceedings of SPIE, vol. 5605, SPIE, Bellingham, WA, vol. V, 2004, pp. 226–237.
</ref><ref>R. Sudarsan, Y.H. Han, S.C. Feng, U. Roy, F. Wang, R.D. Sriram, K. Lyons, Object-oriented representation of electro-mechanical assemblies using UML, NISTIR 7057, NIST, Gaithersburg, MD, 2003.</ref>). The NIST core product model has been developed to
unify and integrate product or assembly information. The CPM
provides a base-level product model that is: not tied to any
Line 32 ⟶ 33:
'''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
Line 40 ⟶ 41:
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>.
In terms of representation scenarios, '''design knowledge''' can
Line 55 ⟶ 56:
collection of design knowledge into a certain case for
description. '''Case-based design''' is an example of this approach
<ref>W.H.Wood III, A.M. Agogino, Case based conceptual design information server for concurrent engineering, Computer-Aided Design 8 (5) (1996) 361–369.
design knowledge representation. For instance, researchers at
the Engineering Design Centre at Lancaster University, UK
Line 68 ⟶ 70:
capture 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>
support system (PROSUS) based on a model of the design
process rather than the product. It uses design matrix to
Line 76 ⟶ 78:
design activity.
'''Ontologies''' are being used for product representation (e.g. <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>
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
Line 118 ⟶ 120:
* 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
* R. Sudarsan, Y.H. Han, S.C. Feng, U. Roy, F. Wang, R.D. Sriram, K. Lyons, Object-oriented representation of electro-mechanical assemblies using UML, NISTIR 7057, NIST, Gaithersburg, MD, 2003.
|