Using IoTGolog to formalize IoT scenarios

Shah Rukh Humayoun, Yael Dubinsky, Ragaad Altarawneh

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

Abstract

Internet of Things (IoT) scenarios exist in various domains and due to the vast changes in technology and systems modernization, they are constantly evolving. In order to cope with this dynamicity, there is a need to provide a robust yet flexible way to design, develop, and evaluate the IoT architecture and implementation. We present IoTGolog, a formal task modeling language to define and evaluate IoT scenarios. Using IoTGolog, characteristics of the IoT scenario as well as the tests to evaluate it are formalized. This provides accuracy and better control over the IoT evolution. IoTGolog extends our previous work on TaMoGolog and MobiGolog for general and mobile-based scenarios respectively. We illustrate IoTGolog for the case of car emergency response system.

Original languageEnglish
Title of host publicationIEEE World Forum on Internet of Things, WF-IoT 2015 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages234-238
Number of pages5
ISBN (Electronic)9781509003655
DOIs
StatePublished - 2015
Externally publishedYes
Event2nd IEEE World Forum on Internet of Things, WF-IoT 2015 - Milan, Italy
Duration: 14 Dec 201516 Dec 2015

Publication series

NameIEEE World Forum on Internet of Things, WF-IoT 2015 - Proceedings

Conference

Conference2nd IEEE World Forum on Internet of Things, WF-IoT 2015
Country/TerritoryItaly
CityMilan
Period14/12/1516/12/15

Bibliographical note

Publisher Copyright:
© 2015 IEEE.

Keywords

  • Internet of Things (IoT)
  • IoTGolog
  • TaMoGolog
  • formal languages
  • mobile systems
  • task models

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Computer Science Applications
  • Hardware and Architecture

Fingerprint

Dive into the research topics of 'Using IoTGolog to formalize IoT scenarios'. Together they form a unique fingerprint.

Cite this