• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 2002.10a
• /
• pp.211-218
• /
• 2002

An entity-based integrated design product and process model uses product and process entities to describe design information and design activities, respectively. The concepts and notation for product and process entities in the entity-based integrated design model are similar to the concepts of object-oriented programming languages such as C++ and Smalltalk. This paper uses C++ to program an entity-based integrated design model for building frames structures. The design information and activities involved in the three dimensional building space, the locations of frames, and the grouping of frames represented as entities in the entity-based integrated design model are transformed to C++ codes. Each product or process entity can be basically transformed to an class. The attributes of an entity can be defined as variables and member functions of a class.

• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 1998.04a
• /
• pp.191-198
• /
• 1998

An entity-based integrated design model can be used to organize and represent information and activities involved in design. The model involves a number of product and process entities. Product entities describe design information, and process entities describe design activities. The relationships among entities Includes organizational, interaction, and sequence relationships. The paper focuses interaction relationships among design information. The interaction relationships can be represented as constraints. Types of constraints includes demand constraints, dependency constraints, and interaction constraints. The paper describes dependency and Interaction constraints. The concepts of representing and processing dependency and interaction constraints in an entity-based integrated design model are presented.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.11 no.5
• /
• pp.11-17
• /
• 2011

In this paper, we propose ER_Modeler, which is a logical database design tool based on entity-relationship model. ER_Modeler provides the entity-relationship diagrams to be built graphically on windows and generates the graphs into the appropriate data definition language for creating relational database tables. Furthermore, ER_Modeler provides the import/export functions using XML to guarantee the interoperability with ERwin which is one of the most popular commercial products.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.17 no.2
• /
• pp.223-234
• /
• 2014

This paper proposes a flexible and highly reusable modeling methodology for a next-generation combat entity which enables joint analysis of performance/engagement effectiveness. According to the scope of the proposed work, the paper is divided into two parts; Part 1 focuses on a conceptual model design, whereas Part 2 proposes detailed model specification and implementation. In Part 1, we, first, classify the combat entity model as combat logic and battlefield function sub-models for joint analysis. Based on the sub-models, we propose two dimensional model partition method, which creates six groups of a single combat entity model by two dimensions: three-activity and two-abstraction. This grouping enables us to reconfigure the combat entity model by sharing the same interface within the group, and the same interface becomes the fundamental basis of the flexible model composition. Furthermore, the proposed method provides a model structure that effectively reflects the real world and maximizes the multi-level reusability of a combat entity model. As a case study, we construct a model design for anti-surface ship warfare. The case study proves enhancement of model reusability in the process of scenario expansion from pattern running to wire guided torpedo operations.

• Proceedings of the Computational Structural Engineering Institute Conference
• /
• 1997.10a
• /
• pp.189-196
• /
• 1997

The development of computer integrated systems for structural design requires models to describe and organize information and activities involved in design. An entity-based integrated design model involves a number of product and process entities. Product entities and process entities describe design information and design activities, respectively. One type of relationships among entities is interaction relationships, which describe interdependencies among design information. The interaction relationships can be represented as constraints. Types of constraints include demand constraints, dependency constraints, and interaction constraints. The concepts of representing and processing demand constraints in an entity-based integrated design model are presented.

• Korean Journal of Construction Engineering and Management
• /
• v.5 no.4 s.20
• /
• pp.79-86
• /
• 2004

One of the most difficult tasks in pavement management information systems is establishing the links between performance measures of a structure and the design and construction inputs. In-situ pavement performance can be considered a response variable to many project input variables, such as design, construction, and traffic loading effects. If we are to fully understand the component of pavement performance and specify the inputs through design and construction specifications to achieve that performance we must develop quantitative relationship between input and response variables through a scientific, fully integrated Pavement Performance Analysis System (PPAS). Hence, the objective of this study is to design a database model required for developing an effective database template that will allow analysis of pavement performance measures based on design and construction information linked by location. In order to select the most appropriate database model, a conceptual database model (Entity Relationship Model) and dimensional model, which is believed to be the most effective modeling technique for data warehouse project, are designed and compared. It is believed that other state highway agencies could adopt the proposed design strategy for implementing a PPAS at the discretion of the state highway agencies.

• Korean Journal of Computational Design and Engineering
• /
• v.9 no.3
• /
• pp.226-237
• /
• 2004

If the topology changes in the re-generation step of the history-based and feature-based CAD systems, it is difficult to identify an entity in the old model and find the same entity in the new model. This problem is known as 'persistent naming problem'. To exchange parametric CAD models, the persistent naming problem and the naming mapping problem must be solved among different CAD system, which use different naming scheme. For CAD model exchange the persistent naming has its own characteristics compare to that for CAD system development. This paper analyses previous researches and proposes a solution to the persistent naming problem for CAD model exchanges and to the naming mapping problem among different naming schemes.

• Korean Journal of Computational Design and Engineering
• /
• v.11 no.1
• /
• pp.27-40
• /
• 2006

The exchange of parameterized feature-based CAD models is important for product data sharing among different organizations and automation systems. The role of feature-based modeling is to gonerate the shape of product and capture design intends In a CAD system. A feature is generated by referring to topological entities in a solid. Identifying referenced topological entities of a feature is essential for exchanging feature-based CAD models through a neutral format. If the CAD data contains the modification history in addition to the construction history, a matching mechanism is also required to find the same entity in the new model (post-edit model) corresponding to the entity in the old model (preedit model). This problem is known as the persistent naming problem. There are additional problems arising from the exchange of parameterized feature-based CAD models. Authors have analyzed previous studies with regard to persistent naming and characteristics for the exchange of parameterized feature-based CAD models, and propose a solution to the persistent naming problem. This solution is comprised of two parts: (a) naming of topological entities based on the object spore information (OSI) and secondary name (SN); and (b) name matching under the proposed naming.

• Archives of design research
• /
• v.13 no.4
• /
• pp.67-76
• /
• 2000

Websites support various user activities in a wide range of contents domain and so they require different approach to extract principal design problems. In the point of media perspective on websites, this paper figures out the relationship between designer, user and website and discusses design factors of usability. It aims for the basic framework for interface design. In the media perspective website is an information entity mediating user and designer. Information entity is composed of various design factors relating to user, designer, website and others. It intends that user and information entity are accommodative to each other and have common conceptual model. To do so it is necessary for achieving usability objectives such as effectiveness, efficiency and satisfaction based on the understanding user goal, cognitive and affective characteristics. In the point of usability we examine design factors and features that are appropriate for users cognitive and affective function according to information entity model that constitutes contents, organization and representation level.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.1-12
• /
• 2005

The XML is emerging as standard language for data exchange on the Web. Therefore a demand of XML Schema(W3C MLL Schema Spec.) that verifies XML document becomes increasing. However, XML Schema has a weak point for design because of its complication despiteof various data and abundant expressiveness. This paper shows a simple way of design for XML Schema using a fundamental means for database design, the Entity-Relationship model. The conversion from the Entity-Relationship model to XML Schema can not be directly on account of discordance between the two models. So we present some algorithms to generate XML Schema from the Entity-Relationship model. The algorithms produce XML Schema codes using a hierarchical view representation. An important objective of this automatic generation is to preserve XML Schema's characteristics such as reusability, global and local ability, ability of expansion and various type changes.