• Journal of KIBIM
• /
• v.13 no.2
• /
• pp.37-46
• /
• 2023

The main objective of this study is to propose a method to enhance building safety using the Industry Foundation Classes (IFC) schema in Building Information Modeling (BIM). To achieve this goal, a fire object relationship diagram is created by using the Model View Definition (MVD) and Property Set (Pset) methodology, as well as the Work Breakdown Structure (WBS) based object relationship analysis. The proposed method illustrates how to represent objects and tasks related to fire prevention and human safety during a building fire, including variables that are relevant to these aspects. Furthermore, the proposed method offers the advantage of considering both the IFC object hierarchy and the project work hierarchy when creating new objects, thereby expanding the attribute information for fire safety and maintenance. However, upon confirmation via an IFC viewer after development, a problem with the accuracy of mapping between attributes and objects arises due to the issue of proxy representation of related object information and newly added object information in standard IFC. Therefore, in future research, a mapping method for fire safety objects will be developed to ensure accurate representation, and the scope of utilization of the fire safety object diagram will be expanded. Furthermore, efforts will be made to enhance the accuracy of object and task representation. This research is expected to contribute significantly to the technological development of building safety and fire facility design in the future.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.23 no.12
• /
• pp.1588-1595
• /
• 2019

This paper presents the technique on structuring information of the diagram repository for UML diagrams. Because object interactions are the body of object-oriented programming, this paper handles especially the sequence diagrams and class diagrams among UML diagrams. Based on class diagrams, sequence diagrams represent the procedure of object interactions in run-time and then the corresponding codes are generated from the contents of those sequence diagrams. To do this work, this paper presents a method to construct the information repository for generating code from the contents of sequence diagrams. This paper classifies the five message types of sequence diagrams and then extracts the needed information including items and values on the corresponding message types for constructing message repositories. Because sequence diagram is composed of messages included, the final repository is constructed by collecting each of structured repositories on messages sequentially.

• Journal of Korea Society of Industrial Information Systems
• /
• v.15 no.5
• /
• pp.149-158
• /
• 2010

A messenger program in this paper was designed and implemented using Use Case Diagram, Class Diagram, Activity Diagram, and Sequence Diagram. We selected total 7 major functionalities such as PC server, login, friends management, chatting, file transfer, account management, etc. The followings are various implementation results from this paper. First, developers could easily understand the desired product and programming flow from using UML Diagrams. Second, PDA users could communicate with developers for a long time without time constraints. Third, there was high usability of UML Diagram in the phase of objected-oriented analysis. Forth, it was easy to update and maintain a program.

• Journal of the Korea Society of Computer and Information
• /
• v.7 no.4
• /
• pp.157-162
• /
• 2002

In this paper, we implement the XML and data modeling by the UML tool, in which the class diagram is constructed from the sequence diagram after making the use case diagram. For the XML modeling. the guiding line will be presented to transform the UML class into the XML document, and then an example to draw the XML DTD from the UML class will be also shown. Furthermore, through the proposed data modeling, the integrated design methods for the transformation of the UML class into relational database schema. object-relational database schema and object-oriented database schema also will be proposed. Finally, we will be presented schema for each database system.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.8 no.11
• /
• pp.3896-3915
• /
• 2014

The Reverse k Nearest Neighbor (RkNN) query is valuable for finding objects influenced by a specific object and is widely used in both scientific and commercial systems. However, the influence level of each object is unknown, information that is critical for some applications (e.g. target marketing). In this paper, we propose a new query type, Ordered Reverse k Nearest Neighbor (ORkNN), and make efforts to adapt it in an on-demand scenario. An Order-k Voronoi diagram based approach is used to answer ORkNN queries. In particular, for different values of k, we pre-construct only one Voronoi diagram. Algorithms on both the server and the clients are presented. We also present experimental results that suggest our proposed algorithms may have practical applications.

• The Journal of Society for e-Business Studies
• /
• v.3 no.2
• /
• pp.179-202
• /
• 1998

