Modelling and control of engineering plant processes

Al-Fedaghi, Sabah; AlQallaf, Abdulaziz

doi:10.1504/ijass.2018.096122

Cited by 6 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…3. An object-oriented representation of a light bulb (redrawn from [13]). Behavior in a TM is represented by events.…”

Section: Thinging Machinementioning

confidence: 99%

Programming Is Diagramming Is Programming

Al-Fedaghi¹,

Haidar²

2019

JSW

View full text Add to dashboard Cite

It is said that "programming is writing is programming." Both programming and writing involve high-level plans. Programming involves understanding the problem, creating a design, and coding. In this paper, we further explore the nature of programming based on the concept that "programming is diagramming." A diagram can be coded, and both the code and diagram approximate the conceptual (mental) form of the programmer behind both. We adopt a new diagramming technique called a thinging machine (TM) and build a TM diagram of the solution to the involved problem, which is sliced to produce program statements, much as flowcharts are converted to code. The TM introduces a simplified form with its five basic operations, which are repeated throughout the flow of events until reaching the end of the solution description. A case study is given that establishes an account through which a user can apply for a modeled job. The resulting diagram and program point to a viable approach to developing computer programs.

show abstract

“…3. An object-oriented representation of a light bulb (redrawn from [13]). Behavior in a TM is represented by events.…”

Section: Thinging Machinementioning

confidence: 99%

Programming Is Diagramming Is Programming

Al-Fedaghi¹,

Haidar²

2019

JSW

View full text Add to dashboard Cite

show abstract

“…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

“…papers(Al-Fedaghi & Atiyah, 2018;Al-Fedaghi & Al-Huwais, 2018);Al-Fedaghi & AlQallaf, 2018;Al-Fedaghi&Alnasser,2018;Al-Fedaghi,2013,6(3),59-70;Al-Fedaghi,2013,4(3),30; Al-Fedaghi,2008,Al-Fedaghi,2006,tobeusedasathinkingstyleandasavehicleforbuildinga networkarchitecturediagram.…”

mentioning

confidence: 99%

Conceptual Modeling of an IP Phone Communication System

Al-Fedaghi

Aldamkhi

2021

International Journal of Interdisciplinary Telecommunications and Networking

View full text Add to dashboard Cite

In computing, a network generally denotes devices, often referred to as nodes, connected by links. Networks that are modeled with diagrams consist of hundreds of symbols, images, pictures, and icons, such as a computer, a server rack, or a cloud-based storage system. Network representations provide valuable insights into understanding the systems' underlying structures and mechanisms. Nevertheless, this unusually large number of superficial symbols and icons reflects a need for more systematic representations of the interiority of nodes. To give uniformity to this cascade of notions of basic units of nodes in network diagrams, the authors propose adoption of a new modeling methodology, called a thinging (abstract) machine (TM) (abstract machine of things) that represents all notions as a single diagrammatic machine. Because of the large number of network types, in this paper, they specifically and without loss of generality focus on IP telephone (internet protocol telephone) networks to exemplify communication networks. A real case study of IP telephone networks is modeled using TM.

show abstract

Modelling and control of engineering plant processes

Cited by 6 publications

References 10 publications

Programming Is Diagramming Is Programming

Programming Is Diagramming Is Programming

Five Generic Processes for Behavior Description in Software Engineering

Conceptual Modeling of an IP Phone Communication System

Contact Info

Product

Resources

About