Deriving system behavior from UML state machine diagram

Applied to Missile project

Hyun Seok Min, Sang Mun Chung, Jin Young Choi

Research output: Contribution to journalArticle

5 Citations (Scopus)

Abstract

Traditionally, System Analysis and Software Design are treated as separate processes. Software Design is based on System Analysis but they have little direct relationship to each other. UML (Unified Modeling Language) is widely accepted by industry as the de facto standard for System Analysis and Software Design. The primary tool for System Analysis is the Use Case Diagram and its Scenarios, while the primary tools for Software Design are the Class Diagram and Sequence Diagram. State Machine Diagram is also very useful for behavioral modeling. Our aim is to derive system behavior from software design, so that separate processes can work together. This paper suggests how to make a system-wide State Machine Diagram by gathering State Machine Diagrams in the system using predefined Stereotypes and Synchronization/Externalization. The resulting system-wide State Machine Diagram can be used for various things, such as automatic test case generation for the system, deadlock detection, and Use Case scenario consistency checking. The proposed method is applied to the Missile project of ADD (Agency for Defense Development) in South Korea. The result is very promising. It is expected to be applied to more projects.

Original languageEnglish
Pages (from-to)53-77
Number of pages25
JournalJournal of Universal Computer Science
Volume19
Issue number1
Publication statusPublished - 2013 Apr 5

Fingerprint

Unified Modeling Language
Missile
State Machine
Software design
Missiles
Software Design
Diagram
Systems analysis
Systems Analysis
Use Case
Behavioral Modeling
Scenarios
Synchronization
Deadlock
Thing
Industry

Keywords

  • Consistency
  • Deadlock
  • State Machine Diagram
  • System
  • Test
  • UML

ASJC Scopus subject areas

  • Computer Science(all)
  • Theoretical Computer Science

Cite this

Deriving system behavior from UML state machine diagram : Applied to Missile project. / Min, Hyun Seok; Chung, Sang Mun; Choi, Jin Young.

In: Journal of Universal Computer Science, Vol. 19, No. 1, 05.04.2013, p. 53-77.

Research output: Contribution to journalArticle

@article{f4f8bfe4ed534ef382341864c28438d3,
title = "Deriving system behavior from UML state machine diagram: Applied to Missile project",
abstract = "Traditionally, System Analysis and Software Design are treated as separate processes. Software Design is based on System Analysis but they have little direct relationship to each other. UML (Unified Modeling Language) is widely accepted by industry as the de facto standard for System Analysis and Software Design. The primary tool for System Analysis is the Use Case Diagram and its Scenarios, while the primary tools for Software Design are the Class Diagram and Sequence Diagram. State Machine Diagram is also very useful for behavioral modeling. Our aim is to derive system behavior from software design, so that separate processes can work together. This paper suggests how to make a system-wide State Machine Diagram by gathering State Machine Diagrams in the system using predefined Stereotypes and Synchronization/Externalization. The resulting system-wide State Machine Diagram can be used for various things, such as automatic test case generation for the system, deadlock detection, and Use Case scenario consistency checking. The proposed method is applied to the Missile project of ADD (Agency for Defense Development) in South Korea. The result is very promising. It is expected to be applied to more projects.",
keywords = "Consistency, Deadlock, State Machine Diagram, System, Test, UML",
author = "Min, {Hyun Seok} and Chung, {Sang Mun} and Choi, {Jin Young}",
year = "2013",
month = "4",
day = "5",
language = "English",
volume = "19",
pages = "53--77",
journal = "Journal of Universal Computer Science",
issn = "0948-6968",
publisher = "Springer Verlag",
number = "1",

}

TY - JOUR

T1 - Deriving system behavior from UML state machine diagram

T2 - Applied to Missile project

AU - Min, Hyun Seok

AU - Chung, Sang Mun

AU - Choi, Jin Young

PY - 2013/4/5

Y1 - 2013/4/5

N2 - Traditionally, System Analysis and Software Design are treated as separate processes. Software Design is based on System Analysis but they have little direct relationship to each other. UML (Unified Modeling Language) is widely accepted by industry as the de facto standard for System Analysis and Software Design. The primary tool for System Analysis is the Use Case Diagram and its Scenarios, while the primary tools for Software Design are the Class Diagram and Sequence Diagram. State Machine Diagram is also very useful for behavioral modeling. Our aim is to derive system behavior from software design, so that separate processes can work together. This paper suggests how to make a system-wide State Machine Diagram by gathering State Machine Diagrams in the system using predefined Stereotypes and Synchronization/Externalization. The resulting system-wide State Machine Diagram can be used for various things, such as automatic test case generation for the system, deadlock detection, and Use Case scenario consistency checking. The proposed method is applied to the Missile project of ADD (Agency for Defense Development) in South Korea. The result is very promising. It is expected to be applied to more projects.

AB - Traditionally, System Analysis and Software Design are treated as separate processes. Software Design is based on System Analysis but they have little direct relationship to each other. UML (Unified Modeling Language) is widely accepted by industry as the de facto standard for System Analysis and Software Design. The primary tool for System Analysis is the Use Case Diagram and its Scenarios, while the primary tools for Software Design are the Class Diagram and Sequence Diagram. State Machine Diagram is also very useful for behavioral modeling. Our aim is to derive system behavior from software design, so that separate processes can work together. This paper suggests how to make a system-wide State Machine Diagram by gathering State Machine Diagrams in the system using predefined Stereotypes and Synchronization/Externalization. The resulting system-wide State Machine Diagram can be used for various things, such as automatic test case generation for the system, deadlock detection, and Use Case scenario consistency checking. The proposed method is applied to the Missile project of ADD (Agency for Defense Development) in South Korea. The result is very promising. It is expected to be applied to more projects.

KW - Consistency

KW - Deadlock

KW - State Machine Diagram

KW - System

KW - Test

KW - UML

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

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

M3 - Article

VL - 19

SP - 53

EP - 77

JO - Journal of Universal Computer Science

JF - Journal of Universal Computer Science

SN - 0948-6968

IS - 1

ER -