• 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
• /
• 2000.04a
• /
• pp.1027-1030
• /
• 2000

객체 지향 프로그램의 이해 및 테스팅을 효과적으로 수행하기 위해서는 객체 간의 상호 작용을 우선 이해하여야 한다. UML로 작성된 시스템 명세에서는 각각의 클래스에 대한 행동이 UML 상태 다이어그램으로 기술되어 있어 전체 시스템의 행동을 유추하는데 어려움이 따른다. 이 연구에서는 객체 지향 프로그램의 상태 다이어그램을 기반으로 객체간 행동 테스팅을 수행하기 위해서 UML 상태 다이어그램들을 합성하여 객체간 행동을 추출, 생성하는 과정을 기술한다. 추출, 합성된 객체간 행동 모델은 기존의 널리 알려진FSM 기반 테스팅 기법들을 그대로 이용할 수 있다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.04a
• /
• pp.682-684
• /
• 2001

주어진 도메인에 대한 설계 및 구현 이전 단계인 분석 과정에서 객체지향의 방법을 적용할 수 있는 모델링 언어인 UML(Unified Modeling Language) 다이어그램 중 Use Case 다이어그램, 클래스 다이어그램, 순서도 등 3가지 모델들 간의 일관성(consistency)을 유지하기 위한 기준이나 구체적인 지침에 관한 여러 가지 형태의 연구들이 이미 행해져 왔지만, 본 논문에서는 이러한 다이어그램들 간의 일관성을 유지하는데 있어서 지켜져야 하는 기준과 checklist를 예제를 통해서 제시한다.

• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.6
• /
• pp.657-668
• /
• 2002

Software life cycle consists of requirement analysis, design, implementation, and maintenance phases, and the product of each phase has various format. The UML normalizes such products, and the class diagram, use case diagram, activity diagram and collaboration diagram are usually used for the requirement analysis phase. Because most of UML development tools store such diagrams in a file, there nay be some difficulties of information retrieval and co-work among users. To cope with the difficulties, this paper proposes a database supported methodology to store and manage the diagrams produced by the requirement analysis. In this methodology, the constituents of class, use case, activity and collaboration diagram are first analyzed and then transformed in the form of relational fables. The constituents of such diagrams are stored as tables in a database, and can be easily retrieved from the database by using some queries. This database supported methodology provides the concurrent sharing and high reuse of diagrams.

• 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.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.10b
• /
• pp.172-174
• /
• 2003

최근 XML 문서가 급증함에 따라 웹-기반 XML 응용 문서의 중요성이 많이 부각되고 있는 실정이다. 웹-기반 XML 응용 문서 중 대표적인 예로 OSD가 있다. OSD는 소프트웨어 패키지와 그들 간의 관계를 정의하는 것이다. UML은 객체지향 표준 모델링 방법으로 객체지향 코드 생성이나 데이터베이스 스키마 생성을 용이하게 해주는 표기법이다. 따라서, 본 연구는 XMI를 이용하여 OSD로 부터 UML 클래스 다이어그램을 생성하는 시스템을 구현한다. 본 연구의 의의는 향후 늘어나는 웹 기반 XML 응용인 OSD의 표준 모델링 방법을 제안함으로써 객체지향 문서 관리의 기반이 되도록 한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2006.06c
• /
• pp.169-171
• /
• 2006

본 논문에서는 UML 다이어그램으로부터 시맨틱 웹 서비스 기술 표준인 OWL-S문서를 생성하는 방법을 제안한다. 특히 온톨로지의 기술을 위해 클래스 다이어그램을 사용하고, 프로세스의 흐름을 기술하기 위해 시퀀스 다이어그램 및 액티비티 다이어그램을 사용한다. 제안된 방법은 UML 모델의 재사용 및 기존 연구들이 처리하지 못하는 복합프로세스의 생성이 가능하다는 장점을 가진다.

• Journal of KIISE:Software and Applications
• /
• v.32 no.6
• /
• pp.486-501
• /
• 2005

XPDL is a XML-based language for process definition exchange that is proposed by WfMC. This paper propose a model which model XPDL document structure (Schema) using UML in order to define and to exchange workflow process, and make business flow understanding ease for inter-business cooperation. So, we define mapping rules in which map XPDL documents into UML class diagram and UML activity diagram. By these mapping rules, elements composing XPDL process meta-model are mapped into UML class diagram, and process activities are mapped into UML activity diagram. Also, we apply proposed mapping technique to model a workflow of (')Credit card state check system.(')

• The KIPS Transactions:PartD
• /
• v.19D no.1
• /
• pp.39-48
• /
• 2012

In order to quickly understand which changes of source codes have been made and to perform effective maintenance of a system, it is important to visualize the changed parts. Although there are many works for analyzing software changes, there are few works for visualizing both of the change types and change quantifications for Java based systems. In this paper, we propose a change analysis technique based on class diagram and provide a change visualization technique by using change quantification information. In order to check the structural changes in source codes, source codes are transformed to class diagrams by reverse engineering methods. On the class diagrams, the changes are analyzed and quantified by numbers. Based on the change quantification, the changes are visualized on the class diagram by color spectrum. By using visualization techniques, maintainers can easily recognize the code changes to reduce the cost and time of maintenance.

• Journal of KIISE:Computing Practices and Letters
• /
• v.6 no.4
• /
• pp.393-402
• /
• 2000

The Unified Modeling Language(UML) became the standard object oriented modeling language approved by Object Management Group(OMG). However, C++ codes which are generated by some CASE tools supporting UML do not reflect the correct semantics of one-to-many relationship and aggregation relationship. Additionally, since the commercial CASE tools support too many programming languages on one UML class diagram, they do not support efficiently the characteristics of C++ language. Our C++ code generator supports one-to-many relationship, aggregation relationship, code patterns and design patterns. In this paper, we describe design and implementation of the efficient C++ code generator based on UML class diagram.