• Proceedings of the Korea Information Processing Society Conference
• /
• 2007.11a
• /
• pp.415-418
• /
• 2007

최근 활발히 진행되고 있는 모델 기반 공학에 관한 연구 중 모델 변환은 소스 모델을 입력 받아 다른 차원의 뷰를 제공하는 타겟 모델을 출력한다. 이러한 모델 변환은 메타모델을 사용하여 동일한 시스템을 서로 다른 이해관계자들의 관점에서 이해할 수 있는 방법을 제공한다. 동일한 시스템이라 하더라도 개발자와 시험자 그리고 사용자들이 보는 주요 관점은 다를 수 있다. 본 논문에서는 시험자의 관점에서 수직적 분할 시험이 가능하도록 입력 모델인 UML의 행위 다이어그램으로부터 출력 모델인 단위 시험을 위한 상태 다이어그램으로의 모델 변환에 대해 연구하고, 생성된 상태 다이어그램을 통해 시험 사례를 작성한다.

• Journal of KIISE
• /
• v.42 no.11
• /
• pp.1410-1422
• /
• 2015

In order to design a system, software developers use an object model such as the UML class diagram. Object-Relational Transformation Methodology (ORTM) is a methodology to transform the relationships that are expressed in the object model into relational database tables, and it is applied for the implementation of the designed system. Previous ORTM studies have suggested a number of transformation methods to represent one relationship. However, there is an implementation problem that is difficult to apply because the usage criteria for each transformation method do not exist. Therefore, this paper proposes a binary decision diagram-based modeling rule for each relationship. Hence, we define the conditions for distinguishing the transformation methods. By measuring the query execution time, we also evaluate the modeling rules that are required for the verification. After evaluation, we re-define the final modeling rules which are represented by propositional logic, and show that our proposed modeling rules are useful for the implementation of the designed system through a case study.

• Journal of Digital Contents Society
• /
• v.11 no.1
• /
• pp.25-38
• /
• 2010

There is no guideline or standard for the specification of the open-source-framework-based Spring AOP, and it causes confusion in development and maintenance. Moreover, the inconsistency between the existing MVC model, the AOP model that is used for Struts framework and the UML diagram makes the aspect reuse more difficult. In this study, a widened existing method was proposed so that Aspect, Pointcut and Advice could be expressed by either UML or XML to ensure that the Spring AOP can accept the combined use of the existing MVC model and the AOP model, which is used for Struts framework. Relationship was defined so that the mutual conversion could be possible with the proposed expression method, and the realization of simple development and maintenance was verified via the examples of mutual conversion. In addition, a packaging method to efficiently reuse aspect was proposed, and the possibility of reuse was verified.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.11
• /
• pp.25-34
• /
• 2011

In this paper we present an integrated design methodology for relational database based on object-oriented analysis and design. The integrated design methodology is based on business profile and has six phases. In the first phase, business use cases are identified and described by macroactivity diagrams and then the macroactivity diagrams are transformed to detailed business activity diagrams by using objects, object flows and business worker's responsibilities. In the third phase, the detailed business activity diagrams are transformed to business class diagrams that describe the static structure of the entire business system based on detailed business activity diagrams. In the four phase, the business class diagrams are transformed to class diagrams that represent the initial conceptual model of the target relational database. In the five phase, we add additional transformations on the class diagrams with generalization and specialization of associations, roles, activities, additional classes and redundant associations. Eventually, the final class diagrams are transformed to relational database schema. The methodology presented in this paper by applying that proposal for organic connection between object-oriented analysis and design methodology and relational database design methodology. And it will be able to deal with integration management. By the integrated design methodology, we can make more easily software systems based on relational database. In the case study, proposal integrated design methodology applied for a visa issuing system.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2010.11a
• /
• pp.340-343
• /
• 2010

스마트폰 어플리케이션은 소프트웨어의 평가를 구매자가 쉽게 확인 및 작성할 수 있어 품질이 매출에 직접적으로 영향을 끼쳐 소프트웨어의 품질을 향상시키기 위해서 테스트가 요구된다. 하지만 기존의 스마트폰 어플리케이션은 테스트 용이성을 고려하지 않고 개발되어 테스트를 위해 많은 비용이 증가한다. 본 논문은 이 문제를 해결하고자 소프트웨어 설계 단계에서 모델변환을 적용하여 테스트 용이성을 향상 시키는 방법을 제안한다. 대상 모델은 UML의 클래스 다이어그램이고 테스트 용이성 측정을 위해서 Binder방법을 사용한다. 적용사례로 안드로이드 기반의 소프트웨어인 SnakePlus를 구현하고, 이를 대상으로 설계 모델을 모델변환을 하여 테스트 용이성을 향상 시킨다.