dc.contributor.advisor | Seppänen, Ville | |
dc.contributor.author | Korhonen, Miiro | |
dc.date.accessioned | 2021-08-19T06:14:36Z | |
dc.date.available | 2021-08-19T06:14:36Z | |
dc.date.issued | 2021 | |
dc.identifier.uri | https://jyx.jyu.fi/handle/123456789/77433 | |
dc.description.abstract | 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. | en |
dc.format.extent | 90 | |
dc.format.mimetype | application/pdf | |
dc.language.iso | en | |
dc.rights | In Copyright | en |
dc.subject.other | DevOps | |
dc.subject.other | public safety | |
dc.subject.other | automatic monitoring | |
dc.subject.other | mission-critical communication | |
dc.title | DevOps : automatic monitoring in public safety applications | |
dc.type | master thesis | |
dc.identifier.urn | URN:NBN:fi:jyu-202108194598 | |
dc.type.ontasot | Pro gradu -tutkielma | fi |
dc.type.ontasot | Master’s thesis | en |
dc.contributor.tiedekunta | Informaatioteknologian tiedekunta | fi |
dc.contributor.tiedekunta | Faculty of Information Technology | en |
dc.contributor.laitos | Informaatioteknologia | fi |
dc.contributor.laitos | Information Technology | en |
dc.contributor.yliopisto | Jyväskylän yliopisto | fi |
dc.contributor.yliopisto | University of Jyväskylä | en |
dc.contributor.oppiaine | Tietojärjestelmätiede | fi |
dc.contributor.oppiaine | Information Systems Science | en |
dc.type.coar | http://purl.org/coar/resource_type/c_bdcc | |
dc.rights.accesslevel | restrictedAccess | |
dc.type.publication | masterThesis | |
dc.contributor.oppiainekoodi | 601 | |
dc.subject.yso | monitorointi | |
dc.subject.yso | automaatio | |
dc.subject.yso | monitoring | |
dc.subject.yso | automation | |
dc.format.content | fulltext | |
dc.rights.url | https://rightsstatements.org/page/InC/1.0/ | |
dc.rights.accessrights | 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äskylä University Library (https://kirjasto.jyu.fi/collections/archival-workstation). | en |
dc.rights.accessrights | Tekijä ei ole antanut lupaa avoimeen julkaisuun, joten aineisto on luettavissa vain Jyväskylän yliopiston kirjaston arkistotyösemalta. Ks. https://kirjasto.jyu.fi/kokoelmat/arkistotyoasema.. | fi |
dc.type.okm | G2 | |