Control of Waste Water Treatment as a Flow Machine: A Case Study

Al-Fedaghi, Sabah; Al-Azmi, Reem

doi:10.23919/iconac.2018.8748989

Cited by 4 publications

(2 citation statements)

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

“…The next section introduces TM to be used both as a thinking style and as a vehicle for depicting the capturing inventory processes [21][22][23][24][25][26].…”

Section: Place_ Order Invoiced Madementioning

confidence: 99%

Conceptual Modeling of Inventory Management Processes as a Thinging Machine

Al-Fedaghi¹,

Al-Huwais²

2018

ijacsa

Self Cite

View full text Add to dashboard Cite

A control model is typically classified into three forms: conceptual, mathematical and simulation (computer). This paper analyzes a conceptual modeling application with respect to an inventory management system. Today, most organizations utilize computer systems for inventory control that provide protection when interruptions or breakdowns occur within work processes. Modeling the inventory processes is an active area of research that utilizes many diagrammatic techniques, including data flow diagrams, Universal Modeling Language (UML) diagrams and Integration DEFinition (IDEF). We claim that current conceptual modeling frameworks lack uniform notions and have inability to appeal to designers and analysts. We propose modeling an inventory system as an abstract machine, called a Thinging Machine (TM), with five operations: creation, processing, receiving, releasing and transferring. The paper provides side-by-side contrasts of some existing examples of conceptual modeling methodologies that apply to TM. Additionally, TM is applied in a case study of an actual inventory system that uses IBM Maximo. The resulting conceptual depictions point to the viability of FM as a valuable tool for developing a high-level representation of inventory processes.

show abstract

Modeling with Thinging for Intelligent Monitoring System

Al-Fedaghi

Atiyah²

2019

2019 IEEE 89th Vehicular Technology Conference (VTC2019-Spring)

View full text Add to dashboard Cite

Control of Waste Water Treatment as a Flow Machine: A Case Study

Cited by 4 publications

References 7 publications

Five Generic Processes for Behavior Description in Software Engineering

Five Generic Processes for Behavior Description in Software Engineering

Conceptual Modeling of Inventory Management Processes as a Thinging Machine

Modeling with Thinging for Intelligent Monitoring System

Contact Info

Product

Resources

About