TY - JOUR
T1 - Managing the integrity of design data generated by multiple applications
T2 - The principle of patching
AU - Eastman, Chuck
AU - Parker, D. Stott
AU - Jeng, Tay Sheng
N1 - Funding Information:
An often used strategy is to use an engineering database (DB) as the product design repository, carrying the data describing a design for use by the multiple users and applications. An extensive literature on database use in engineering design addresses * Research supported by NSF grant IRI-9319982. Correspondence and offprint requests to: Professor C. M. Eastman, College of Architecture, Georgia Institute of Technology, Architecture Building Room 209, Atlanta, GA, USA. E-mail: chuck.-eastman@arch.gatech.edu, tjeng@arch.gatech.edu, stott@cs.ucla. edu.
PY - 1997
Y1 - 1997
N2 - The purpose of this work is to develop automatic methods of semantic integrity maintenance, in support of concurrent engineering. Semantic integrity relations in any final engineering design are built up incrementally, through the use of different computer applications. Here, the structure of these integrity relations are formalised for representation within a database. When changes to a design have to be made, they can invalidate integrity relations in other parts of the design. Formal methods are defined for identifying what data and integrity relations are invalidated by any change. Methods for making changes that minimise re-design are described and formalised. Opportunities for using semantic integrity to assess progress on a design are reviewed.
AB - The purpose of this work is to develop automatic methods of semantic integrity maintenance, in support of concurrent engineering. Semantic integrity relations in any final engineering design are built up incrementally, through the use of different computer applications. Here, the structure of these integrity relations are formalised for representation within a database. When changes to a design have to be made, they can invalidate integrity relations in other parts of the design. Formal methods are defined for identifying what data and integrity relations are invalidated by any change. Methods for making changes that minimise re-design are described and formalised. Opportunities for using semantic integrity to assess progress on a design are reviewed.
UR - http://www.scopus.com/inward/record.url?scp=0030649338&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=0030649338&partnerID=8YFLogxK
U2 - 10.1007/BF01596599
DO - 10.1007/BF01596599
M3 - Article
AN - SCOPUS:0030649338
VL - 9
SP - 125
EP - 145
JO - Research in Engineering Design - Theory, Applications, and Concurrent Engineering
JF - Research in Engineering Design - Theory, Applications, and Concurrent Engineering
SN - 0934-9839
IS - 3
ER -