Aug 2026· Conference on Applications, Technologies, Architectures, and Protocols for Computer Communication· pp. 1816-1821· 0 citations· 11 references
Computer Science
TL;DR
An automated HCPN modeling method is proposed that transforms Netflix Conductor workflow specifications into hierarchical HCPN models using predefined rules and preserves workflow structure, control flow, and data dependencies, and generates models suitable for formal verification.
Abstract
Microservice architecture, with distributed deployment and loose coupling, is widely used in networked service systems. As the number of service modules grows and cross-service interactions become complex, formal modeling and verification face challenges. Hierarchical Colored Petri Net (HCPN)-based model checking can verify full execution paths, but manual modeling is costly, error-prone, and prone to state-space explosion. This paper proposes an automated HCPN modeling method that transforms Netflix Conductor workflow specifications into hierarchical HCPN models using predefined rules. The method preserves workflow structure, control flow, and data dependencies, and generates models suitable for formal verification. Experimental results show that the generated HCPN models are consistent with the original workflows and can automatically detect errors such as data inconsistency and business-data state inconsistency. Compared with existing methods, this approach reduces manual effort, lowers modeling cost, and provides more comprehensive support for data representation and error detection.
This study investigates the process of managing output events in microservice systems where business logic is isolated from infrastructure dependences and events are transmitted asynchronously by external event transport mechanisms.
The task addressed relates to the lack of a holistic architectural method for isolating business logic from event transport mechanisms. As their number increases, the application code becomes more complicated, its testability deteriorates, and technical debt also increases.
This work reports a method developed for centralized management of output events, consisting of six components (Key, Info, RoutingRule, EventContract, EventDispatcher, EventManager). It provides complete isolation of business logic from event transport mechanisms through declarative routing rules and dependence inversion. This method supports conditional and multicast routing without the need to make changes to the application code. The method is defined through abstract interfaces and is independent of the programming language by default. Its effectiveness has been confirmed on six control projects with a 2 × 3 design: two implementations (baseline and proposed) at three levels of complexity.
Applying the method to a project with three event transport mechanisms and fifteen use cases provides an increase in the use case maintainability index by 4.9 points (5.5%). Halstead effort is reduced by 47%, technical debt by 14.7%, average cyclomatic complexity by 28%; features with excessive cyclomatic complexity are absent compared to the baseline implementation. The applicability hypothesis has been empirically confirmed: the method is appropriate for microservices with more than two event transport mechanisms or more than ten use cases that generate events
V. Lakhai, M. Seniv· Eastern-European Journal of...· 0 citations
Today, many businesses suffer from fragmented workflows, isolated data, and uncoordinated process execution. Together these problems not only restrict operation efficiency but also decision making capacity. When organizations grow, the existence of non-standardized workflows results in work duplication, transparency loss and difficulty in quality maintenance among different departments. So, in this situation, standardization is not only a good practice but is also a means to guarantee agility, responsibility, and growth. At the beginning, Customer Relationship Management (CRM) systems were mainly considered as a means to handle customer interactions but nowadays they are also used for process modeling and workflow orchestration. Centralization of data and inclusion of processes into CRM environments allow companies to coordinate cross-functional activities, automate mundane jobs, and have a single source of truth. This paper presents a CRM-based method for standardizing enterprise workflows and includes the following steps: process mapping, stakeholder agreement, and system configuration on an ongoing basis. A case study is used to illustrate how a company in the phase of expansion managed to convert its scattered operations into a single streamlined, CRM-based workflow environment. The results show that the company has achieved major benefits such as making their processes more transparent, reducing the cycle time, increasing user understandability, improving data quality, and providing better decision support on top of that. This research above all offers implementation tips to create scalable workflows in CRM environments and it also highlights the fact that one cannot get rid of the trade-off between flexibility and structure. As a whole, the paper reveals that process modeling powered by CRM may be seen as a major instrument that companies can rely on when transforming their operations to standard, modern, and resilient systems.
Satyendra Kumar Vanapalli· American International Journ...· 0 citations
A formal verification framework that consists of a combination of specifications of temporal logic, model checking and modeling of service interactions graphs to study the behavior of the system and confirm the correctness properties is suggested.
Aparna S. Patil, Pratibha V. Kashid, Sourabh Rungta et al.· Journal of Intelligent Decis...· 0 citations
This study investigates whether a frontier LLM can generate Dockerfiles and Docker Compose configurations for multi-service applications using repository contents without access to developer-authored deployment artifacts and analytically derives a minimal explicit deployment specification for information that cannot be reliably inferred from repository artifacts.
Oleg Grynets, Kyrylo Fursov, V. Lyashkevych et al.· arXiv.org· 0 citations
Internet of Medical Things (IoMT) systems involve many interconnected devices that continuously collect, process, and share sensitive health data, creating significant privacy risks. Ensuring that these systems comply with GDPR is particularly challenging because legal requirements are complex, often timedependent, and difficult to validate at the level of individual data operations. This paper addresses this challenge by proposing a new formal verification approach that models the main IoMT operations, including data collection, transfer, storage, processing, and automated decision-making, as a GDPR-aware timed automaton. The proposed approach encodes legal requirements as formal rules and verifies compliance using a model checker through safety, liveness, and reachability properties. A remote cardiac monitoring scenario is presented to demonstrate typical data flows and interactions among smart medical devices, with business process models to represent the system. Experimental results show that the approach remains efficient as system complexity increases, providing a practical solution for developing IoMT applications that integrate privacy-by-design principles from the outset.
Masoud Barati· International Conference on...· 0 citations
Results suggest that localized multi-agent automation can make time-series modeling easier, and significantly reduces measured per-run cost, while staying within a comparable energy consumption.
Unknown authors· 1 citation
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.
