• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.75-83
• /
• 2011

Unified Modeling Language (UML) is widely accepted in industry and particularly UML State Machine Diagram is popular for describing the dynamic behavior of classes. This paper discusses deadlock detection of System using UML State Machine Diagram. Since a State Machine Diagram is used for indivisual class' behavior, all the State Machine Diagrams of the classes in the system are combined to make a big system-wide State Machine Diagram to describe system behavior. Generally this system-wide State Machine Diagram is very complex and contains invalid state and transitions. To make it a usable and valid State Machine Diagram, synchronization and externalization are applied. The reduced State Machine Diagram can be used for describing system behavior thus conventional model-checking technique can be applied. This paper shows how deadlock detection of system can be applied with simple examples. All the procedures can be automatically done in the tool.

• Communications of the Korean Institute of Information Scientists and Engineers
• /
• v.31 no.5
• /
• pp.40-45
• /
• 2013

• 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.19D no.4
• /
• pp.281-292
• /
• 2012

A wide variety of smartphone applications is increasing the usage time of smartphone. Due to the increased time, it becomes difficult to providing stable services to users with limited battery capacity. The past works have been performed the power management of mobile device toward long-lasting battery development or low-power electric devices. However as the complexity of software embedded into system are increased, the research interests of the software power analysis is also increased. Among these studies on the software power analysis, model-based analysis technique is one of major interests because it can be able to analyze the power consumption before the development of source codes, then the analysis result can be used in the development of the software system, This paper suggests a model-based power analysis technique using UML state machine diagram. Our proposed technique estimates the power consumption by the simulation of Perti-net which is transformed from the state machine diagram.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.13 no.1
• /
• pp.129-134
• /
• 2013

Previous research is focus on testcase generation automation using message sequence diagram based on metamodel. but that research is not enough for testcase genaeration automation using state diagram based metamodel. so in this paper is adopt Model Driven Architecture (MDA) mechanism for using metamodel and model transformation. and we suggest testcase automation mechanism using state diagram in UML. we will decrease cost of embedded software design and testcase genaration and increase quality of embedded software using metamodel mechanism.

• Proceedings of the Korean Information Science Society Conference
• /
• 2012.06b
• /
• pp.126-128
• /
• 2012

소프트웨어 시스템의 안전성을 보장하기 위해 여러 안전성 분석 기법들이 사용되고 있으며, 안전성 분석의 결과인 안전성 요구사항을 시스템이 만족하고 있는지 확인하는지 확인하는 안전성 평가과정이 수행되고 있다. 안전성 평가는 많은 시간과 비용이 드는 문제점을 가지고 있다. 본 논문은 안전성 평가에 드는 시간과 비용을 줄이기 위해 테스트 케이스를 이용하여 안전성 요구사항을 소프트웨어 개발의 가장 기본적인 검증기법인 테스팅을 이용하여 시스템이 만족하는지 확인하는 방법을 제안하고 핸드폰의 카메라 컨트롤러 예제를 이용한 사례 연구를 진행하였으며 이를 지원 위한 도구인 TC2SMV를 개발하였다. TC2SMV는 UML의 state chart diagram에서 생성된 test case들을 SMV 입력 프로그램으로 자동으로 변환하여 사용자가 SMV 모델체킹을 수행할 수 있는 환경을 제공한다.

• Journal of Information Processing Systems
• /
• v.2 no.2
• /
• pp.114-123
• /
• 2006

We present in this paper the methodology for automatic generation of OWL-S service model ontology along with the results and issues. First, we extract information related to atomic services and their properties such as IOPE from the UML class diagram, and retrieve information related to the composition of services from the UML state-chart diagram. Then, the XSLT applications utilize the acquired information to generate the OWL-S service model ontology through the predefined mappings between OWL-S constructs for composite services and UML state-chart primitives. For the justification of generated service ontology, several validation checks are performed. Our service ontology generation method is general and fully automatic, as well as effective, in that it is achieved in an environment familiar to developers, and information needed to generate service ontology is provided necessarily during service development. It is also noticeable to facilitate representing the condition with GUI rather than a complex language such as OCL.

• 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.16D no.1
• /
• pp.65-72
• /
• 2009

Component based development has increasingly become important in the software industry. However, in the current component based development approach with UML, the absence of behavioral description of components brings about a cost problem which causes semantic errors on the testing phase. Accordingly we cannot grasp the usage pattern of component by its provided interfaces which refer to an abstraction of software component. And we cannot guarantee the behavioral conformance of the provided and required interfaces of components. In order to solve these problems, we describe the behaviors of component interfaces by state machine diagram and guarantee their behavior conformance at the modeling phase. We also propose a method to guarantee the behavior conformance of component interfaces with concept of observation equivalence and invocation consistency. And we provide an analyzing tool which checks interface behavior conformance.

• Journal of Korea Society of Industrial Information Systems
• /
• v.16 no.5
• /
• pp.83-92
• /
• 2011

IDEF is a widely used methodology for traditional structured software development. As object-oriented softwares are widely used, an object-oriented version of IDEF, IDEF4, is developed. UML is de facto standard for object-oriented software development methods. Whereas IDEF is widely used for CALS/EC, UML is used for general object-oriented software development. Most software developers are not familiar with IDEF4 but familiar with UML. Moreover, UML has many CASE tools. So we can develop software efficiently if we convert IDEF4 model to UML model. In this paper, we transform IDEF4 models to UML models. We explain the rules and methods to convert IDEF4 model to UML model and applied the transform methods and rules to a case study.