State-Based Behavior Modeling in Software and Systems Engineering
Sabah Al-Fedaghi

TL;DR
This paper critically analyzes state-based modeling in systems engineering, comparing traditional state machine diagrams with the thinging machine (TM) approach, and demonstrates TM's systematic advantages through a case study of an assembly line.
Contribution
It introduces a TM-based approach to state modeling, offering a clearer and more systematic alternative to traditional state machine diagrams in system behavior analysis.
Findings
TM states are defined as compound events.
TM modeling provides a more systematic representation.
The assembly line model demonstrates TM's effectiveness.
Abstract
The design of complex man-made systems mostly involves a conceptual modeling phase; therefore, it is important to ensure an appropriate analysis method for these models. A key concept for such analysis is the development of a diagramming technique (e.g., UML) because diagrams can describe entities and processes and emphasize important aspects of the systems being described. The analysis also includes an examination of ontological concepts such as states and events, which are used as a basis for the modeling process. Studying fundamental concepts allows us to understand more deeply the relationship between these concepts and modeling frameworks. In this paper, we critically analyze the classic definition of a state utilizing the thinging machine (TM) model. States in state machine diagrams are considered the appropriate basis for modeling system behavioral aspects. Despite its wide…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsAssembly Line Balancing Optimization · Flexible and Reconfigurable Manufacturing Systems · Petri Nets in System Modeling
