• Annual Conference of KIPS
• /
• 2005.11a
• /
• pp.91-94
• /
• 2005

공학적 기반의 응용 프로그램에서는 복합관계(complex relationship) 및 복합객체(complex object)의 개념이 요구되는데, 이러한 개념들은 비즈니스 응용에 적합한 관계형 데이터베이스로 다루기에는 저장과 검색 시 많은 문제점을 야기한다. 이와 같은 문제점을 해결하기 위해서 객체 관계형 데이터베이스 시스템이 출현하게 되었다. 한편, 고전적인 데이터베이스 설계 기법은 개체 관계형 모델(Entity Relationship Model)과 같은 개념적 모델을 사용하며 데이터 중심의 구조적 관점(structural aspect)만을 고려하는 반면, UML(Unified Modeling Language)같은 객체지향형 설계 도구를 사용하여 데이터베이스를 설계할 경우 구조적 관점 및 행위적 관점(behavioral aspect)을 모두 포함한다. UML은 확장 가능한 언어로서, 특정 응용프로그램에 대한 새로운 스테레오타입(stereotype)의 사용이 가능하다. 데이터베이스 설계를 위한 확장된 UML의 스테레오타입이 제안되었지만, 대부분 관계형 데이터베이스에 초점이 맞추어져 있다. 본 논문에서는 객체 관계형 데이터베이스 설계를 위한 확장된 UML 스테레오타입을 기술하며, 복합관계 및 복합객체를 지원하기 위해 Aggregation, Composition, Association의 개념을 재정의한 설계기법을 제안하고, 제안한 설계기법을 지원하는 설계 도구(ORDesigner)의 구현에 대해서 기술한다.

• The Journal of Society for e-Business Studies
• /
• v.8 no.1
• /
• pp.85-102
• /
• 2003

Nowadays an information exchange on XML such as B2B electronic commerce is spreading. Therefore the systematic and stable management mechanism for storing the exchanged information is needed. For this goal there are many research activities for connection between XML application and relational database. But because XML data have hierarchical structures and relational database can store only flat-structured data, we need to make the conversion rule which changes the hierarchical architecture to 2-dimensional information. Accordingly the modeling methodology for storing each structured information in relational database is needed. In this paper, we introduce a XML modeling methodology to design W3C XML schema using UML and we propose a unified design methodology for relational database schema to store XML data efficiently in relational databases. In the second place, in order to verify objectivity of a unified design methodology. By the way of Ronald Bourret, First we introduce the method of the transformation from XML schema to object model and second we translate object model into relational database schema. Therefore we show the mutual consistency between those consequence, and so can verify a unified design methodology.

• Proceedings of the IEEK Conference
• /
• 2002.07b
• /
• pp.920-923
• /
• 2002

In this paper, we propose Class Diagram With Constraints (CDWC) as an object oriented modeling technique which makes validation possible in software development. CDWC is a simple and basic model for the object oriented analysis, and has a reasonable strictness for software developers. CDWC consists of class diagrams and constraints (invariant and pre/post conditions), using UML and a subset of OCL.. We introduce a method of validation of CDWC using the verification technique of algebraic formal specification language CafeOBJ.

• Proceedings of the Korean Society of Surveying, Geodesy, Photogrammetry, and Cartography Conference
• /
• 2004.04a
• /
• pp.395-400
• /
• 2004

This study consists of three steps of data modeling procedures. The first step is to identify possible items for the data model based on literature review and expert interviews. The second step is to design delineate possible sub-themes, feature classes, feature types, attributes, attribute domains, and their relationships. These are presented in various UML class diagrams, and each feature type is clearly defined and modeled. The data model also shows geometry objects and their topological relationships in UML diagrams. Finally, a standardized data model has been provided to avoid possible conflicts in the field of geographic and Facility Area, and thus this study and the data model will eventually assist in alleviating efforts to build standardized geographic information databases for Facility Area.

• The KIPS Transactions:PartD
• /
• v.16D no.1
• /
• pp.83-92
• /
• 2009

Complicated business logic makes program complexity more complicated. It's inevitable that the program must undergo reengineering processes all the way of in its lifetime. Hot spot analysis that has diverse purposes is getting an important question more and more. As a rule, reengineering process is done by UML model-based approach to analyze the legacy system. The smallest fragment of targets to be analysed is unit, that is function or class. Today's software development is to deal with huge change of software product and huge class including heavy quantity of LOC(Lines Of Code). However, analysis of unit is not precise approach process for reliable reengineering consequence. In this paper, we propose very precise hot spot analysis approach using Aspect-Oriented Programming languages, such as AspectJ. Typically the consistency between UML and source is needed code to redefine the modified library or framework boundaries. But reengineering approach using AOP doesn't need to analyze UML and source code. This approach makes dynamic event log data that contains detailed program interaction information. This dynamic event log data makes it possible to analyze hot spot.

• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.75-83
• /
• 2011

Unified Modeling Language (UML) is widely accepted in industry and particularly UML State Machine Diagram is popular for describing the dynamic behavior of classes. This paper discusses deadlock detection of System using UML State Machine Diagram. Since a State Machine Diagram is used for indivisual class' behavior, all the State Machine Diagrams of the classes in the system are combined to make a big system-wide State Machine Diagram to describe system behavior. Generally this system-wide State Machine Diagram is very complex and contains invalid state and transitions. To make it a usable and valid State Machine Diagram, synchronization and externalization are applied. The reduced State Machine Diagram can be used for describing system behavior thus conventional model-checking technique can be applied. This paper shows how deadlock detection of system can be applied with simple examples. All the procedures can be automatically done in the tool.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.3
• /
• pp.818-830
• /
• 2000

Automation tools for program analysis are needed in order to program understand and maintain, extract the characteristics of object-oriented program such as class name, member function and data member. In this paper, we carried out design and implementation of the automation tool for effective maintenance of object-oriented software. Being based on Reverse Engineering, this approach extracts class relationship information from C++ source code and generates object-oriented model of class diagram using UML as the standard object-oriented methodology. Therefore, this paper provides developers visualized including class information, definitions of classes, inheritance relationships, set relationships, and simple reference relationships. Finally in this paper, we propose a method that construct class relationship information to table in analysis state and make form of table construction to link form so tat developers can perform understanding and maintaining program efficiently. And this method enable to restructure and reuse in object-oriented model.

• Journal of Internet Computing and Services
• /
• v.12 no.1
• /
• pp.119-130
• /
• 2011

As a de facto standard for system modeling, UML diagrams have been widely used in the industry. Of these, the class diagram is useful to visualize the classes and their relationships and thus directly influences the forward and reverse processes of system modeling and development. Many earlier studies have attempted to examine as to what impact the layout and complexity of the class diagram would have on the comprehension of system modeling. However, their findings have been equivocal and it is not easy to understand the effects of diagram layout. Accordingly this research relied on the guidelines of diagram layout suggested in the earlier studies and designed a 2 (layout) x 2 (complexity) factorial design to examine their impact on diagram comprehension. 47 subjects were participated in the experiment where class diagrams were provided differently in their layout and complexity. We found that a good layout was significantly more effective than the bad. Furthermore the results were significantly persistent in the complex group than the simple. However, there was no interaction effect between layout and complexity of the diagram.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.7 no.6
• /
• pp.1567-1572
• /
• 2012

An IPC(instrument panel Cluster) is a useful device that provides driving information to the driver. The information includes the vehicle speed, RPM, mileage, etc. The traditional IPC has been mostly implemented with mechanical technique. According to increment of needs for the convenience of IPC by user, the IPC must provide graphical interface and efficient driving information. Also the user-friendly IPC is needed by drivers. Thus flexible and robust software structure and development methods are required in order to develop IPC. In this paper, we propose software architecture and design method for the IPC using modeling method. We use MVC model and UML to model software architecture because they have flexible and robust characteristics. We can develop the various forms of information screen by separating views from model by using state diagram and class diagram in UML. Through this, the cost saving and ease of maintenance can be expected. The development time and cost can be reduced by using proposed method.

• The Journal of the Korea institute of electronic communication sciences
• /
• v.7 no.6
• /
• pp.1321-1326
• /
• 2012

An IPC(instrument panel Cluster) is a useful device that provides driving information to the driver. The information includes the vehicle speed, RPM, mileage, etc. The traditional IPC has been mostly implemented with mechanical technique. According to increment of needs for the convenience of IPC by user, the IPC must provide graphical interface and efficient driving information. Also the user-friendly IPC is needed by drivers. Thus flexible and robust software structure and development methods are required in order to develop IPC. In this paper, we propose software architecture and design method for the IPC using modeling method. We use MVC model and UML to model software architecture because they have flexible and robust characteristics. We can develop the various forms of information screen by separating views from model by using state diagram and class diagram in UML. Through this, the cost saving and ease of maintenance can be expected. The development time and cost can be reduced by using proposed method.