Event Driven Architecture Embedded

Abstract In this paper we present an event driven multi-threading architecture and its underlying event flow system model of computation as a framework for the implementation of complex reactive and communication systems. Existing process oriented specification languages can be used to specify the system and embedded in the model.

An event-based or event-driven architecture responds to events in the software system and differs from ordinary architectures that respond to requests. An event is any significant occurrence or change in the state of the system hardware or software.

We discuss the main concepts behind event-driven programming, which, after object-oriented programming, is another fundamental stepping stone in understanding modern embedded software.

As with any programming approach, event-driven programming for embedded systems comes with its own set of challenges. Memory and performance constraints are common in resource-constrained embedded systems.

With event-driven architecture EDA, various system components communicate with one another by generating, identifying, and reacting to events. These events can be important happenings, like user actions or changes in the system's state. In EDA, components are independent, meaning they can function without being tightly linked to one another.

The event-driven architecture enables the embedded system to respond to events in real-time, allowing efficient resource utilization and modularity. It decouples different components, making it easier to add or modify functionality without affecting the entire system.

Event-Driven Programming Embedded systems need a program structure that can respond to a multitude of possible event sequences, any of which can arrive at unpredictable times. This program structure is generally called event-driven programming.

Event driven architecture for hard real-time embedded systems Author Francois Bossard Advanced studies Engineer in embedded software

Moreover, event-driven architecture can bring an additional benefit decoupling. Since event triggering and handling are separated, you can easily add, remove, or modify event handling functions without affecting other parts of the code.

Recently I discovered event-driven architecture for embedded systems. Where a framework is responsible for handling events and execute tasks. I came across the QP Framework of Quantum Leaps, I also read a book about the framework and event driven consepts. I wonder how popular such concepts are for embedded systems? I have always used polling design patterns which seems less complex but you