PDF

Description

Object-oriented concepts can make a design database more reactive to changes in its contents. By embedding change semantics in the database model, the design engineer can be relieved of managing the detailed effects of changes. However, mechanisms are needed to limit the scope of change propagation and to unambiguously identify the objects to which propagated changes should apply. We propose new mechanisms, based on group check-in/check-out, browser contexts and paths, configuration constraints, and rules, to support a powerful automatic change capability within a design database.

Details

Files

Statistics

from
to
Export
Download Full History