Automatic consistency checking of use case scenarios

Hyunseok Min, Jin Young Choi

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Unified Modeling Language (UML) is widely accepted in the industry. UML 2.0 has 13 diagrams to explain the system's structure and behavior. These 13 diagrams describe certain aspects of the system. Because each diagram is a unique view of the system, conflict might arise between UML models. One particular case is Use Case Scenarios. Since Use Case analysis is mostly done in the early stage of the project, it is possible to have an inconsistency with other UML models. After the Use Case analysis, system design is started with Class Diagrams. The behavior of the class is designed with Statechart, which is the most popular way. When Statechart is used to describe the behavior of each class, there might be an inconsistency with the system behavior of Use Case Scenarios. This paper shows how to derive a System-wide Statechart by merging all the Statecharts in one application. After that, consistency with other UML models such as Use Case scenarios, which are often shown as Sequence Diagram, is checked automatically.

Original languageEnglish
Title of host publicationProceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009
Pages166-173
Number of pages8
Publication statusPublished - 2009 Dec 1
Event13th IASTED International Conference on Software 13th IASTED International Conference on Software Engineering and Applications, SEA 2009 - Cambridge, MA, United States
Duration: 2009 Nov 22009 Nov 4

Other

Other13th IASTED International Conference on Software 13th IASTED International Conference on Software Engineering and Applications, SEA 2009
CountryUnited States
CityCambridge, MA
Period09/11/209/11/4

Fingerprint

Unified Modeling Language
Merging
Systems analysis
Industry

Keywords

  • Consistency
  • Statechart
  • System
  • UML
  • Use case

ASJC Scopus subject areas

  • Software

Cite this

Min, H., & Choi, J. Y. (2009). Automatic consistency checking of use case scenarios. In Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009 (pp. 166-173)

Automatic consistency checking of use case scenarios. / Min, Hyunseok; Choi, Jin Young.

Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009. 2009. p. 166-173.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Min, H & Choi, JY 2009, Automatic consistency checking of use case scenarios. in Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009. pp. 166-173, 13th IASTED International Conference on Software 13th IASTED International Conference on Software Engineering and Applications, SEA 2009, Cambridge, MA, United States, 09/11/2.
Min H, Choi JY. Automatic consistency checking of use case scenarios. In Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009. 2009. p. 166-173
Min, Hyunseok ; Choi, Jin Young. / Automatic consistency checking of use case scenarios. Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009. 2009. pp. 166-173
@inproceedings{8b683736335e450691e694216a4a0c5e,
title = "Automatic consistency checking of use case scenarios",
abstract = "Unified Modeling Language (UML) is widely accepted in the industry. UML 2.0 has 13 diagrams to explain the system's structure and behavior. These 13 diagrams describe certain aspects of the system. Because each diagram is a unique view of the system, conflict might arise between UML models. One particular case is Use Case Scenarios. Since Use Case analysis is mostly done in the early stage of the project, it is possible to have an inconsistency with other UML models. After the Use Case analysis, system design is started with Class Diagrams. The behavior of the class is designed with Statechart, which is the most popular way. When Statechart is used to describe the behavior of each class, there might be an inconsistency with the system behavior of Use Case Scenarios. This paper shows how to derive a System-wide Statechart by merging all the Statecharts in one application. After that, consistency with other UML models such as Use Case scenarios, which are often shown as Sequence Diagram, is checked automatically.",
keywords = "Consistency, Statechart, System, UML, Use case",
author = "Hyunseok Min and Choi, {Jin Young}",
year = "2009",
month = "12",
day = "1",
language = "English",
isbn = "9780889868120",
pages = "166--173",
booktitle = "Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009",

}

TY - GEN

T1 - Automatic consistency checking of use case scenarios

AU - Min, Hyunseok

AU - Choi, Jin Young

PY - 2009/12/1

Y1 - 2009/12/1

N2 - Unified Modeling Language (UML) is widely accepted in the industry. UML 2.0 has 13 diagrams to explain the system's structure and behavior. These 13 diagrams describe certain aspects of the system. Because each diagram is a unique view of the system, conflict might arise between UML models. One particular case is Use Case Scenarios. Since Use Case analysis is mostly done in the early stage of the project, it is possible to have an inconsistency with other UML models. After the Use Case analysis, system design is started with Class Diagrams. The behavior of the class is designed with Statechart, which is the most popular way. When Statechart is used to describe the behavior of each class, there might be an inconsistency with the system behavior of Use Case Scenarios. This paper shows how to derive a System-wide Statechart by merging all the Statecharts in one application. After that, consistency with other UML models such as Use Case scenarios, which are often shown as Sequence Diagram, is checked automatically.

AB - Unified Modeling Language (UML) is widely accepted in the industry. UML 2.0 has 13 diagrams to explain the system's structure and behavior. These 13 diagrams describe certain aspects of the system. Because each diagram is a unique view of the system, conflict might arise between UML models. One particular case is Use Case Scenarios. Since Use Case analysis is mostly done in the early stage of the project, it is possible to have an inconsistency with other UML models. After the Use Case analysis, system design is started with Class Diagrams. The behavior of the class is designed with Statechart, which is the most popular way. When Statechart is used to describe the behavior of each class, there might be an inconsistency with the system behavior of Use Case Scenarios. This paper shows how to derive a System-wide Statechart by merging all the Statecharts in one application. After that, consistency with other UML models such as Use Case scenarios, which are often shown as Sequence Diagram, is checked automatically.

KW - Consistency

KW - Statechart

KW - System

KW - UML

KW - Use case

UR - http://www.scopus.com/inward/record.url?scp=77954194837&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=77954194837&partnerID=8YFLogxK

M3 - Conference contribution

AN - SCOPUS:77954194837

SN - 9780889868120

SP - 166

EP - 173

BT - Proceedings of the 13th IASTED International Conference on Software Engineering and Applications, SEA 2009

ER -