Thinging Machines for Requirements Engineering: Superseding Flowchart-Based Modeling
January 28, 2025 Β· Declared Dead Β· π arXiv.org
"No code URL or promise found in abstract"
Evidence collected by the PWNC Scanner
Authors
Sabah Al-Fedaghi
arXiv ID
2501.16712
Category
cs.SE: Software Engineering
Citations
0
Venue
arXiv.org
Last Checked
5 months ago
Abstract
This paper directs attention to conceptual modeling approaches that integrate advancements and innovations in requirements engineering. In some current (2024) works, it is claimed that present elicitation of requirements models focus on collecting information using natural language, which yields ambiguous specifications. It is proposed that a solution to this problem involves using complexity theory, transdisciplinarity, multidimensionality and knowledge management. Examples are used to demonstrate how such an approach helps solve the problem of quality and reliability in requirements engineering. The modeling method includes flowchart-like diagrams that show the relationships among system components and values in various modes of operation as well as path graphs that represent the system behavior. This paper focuses on the diagrammatic techniques in such approaches, with special attention directed to flowcharting (e.g., UML activity diagrams, business process model and notation (BPMN) business process diagrams). We claim that diagramming methods based on flowcharts is an outdated technique, and we promote an alternative diagrammatic modeling methodology based on thinging machines (TMs). TMs involve a high-level diagrammatic representation of a real-world system that integrates various component specifications to be refined into a more concrete executable form. TM modeling is a valuable tool to integrate requirements elicitation and address present challenges comprehensively. To demonstrate that, case studies are re-modeled using TMs. A TM model involves static, dynamic diagrams and event chronology charts. This study contrasts the flowchart-based and the TM approaches. The results point to the benefits of adopting the TM diagramming method.
Community Contributions
Found the code? Know the venue? Think something is wrong? Let us know!
π Similar Papers
In the same crypt β Software Engineering
R.I.P.
π»
Ghosted
R.I.P.
π»
Ghosted
Microservices: yesterday, today, and tomorrow
π
π
The Cartographer
A Survey of Machine Learning for Big Code and Naturalness
R.I.P.
π»
Ghosted
An Overview on Smart Contracts: Challenges, Advances and Platforms
R.I.P.
π»
Ghosted
Slither: A Static Analysis Framework For Smart Contracts
R.I.P.
π»
Ghosted
ContractFuzzer: Fuzzing Smart Contracts for Vulnerability Detection
Died the same way β π» Ghosted
R.I.P.
π»
Ghosted
Federated Learning: Strategies for Improving Communication Efficiency
R.I.P.
π»
Ghosted
In-Datacenter Performance Analysis of a Tensor Processing Unit
R.I.P.
π»
Ghosted
Deep Convolutional Neural Networks for Computer-Aided Detection: CNN Architectures, Dataset Characteristics and Transfer Learning
R.I.P.
π»
Ghosted