• Journal of KIISE:Computing Practices and Letters
• /
• v.8 no.3
• /
• pp.268-276
• /
• 2002

In this paper we suggest a method to produce automatically teat data using UML development diagrams, and analytically describe the application of a tool, Automatic UML-based Test Data Generation (AUTEG) developed using XML technology, to the examples of insurance system. Our AUTEG automatically generates test diagrams that enable to detect errors existing at the interface area between modules composing the whole system, along with test data by applying the existing white-box test technique to the test diagram. Our AUTEG can be applied to the integration test as well as the system test and using the tool, users may make the unit modules of the integration test into several groups.

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

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.843-852
• /
• 2001

Statistics concerning software errors indicate that more errors are introduced in analysis and design phase than implementation phase. Therefore, it is needed to check whether the design modeling is appropriate for own function and structure. This paper discussed the effective test method for the object-oriented design model, i.e., UML. A new method was proposed for generating test data. This method consists of category partition theory by the representation each element in UML model with OCL (Object Constraint Language). Test data generated in this way can be used for testing the source code functionality as well as for checking the design model.

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

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.15 no.7
• /
• pp.2476-2495
• /
• 2021

Model-based software architecture verification and test scenarios generation are becoming more and more important in the software industry. Based on the existing temporal graph grammar, this paper proposes a new formalization method of the context-sensitive graph grammar for aiming at UML activity diagrams, which is called the UML Activity Graph Grammar, or UAGG. In the UAGG, there are new definitions and parsing algorithms. The proposed mechanisms are able to not only check the structural correctness of the UML activity diagram but also automatically generate the test scenario according to user constraints. Finally, a case study is discussed to illustrate how the UAGG and its algorithms work.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.16 no.6
• /
• pp.1291-1299
• /
• 2012

UML is a semantically rich language, but it is difficult to ensure consistency of the diagrams you have written. Therefore, in this paper, we propose cross checking rules to improve consistency between UML diagrams, especially between UML static diagram and dynamic diagram. We use metamodels in order to more clearly reflect interactions of UML elements in the checking rules and use OCL(Object Constraint Language) to accurately represent the checking rules. By comparing with the well-formedness rules of UML specification, we focus on consistency of UML diagrams. And we derive metamodels of static diagram and dynamic diagram, analysis the relationships of UML diagrams and finally, we test the usability of derived rules through a case study.

• The Journal of Society for e-Business Studies
• /
• v.9 no.1
• /
• pp.1-19
• /
• 2004

The systematic testing is frequently regretted in recent web applications because of time and cost pressure. Moreover developers have difficulties with applying the traditional testing techniques to testing web application. The approach of creating test cases for a web application from a sequence model is proposed for the rapid and efficient testing. Test cases for web application are extracted from call messages (including self-call messages) of UML (Unified Modeling Language) sequence diagram. A test case consists of messages, script functions, or server pages and additional values. Moreover a simple testing tool for web application is proposed. A URL for testing web application is created and executed by this testing tool. The URL consists of server page address and additional values. This test tool is made using Microsoft Visual Basic. The efficiency of proposed method and tool has been shown using a practical case study which reflects the development project of the web application for supporting member management.

• The KIPS Transactions:PartD
• /
• v.14D no.7
• /
• pp.753-762
• /
• 2007

Traceability has been held as an important factor in testing activities as well as model driven development. Vertical traceability affords us opportunities to improve manageability from models and test cases to code in testing and debugging phase. Traceability also makes overcome to difficulties of going up-and-down abstraction level to find out error spot of faults discovered by testing This paper represents a vertical test method which connects a system test level and an integration test level in a test stage by using UML. Experiment of how traceability works and how effective focus on error spots has been included using concrete examples of tracing from models to the code.

• The KIPS Transactions:PartD
• /
• v.16D no.2
• /
• pp.213-222
• /
• 2009

Traceability has been held as an important factor in testing activities as well as model driven development. Vertical traceability affords us opportunities to improve manageability from models and test cases to code in testing and debugging phase. Traceability also overcomes difficulties by the separation between abstraction levels when we trace errors from models to source code after test. To support a rigorous test this paper proposes XML based traceability which vertically trace from model and test case to source code. This paper explains how the traceability works and finds out error spots Through experiments using a concrete example.

• The KIPS Transactions:PartD
• /
• v.16D no.4
• /
• pp.517-526
• /
• 2009

It is possible to indicate the complex design and execution of object-oriented program with dynamic UML diagram. This paper shows the way how to make several test cases from sequence, state, and activity diagram among dynamic UML diagram. Three dynamic UML diagrams about withdrawal work of ATM simulation program are drawn. Then different test cases are created from these diagrams using previously described ways. To evaluate effectiveness of test cases, mutation testing is executed. Mutants are made from MuClipse plug-in tool based on Eclipse which supports many traditional and class mutation operators. Finally we've got the result of mutation testing and compare effectiveness of test cases, etc. Through this document, we've known some hints that how to choose the way of making test cases.