scispace - formally typeset
F

Farhad Arbab

Researcher at Centrum Wiskunde & Informatica

Publications -  292
Citations -  7175

Farhad Arbab is an academic researcher from Centrum Wiskunde & Informatica. The author has contributed to research in topics: Reo Coordination Language & Component (UML). The author has an hindex of 38, co-authored 287 publications receiving 7028 citations. Previous affiliations of Farhad Arbab include Leiden University & University of Southern California.

Papers
More filters
Book ChapterDOI

Coordination models and languages

TL;DR: This chapter defines and presents in sufficient detail the fundamental concepts of what constitutes a coordination model or language and describes the main existing coordination models and languages as either ``data-driven'' or ``control-driven'''' (also called ``process-'''' or ``task-oriented'').
Journal ArticleDOI

Reo: a channel-based coordination model for component composition

TL;DR: Reo as discussed by the authors is a channel-based exogenous coordination model in which complex coordinators, called connectors, are compositionally built out of simpler ones, and each connector imposes a specific coordination pattern on the entities (for example, components) that perform I/O operations through that connector.
Journal ArticleDOI

Modeling component connectors in Reo by constraint automata

TL;DR: This paper covers the foundations for building tools to address concerns such as the automated construction of the automaton for a given component connector, equivalence checking or containment checking of the behavior of two given connectors, and verification of coordination mechanisms.
Journal ArticleDOI

Enterprise architecture: Management tool and blueprint for the organisation

TL;DR: This is an editorial to a special issue of ISF on enterprise architecture that defines the concept of enterprise architecture, notivate its importance, and introduces the papers in this special issue.
Book ChapterDOI

The IWIM Model for Coordination of Concurrent Activities

TL;DR: The concurrent applications of today essentially use a set of ad hoc templates to coordinate the cooperation of their active components, showing the lack of proper coordination languages that can be used to explicitly describe complex cooperation protocols in terms of simple primitives and structuring constructs.