• Journal of KIISE:Software and Applications
• /
• v.30 no.12
• /
• pp.1193-1207
• /
• 2003

Various web applications are developed as the Internet is popularized in many fields. However, in most cases of web application development, systematic analysis is omitted and developers jump into the implementation. Therefore developers have difficulties with applying the development methods for a large scale project. The approach of creating an analysis models of a web application from a business model is proposed for the rapid and efficient development. The analysis process, tasks and techniques are proposed for this approach. The use case diagram and web page list are created from business modes that is depicted using the notation of UML activity diagram. The page diagram and logical / physical database models are created using the use case diagram and the web page list. These analysis models are refined during the detailed design phase. The efficiency of proposed method has been shown using a practical case study which reflects the development project of the web application for supporting the association of auto repair shops.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.8
• /
• pp.1970-1976
• /
• 2009

It is more emphasized on the software architecture recently, as the scale of a software becomes huge and the need of the software management becomes more dynamic. Software architecture is a representation of structures of software framework just like the blueprint of building architecture. In order to describe software components and their relationships accurately and entirely, software architecture is documented in some different views, by using of modeling tools. UML(Unified Modeling Language) is a software modeling tool recently used for documentation of software and as well as software architecture. Nevertheless, what we have to agree with is that UML is not easy to use and its standard changed continuously. And also the documentation with UML is found some burden because of its difficulties in learning and using. This inconvenience enforces us to purchase and use commercial tool for UML. The study introduces the architecture views refined from 4+1 Views for architecture design and shows how to represent architecture views for software architecture. Especially, we simplifies UML diagrams for the purpose of focusing on architecture views and facile manipulation. At the end, we add the evaluation on the refined architecture views as well as refined UML diagram.

• The KIPS Transactions:PartD
• /
• v.15D no.1
• /
• pp.87-98
• /
• 2008

In company with the demand of powerful processing units for embedded systems, the method to develop embedded software is also required to support the demand in new approach. In order to improve the resource utilization and system performance, software modeling techniques have to consider the features of hardware architecture. This paper proposes a partitioning technique of UML-based software models, which focus the generation of the allocatable software components into multiprocessor architecture. Our partitioning technique, at first, transforms UML models to CBCFGs(Constraint-Based Control Flow Graphs), and then slices the CBCFGs with consideration of parallelism and data dependency. We believe that our proposition gives practical applicability in the areas of platform specific modeling and performance estimation in model-driven embedded software development.

• Journal of the Korean Institute of Intelligent Systems
• /
• v.15 no.6
• /
• pp.780-787
• /
• 2005

Many researches and validations for the complexity metrics of the object-oriented systems have been studied. Most of them are aimed for the measurement of the partial aspects of the systems, for example, the coupling between objects, the complexity of inheritance structures, the cohesion of methods, and so on. But the software practitioners want to measure the complexity of overall system, not partial. We studied the complexity of the overall structures of object-oriented systems by analyzing the class diagram of UML. The class diagram is composed of classes and their relations. There are three kinds of relations, association, generalization, and aggregation, which are making the structure of object-oriented systems to be difficult to understand. We proposed a heuristic metric to measure the complexity of object-oriented systems by putting together the three kinds of the relations. Tn analyze the complexity of the structure of a object-oriented system for the maintainability of the system, we measured the degree of understandability of it, the reverse engineering time to draw a class diagram from the source codes, and the number of errors in the diagram. The results of this experiment shows that our proposed metric has a considerable relationship with the complexity of object-oriented systems. The metric will be helpful to the software developers for their designing tasks by evaluating the complexity of the structures of object-oriented systems and redesigning tasks , of them for the future maintainability.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.133-136
• /
• 2004

데이터 웨어하우스(Data Warehouse : DW)는 데이터베이스에 저장되어 있는 데이터를 신속한 의사 결정 지원을 위해 최종 사용자가 여러 곳의 기업 내에 흩어져 있는 방대한 데이터를 손쉽고 빠르게 접근할 수 있도록 활용되고 있다. 현재 데이터 웨어하우스의 중요성이 부각되고 있는 가운데 온라인 분석 처리(On Line Analytical Processing : OLAP) 시스템이 데이터 웨어하우스 안에서 활용되고 발전되고 있다. 기존 연구에서는 서로 다른 OLAP 제품에서 공통으로 사용할 수 있는 모델을 적용하여 OLAP 메타데이터 교환 시스템을 설계해왔다. 그러나 본 논문에서는 서로 다른 OLAP 제품을 공통으로 사용할 수 있는 질의 언어 시스템 설계 전 단계인 논리적 설계를 UML snowflake 다이어그램을 이용하여 설계 하였다. 실험결과, XML 문서의 변환된 OLAP 메타 데이터를 이용하여 UML snowflake 다이어그램 설계를 통해 통합된 OLAP 제품의 XML 문서 구조가 논리적으로 설계되어 메타 데이터가 통합됨을 알 수가 있다.

