DevOps – concept and structural representation
DOI:
https://doi.org/10.20535/kpisn.2021.4.261938Keywords:
competitive advantage, collaboration, software product management, DevOps processes, DevOps metrics, DevOps concept, DevOps system engineering, DevOps model, DevOpsAbstract
Problems. Today, along with a huge number of methods, technologies and means of improving business efficiency, the concept of
DevOps (Development & Operations) is also gaining rapid development.
In particular, the application of the DevOps concept in business leads practitioners to the question of the feasibility of application,
formalization of this process, and usually the development of their own DevOps system focused on achieving the specified values of the
metrics of the organizational structure.
Research goal and objectives. The purpose of this article is to study the essence, concept and definition of the DevOps concept,
define the entities of the DevOps concept and formalize the unified DevOps model.
Methods of research. Methodology of comparative analysis of scientific results and engineering practices of DevOps implementation,
systematization of entity classes of the DevOps concept in the form of a Venn diagram, graphic modeling of a unified DevOps model.
Research results. The practical value and effectiveness of DevOps implementation, the lack of theoretical research and justification
of DevOps systems engineering methods, apart from examples of individual patterns and individual architectural solutions of DevOps for
the IT industry, have been established.
The article substantiates and proposes a structural representation of the DevOps concept in the form of a Venn diagram as a system
of entities of production, support, management of production and support processes, and relationships between them. These results make
it possible to choose theoretical and applied tools for the formalization of a unified model of DevOps systems.
Conclusions. The unified model of the DevOps system in the form of a diagram of components and formalized specifications of
the interfaces between these components and the unified model of the DevOps system in the form of a diagram of the activities of these
components make it possible to proceed to the development of well-founded engineering methods of DevOps systems.
References
M. Senapathi, J. Buchan, H. Osman, “DevOps capabilities, practices, and challenges: Insights from a case study”, in Proc. 22nd Int. Conf. Eval. Assess. Software Eng., 2018.
P. Jha, R. Khan, “A review paper on DevOps: Beginning and more to know”, Int. J. Comp. Applic., vol. 180, no. 48, pp. 16–20, 2018. doi: 10.5120/ijca2018917253
DevOps 101 with Atlassian [Online]. Available: https://www.atlassian.com/blog/wp-content/uploads/devops-101-atlassian.pdf
“Competitive Advantage through DevOps”, Harvard Business Review Analytyc Service, Res. Rep., 2019.
“2021 Puppet State of DevOps”, CircleCI, Report, 2021.
P. Haindl, R. Plösch, “Focus areas, themes, and objectives of non-functional requirements in DevOps: A systematic mapping study”, in 46th Euromicro Conf. Software Eng. Advanc. Applic., Portoroz, Slovenia, pp. 394–403, 2020. doi: 10.1109/SEAA51224.2020.00071
C. Scoular, D. Duckworth, J. Heard, D. Ramalingam, “Collaboration: Definition and structure”, The Australian Council for Educational Research, report, 2020.
M.L. Pedra, M.F. Silva, L.G. Azevedo, “DevOps adoption: Eight emergent perspectives”, ArXiv abs/2109.09601, 2021.
D. López-fernández, J. Díaz, J.G. Martín, J.E. Pérez, Á. González-Prieto, “DevOps team structures: Characterization and implications”, ArXiv abs/2101.02361, 2021.
M. Gokarna, R. Singh, “DevOps: A historical review and future works”, in Proc. 2021 Int. Conf. Comp. Commun. Intell. Syst., Greater Noida, India, pp. 366–371, 2021. doi: 10.1109/ICCCIS51004.2021.9397235
K. Maroukian, S.R. Gulliver, “Leading DevOps practice and principle adoption”, ArXiv abs/2008.10515, 2020.
N. Bhuiyan, “A framework for successful new product development”, J. Indust. Eng. Manag., vol. 4, no. 4, 2011. doi: 10.3926/jiem.334.
R.G. Oliveira, “Lean and performance measuring – Developing a new performance measurement framework to fit lean”, M.S. thesis, Universidade de Porto, 2018.
M. Sallin, M. Kropp, C. Anslow, J.W. Quilty, A. Meier, “Measuring software delivery performance using the four key metrics of DevOps”, in Agile Processes in Software Engineering and Extreme Programming. XP 2021. Lecture Notes in Business Information Processing, vol 419, P. Gregory, C. Lassenius, X. Wang, P. Kruchten, eds. Cham: Springer, 2021. doi: 10.1007/978-3-030-78098-2_7
R. Pietrantuono, A. Bertolino, G.D. Angelis, B. Miranda, S. Russo, “Towards continuous software reliability testing in DevOps”, in 2019 IEEE/ACM 14th Int. Workshop on Automation of Software Test, Montreal, QC, Canada, 2019. doi: 10.1109/AST.2019.00009
“What is DevOps?” [Online]: Available: https://www.atlassian.com/devops
A. Kosyakov, S.M. Beamer, S.J. Seymour, W.N. Sweet, Systems Engineering. Principles and Practice. Moscow, Russia: DMK Press, 2014, 624 p.
D.K. Hitchins, Systems Engineering. A 21st Century Systems Methodology. Wiley, 2007, 528 p.
Downloads
Published
Issue
Section
License
Copyright (c) 2022 Павло Маслянко, Іван Савчук
This work is licensed under a Creative Commons Attribution 4.0 International License.
Authors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under CC BY 4.0 that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work
