Back to search

Institutional Repository of Vilnius University

Veiklos automatizavimas Android sistemoje remiantis įvykiais grįsta architektūra /

Abstract

dc:description

In recent years, event-driven architecture has begun to gain popularity, but there are still a lot of misconceptions, so it is hard to say which systems actually use event-driven architecture and which just something similar. Because of these misunderstandings, even companies that have event-driven systems take little care in them. This paper will describe what is an event-driven architecture and how it is commonly represented in systems. From the name of event-driven architecture alone, it can be understood that the main element of this architecture is an event, but this concept is ambiguous. In programming, an event can be portrayed as a change in system state or an object describing that change. Even if the event occurred a long time ago, its description is retained in the system's working memory if it is still relevant and, depending on the structure, it can be stored in a log. This type of data transfer allows to keep system elements decoupled and use a system in which it is important to create a process that can read the event description, rather than a central component that knows about all the processes. Although event-driven architecture in practical implementations rarely exactly matches the theoretical model, they have similarities to one of two topologies: mediator and broker. Or, the system employs one of three event-driven patterns: event notification, event-carried state transfer, and event-sourcing. Based on this architecture, it is convenient to implement automation systems. Automation allows human labor to be changed by the technological one. It can occur in one of two ways, but only one is relevant in this work. The automation system described here is designed to replace user-specified actions with software and is implemented in the Android operating system, while using “Android Studio” programming environment to build the application prototype, so the program descriptions will be based on the documentation of this environment. The system described in this paper consists of two main parts (the user interface and the service) and the database. In it, all communication between the components takes place only through the database. The system was developed in a way that avoided many errors related to the event-driven architecture.

Degree

thesis:*
Grantor dc:publisher
Institutional Repository of Vilnius University
Year dc:date
2020

Author and committee

dc:creator, dc:contributor.*
Author dc:creator
  • Skinderytė, Violeta,
Contributors dc:contributor
  • Vaicekauskas, Rimantas

Rights

dc:rights
Statement dc:rights
  • info:eu-repo/semantics/openAccess
Language dc:language
lit

Identifiers

dc:identifier.*

Chain of custody

source
Harvested from
Vilnius University
Base URL
epublications.vu.lt/oai
Last updated
2026-11-19
Source record
OAI-PMH GetRecord
related terms
citation

Skinderytė, Violeta,. Veiklos automatizavimas Android sistemoje remiantis įvykiais grįsta architektūra /. Institutional Repository of Vilnius University, 2020. https://repository.vu.lt/VU:ELABAETD81805586&prefLang=en_US