• Journal of the Korea Institute of Military Science and Technology
• /
• v.24 no.6
• /
• pp.664-675
• /
• 2021

Air force air-to-air combat tactics are occurring at a high speed in three-dimensional space. The specification of the tactics requires dealing with a quite amount of information, which makes it a challenge to accurately describe the maneuvering procedure of the tactics. The specification of air-to-air tactics using natural languages is not suitable because of the intrinsic ambiguity of natural languages. Therefore, this paper proposes an approach of using UML Sequence Diagram to describe air-to-air combat tactics. Since the current Sequence Diagram notation is not sufficient to express all aspects of the tactics, we extend the syntax of the Sequence Diagram to accommodate the required features of air-to-air combat tactics. We evaluate the applicability of the extended Sequence Diagram to air-to-air combat tactics using a case example, that is the manned-unmanned teaming combat tactic. The result shows that Sequence Diagram specification is more advantageous than natural language specification in terms of readability, conciseness, and accuracy. However, the expressiveness of the Sequence Diagram is evaluated to be less powerful than natural language, requiring further study to address this issue.

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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.18 no.3
• /
• pp.633-652
• /
• 2024

Software testing is an important phase as it ensures the software quality. The software testing process comprises of three steps: generation, execution, and evaluation of test cases. Literature claims the usage of single and multiple 'Unified Modeling Language' (UML) diagrams to generate test cases. Using multiple UML diagrams increases test case coverage. However, the existing approaches show limitations in test case generation from UML diagrams. Therefore, in this research study, we propose an approach to generate the test cases using UML State Chart Diagram (SCD), Activity Diagram (AD), and Sequence Diagram (SD). The proposed approach transforms UML diagrams into intermediate forms: SCD Graph, AD Graph, and SD Graph respectively. Furthermore, by integrating these three graphs, a System Testing Graph (STG) is formed. Finally, test cases are identified from STG by using a traversal algorithm such as Depth First Search (DFS) that is an optimization method. The results show that the proposed approach is better compared to existing approaches in terms of coverage and performance. Moreover, the generated test cases have the ability to detect faults at the unit level, integration, and system level testing.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.397-399
• /
• 2001

Unified Modeling Language(UML)은 개발하고자 하는 시스템을 Visualizing, Specifying, Constructing, Documenting 화 해주는 graphical language 이다. 우리는 이러한 모델링 언어를 통하여, 객체지향 분석/설계 과정에 이용하고 있다. 그러나, EJB 로 Mapping 하기 위한 충분한 연구가 이루어지지 않아 개발자들이 EJB 로 UML 을 설계 및 구현을 명확하게 옮기지 못하였다. 본 논문에서는 이 점에 중점을 두고 UML Modeling 을 통해 설계 및 구현된 내용중 UML 의 Sequence Diagram 의 요소들을 EJB Bean으로의 구현시 Mapping 지침을 제시한다

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

• Journal of KIISE:Software and Applications
• /
• v.26 no.9
• /
• pp.1105-1113
• /
• 1999

객체 지향 소프트웨어의 확장과 더불어 소프트웨어의 재사용성의 중요도가 부각되면서 소프트웨어를 콤포넌트 단위로 구현하는 추세이다. 따라서 콤포넌트 기반의 소프트웨어 개발에서의 통합 테스트가 중요한 이슈로 떠오르고 있다. 그러나 콤포넌트들의 통합 테스트에 대한 연구는 미흡한 상태이다. 본 논문에서는 UML을 기반으로 체계적인 통합 테스트 모형을 제안하고. 나아가 본 논문에서는 "멀티미디어 정보처리 시스템"의 사례를 본 논문의 콤포넌트 통합 테스트 모형에 적용한 결과를 분석하여 기술한다. 콤포넌트 통합 테스트 모형은 UML(Unified Modeling Language)의 순서도(sequence diagram)와 협력도(collaboration diagram)를 이용하여 전체 시스템에서 UML의 사건흐름을 구성하는 콤포넌트들 사이의 인터페이스 영역에 존재하는 오류들을 추출한다. 그리고 UML을 기반으로 통합 테스트를 수행함으로써, 테스트 준비 작업을 줄이고, 기존의 UML 지원 도구들과 연계하여 테스트 자동화 도구의 구현을 앞당길 수 있다. 또한 시스템의 순차적 흐름 뿐 아니라, 동시에 수행되는 흐름에 대한 정보까지 모두 수용하여 테스트함으로써, 콤포넌트 기반의 분산 환경의 특성에 적합하다. Abstract As the object-oriented approach to software development becomes more mature, software development from pre-existing, independently developed components becomes an important aim of software engineering. Therefore, integration testing becomes an important aspect of component-based software development. However, there has been little work done in the area of the component-based integration testing. In this paper, we propose the "component integration test model" which is based on UML. Furthermore, we describe a case study on "Multimedia Information Processing System" conducted to analyse the result from which our model is applied. Our model extracts the faults, which exist in interfaces of components, using sequence diagram and collaboration diagram of UML(Unified Modeling Language). As our model is based on UML, the preparation effort for testing is reduced and its test-tools can be implemented more easily through linking existing UML tool. And our model accepts the information of concurrent flow represented by collaboration diagram as well as sequential flow, so it is more suitable to component-based distributed environment.based distributed environment.

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

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2001.10a
• /
• pp.717-719
• /
• 2001

인터넷의 급격한 확산에 따라 컴퓨터 응용산업은 이를 응용하려는 노력과 연구가 활발히 진행되었다. 또한, 다변화되는 수요환경에 따라 점차 응용소프트웨어의 효율성에 문제점이 제기 되었고, 이를 보완할 수 있는 보다 포괄적이고 효과적인 소프트웨어 분석 및 개발기법들이 제시되었다. 이에, 본 논문에서는 이들 요소들을 적용하여 자동화시스템에서 운용한 수 있는 인격제어관리시스템을 구현 및 개발하였다. 즉, 본 시스템의 개발을 위한 분석 부분에서는 UML을 이용한 Use Case Diagram, Sequence Diagram, Collaboration Diagram등을 활용하였으며, 개발 부분에서는 웹 기반의 문서 데이터 표준을 위하여 XML을 이용하였고 Java언어로 이를 보완하였다.

• KIISE Transactions on Computing Practices
• /
• v.22 no.1
• /
• pp.32-37
• /
• 2016

In model-based testing using sequence diagrams, test cases are automatically derived from the sequence diagrams. For the generation of test cases, scenarios need to be found for representing as a sequence diagram, and to extract test paths satisfying the test coverage. However, it is hard to automatically extract test paths from the sequence diagram because a sequence diagram represents loop, opt, and alt information using CombinedFragments. To resolve this problem, we propose a transformation process that transforms a sequence diagram into an activity diagram which represents scenarios as a type of control flows. In addition, we generate test cases from the activity diagram by applying a test coverage concept. Finally, we present a case study for test cases generation from a sequence diagram.