Browse Prior Art Database

Data Management System for Composite Feature Modeling

IP.com Disclosure Number: IPCOM000112780D
Original Publication Date: 1994-Jun-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 4 page(s) / 90K

Publishing Venue

IBM

Related People

Numao, M: AUTHOR [+2]

Abstract

A system is disclosed that manages the data of a feature-based 3D solid modeler, with the unit of a composite feature using a concept class hierarchy.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Data Management System for Composite Feature Modeling

      A system is disclosed that manages the data of a feature-based
3D solid modeler, with the unit of a composite feature using a
concept class hierarchy.

      A composite feature is a chunk of information for CAD/CAE
systems that contains a partial form of mechanical parts and its
attributes, like hole and bearing.  It can be more complicated than
conventional features.  Therefore, on composite feature modeling,
namely, using composite features as a unit of modeling, the modeling
process gets more efficient.  At the same time, the design process is
regarded as a process to build the more complicated composite feature
from available composite features.  Consequently, the management of
composite feature data that were previously generated is critical to
the efficiency of the modeling process.  The disclosed system stores
and retrieves composite features that are created during the modeling
process, in a designer-friendly way using concept classes.

      Fig. 1 shows the system configuration.  In this Figure, CF
represents Composite Feature.  There are two components.  One is the
database server 1 that stores the composite feature data using class
hierarchy.  This component is isolated so that multiple clients,
namely, CAD applications, can access the database at the same time.
Another is the component included in existing CAD system 2, where
extract 3/re-attach 4 composite feature data is available from/to CAD
models and register/query 5 the data is available to/from the
database server.

      In the database, a concept class hierarchy like Fig. 2 is
configured.  Each class represents a concept of composite features,
like step or hole.  A composite feature is stored as an instance of
the most specific class among the classes that imply it.

      Basically, the description of a class can be any form, provided
that the r...