go-v.orgdoi

Requirements Validation of Event-Driven Supply Chains Using Model-Based Systems Engineering

Amirali Amiri · IEEE International Conference on Software Services Engineering (SSE) · 2025

  • DOI 10.34726/11633
  • Publisher Institute of Electrical and Electronics Engineers
  • Type conference-paper
  • Issued 2025

Not cached yet. This record was fetched live for this request and is stored after the lookup. Reopening the page should serve the cached copy.

IEEE International Conference on Software Services Engineering (SSE) · Institute of Electrical and Electronics Engineers · conference-paper · 2025

Abstract

Supply Chain Management (SCM) plays a vital role in business operations, necessitating careful designing and planning. Emerging technologies, such as the Internet of Things (IoT), facilitate real-time, event-driven monitoring of supply chain performance. However, integrating IoT into SCM presents significant challenges for system architects, particularly in validating requirements due to the diversity of IoT technologies and communication frameworks. Model-Based Systems Engineering (MBSE) offers a structured approach to system design by providing models and views, along with tools that automate essential processes.

In this paper, we propose an MBSE-based approach for requirements validation in event-driven supply chain management. Additionally, we introduce tool support to enhance usability. An architectural overview demonstrates how system designers can customize the tool to meet their specific requirements. Our approach is designed for system architects, supporting iterative modeling until the requirements are validated as illustrated through a sample case study.

Open the resolved locator · 10.34726/11633

Metadata licence: OpenAlex metadata (CC0)

Registry
OpenAlex DOI index + API
Fetched
2026-11-20 15:32 UTC
Cache state
not cached yet (bulk-index+openalex)
Locator
https://repositum.tuwien.at/handle/20.500.12708/222668
Metadata licence
OpenAlex metadata (CC0)
Scope
Metadata as returned by the resolver; abstracts are never generated here.