Thesis/onderzoeksrapport
1
0
Fork 0
Code Issues Pull Requests Projects Releases 2 Wiki Activity

stuk toegevoegd over devops

Browse Source
This commit is contained in:
Martijn Remmen
2022-06-11 23:24:01 +02:00
parent e85d867a62
commit 0e30a781e6
3 changed files with 48 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
bibliography.bib
View File

@ -103,4 +103,40 @@
year = 2022,
url = {https://github.com/ansible/awx},
urldate = {2022-06-08}
}
@article{khan_critical_2022,
title = {Critical {Challenges} to {Adopt} {DevOps} {Culture} in {Software} {Organizations}: {A} {Systematic} {Review}},
volume = {10},
issn = {2169-3536},
shorttitle = {Critical {Challenges} to {Adopt} {DevOps} {Culture} in {Software} {Organizations}},
url = {https://ieeexplore.ieee.org/document/9690862/},
doi = {10.1109/ACCESS.2022.3145970},
abstract = {DevOps is a set of practices and a cultural movement that aims to break down barriers between development and operation teams to improve collaboration and communication. Different organizations have embraced DevOps principles due to the massive potential, such as a much shorter time to production, increased reliability and stability. However, despite the widespread adoption of DevOps and its infrastructure, there is a lack of understanding and literature on the key concepts, practices, tools, and challenges associated with implementing DevOps strategies. The main goal of this research paper is to explore and discuss challenges related to DevOps culture and practices. Moreover, it describes how DevOps works in an organization, provides a detailed explanation of DevOps, and investigates the cultural challenges that organizations face when implementing DevOps. The proposed paper reveals ten critical challenges that need to be addressed in adopting the DevOps culture. The challenges are further analyzed on the basis of the various continents. According to the findings, the following critical challenges are considered during the implementation of a DevOps culture: lack of collaboration and communication, Lack of skill and knowledge, complicated infrastructure, Lack of management, Lack of DevOps approach, and trust confidence problems.},
language = {en},
urldate = {2022-05-13},
journal = {IEEE Access},
author = {Khan, Muhammad Shoaib and Khan, Abudul Wahid and Khan, Faheem and Khan, Muhammad Adnan and Whangbo, Taeg Keun},
year = {2022},
pages = {14339--14349},
}
@inproceedings{jabbari_what_2016,
address = {Edinburgh Scotland UK},
title = {What is {DevOps}?: {A} {Systematic} {Mapping} {Study} on {Definitions} and {Practices}},
isbn = {978-1-4503-4134-9},
shorttitle = {What is {DevOps}?},
url = {https://dl.acm.org/doi/10.1145/2962695.2962707},
doi = {10.1145/2962695.2962707},
abstract = {Objective:This study aims to characterize DevOps by exploring central components of DevOps definitions reported in the literature, specifying practices explicitly proposed for DevOps and investigating the similarities and differences between DevOps and other existing methods in software engineering.
Method: A systematic mapping study was conducted that used six electronic databases: IEEE, ACM, Inspec, Scopus, Wiley Online Library and Web of Science.
Result: 44 studies have been selected that report a definition of DevOps, 15 studies explicitly stating DevOps practices, and 15 studies stating how DevOps is related to other existing methods. Papers in some cases stated a combination of a definition, practices, and relations to other methods, the total number of primary studies was 49.
Conclusion: We proposed a definition for DevOps which may overcome inconsistencies over the various existing definitions of individual research studies. In addition, the practices explicitly proposed for DevOps have been presented as well as the relation to other software development methods.},
language = {en},
urldate = {2022-06-11},
publisher = {ACM},
author = {Jabbari, Ramtin and bin Ali, Nauman and Petersen, Kai and Tanveer, Binish},
month = may,
year = {2016},
pages = {1--11},
}