Database supporting evolutionary product model development for design

Charles Eastman, Tay Sheng Jeng

Research output: Contribution to journalArticle

33 Citations (Scopus)

Abstract

This paper presents the facilities in the EDM-2 product modeling and database language that support model evolution. It reviews the need for model evolution as a system and/or language requirement to support product modeling. Four types of model evolution are considered: (1) translation between distinct models, (2) deriving views from a central model, (3) modification of an existing model, and (4) model evolution based on writable views associated with each application. While the facilities described support all for types of evolution, the last type is emphasized. The language based modeling capabilities described in EDM-2 include: (a) mapping facilities for defining derivations and views within a single model or between different models; (b) procedural language capabilities supporting model addition, deletion and modification; (c) support for object instance migration so as to partition the set of class instances into multiple classes; (d) support for managing practical deletion of portions of a model; (e) explicit specification and automatic management of integrity between a building model and various views. The rationale and language features, and in some cases, the implementation strategy for the features, are presented.

Original languageEnglish
Pages (from-to)305-323
Number of pages19
JournalAutomation in construction
Volume8
Issue number3
DOIs
Publication statusPublished - 1999 Feb

Fingerprint

Specifications

All Science Journal Classification (ASJC) codes

  • Control and Systems Engineering
  • Civil and Structural Engineering
  • Building and Construction

Cite this

@article{58c62d2df8ab4d278d2c79633d3ef487,
title = "Database supporting evolutionary product model development for design",
abstract = "This paper presents the facilities in the EDM-2 product modeling and database language that support model evolution. It reviews the need for model evolution as a system and/or language requirement to support product modeling. Four types of model evolution are considered: (1) translation between distinct models, (2) deriving views from a central model, (3) modification of an existing model, and (4) model evolution based on writable views associated with each application. While the facilities described support all for types of evolution, the last type is emphasized. The language based modeling capabilities described in EDM-2 include: (a) mapping facilities for defining derivations and views within a single model or between different models; (b) procedural language capabilities supporting model addition, deletion and modification; (c) support for object instance migration so as to partition the set of class instances into multiple classes; (d) support for managing practical deletion of portions of a model; (e) explicit specification and automatic management of integrity between a building model and various views. The rationale and language features, and in some cases, the implementation strategy for the features, are presented.",
author = "Charles Eastman and Jeng, {Tay Sheng}",
year = "1999",
month = "2",
doi = "10.1016/S0926-5805(98)00079-X",
language = "English",
volume = "8",
pages = "305--323",
journal = "Automation in Construction",
issn = "0926-5805",
publisher = "Elsevier",
number = "3",

}

Database supporting evolutionary product model development for design. / Eastman, Charles; Jeng, Tay Sheng.

In: Automation in construction, Vol. 8, No. 3, 02.1999, p. 305-323.

Research output: Contribution to journalArticle

TY - JOUR

T1 - Database supporting evolutionary product model development for design

AU - Eastman, Charles

AU - Jeng, Tay Sheng

PY - 1999/2

Y1 - 1999/2

N2 - This paper presents the facilities in the EDM-2 product modeling and database language that support model evolution. It reviews the need for model evolution as a system and/or language requirement to support product modeling. Four types of model evolution are considered: (1) translation between distinct models, (2) deriving views from a central model, (3) modification of an existing model, and (4) model evolution based on writable views associated with each application. While the facilities described support all for types of evolution, the last type is emphasized. The language based modeling capabilities described in EDM-2 include: (a) mapping facilities for defining derivations and views within a single model or between different models; (b) procedural language capabilities supporting model addition, deletion and modification; (c) support for object instance migration so as to partition the set of class instances into multiple classes; (d) support for managing practical deletion of portions of a model; (e) explicit specification and automatic management of integrity between a building model and various views. The rationale and language features, and in some cases, the implementation strategy for the features, are presented.

AB - This paper presents the facilities in the EDM-2 product modeling and database language that support model evolution. It reviews the need for model evolution as a system and/or language requirement to support product modeling. Four types of model evolution are considered: (1) translation between distinct models, (2) deriving views from a central model, (3) modification of an existing model, and (4) model evolution based on writable views associated with each application. While the facilities described support all for types of evolution, the last type is emphasized. The language based modeling capabilities described in EDM-2 include: (a) mapping facilities for defining derivations and views within a single model or between different models; (b) procedural language capabilities supporting model addition, deletion and modification; (c) support for object instance migration so as to partition the set of class instances into multiple classes; (d) support for managing practical deletion of portions of a model; (e) explicit specification and automatic management of integrity between a building model and various views. The rationale and language features, and in some cases, the implementation strategy for the features, are presented.

UR - http://www.scopus.com/inward/record.url?scp=0033075853&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=0033075853&partnerID=8YFLogxK

U2 - 10.1016/S0926-5805(98)00079-X

DO - 10.1016/S0926-5805(98)00079-X

M3 - Article

AN - SCOPUS:0033075853

VL - 8

SP - 305

EP - 323

JO - Automation in Construction

JF - Automation in Construction

SN - 0926-5805

IS - 3

ER -