2003
DOI: 10.1080/09544820310001606902
|View full text |Cite
|
Sign up to set email alerts
|

A collaborative design system for product data integration

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2009
2009
2018
2018

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 35 publications
(10 citation statements)
references
References 1 publication
0
10
0
Order By: Relevance
“…Nonetheless, it can be said that the constraint-based design approach is one of the efficient ways of allowing multidisciplinary design participants to share their heterogeneous design knowledge and resolve their conflicts (e.g. Kleiner et al 2003) and collaborative design starts with an effort to find a common way of representing and manipulating the design problem.…”
Section: Limitations and Future Researchmentioning
confidence: 99%
“…Nonetheless, it can be said that the constraint-based design approach is one of the efficient ways of allowing multidisciplinary design participants to share their heterogeneous design knowledge and resolve their conflicts (e.g. Kleiner et al 2003) and collaborative design starts with an effort to find a common way of representing and manipulating the design problem.…”
Section: Limitations and Future Researchmentioning
confidence: 99%
“…In the industrial realm there have been similar attempts to co-ordinate information flows through the design process (Broadbent et al 1999, Davis et al 2001, Roller et al 2002, Kleiner et al 2003 to improve design team performance. Document-centric systems, such as the LIRÉ system (Davis et al 2001) developed at Carnegie Mellon University and based on an extensive information flow analysis in order to deduce design team workflow, attempt to utilise the undoubted potential of digital information storage for quick retrieval and utilisation but do not generally address the characteristics of team interaction, particularly during specialist tasks such as concept generation.…”
Section: Groupwarementioning
confidence: 99%
“…Links are then defined in the corresponding format while translators convert the information from the common model to the application-specific models and vice versa. Although this approach was very often undertaken, [1][2][3][4][5][6] no unified standard has yet evolved to describe product data in a common format which can be used across various disciplines and for the design of different product types.…”
Section: A Unified Product Model For Data Consistencymentioning
confidence: 99%