Modeling with Thinging for Intelligent Monitoring System

Al-Fedaghi, Sabah; Atiyah, Yousef

doi:10.1109/vtcspring.2019.8746526

Cited by 4 publications

(3 citation statements)

References 13 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

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

View full text Add to dashboard Cite

show abstract

“…The TM model has been applied to many real systems, such as phone communication [16], physical security [17], vehicle tracking [18], unmanned aerial vehicles [19], and programming [20]. www.ijacsa.thesai.org…”

Section: Thing Machine With Five Generic Processesmentioning

confidence: 99%

“…9, 2019 364 | P a g e www.ijacsa.thesai.org Triggering the not busy state results in taking a new customer from the queue, as mentioned previously (10), and also updates the queue data (16). Thus,  The front value is retrieved (17) and decremented (18), and the new value is stored (19).…”

Section: Thing Machine Modeling Examplementioning

confidence: 99%

Authentication Modeling with Five Generic Processes

Al-Fedaghi¹,

Bayoumi²

2019

IJACSA

View full text Add to dashboard Cite

Conceptual modeling is an essential tool in many fields of study, including security specification in information technology systems. As a model, it restricts access to resources and identifies possible threats to the system. We claim that current modeling languages (e.g., Unified Modeling Language, Business Process Model and Notation) lack the notion of genericity, which refers to a limited set of elementary processes. This paper proposes five generic processes for modeling the structural behavior of a system: creating, releasing, transferring, receiving, and processing. The paper demonstrates these processes within the context of public key infrastructure, biometric, and multifactor authentication. The results indicate that the proposed generic processes are sufficient to represent these authentication schemes.

show abstract

Software Architecture as a Thinging Machine: A Case Study of Monthly Salary System

Al-Fedaghi

Makdessi

2019

Intelligent Systems Applications in Software Engineering

View full text Add to dashboard Cite

Modeling with Thinging for Intelligent Monitoring System

Cited by 4 publications

References 13 publications

Five Generic Processes for Behavior Description in Software Engineering

Five Generic Processes for Behavior Description in Software Engineering

Authentication Modeling with Five Generic Processes

Software Architecture as a Thinging Machine: A Case Study of Monthly Salary System

Contact Info

Product

Resources

About