A Small Company as a Thinging Machine

Al-Fedaghi, Sabah; Aljenfawi, Hesah

doi:10.1145/3285957.3285988

Cited by 11 publications

(14 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Currently, no formal proof exists that the five TM stages are sufficient to describe all behavior processes. The TM model has been applied to many real systems, such as in phone communication [29], physical security [17], vehicle tracking [19], intelligent monitoring [32], asset management [20], information leakage [22], engineering plants [23], inventory management processes [24], procurement processes [26], public key infrastructure network architecture [26], bank check processing [35], waste water treatment [39], computer attacks [26], provenance [42], services in banking industry architecture network [31], and digital circuits [37]. Additionally, we will expend extensive effort to partially substantiate the claim of the genericity of the TM stages in different fields.…”

Section: Tm Substantiationmentioning

confidence: 99%

Five Generic Processes for Behavior Description in Software Engineering

Al-Fedaghi

2019

SSRN Journal

Self Cite

View full text Add to dashboard Cite

Behavior modeling and software architecture specification are attracting more attention in software engineering. Describing both of them in integrated models yields numerous advantages for coping with complexity since the models are platform independent. They can be decomposed to be developed independently by experts of the respective fields, and they are highly reusable and may be subjected to formal analysis. Typically, behavior is defined as the occurrence of an action, a pattern over time, or any change in or movement of an object. In systems studies, there are many different approaches to modeling behavior, such as grounding behavior simultaneously on state transitions, natural language, and flowcharts. These different descriptions make it difficult to compare objects with each other for consistency. This paper attempts to propose some conceptual preliminaries to a definition of behavior in software engineering. The main objective is to clarify the research area concerned with system behavior aspects and to create a common platform for future research. Five generic elementary processes (creating, processing, releasing, receiving, and transferring) are used to form a unifying higher-order process called a thinging machine (TM) that is utilized as a template in modeling behavior of systems. Additionally, a TM includes memory and triggering relations among stages of processes (machines). A TM is applied to many examples from the literature to examine their behavioristic aspects. The results show that a TM is a valuable tool for analyzing and modeling behavior in a system.

show abstract

Section: Tm Substantiationmentioning

confidence: 99%

Five Generic Processes for Behavior Description in Software Engineering

Al-Fedaghi

2019

SSRN Journal

Self Cite

View full text Add to dashboard Cite

show abstract

“…This paper promotes conceptual modeling that is based on the Heideggerian [7] notion of thinging as a framework for computational thinking. Heideggerian thinging is generalized as an abstract thinging machine (TM) [8][9][10][11][12][13].…”

Section: A Conceptualizationmentioning

confidence: 99%

Thinging for Computational Thinking

Al-Fedaghi¹,

Alkhaldi²

2019

ijacsa

View full text Add to dashboard Cite

This paper examines conceptual models and their application to computational thinking. Computational thinking is a fundamental skill for everybody, not just for computer scientists. It has been promoted as skills that are as fundamental for all as numeracy and literacy. According to authorities in the field, the best way to characterize computational thinking is the way in which computer scientists think and the manner in which they reason how computer scientists think for the rest of us. Core concepts in computational thinking include such notions as algorithmic thinking, abstraction, decomposition, and generalization. This raises several issues and challenges that still need to be addressed, including the fundamental characteristics of computational thinking and its relationship with modeling patterns (e.g., object-oriented) that lead to programming/coding. Thinking pattern refers to recurring templates used by designers in thinking. In this paper, we propose a representation of thinking activity by adopting a thinking pattern called thinging that utilizes a diagrammatic technique called thinging machine (TM). We claim that thinging is a valuable process as a fundamental skill for everybody in computational thinking. The viability of such a proclamation is illustrated through examples and a case study. This paper promotes conceptual modeling that is based on the Heideggerian [7] notion of thinging as a framework for computational thinking. Heideggerian thinging is generalized as an abstract thinging machine (TM) [8][9][10][11][12][13]. B. Core ConceptsAs will be described in this paper, we propose five basic concepts to model computational thinking: The notion of thing; The notion of TM; Five flow operations of things: create, process, release, transfer, and receive; and  Triggering.

show abstract

“…In the next section, we present a review of the TM model (also called the Flow thing model) as it is introduced in several publications [18][19][20][21][22][23][24]. The example in the section is a new contribution.…”

Section: Aim With Regard To Exploring a New Modelingmentioning

confidence: 99%

“…In the acquirer bank, the transaction data is processed into decrypted data (17). Then, the transaction flows to the payment processing network (18) where it is processed (19) and the following can happen:…”

Section: A Consumer E-purchasementioning

confidence: 99%

“… Returning back to the processing at (19), if the transaction in the electronic payment network is not considered a risk or possible fraud, then the transaction flows to the issuer bank (24) to be processed (25). This processing triggers a release of the customer's current balance from the centralized banking database (26) to be compared with the transaction amount that is received by the acquirer bank (27).…”

Section: A Consumer E-purchasementioning

confidence: 99%

See 1 more Smart Citation

Thinging Machine Applied to Information Leakage

Al-Fedaghi¹,

BehBehani²

2018

ijacsa

View full text Add to dashboard Cite

This paper introduces a case study that involves data leakage in a bank applying the so-called Thinging Machine (TM) model. The aim is twofold: (1) Presenting a systematic conceptual framework for the leakage problem that provides a foundation for the description and design of a data leakage system. (2) The aim in (1) is developed in the context of experimentation with the TM as a new methodology in modeling. The TM model is based on slicing the domain of interest (a part of the world) to reveal data leakage. The bank case study concentrates on leakage during internal operations of the bank. The leakage spots are exposed through surveying data territory throughout the bank. All streams of information flow are identified, thus points of possible leakage can be traced with appropriate evidence. The modeling of flow may uncover possible hidden points of leakage and provide a base for a comprehensive information flow policy. We conclude that a TM based on the Heideggerian notion of thinging can serve as a foundation for early stages of software development and as an alternative approach to the dominant object-orientation paradigm. Keywords-Thinging; bank system; abstract machine; software development cycle; heideggerI.

show abstract

A Small Company as a Thinging Machine

Cited by 11 publications

References 15 publications

Five Generic Processes for Behavior Description in Software Engineering

Five Generic Processes for Behavior Description in Software Engineering

Thinging for Computational Thinking

Thinging Machine Applied to Information Leakage

Contact Info

Product

Resources

About