This study reviews the concept of Integrated Logistic Support(ILS), ILS standards, ILS elements, and the processes of developing ILS elements and Logistics Support Analysis(LSA). It also examines the potentials of applying ILS development process to building CALS systems in commercial sectors in order to accomplish business process innovation and achieve life-cycle cost savings in product and equipment management. In order to utilize the ILS approach for commercial industries, we need customizing the process of Logistics Support Analysis defined in MIL-STD-1388-lA. The success of ILS implementation depends on the determination of the range of ILS elements in relation with the application environment, and the appropriate development of those elements. During the development process, in order to analyze and design logistics flow processes and supporting activities, we suggest the object-oriented logistics process modeling approach with basic concepts and constructs embedded in objects. Several diagrams including Class Diagram, Class-Instance Diagram, and Integrated Instance Diagram, are provided. Simple Steps to follow are suggested for the analysis and design of inter-organizational logistics flow and support processes. The outcomes of the study are expected to contribute to stimulating the utilization of ILS concepts and development process during building commercial CALS systems.

• Proceedings of the Korean Information Science Society Conference
• /
• 1998.10b
• /
• pp.371-373
• /
• 1998

이 기종간의 효율적인 문서 교환을 목적으로 생겨난 SGML(Standard Generalized Markup Language)은 현재 여러 많은 연구기관 및 재단에서 문서의 표준으로 잡아가고 있다. 최근에 와서는 SGML, DTD를 모델링 하기 위한 여러 방법이 제시되고 있다. 본 논문은 이런 SGML, DTD를 객체지향 Class Diagram에 기반 한 형태로 변환하는 알고리즘을 제시한다. 이를 통해 우리는 점점 그 규모가 방대해 지고 있는 SGML 문서를 객체지향 DB로 저장할 수 있게 될 것이다.

• Journal of KIISE:Software and Applications
• /
• v.27 no.4
• /
• pp.357-369
• /
• 2000

SMIL(Synchronized Multimedia integration Language) allows integrating a set of independent multimedia objects into a synchronized multimedia presentation. In this paper, I propose modeling rules, formal models, modeling function and an algorithm for SMIL documents using use case diagram and sequence diagram of UML(Unified Modeling Language), It will be used the use case diagram and collaboration diagram for object-oriented visualizing tool to describe the temporal behavior of the presentation. The main contribution of this paper is that developers of SMIL documents easily generate them using this rules and algorithm. And, the formal models and modeling functions provide an environment for processing object-oriented documents.

• International Journal of Computer Science & Network Security
• /
• v.21 no.5
• /
• pp.139-150
• /
• 2021

Object orientation has become the predominant paradigm for conceptual modeling (e.g., UML), where the notions of class and object form the primitive building blocks of thought. Classes act as templates for objects that have attributes and methods (actions). The modeled systems are not even necessarily software systems: They can be human and artificial systems of many different kinds (e.g., teaching and learning systems). The UML class diagram is described as a central component of model-driven software development. It is the most common diagram in object-oriented models and used to model the static design view of a system. Objects both carry data and execute actions. According to some authorities in modeling, a certain degree of difficulty exists in understanding the semantics of these notions in UML class diagrams. Some researchers claim class diagrams have limited use for conceptual analysis and that they are best used for logical design. Performing conceptual analysis should not concern the ways facts are grouped into structures. Whether a fact will end up in the design as an attribute is not a conceptual issue. UML leads to drilling down into physical design details (e.g., private/public attributes, encapsulated operations, and navigating direction of an association). This paper is a venture to further the understanding of object-orientated concepts as exemplified in UML with the aim of developing a broad comprehension of conceptual modeling fundamentals. Thinging machine (TM) modeling is a new modeling language employed in such an undertaking. TM modeling interlaces structure (components) and actionality where actions infiltrate the attributes as much as the classes. Although space limitations affect some aspects of the class diagram, the concluding assessment of this study reveals the class description is a kind of shorthand for a richer sematic TM construct.

• The Journal of Society for e-Business Studies
• /
• v.9 no.3
• /
• pp.145-154
• /
• 2004

Class extraction of object or component based software development methodology is the major factor for software quality. Each method has the class definition and extraction method however there are some troubles when the beginners try. Especially, the conceptual gap results to make the class extraction hard. This research suggests three diagrams to support it. They are Information diagram, Behavio diagram and Management diagram. They specify which services a stakeholder wants, which information to support the service, which actions to solve the service and who has the responsibility for those. Any analysis process which takes class extraction can utilize these diagrams.