• Korean Journal of Ecology and Environment
• /
• v.38 no.spc
• /
• pp.76-83
• /
• 2005

The marked increase in the number of environmental problems, combined with the increase in their intensity and spatial extent, has resulted in an ever-increasing need for constant monitoring. This is complicated by the occurrence of new and complicated environmental issues that often prevent a thorough understanding of the entire monitoring framework. In the present study, a diagrammatic method was developed to present the entire framework of a monitoring plan. The diagram was separated into three sections- "Problem Section", "Research Process and Data Section" and "Entities Section" - to clearly present the disparate relationships between monitoring objectives and the monitoring procedure. Notation of the diagrams was undertaken using Unified Modeling Language (UML). A hypothetical monitoring plan for an environmental problem was designed to assess usefulness of the diagrammatic method. The diagram was capable of reviewing and revising the monitoring plan and could be used to select a monitoring procedure according to the monitoring objectives of the plan. The results suggested that this diagrammatic method was effective for designing an appropriate monitoring plan for a given monitoring objective.

• Proceedings of the Korean Information Science Society Conference
• /
• 1999.10a
• /
• pp.513-515
• /
• 1999

웹은 소규모 정보에서 대규모 서비스에 이르기까지 광범위한 영역을 가지고 다양한 서버와 분산된 작업흐름 시스템에 대한 전역적인 환경으로 발전되어 오고 있다. 웹을 기반으로 하는 애플리케이션은 플랫폼에 관계 없이 접근가능한 브라우저와 표준화된 문서환경을 제공하며, 최소의 비용으로 단시간에 개발과 유지보수가 용이하다. 이러한 장점은 구조적인 변화와 웹 기반 구현기술의 발전을 가져왔지만 대부분의 웹 애플리케이션의 생성은 체계적인 프로세스없이 개발자의 지식과 경험에 의존하여 임시적으로 개발되어 왔다. 따라서, 고수준의 추상화를 제공하지 않는 저수준 기술에 기반한 애플리케이션 개발을 개선하고 웹을 기반으로한 애플리케이션 구축에 적용가능한 컴퍼넌트기반 개발 프로세스를 제안한다. 또한, 웹 애플리케이션에 적용 가능한 컴퍼넌트를 개발하기 위해서 분석, 설계 모델링 방법으로 네비게이션 다이아그램을 사용한다. 이는 모델링을 위한 고수준의 추상화 정의를 가능하게 함으로써 역으로의 개발을 통한 유지보수가 가능하며 구현기술의 재사용성을 기대할 수 있다.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.9
• /
• pp.349-354
• /
• 2019

s programming education becomes more important in recent years, it is necessary to learn how the source code written by students reflects Object-Oriented(OO) concepts. We present a tool called the Round-Trip Translator(RTT) that transforms the Unified Modeling Language(UML) class diagram and Java source code to provide a web-based environment that provides real-time synchronization of UML and source code. RTT was created by improving existing RTE and is a tool for students who are learning OO concepts to understand how their UML or source code reflects the concepts that user intended. This study compares the efficiency and user- friendliness of RTT with the existing Round-Trip Engineering-based tools. The results show that students have improved understanding of OO concepts through UML and source code translation by using the RTT. We also found out that students were satisfied with the use of the RTT, which provides more efficient and convenient user interface than the existing tools.

• Proceedings of the Korea Information Processing Society Conference
• /
• 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)의 구현에 대해서 기술한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2000.10a
• /
• pp.442-444
• /
• 2000

이 논문에서는 산업계의 표준으로 널리 사용되고 있는 객체 지향 시스템의 명세 언어인 UML의 sequence diagram을 이용하여 객체 지향 시스템을 검증하는 방법과 이 방법을 테스팅 오라클을 생성하는데 사용할 수 있는 프레임웍을 제시하였다. 우리는 sequence diagram을 테스팅 결과의 검증에 사용하기 위하여 정형적으로 재정의 하였다. 그리고 시제 논리의 강력한 검증 능력을 사용하기 위해서 Half-Order Dynamic Temporal Logic(HDTL)이라 불리는 새로운 시제 논리를 정의하였고 sequence diagram을 HDTL 논리식으로 변화시키는 의미 함수(semantic function)를 정의하였다. HDTL에서 오토마톤을 생성하기 위해서 Tableau 방법을 변형하여 적용시켰다. 이 결과 생성된 오토마톤은 이상 상태(anomaly), 즉 sequence diagram에 표현되지 않은 사건(evevt)의 발생을 검색하는 오라클로 사용할 수 있다. 테스팅의 결과를 수작업으로 검증하는 것은 매우 어렵고 오류가 발생하기 쉬운 작업이므로 제안한 방법은 유용하게 사용될 수 있다.