Composable DevOps: Automated Ontology Based DevOps Maturity Analysis

Abstract

In this era of the emerging digitized, mobilized, and cloudified enterprises, the concept of the "composable business" is the most critical piece which ties everything together. The digital enterprise is here, and its prime characteristic is that is essentially detaches and segregates existing businesses and reassembles them according to market demands. Every industry, from transportation to eyewear is up for disruption, and developers are in the forefront of this movement. In turn, these developers are under intense pressure to accelerate time to market. The composable enterprise approach requires a reconsideration of traditional models of the entire IT organization. These organization and their processes need to be broken up into components that follow certain key design principles such as The Minimal Functions with least Dependencies, portability, Shared Knowledge, Predictable Contracts and Maximized Human Value. The last three bullet points encapsulate the very definition of DevOps [3]. The concept of better integration between Development andOperations is a valuable objective. The goal is to foster measurable incremental cultural change to derive most overall value out of the union of people, process and technology. But the cultural issues, reward models, and risk allocation create obvious barriers in attaining those goals. The common industry belief is to use the composable enterprise framework to build a platform using the right tools and you will have attained DevOps nirvana. In this paper we will explore valuable lessons learned from our mistakes in tool centric adoption of IT Infrastructure Library (ITIL) [8] . We will also show how we applied those lessons to develop a lightweight composable/contextual DevOps framework that learns and measure itself to avoid those cultural pitfalls.

Towards a benefits dependency network for DevOps based on a systematic literature review

“…Farroha and Farroha mention that the focus is on team and communication rather than tools and processes to improve business value that points to simplicity and agility in technology, process, and human factors in addition to enabling trust and supporting innovation, which has been also highlighted by McCarthy et al as DevOps principles.…”

“…Break down barriers between development and operations by enabling trust, sharing tools and supporting communication, collaboration, and integration. () The focus is on teamwork, communication, and collaboration rather than tools and processes, eg, maximize team performance. () Pr2: automation.…”

“…() The focus is on teamwork, communication, and collaboration rather than tools and processes, eg, maximize team performance. () Pr2: automation. Automate build, deployment, and test to achieve fast software creation through repeatable processes and operations resulting in, eg, short lead times, rapid delivery, and fast feedback from end‐users.…”

“…Bang et al state that the measurement perspective of DevOps covers the measurement of the process, value, cost, and technical metrics. Pr6: composability. Follow certain design principles to achieve DevOps such as the minimal functions with least dependencies, portability, predictable contract, and maximized human value …”

“…It should be mentioned that only 3 papers() have had an overlap of DevOps principles, practices, challenges, and benefits that shows a lack of comprehension of DevOps in terms of different characteristics in the selected studies. Table shows the frequency of the 40 studies used in our research in accordance with each objective (DevOps principles, practices, challenges, and benefits).…”