Time as non-functional requirement in distributed control systems

Thomas Hadlich, Stephan Home, Christian Diedrich, Karin Eckert, Timo Frank, Alexander Fay, Birgit Vogel-Heuser

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

11 Scopus citations

Abstract

When designing a distributed control system consisting of heterogeneous components whose properties are usually not well known, it is difficult or even impossible to use an analytical approach to verify the fulfillment of all requirements. In this contribution, it is shown (at the example of different implementation scenarios for a typical control function) that detailed knowledge about the communication system is required to reliably assess and compare different designs of distributed systems with regard to a real-time characteristic. However, automation engineers typically can neither be expected to have such detailed knowledge about the internal details of computing and communication, nor do they have the time to study different design alternatives in detail. This motivates further work of the authors towards better engineering support for the design of distributed automation systems, by providing helpful advice regarding design decisions.

Original languageEnglish
Title of host publicationProceedings of 2012 IEEE 17th International Conference on Emerging Technologies and Factory Automation, ETFA 2012
DOIs
StatePublished - 2012
Event2012 IEEE 17th International Conference on Emerging Technologies and Factory Automation, ETFA 2012 - Krakow, Poland
Duration: 17 Sep 201221 Sep 2012

Publication series

NameIEEE International Conference on Emerging Technologies and Factory Automation, ETFA

Conference

Conference2012 IEEE 17th International Conference on Emerging Technologies and Factory Automation, ETFA 2012
Country/TerritoryPoland
CityKrakow
Period17/09/1221/09/12

Fingerprint

Dive into the research topics of 'Time as non-functional requirement in distributed control systems'. Together they form a unique fingerprint.

Cite this