DevOps automatic monitoring in public safety applications

Nowadays, the software is being developed in a rapidly changing and unpredictable market. Technologies and tools have evolved fast, and companies are increasingly dependent on effective communication and information. The DevOps model has also been built on these needs. The DevOps model has its roots...

Täydet tiedot

Bibliografiset tiedot
Päätekijä: Korhonen, Miiro
Muut tekijät: Informaatioteknologian tiedekunta, Faculty of Information Technology, Informaatioteknologia, Information Technology, Jyväskylän yliopisto, University of Jyväskylä
Aineistotyyppi: Pro gradu
Kieli:eng
Julkaistu: 2021
Aiheet:
Linkit: https://jyx.jyu.fi/handle/123456789/77433
_version_ 1826225692907405312
author Korhonen, Miiro
author2 Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_facet Korhonen, Miiro Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä Korhonen, Miiro Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_sort Korhonen, Miiro
datasource_str_mv jyx
description Nowadays, the software is being developed in a rapidly changing and unpredictable market. Technologies and tools have evolved fast, and companies are increasingly dependent on effective communication and information. The DevOps model has also been built on these needs. The DevOps model has its roots in software development models such as Agile and Lean thinking. Essential components in the DevOps model include automation and continuous practices. Public safety is an essential part of a functioning society. Public safety systems and applications provide, for example, a reliable way for authorities, such as police or fire services, to communicate quickly and seamlessly in critical situations. TETRA’s transition to the broader use of consumer LTE networks has been rapid in the public safety sector. This research examines the DevOps principles of automation and automatic monitoring and how these principles are reflected in the public safety framework. The research has been executed in collaboration with the client company. The research combines a literature review and an empirical semi- structured interview. The study revealed that there is no unambiguous definition for the DevOps model. The DevOps model can be seen as a methodology that affects the entire organizational culture. The main idea of the model is to break barriers between development and operations teams. According to the model, cooperation can be improved by improving communication, utilizing continuous practices, automation, and tools to streamline processes and avoid waste. There are many automation tools available on the market, but implementing them into the current situation of the client company was seen as challenging. In the interviews, several themes emerged, which were seen as a challenge for implementing automation and automatic monitoring. Challenges included customers’ private networks and a reluctance to release data outside the organization. Challenges also included platforms and storing data.
first_indexed 2021-08-19T20:01:12Z
format Pro gradu
fullrecord [{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Korhonen, Miiro", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2021-08-19T06:14:36Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2021-08-19T06:14:36Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2021", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/77433", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Nowadays, the software is being developed in a rapidly changing and unpredictable market. Technologies and tools have evolved fast, and companies are increasingly dependent on effective communication and information. The DevOps model has also been built on these needs. The DevOps model has its roots in software development models such as Agile and Lean thinking. Essential components in the DevOps model include automation and continuous practices.\n\nPublic safety is an essential part of a functioning society. Public safety systems and applications provide, for example, a reliable way for authorities, such as police or fire services, to communicate quickly and seamlessly in critical situations. TETRA\u2019s transition to the broader use of consumer LTE networks has been rapid in the public safety sector.\n\nThis research examines the DevOps principles of automation and automatic monitoring and how these principles are reflected in the public safety framework. The research has been executed in collaboration with the client company. The research combines a literature review and an empirical semi- structured interview.\n\nThe study revealed that there is no unambiguous definition for the DevOps model. The DevOps model can be seen as a methodology that affects the entire organizational culture. The main idea of the model is to break barriers between development and operations teams. According to the model, cooperation can be improved by improving communication, utilizing continuous practices, automation, and tools to streamline processes and avoid waste.\n\nThere are many automation tools available on the market, but implementing them into the current situation of the client company was seen as challenging. In the interviews, several themes emerged, which were seen as a challenge for implementing automation and automatic monitoring. Challenges included customers\u2019 private networks and a reluctance to release data outside the organization. Challenges also included platforms and storing data.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2021-08-19T06:14:36Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2021-08-19T06:14:36Z (GMT). No. of bitstreams: 0\n Previous issue date: 2021", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "90", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.format.mimetype", "value": "application/pdf", "language": null, "element": "format", "qualifier": "mimetype", "schema": "dc"}, {"key": "dc.language.iso", "value": "eng", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "DevOps", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "public safety", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "automatic monitoring", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "mission-critical communication", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "DevOps : automatic monitoring in public safety applications", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "master thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202108194598", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "yvv.contractresearch.collaborator", "value": "business", "language": "", "element": "contractresearch", "qualifier": "collaborator", "schema": "yvv"}, {"key": "yvv.contractresearch.funding", "value": "5000", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "yvv.contractresearch.initiative", "value": "business", "language": "", "element": "contractresearch", "qualifier": "initiative", "schema": "yvv"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_bdcc", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "restrictedAccess", "language": null, "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "masterThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.subject.oppiainekoodi", "value": "601", "language": "", "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "monitorointi", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "automaatio", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "monitoring", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "automation", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.format.content", "value": "fulltext", "language": null, "element": "format", "qualifier": "content", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}, {"key": "dc.rights.accessrights", "value": "The author has not given permission to make the work publicly available electronically. Therefore the material can be read only at the archival workstation at Jyv\u00e4skyl\u00e4 University Library (https://kirjasto.jyu.fi/collections/archival-workstation).", "language": "en", "element": "rights", "qualifier": "accessrights", "schema": "dc"}, {"key": "dc.rights.accessrights", "value": "Tekij\u00e4 ei ole antanut lupaa avoimeen julkaisuun, joten aineisto on luettavissa vain Jyv\u00e4skyl\u00e4n yliopiston kirjaston arkistoty\u00f6semalta. Ks. https://kirjasto.jyu.fi/kokoelmat/arkistotyoasema..", "language": "fi", "element": "rights", "qualifier": "accessrights", "schema": "dc"}, {"key": "dc.type.okm", "value": "G2", "language": null, "element": "type", "qualifier": "okm", "schema": "dc"}]
id jyx.123456789_77433
language eng
last_indexed 2025-02-18T10:55:33Z
main_date 2021-01-01T00:00:00Z
main_date_str 2021
publishDate 2021
record_format qdc
source_str_mv jyx
spellingShingle Korhonen, Miiro DevOps : automatic monitoring in public safety applications DevOps public safety automatic monitoring mission-critical communication Tietojärjestelmätiede Information Systems Science 601 monitorointi automaatio monitoring automation
title DevOps : automatic monitoring in public safety applications
title_full DevOps : automatic monitoring in public safety applications
title_fullStr DevOps : automatic monitoring in public safety applications DevOps : automatic monitoring in public safety applications
title_full_unstemmed DevOps : automatic monitoring in public safety applications DevOps : automatic monitoring in public safety applications
title_short DevOps
title_sort devops automatic monitoring in public safety applications
title_sub automatic monitoring in public safety applications
title_txtP DevOps : automatic monitoring in public safety applications
topic DevOps public safety automatic monitoring mission-critical communication Tietojärjestelmätiede Information Systems Science 601 monitorointi automaatio monitoring automation
topic_facet 601 DevOps Information Systems Science Tietojärjestelmätiede automaatio automatic monitoring automation mission-critical communication monitoring monitorointi public safety
url https://jyx.jyu.fi/handle/123456789/77433 http://www.urn.fi/URN:NBN:fi:jyu-202108194598
work_keys_str_mv AT korhonenmiiro devopsautomaticmonitoringinpublicsafetyapplications