Katz, R. H. R., Bhateja, E., Chang, D. Gedye, and V. Trijanto, "Design Version Management," IEEE Design and Test, Vol 4, No.1, pp. 12-22, Feb. 1987. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Versions, Configurations, and Constraints in CEDB - Howard, Keller, Gupta.. (1994) (Correct)
....as a rooted DAG have been proposed in [Klahold 86, Ecklund 87] The versions are connected by derived from links. Versions of an assembly of entities: Previous research efforts have defined configurations as the version of a composite entity in terms of the versions of its components [Katz 87, Ketabchi 87, Landis 86, Lorie 83] Versions, Configurations, and Constraints in CEDB Draft version: March 29, 1994 page 3 . Inheritance among versions: Type version inheritance [Batory 85] as well as instance instance inheritance schemes along descendant of, equivalent to, and component of ....
Katz, R. H. R., Bhateja, E., Chang, D. Gedye, and V. Trijanto, "Design Version Management," IEEE Design and Test, Vol 4, No.1, pp. 12-22, Feb. 1987.
Managing Engineering Data for Complex Products - Baldwin, Chung (1995) (Correct)
....used by designers, analyst, and managers. One of the main functions of a design framework is design data management managing the enormous amount of data generated during the design process. Design data management includes storing meta data data about the relationships among data entities [10, 17]. Important relationships such as is derived from , is a type of , and is a component of are easily lost when design data is managed in an ad hoc manner. 1.1 The challenge of managing engineering data Complex designs can be synthesized either bottom up or top down. In bottom up synthesis, ....
....family will offer the customer many options, such as size, power, color, and features. Designers must specify the design parametrically as a function of these options. To make navigating through the tremendous amount of design data easier, it must be organized along several different dimensions [10]. First, all the data which describes the same physical entity should be organized such that it can be treated as a collection. Second, a designer may wish to look at the derivation hierarchy to see what alternatives have already been explored. Third, organizing data into a classification ....
[Article contains additional citation context not shown here]
Randy H. Katz, Rajiv Bhateja, Ellis E-Li Chang, David Gedye, and Vony Trijanto. Design version management. In IEEE Design and Test, pages 12--22, 1987.
Handling Lisp Program Structures in an Object-Oriented Database - Ripoche (1993) (Correct)
....expression can be selected from these traces and evaluated later for a different purpose. Practically, each top level expression is stored in a list. The Session class is defined as follows : class Session type tuple(user: string, date: Date, comment: Text, transcript: list(Cell) end; Versions [5, 6, 14] record the history of the modifications on data. Data can be modified by the functions that change the values of symbols (setq, define, or by the functions that physically modify lists (rplaca, rplacd, In order to store the succession of values in symbols, class Symbol is ....
Katz R.H., Bhateja R., Chang E., Gedye D., Trijanto V., Design version management, IEEE DESIGN and TEST, 1987, 12-22.
A Framework-Solution for the EMC-Analysis-Domain based on.. - John, Pörtner (1992) (Correct)
No context found.
R.H. Katz, R. Batheja, E. Chang, D. Gedye, V. Trijanto, Design Version Management, IEEE Design & Test, Feb. 1987, pp. 12-21
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC