@book{richards_fundamentals_2020,
	address = {Sebastopol, CA},
	edition = {First edition},
	title = {Fundamentals of software architecture: an engineering approach},
	isbn = {978-1-4920-4345-4},
	shorttitle = {Fundamentals of software architecture},
	publisher = {O'Reilly Media, Inc},
	author = {Richards, Mark},
	year = {2020},
}

@online{topdesk_asset_management, 
    author = {TOPdesk},
    title = {Asset Management},
    year = 2022,
    url = {https://www.topdesk.com/nl/features/asset-management-software/ },
    urldate = {2022-05-02}
}

@online{topdesk_itsm, 
    author = {TOPdesk},
    title = {IT Service Management},
    year = 2022,
    url = {https://www.topdesk.com/nl/itsm-software/ },
    urldate = {2022-05-02}
}

@online{superputty, 
    author = {Jim Radford},
    title = {SuperPuTTY},
    year = 2022,
    url = {https://github.com/jimradford/superputty },
    urldate = {2022-05-02}
}

@online{openssh, 
    author = {OpenSSH},
    title = {OpenSSH SSH Protocol Suite Features},
    year = 2022,
    url = {https://www.openssh.com/features.html },
    urldate = {2022-05-02}
}

@online{cattools, 
    author = {Solarwinds},
    title = {Kiwi CatTools -- Network Automation and Configuration Management software},
    year = 2022,
    url = {https://www.kiwisyslog.com/kiwi-cattools },
    urldate = {2022-05-02}
}

@online{prtg, 
    author = {Paessler},
    title = {PRTG Network Monitor},
    year = 2022,
    url = {https://www.paessler.com/prtg },
    urldate = {2022-05-02}
}

@online{ansible, 
    author = {Red Hat},
    title = {Ansible},
    year = 2022,
    url = {https://www.ansible.com/ },
    urldate = {2022-05-02}
}

@online{ansible_install_requirements, 
    author = {Red Hat},
    title = {Ansible Installation Prerequisites},
    year = 2022,
    url = {https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#prerequisites },
    urldate = {2022-05-06}
}

@article{shahin_continuous_2017,
	title = {Continuous {Integration}, {Delivery} and {Deployment}: {A} {Systematic} {Review} on {Approaches}, {Tools}, {Challenges} and {Practices}},
	volume = {5},
	issn = {2169-3536},
	shorttitle = {Continuous {Integration}, {Delivery} and {Deployment}},
	url = {http://ieeexplore.ieee.org/document/7884954/},
	doi = {10.1109/ACCESS.2017.2685629},
	abstract = {Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. With the increasing interest in the literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices. This paper aimed at systematically reviewing the state of the art of continuous practices to classify approaches and tools, identify challenges and practices in this regard, and identify the gaps for future research. We used the systematic literature review method for reviewing the peerreviewed papers on continuous practices published between 2004 and June 1, 2016. We applied the thematic analysis method for analyzing the data extracted from reviewing 69 papers selected using predefined criteria. We have identified 30 approaches and associated tools, which facilitate the implementation of continuous practices in the following ways: 1) reducing build and test time in continuous integration (CI); 2) increasing visibility and awareness on build and test results in CI; 3) supporting (semi-) automated continuous testing; 4) detecting violations, flaws, and faults in CI; 5) addressing security and scalability issues in deployment pipeline; and 6) improving dependability and reliability of deployment process. We have also determined a list of critical factors, such as testing (effort and time), team awareness and transparency, good design principles, customer, highly skilled and motivated team, application domain, and appropriate infrastructure that should be carefully considered when introducing continuous practices in a given organization. The majority of the reviewed papers were validation (34.7\%) and evaluation (36.2\%) research types. This paper also reveals that continuous practices have been successfully applied to both greenfield and maintenance projects. Continuous practices have become an important area of software engineering research and practice. While the reported approaches, tools, and practices are addressing a wide range of challenges, there are several challenges and gaps, which require future research work for improving the capturing and reporting of contextual information in the studies reporting different aspects of continuous practices; gaining a deep understanding of how software-intensive systems should be (re-) architected to support continuous practices; and addressing the lack of knowledge and tools for engineering processes of designing and running secure deployment pipelines.},
	language = {en},
	urldate = {2022-05-09},
	journal = {IEEE Access},
	author = {Shahin, Mojtaba and Ali Babar, Muhammad and Zhu, Liming},
	year = {2017},
	pages = {3909--3943},
}

@online{cisco_netwerk_security, 
    author = {Cisco},
    title = {Wat is netwerk security?},
    year = 2022,
    url = {https://www.cisco.com/c/nl_nl/products/security/what-is-network-security.html},
    urldate = {2022-05-12}
}

@online{ansible_awx, 
    author = {Ansible Community Contributors},
    title = {Ansible AWX GitHub Repository},
    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},
}