<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Application Of MLOps Practices For Biomedical Image Classification</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Oleh</forename><surname>Berezsky</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Oleh</forename><surname>Pitsun</surname></persName>
							<email>o.pitsun@wunu.edu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Grygory</forename><surname>Melnyk</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Yuriy</forename><surname>Batko</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Bohdan</forename><surname>Derysh</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Petro</forename><surname>Liashchynskyi</surname></persName>
							<email>p.liashchynskyi@st.wunu.edu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution" key="instit1">West</orgName>
								<orgName type="institution" key="instit2">Ukrainian National University</orgName>
								<address>
									<addrLine>11 Lvivska st</addrLine>
									<postCode>46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Application Of MLOps Practices For Biomedical Image Classification</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">7EB57425762772D9712D5A0FF5E83CAB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T23:22+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Machine learning</term>
					<term>MLOps</term>
					<term>biomedical images</term>
					<term>programming</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>With active hardware development, the number of software machine learning-based systems has increased dramatically in all areas of human activity, in particular, in medicine. The use of machine learning elements in software systems requires the organization of a pipeline process of software development, testing, and support. The application of MLOps technologies will improve the quality and speed of system development, as well as simplify the process of adjusting the algorithm parameters to improve the system operation quality. The purpose of this work is to develop an MLOps pipeline that will consider all the necessary stages of software development based on machine learning algorithms for biomedical image processing.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">Introduction</head><p>Many software development companies in various fields have begun to actively implement machine learning techniques. A large number of funds will be allocated for these needs. According to Deeplearning.ai reports <ref type="bibr" target="#b0">[1]</ref>, only 22 percent of all projects using artificial intelligence have successfully implemented the process of using machine learning models. The standard software development process uses only programming languages, frameworks, and libraries. The process of developing software using elements of machine learning requires the development of neural network architectures, tools for processing large volumes of data, and training and testing system modules. The software development industry has faced a number of challenges that have led to the development of the DevOps model. This model provides a pipelined development process that allows optimizing the code development process. <ref type="bibr">Leite et al. in</ref>  <ref type="bibr" target="#b1">[2]</ref> presented the concepts and peculiarities of DevOps technology. In the work <ref type="bibr" target="#b2">[3]</ref>, the authors provided tools and techniques that are widely used in DevOps-based software development.</p><p>The MLOps model is aimed to organize the machine learning process. MLOps uses DevOps practices for machine learning and allows programmers to work collaboratively on a single project. This allows for increasing the speed of development and provides rapid data analysis by means of using monitoring tools. Thus, the use of this approach allows implementing machine learning in modern projects on an industrial scale, and not only in a test form. The peculiarity of this publication is that we analyze all the steps necessary for the high-quality implementation of machine learning elements in the process of development and maintenance of specialized software based on image processing. The novelty of the work is that the necessary additional steps inherent only in the stage of processing biomedical images are taken into account.</p><p>The life cycle of machine learning-based software development consists of the following components:</p><p>-obtaining data (biomedical images); -data processing, bringing it to the required form, for example, image filtering, image segmentation, etc.; -development of neural network architecture, for example, convolutional neural network; -architecture tuning; -deployment; -monitoring of work results. One of the key approaches for project code deployment is the use of continuous integration and continuous delivery.</p><p>MLOps develops the software development pipeline by providing a closer collaboration between data groups. This accelerates the speed of project release and the ability to adapt the input parameters of machine learning algorithms depending on the indicators of the monitoring results. MLOps is an extension of the concept of DevOps and is designed to run machine learning models in production. The purpose of this work is to develop an MLOps pipeline that considers all the necessary stages of software development based on machine learning algorithms for biomedical image processing.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Literature review</head><p>Analysis of recent publications of scientists in this field is presented in the literature review.</p><p>In work <ref type="bibr" target="#b3">[4]</ref>, the authors investigated the "MLOps" concept and highlighted the advantages of its application for software development.</p><p>Yue Zhou in <ref type="bibr" target="#b4">[5]</ref> reviewed such platforms as TensorFlow Extended, ModelOps, and Kubeflow. As a result of the analysis, the author highlighted the systems' imperfections from the ML pipelines' point of view. The author analyzed the speed of each stage in ML pipelines.</p><p>Kreuzberger et al. in <ref type="bibr" target="#b5">[6]</ref> conducted a generalized analysis of MLOps approaches and modern architectures. The authors analyzed publications, software tools, and expert feedback in this area.</p><p>In the book "Practical MLOps" <ref type="bibr" target="#b6">[7]</ref>, the authors provided examples of using MLOps solutions in combination with AWS, Microsoft Azure, and Google Cloud services. The authors also provided the best solutions for applying MLOps-based practices at the stage of system monitoring.</p><p>Application of MLOps-practices using AWS SageMaker, Google Cloud, and Microsoft Azure services is considered in work <ref type="bibr" target="#b7">[8]</ref>. In addition, the authors presented the results of using the PyTorch, Keras, and TensorFlow libraries.</p><p>Reddy et al. in <ref type="bibr" target="#b8">[9]</ref> proposed a framework for the machine learning process (MLOps) for platform development. This platform optimizes data and integrates processes, as well as brings together all processes by automating the project deployment phase.</p><p>Currently, there is a problem with harmonizing software development standards in medicine with elements of artificial intelligence. The authors in <ref type="bibr" target="#b9">[10]</ref> provided arguments for the need to implement software development standards at the international level.</p><p>Kaminwar et al. in the work "Structured Verification of Machine Learning Models in Industrial Settings" <ref type="bibr" target="#b10">[11]</ref> showed 5 stages of the life cycle of developing software applications based on machine learning.</p><p>The DevOps methodology appeared much earlier than the concept of MLOps and involved approaches to software development without the use of machine learning elements. In a research study <ref type="bibr" target="#b11">[12]</ref>, Erich et al. provided ways to use the DevOps methodology in software development in organizations that operate in various industries. In research <ref type="bibr" target="#b12">[13]</ref>, the authors focused their attention on automation, software development culture, continuous integration, and continuous delivery approaches.</p><p>Therefore, in these publications, scientists paid considerable attention to data processing in general, and in most cases in text format. The main goal of implementing DevOps practices is to eliminate the barrier between software developers and operations <ref type="bibr" target="#b13">[14]</ref>. In work <ref type="bibr" target="#b14">[15]</ref>, the authors emphasized the application of DevOps practices at the level of cloud computing and testing. It made it possible to provide software and services quickly, reliably, and with better quality. DevOps uses a variety of methodologies that unite developers and operations personnel <ref type="bibr" target="#b15">[16]</ref>. Applying DevOps practices of continuous automation for machine learning is described in <ref type="bibr" target="#b16">[17]</ref>. In work <ref type="bibr" target="#b17">[18]</ref>, Ebert et al. analyzed modern tools for DevOps specialists.</p><p>The application of machine learning technologies for biomedical image analysis has its own peculiarities. The task of automatic biomedical image segmentation using the U-Net architecture is considered in <ref type="bibr" target="#b18">[19]</ref>. The specific features of immunohistochemical image-based breast cancer diagnosing were demonstrated in <ref type="bibr" target="#b19">[20]</ref>. An adaptive method of immunohistochemical image processing was developed in <ref type="bibr" target="#b20">[21]</ref>. The classification of cytological images was considered in the article <ref type="bibr" target="#b21">[22]</ref>. The process of entire biomedical image processing requires the development of a specialized approach that includes computer vision algorithms, machine learning, and other typical software components.</p><p>Currently, there are other similar tools and prototypes that cannot implement the necessary functionality. However, they have a number of disadvantages:</p><p>-poor documentation; -the platforms are under development, so some functionality is not fully implemented; resource limitation in the free version; -experience with Amazon services is required to get started. Therefore, research and development of a pipeline for biomedical image processing is an urgent task.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Problem statement</head><p>Development of the MLOps methodology for designing a software system for biomedical image processing is an important task.</p><p>The objectives of this work are as follows:</p><p>1. Analyze MLOps platform tools. 2. Develop the main components of the pipeline for image analysis.</p><p>3. Describe the ML-pipeline for biomedical image processing.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Analysis of MLOps tools and platforms</head><p>MLOps provides an entire software development lifecycle, from an idea to the project deployment. Comparison of MLOps tools is a complex process, as there are a large number of evaluation criteria and specificity of a subject area. Table <ref type="table" target="#tab_0">1</ref> provides a comparative analysis of MLOps tools and highlights their advantages and disadvantages. In these directories, there are files of researched images in RGB format. Image labeling is also a component of the MLOps workflow.   The MLOps pipeline for biomedical images processing is characterized by the fact that it is necessary to provide steps related to pre-processing of images, taking into account filtering elements, brightness/contrast level adjustment based on computer vision algorithms.</p><p>For image segmentation, the architecture of the U-net network was developed, which is shown in Figure <ref type="figure" target="#fig_3">4</ref>: The "Model registration" stage involves containerization of the project together with the developed model using Docker. Docker is a software tool that combines operating system code and additional libraries. Containerization allows the creation of a configuration file that includes all the necessary dependencies for project execution.</p><p>The Deploy stage serves to deploy the project in the required environment using such tools as container instances, Kubernetes clusters, or a virtual machine. In this stage, testing is a key procedure. Successful execution of all automatic tests allows deploying and fully engaging the project in the required environment, for example, in the cloud.</p><p>After the implementation of the developed project and machine learning model, it is important to monitor the performance of the developed program. Therefore, monitoring stages are used in the MLOps pipeline. With the help of special tools, it is possible to monitor various work parameters, including system load. Logging in is also an important step. This stage helps to monitor the state of the system not only in real-time, but also during some specific period (e.g., week, day, or hours). Usually, log files are located in the server where the software system is running. There are also tools that allow more convenient record analysis in log files.</p><p>Specially trained engineers are engaged in the analysis of system indicators. Feedback from engineers on the system indicators allows for adjusting the developed project: to improve the architecture of the neural network, use more training data at the training stage, and increase the characteristics of the environment in which the project is deployed. If it is necessary to change any characteristics of the project, then data scientists, developers, or system administrators start working and the project deployment process takes place according to the previous workflow.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Conclusions</head><p>1. A comparative analysis of MLOps tools was carried out, which made it possible to highlight their advantages and disadvantages. In particular, most of the tools include API for working with the system and integrating with known cloud services.</p><p>2. There was developed MLOps workflow for biomedical images. This workflow takes into account the peculiarities of image processing.</p><p>3. Architectures of convolutional neural networks and U-net networks, which are components of the model code built during the workflow execution, were developed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Related Works and Discussion</head><p>In future research, it is planned to improve the existing pipeline by adding functionality to use not only convolutional neural networks, but also other machine learning tools, such as logistic regression, </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: MLOps workflow for biomedical images.</figDesc><graphic coords="5,72.00,173.15,450.60,348.00" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2 :</head><label>2</label><figDesc>Figure 2: Examples of immunohistochemical images</figDesc><graphic coords="6,86.15,72.00,117.95,93.85" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: CNN Architecture</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Architecture of the U-net encoder</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>Comparative analysis of MLOps tools.</figDesc><table><row><cell>MLOps -tool</cell><cell>Advantages</cell><cell>Disadvantages</cell></row><row><cell>Iguazio</cell><cell>Availability of a large number of</cell><cell></cell></row><row><cell></cell><cell>ready-made features.</cell><cell></cell></row><row><cell></cell><cell>A convenient interface for</cell><cell></cell></row><row><cell></cell><cell>implementing the model in real</cell><cell></cell></row><row><cell></cell><cell>life.</cell><cell></cell></row></table><note>o Er (estrogen) o Her2neu o Pr (progesterone) o Ki-67 o Histology</note></figure>
		</body>
		<back>

			<div type="availability">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Availability of a free trial period. API availability.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Poor documentation</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Kubeflow</head><p>Availability of pyTorch, Jupyter, TensorFlow, and scikit-learn. Availability of integration with Kubernetes.</p></div>
			</div>

			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Resource limitation in the free version.</p><p>So, machine learning-based software systems are currently actively developing. Available services provide an opportunity to develop systems that use artificial intelligence. Most of the MLOps tools have a convenient graphical interface that allows for monitoring all stages of program development. Also, a key characteristic of such tools is a typical workflow and components for integration with cloud services.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">MLOps workflow for biomedical image.</head><p>Unlike the DevOps concept, MLOps involves more experiments and tests. MLOps is a set of approaches for communication between data scientists, developers, and operation engineers.</p><p>MLOps workflow consists of 3 main components: 1. Build. 2. Deploy.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Monitor.</head><p>MLOps-workflow for processing biomedical images is shown in Figure <ref type="figure">1</ref>.</p><p>The main difference between DevOps and MLOps is the availability of data. Data can be in structured or unstructured forms. After the formation of the data set, it is necessary to divide it into a test sample and a training sample. There are two main approaches to dividing the sample:</p><p>1. Creation of two directories "test" and "training". 2. Storage of all images in one directory and software division into test or training samples. The developed directory structure for processing immunohistochemical images looks like this:</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">The batch companies slipping on ai goals self training for better vision muppets and models china vs us only the best examples proliferating patents</title>
		<author>
			<persName><surname>Deeplearning</surname></persName>
		</author>
		<ptr target="https://info.deeplearning.ai/the-batch-companies-slipping-on-ai-goals-self-training-for-better-vision-muppets-and-models-china-vs-us-only-the-best-examples-proliferating-patents" />
		<imprint>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A Survey of DevOps Concepts and Challenges</title>
		<author>
			<persName><forename type="first">Leonardo</forename><surname>Leite</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Carla</forename><surname>Rocha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Fabio</forename><surname>Kon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Dejan</forename><surname>Milojicic</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Paulo</forename><surname>Meirelles</surname></persName>
		</author>
		<idno type="DOI">10.1145/3359981</idno>
		<ptr target="https://doi.org/10.1145/3359981" />
	</analytic>
	<monogr>
		<title level="j">ACM Comput. Surv</title>
		<imprint>
			<biblScope unit="volume">52</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page">35</biblScope>
			<date type="published" when="2019-11">2019. November 2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">DevOps and Its Practices</title>
		<author>
			<persName><forename type="first">L</forename><surname>Zhu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Bass</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Champlin-Scharff</surname></persName>
		</author>
		<ptr target="https://ieeexplore.ieee.org/abstract/document/7458765" />
	</analytic>
	<monogr>
		<title level="j">IEEE Software</title>
		<imprint>
			<biblScope unit="volume">33</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="32" to="34" />
			<date type="published" when="2016-06">May-June 2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">What Is MLOps?</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alla</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">K</forename><surname>Adari</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-1-4842-6549-9_3</idno>
		<ptr target="https://doi.org/10.1007/978-1-4842-6549-9_3" />
	</analytic>
	<monogr>
		<title level="m">Beginning MLOps with MLFlow</title>
				<meeting><address><addrLine>Berkeley, CA</addrLine></address></meeting>
		<imprint>
			<publisher>Apress</publisher>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Towards MLOps: A Case Study of ML Pipeline Platform</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Ding</surname></persName>
		</author>
		<ptr target="https://ieeexplore.ieee.org/abstract/document/9361315" />
	</analytic>
	<monogr>
		<title level="m">2020 International Conference on Artificial Intelligence and Computer Engineering (ICAICE)</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="page" from="494" to="500" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Machine Learning Operations (MLOps): Overview, Definition, and Architecture</title>
		<author>
			<persName><forename type="first">D</forename><surname>Kreuzberger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Kühl</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Hirschl</surname></persName>
		</author>
		<idno type="DOI">10.48550/arxiv.2205.02302</idno>
		<ptr target="https://doi.org/10.48550/arxiv.2205.02302" />
	</analytic>
	<monogr>
		<title level="j">Arxiv</title>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">Practical MLOps</title>
		<author>
			<persName><forename type="first">Noah</forename><surname>Gift</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Alfredo</forename><surname>Deza</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2021">2021</date>
			<publisher>O&apos;Reilly Media, Inc</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Beginning MLOps with MLFlow</title>
		<author>
			<persName><surname>Sridhar Alla</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Kalyan</forename><surname>Suman</surname></persName>
		</author>
		<author>
			<persName><surname>Adari</surname></persName>
		</author>
		<idno type="DOI">10.1007/978-1-4842-6549-9</idno>
		<ptr target="https://doi.org/10.1007/978-1-4842-6549-9" />
		<imprint>
			<date type="published" when="2021">2021</date>
			<publisher>Apress</publisher>
			<biblScope unit="volume">XIV</biblScope>
			<pubPlace>Berkeley, CA</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Application of MLOps in Prediction of Lifestyle Diseases</title>
		<author>
			<persName><forename type="first">M</forename><surname>Reddy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Dattaprakash</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kammath</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Kn</surname></persName>
		</author>
		<idno type="DOI">10.1149/10701.1191ecst</idno>
		<ptr target="https://doi.org/10.1149/10701.1191ecst" />
	</analytic>
	<monogr>
		<title level="j">ECS Trans</title>
		<imprint>
			<biblScope unit="volume">107</biblScope>
			<biblScope unit="page">1191</biblScope>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Machine Learning in Healthcare: Mapping a Path to Title 21</title>
		<author>
			<persName><surname>Maximo J Marin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M R</forename><surname>Xander</surname></persName>
		</author>
		<author>
			<persName><surname>Van Wijk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J S</forename><surname>Thomas</surname></persName>
		</author>
		<author>
			<persName><surname>Durant</surname></persName>
		</author>
		<idno type="DOI">10.1093/clinchem/hvab285</idno>
		<ptr target="https://doi.org/10.1093/clinchem/hvab285" />
	</analytic>
	<monogr>
		<title level="j">Clinical Chemistry</title>
		<imprint>
			<biblScope unit="volume">68</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="609" to="610" />
			<date type="published" when="2022-04">April 2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Structured Verification of Machine Learning Models in Industrial Settings</title>
		<author>
			<persName><forename type="first">Jann</forename><surname>Sai Rahul Kaminwar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Janek</forename><surname>Goschenhofer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ingo</forename><surname>Thomas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Bernd</forename><surname>Thon</surname></persName>
		</author>
		<author>
			<persName><surname>Bischl</surname></persName>
		</author>
		<idno type="DOI">10.1089/big.2021.0112</idno>
		<ptr target="http://doi.org/10.1089/big.2021.0112" />
		<imprint>
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
	<note type="report_type">ahead of print</note>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">A qualitative study of DevOps usage in practice</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M A</forename><surname>Erich</surname></persName>
		</author>
		<idno type="DOI">10.1002/smr.1885</idno>
		<ptr target="https://doi.org/10.1002/smr.1885" />
	</analytic>
	<monogr>
		<title level="j">Special Issue: Recent Advances in Agile Software Product Development</title>
		<imprint>
			<biblScope unit="volume">26</biblScope>
			<biblScope unit="issue">9</biblScope>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">DevOps and software quality: A systematic mapping</title>
		<author>
			<persName><forename type="first">Alok</forename><surname>Mishra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Ziadoon</forename><surname>Otaiwi</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.cosrev.2020.100308</idno>
		<ptr target="https://doi.org/10.1016/j.cosrev.2020.100308" />
	</analytic>
	<monogr>
		<title level="j">Computer Science Review</title>
		<imprint>
			<biblScope unit="volume">38</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Adopting DevOps in the real world: A theory, a model, and a case study</title>
		<author>
			<persName><forename type="first">Welder</forename><surname>Pinheiro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Luz</forename></persName>
		</author>
		<author>
			<persName><forename type="first">Gustavo</forename><surname>Pinto</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Rodrigo</forename><surname>Bonifácio</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.jss.2019.07.083</idno>
		<ptr target="https://doi.org/10.1016/j.jss.2019.07.083" />
	</analytic>
	<monogr>
		<title level="j">Journal of Systems and Software</title>
		<imprint>
			<biblScope unit="volume">157</biblScope>
			<date type="published" when="2019">2019</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Devops, A New Approach To Cloud Development &amp; Testing</title>
		<author>
			<persName><forename type="first">Dhaya</forename><surname>Battina</surname></persName>
		</author>
		<author>
			<persName><surname>Sindhu</surname></persName>
		</author>
		<ptr target="http://www.jetir.org/papers/JETIR2008432.pdf" />
	</analytic>
	<monogr>
		<title level="m">International Journal of Emerging Technologies and Innovative Research</title>
				<imprint>
			<date type="published" when="2020">2020</date>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="page" from="982" to="985" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">The Challenges and Mitigation Strategies of Using DevOps during Software Development</title>
		<author>
			<persName><forename type="first">Dhaya</forename><surname>Battina</surname></persName>
		</author>
		<author>
			<persName><surname>Sindhu</surname></persName>
		</author>
		<ptr target="http://www.ijcrt.org/papers/IJCRT2101583.pdf" />
	</analytic>
	<monogr>
		<title level="j">International Journal of Creative Research Thoughts (IJCRT)</title>
		<idno type="ISSN">:2320-2882</idno>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="4760" to="4765" />
			<date type="published" when="2021-01">2021. January 2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Applying DevOps Practices of Continuous Automation for Machine Learning</title>
		<author>
			<persName><forename type="first">Ioannis</forename><surname>Karamitsos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Saeed</forename><surname>Albarhami</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Charalampos</forename><surname>Apostolopoulos</surname></persName>
		</author>
		<idno type="DOI">10.3390/info11070363</idno>
		<ptr target="https://doi.org/10.3390/info11070363" />
	</analytic>
	<monogr>
		<title level="j">Information</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">7</biblScope>
			<biblScope unit="page">363</biblScope>
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title/>
		<author>
			<persName><forename type="first">C</forename><surname>Ebert</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Gallardo</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hernantes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Serrano</surname></persName>
		</author>
		<author>
			<persName><surname>Devops</surname></persName>
		</author>
		<ptr target="https://ieeexplore.ieee.org/document/7458761" />
	</analytic>
	<monogr>
		<title level="j">IEEE Software</title>
		<imprint>
			<biblScope unit="volume">33</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="94" to="100" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Savka Automatic segmentation of immunohistochemical images based on U-NET architectures</title>
		<author>
			<persName><forename type="first">O</forename><surname>Berezsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pitsun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Derysh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Datsko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Berezka</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">4th International Conference on Informatics &amp; Data-Driven Medicine</title>
				<imprint>
			<date type="published" when="2021-11-19">2021. November 19-21, 2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Tesluk Specified diagnosis of breast cancer on the basis of immunogistochemical images analysis</title>
		<author>
			<persName><forename type="first">O</forename><surname>Berezsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pitsun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Datsko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Derysh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Tsmots</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename></persName>
		</author>
		<ptr target="http://ceur-ws.org/Vol-2753/short5.pdf" />
	</analytic>
	<monogr>
		<title level="m">3rd International Conference on Informatics &amp; Data-Driven Medicine</title>
				<meeting><address><addrLine>Växjö, Sweden</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2020-11-19">2020. November 19-21, 2020</date>
			<biblScope unit="page" from="129" to="135" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Adaptive Immunohistochemical Image Pre-processing Method</title>
		<author>
			<persName><forename type="first">O</forename><surname>Berezsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pitsun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Derish</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Berezska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Melnyk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Batko</surname></persName>
		</author>
		<idno type="DOI">10.1109/ACIT49673.2020.9208920</idno>
	</analytic>
	<monogr>
		<title level="m">10th International Conference on Advanced Computer Information Technologies (ACIT)</title>
				<imprint>
			<date type="published" when="2020">2020. 2020</date>
			<biblScope unit="page" from="820" to="823" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Hybrid Intelligent information techology for biomedical image processing</title>
		<author>
			<persName><forename type="first">O</forename><surname>Berezsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Verbovyy</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pitsun</surname></persName>
		</author>
		<idno type="DOI">10.1109/STC-CSIT.2018.8526711</idno>
		<ptr target="https://doi.org/10.1109/STC-CSIT.2018.8526711" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the IEEE International Conference &quot;Computer Science and Information Technologies&quot; CSIT&apos;2018</title>
				<meeting>the IEEE International Conference &quot;Computer Science and Information Technologies&quot; CSIT&apos;2018<address><addrLine>Lviv; Ukraine</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2018-09-14">11-14 September, 2018</date>
			<biblScope unit="page" from="420" to="423" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
