Content deleted Content added
TheDude2006 (talk | contribs) |
TheDude2006 (talk | contribs) m tied to wikifi the article |
||
Line 1:
{{cleanup|date=February 2009}}
{{expert|date=February 2009}}
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==
'''Product knowledge''' has been fairly studied and a number of modeling techniques have been
developed. Most of them are tailored to specific products or
specific aspects of the design activities. For example, [[geometric
modeling]] is used mainly for supporting detailed design, while
[[knowledge modeling]] is working for supporting conceptual
designs. Based on these techniques, a design repository project
at [[NIST]] attempts to model three fundamental facets of an
artifact representation <ref>S. Szykman, R.D. Sriram, W. Regli, The role of knowledge in
(form), an indication of the overall effect that the artifact
creates (function), and a causal account of the operation of the
artifact (behavior). The recent NIST research effort towards the
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>S.J. Fenves, A core product model for representing design information, NISTIR 6736, NIST, Gaithersburg, MD, 2001.</ref> and
a set of derived models defined as extensions of the CPM (e.g.
Line 29 ⟶ 32:
focuses on artifact representation including function, form,
behavior, material, physical and functional decompositions,
and relationships among these concepts. The [[entity-relationship]]
data model influences the model heavily; accordingly, it
consists of two sets of classes, called object and relationship,
equivalent to the [[UML]] class and association class, respectively.
==Design Process Knowledge==
'''Design process knowledge''' can be described in two levels:
Line 44 ⟶ 49:
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==
In terms of representation scenarios, '''design knowledge''' can
also be categorized into off-line and on-line knowledge. Design process knowledge can be categorized into ontologies.
The former refers to existing knowledge representation,▼
===Off-line Knowledge===
including design knowledge in handbook and design ‘‘know-how’’,
etc.; the latter refers to the new design knowledge
Line 54 ⟶ 65:
representation approaches. One is to highly abstract and
categorize existing knowledge including experiences into a
series of design principles, rationales and constraints. [[TRIZ]] is a
good instance of this approach. The other is to represent a
collection of design knowledge into a certain case for
Line 64 ⟶ 75:
established a unique knowledge representation methodology
and knowledge base vocabulary based on the theory of
domains, design principles and [[computer modeling]]. They have
developed a radical software tool for engineering knowledge
management. The tool provides an engineering system designer
with the capability to search a knowledge base of past solutions,
and other known technologies to explored viable alternatives
for product design.
===On-line Knowledge=== The '''on-line knowledge representation''' is to 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>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
(CPDM), PROSUS supports the capture of all outputs of the
design activity.
=== Ontologies ===
'''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
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
▲tools. It uses the ‘‘AI as text’’ approach, where '''knowledge-based systems''' (KBSs) can be seen as a medium to
designers. The system can provide support for designers when
searching for design knowledge.
| |||