<?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">Method and tool of detecting software architecture patterns in the process of computer systems development</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Vasyl</forename><surname>Yatsyshyn</surname></persName>
							<email>vyatcyshyn@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska</addrLine>
									<postCode>56, 46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Workshop on Information Technologies: Theoretical and Applied Problems</orgName>
								<orgName type="laboratory">ITTAP&apos;2024</orgName>
								<address>
									<addrLine>October 23-25</addrLine>
									<postCode>2024</postCode>
									<settlement>Ternopil</settlement>
									<region>Opole</region>
									<country>Ukraine, Poland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Oleh</forename><surname>Pastukh</surname></persName>
							<email>oleg.pastuh@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska</addrLine>
									<postCode>56, 46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Workshop on Information Technologies: Theoretical and Applied Problems</orgName>
								<orgName type="laboratory">ITTAP&apos;2024</orgName>
								<address>
									<addrLine>October 23-25</addrLine>
									<postCode>2024</postCode>
									<settlement>Ternopil</settlement>
									<region>Opole</region>
									<country>Ukraine, Poland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Victoria</forename><surname>Kukharska</surname></persName>
							<email>victoria_kukharska@tntu.edu.ua</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska</addrLine>
									<postCode>56, 46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Workshop on Information Technologies: Theoretical and Applied Problems</orgName>
								<orgName type="laboratory">ITTAP&apos;2024</orgName>
								<address>
									<addrLine>October 23-25</addrLine>
									<postCode>2024</postCode>
									<settlement>Ternopil</settlement>
									<region>Opole</region>
									<country>Ukraine, Poland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Andriy</forename><surname>Palamar</surname></persName>
							<email>palamar.andrij@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska</addrLine>
									<postCode>56, 46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Workshop on Information Technologies: Theoretical and Applied Problems</orgName>
								<orgName type="laboratory">ITTAP&apos;2024</orgName>
								<address>
									<addrLine>October 23-25</addrLine>
									<postCode>2024</postCode>
									<settlement>Ternopil</settlement>
									<region>Opole</region>
									<country>Ukraine, Poland</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Serhii</forename><surname>Kulikov</surname></persName>
							<email>kulikov.serhiy@gmail.com</email>
							<affiliation key="aff0">
								<orgName type="institution">Ternopil Ivan Puluj National Technical University</orgName>
								<address>
									<addrLine>Ruska</addrLine>
									<postCode>56, 46001</postCode>
									<settlement>Ternopil</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">International Workshop on Information Technologies: Theoretical and Applied Problems</orgName>
								<orgName type="laboratory">ITTAP&apos;2024</orgName>
								<address>
									<addrLine>October 23-25</addrLine>
									<postCode>2024</postCode>
									<settlement>Ternopil</settlement>
									<region>Opole</region>
									<country>Ukraine, Poland</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Method and tool of detecting software architecture patterns in the process of computer systems development</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">48EDACDC0BE7F8F207058D16E93D33F0</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:41+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>detection</term>
					<term>pattern</term>
					<term>neural network</term>
					<term>software</term>
					<term>computer system</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>In this paper a method and a tool for automatic detection of software architecture patterns are proposed. The main idea of the developed method is to automatically identify design patterns using artificial intelligence approach to software requirements and meta description of reuse software component. The main value of the method is to increase accuracy of design pattern detection in the process of computer systems development and to avoid developers subjective solutions. This has been achieved by implementing a neural network with dynamic structure, which works out with attributes of software requirements and architecture patterns' meta description. The tool of detecting software architecture patterns is created like a web-service with C# and help to automate the process of proposed method.</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>Modern computer and information systems are characterized by a high level of functional complexity and the processing of a large amount of diverse and complexly structured data. In its turn, it requires from the developers of computer systems introducing new intelligent and effective methods and tools of developing both hardware and software components of the system. At the same time, formalized methods and CASE-tools must be integrated into the general process of developing the system, in particular its software component.</p><p>The most complex and time-consuming processes for any system are the identification, formulation and tracing (communication) of requirements at the stages of the life cycle. This is due to the fact that the requirements are the "foundation" for the further development of the system.</p><p>From the point of view of the software product quality which is felt by the end user of the system, it is advisable to use the recommendations of standards, in particular, ISO/IEC 25010 and ISO/IEC 14598 in the development process.</p><p>The quality characteristics of the software component of the computer system and the processes of their provision are defined by the given standards. At the same time, there are still a number of processes that require automation. This applies to the collection and storage of requirements, the classification of attributes by quality characteristics, and a number of others <ref type="bibr" target="#b0">[1]</ref>.</p><p>The next important stage of software development is designing the system architecture. Architecture can be presented at different levels, starting from conceptual one and ending with the structure of software modules.</p><p>To provide the reflection of the requirements defined at the first stage of software system development at the architecture design stage it is worth using the approach proposed in <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>. With this approach, system requirements from the end user's point of view are presented in the form of a quality model in use of the standard <ref type="bibr" target="#b2">[3]</ref>, and architecture requirements are presented in the form of the same standard external quality model.</p><p>The procedure of quality requirements display in external quality requirement using is developed and given in <ref type="bibr" target="#b3">[4]</ref>. However, for increasing the efficiency of the process of developing software systems, it is necessary to additionally develop a method and tool for automatic detection and optimal selection of an architectural template for the implementation of a requirement or its part. Therefore, the article proposes a method and tool based on a neural network approach for detection optimal architectural patterns in the implementation of software components of computer systems.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Analysis of the software architecture design process features</head><p>Software architecture is an important aspect of a quality software product that affects the program's performance and its life cycle <ref type="bibr" target="#b4">[5]</ref>.</p><p>Software architecture is the structure of a program or computer system which contains software components, externally visible properties of these components, as well as the relationship between them <ref type="bibr" target="#b4">[5]</ref>. This term also refers to the documentation of software architecture. Documenting the software architecture simplifies communication between interested parties and allows to capture high-level system design decisions made at the early design stages and gives the possibility to reuse design components and patterns in other projects.</p><p>K. Lavrishcheva, P. Andon, T. Korotun, G. Koval, O. Kharchenko, I. Sommerville, E. Braude, M. McCall, B. Boehm and other scientists devoted their scientific papers to researching the processes of designing the software systems architecture, their optimization, as well as methods and tools of ensuring and controlling the quality of software systems at the life cycle stages.</p><p>An important contribution to the development and application of software design patterns was made by such IT giants as Google, Microsoft, Hewlett Packard, Amazon and others.</p><p>Among the important tasks that are solved both by scientists and private companies it is worth noting the tasks related to determining and ensuring the balance between the cost, quality and duration of software development. In other words, setting and solving problems are aimed at achieving an acceptable level of quality of software systems with minimal expenditure of time, labor and financial resources. Although many of these problems have been solved at the moment, the problems in the field of designing software systems, namely, the process that directly affects the the final product quality, still remain incompletely solved.</p><p>Taking into account the fact that considerable practical experience has been accumulated in the field of software engineering, it is economically and technically expedient to reuse components that have shown the effectiveness and quality of their application in the software products operation. While building integration platforms such as Onlizer, component reuse is especially important.</p><p>At the current stage of software engineering and computer engineering, so many different design patterns with similar functions have been developed that it is quite difficult to choose the optimal one among them. This is due to the fact that the procedures for the optimal selection of architectural patterns are still weakly formalized, they are based on the empirical judgments of system architects and do not ensure the complete implementation of requirements for software systems. And this does not make it possible to make an optimal decision regarding the choice of a design pattern.</p><p>Therefore, the development of a method and tool of automated detection and selection of the optimal architectural pattern are the urgent tasks in the software architecture design as a component of a more complex computer system. This will minimize the subjective influence of experts or system architects and ensure the full realization of the customer's needs in the software systems properties.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Method of detecting patterns of software architecture based on a neural network approach</head><p>The pattern detection process is proposed to be implemented on the automatic analysis of requirements models and design patterns models (architectural patterns). Models of requirements and patterns can be formed by an expert based on development goals, specifics of the development process, or accepted agreements. For example, the requirements model can be based on the recommendations of the standard <ref type="bibr" target="#b2">[3]</ref> and on the internal quality model, and the pattern model can use the classification presented in <ref type="bibr" target="#b6">[7]</ref>. Since the existing standards and approaches to the formation of requirements models are of a recommendatory and general nature, the obtained models require adaptation for use in the specific conditions of the PS development process, which are determined by the subject area, software type and development goals.</p><p>The requirement model is a collection of attributes forming a set R { A 1 , … , A n }where the attribute value is determined according to the metric scale for the given attribute.</p><p>The scale for attribute values can be of any type but its projection on the interval scale</p><formula xml:id="formula_0">S Ai → S ∫¿{S1,…,Sk }, S i ∈ [0 ;1]¿ must exist.</formula><p>The set of software requirements forms the matrix R:</p><formula xml:id="formula_1">R= [ A 11 … A 1 n … … … A m 1 … A mn ] ,<label>(1)</label></formula><p>where</p><formula xml:id="formula_2">A ij ∈ S A ij is an attribute of R i requirement.</formula><p>Respectively the architectural pattern design model is a collection of attributes forming the</p><formula xml:id="formula_3">set P { A 1 ' , … , A k ' }.</formula><p>Regarding the scale of metric values of the attributes of the design pattern model, a similar requirement of the existence of a projection on the interval scale is put forward: S ∫¿:S A i ' → S ∫¿¿ ¿ A set of pattern models forms a matrix P:</p><formula xml:id="formula_4">P= [ A 11 ' … A 1 k ' … … … A t 1 ' … A tk ' ]<label>(2)</label></formula><p>where A ij ' ∈ S A ij ' is an attribute of the design pattern P i .</p><p>After adapting the models for the specific requirements of the software development process the mapping of matrix elements R and P to the S ∫¿.¿ scale is formed: R ∫¿= [</p><formula xml:id="formula_5">I 11 … I 1 n … … … I m 1 … I mn ] ¿<label>(3)</label></formula><p>where I ij is the mapping of the A ij attribute to the S ∫¿¿ scale:</p><formula xml:id="formula_6">P ∫¿= [ F 11 … F 1 k … … … F t k … F tk ] ¿<label>(4)</label></formula><p>where F ij is the mapping of the P ij attribute to the S ∫¿¿ scale.</p><p>The main component of the process of detecting design patterns is a multi-level neural network which is schematically shown in Figure <ref type="figure" target="#fig_1">2</ref>. The dimensionality of the neural network is determined by the dimensionality of the matrices R and P. The L 1 input layer contains artificial neurons with a linear transform function, which prevents the input signal from degenerating. Values from the rows of the matrix R ∫¿¿ are applied to the input of neurons of the L 1 level.</p><p>The neuron layer L 2 contains artificial neurons with a sigmoid activation function and is the first level of the hidden layer of the neural network.</p><p>Neurons of levels L 3 −L N are artificial neurons with a sigmoid activation function.</p><p>The L N +1 level is composed of artificial neurons with a sigmoid activation function and is the last level of the hidden layer.</p><p>The L N +2 level is composed of artificial neurons with a sigmoid activation function and is the initial level of the neural network. The values of the signals at the output of the L N +2 layer form the probable values of the model attributes of the design patterns P.</p><p>Based on the analysis of the values of the resulting vector at the output of the neural network using the simple moving average method, the probability of the Pi pattern entering the set of requirements R is formed.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Software implementation of a neural network for detecting architectural patterns</head><p>The NeuronDotNet library was used for the software implementation of the neural network which allows using the C# language flexibly construct various neural networks.</p><p>The NeuralNetworkBuilder module containing the static method BuildAndTrainNetwork has been developed for the formation and training of a neural network. In the process of forming a neural network, input and output levels of neurons and neurons of hidden levels are constructed and connections between them are established, as shown in Figure <ref type="figure" target="#fig_2">3</ref>.  After training the neural network can be used to find patterns using the Run method the code of which is shown in Figure <ref type="figure" target="#fig_4">5</ref>. The input of the method is given by is a set of attribute values of the requirements model. The resulting vector of values is analyzed using a simple moving average method to find the likely design pattern and is shown in Figure <ref type="figure" target="#fig_5">6</ref>. The proposed conceptual model and software implementation for detecting design patterns based on requirements models allows to change flexibly approaches to the formation of requirements models and templates, adjust the requirements analysis parameters by changing the configuration of the neural network or its training conditions. In addition, the use of a neural network as the main component of the analyzer allows to ensure the progressiveness of the search parameters, increase the accuracy of detection and automate the process of design templates searching.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">A tool for automated detection of software architectural patterns</head><p>The user interface of the software system for choosing an architectural pattern should provide convenient entry, editing and viewing of information, be intuitive, and ensure the correctness of data entry. To implement the algorithm of the program, it is proposed to use a multiwindow interface with main and subsidiary forms. UML graphical notation was chosen for system analysis and design. Figure <ref type="figure" target="#fig_6">7</ref> shows a use case diagram with an administrator actor.   The template catalog is a part of the website database that stores all information about architectural design patterns. The catalog has a hierarchical, tree-like structure that will reflect the way templates are classified. The directory structure directly depends on which templates are available on the site.</p><p>Figure <ref type="figure" target="#fig_9">9</ref> shows a sequence diagram of actions when working with the system for selecting architectural patterns of software systems.  the user selects the type of information and answers the questions of the dialog component;  the dialog component forms parameters that must be obtained from the user and passes the data to the administrator;  after that the dialog component forms requirements for the intelligent module which in turn transforms the data to be issued to the dialog component;  the intelligent module generates requests to the DBMS;  DBMS sends data to the intelligent module to make recommendations based on the collected statistical data which are displayed to the user.</p><p>As a result of the analysis of the subject area, the following classes are defined for the implementation of the design pattern detection automation tool: user, web page, web server, intelligent component, database and interface -user interface. In Figure <ref type="figure" target="#fig_10">10</ref> the class structure of the design pattern detector according to the established software requirements is presented. It is worth paying attention to the presence of an interface. This is a type of class that does not contain attributes but interacts with other classes through it.</p><p>The activity diagram for the template selection system is shown in Figure <ref type="figure" target="#fig_11">11</ref>. As can be seen from Figure <ref type="figure" target="#fig_11">11</ref>, after choosing a category of templates, the principle of working with the tool for automated selection of design templates is the same: forming a query -selecting data from the database -outputting the result. This diagram shows the steps that are performed before and after the system accesses the database.</p><p>The user, regardless of whether he is authorized or not, must first choose which operation he is going to perform, set the search criteria immediately or view the catalog of template categories.</p><p>According to the selected actions, a request is generated to the system. The intelligent component processes the request and transfers control to another component which forms a request to the database (DB) based on the received parameters.</p><p>DBMS executes the query and returns the result in the form of data which is formatted in a way that is convenient for the end user.</p><p>For authorized users, it is allowed to use the template selection system in accordance with the requirements set for the software. An unauthorized user must specify the analysis criteria.</p><p>The developed software design pattern detector prototype is positioned as a web service, so the main hardware is a web server and a database server.</p><p>The web server contains the following artifacts:</p><p> web-interface which is an ordinary web page responsible for the tool's dialogue with the user;  intelligent component that is responsible for the correct interpretation of requests from the user, issuance and data processing;  database interface forms a request to DBMS based on the criteria obtained from the intelligent component.</p><p>The DBMS artifact is the MongoDB management system. This component is responsible for storing and accessing data.</p><p>An example of the formation of software requirement attributes is presented in Figure <ref type="figure" target="#fig_12">12</ref>. The result returned by the intelligent component for the set of requirements formulated for the project named "Project1" is shown in Figure <ref type="figure" target="#fig_13">13</ref>. As a result, as can be seen from Figure <ref type="figure" target="#fig_9">9</ref>, the distribution of probabilities regarding the optimal choice of software architecture design patterns is obtained.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Conclusion</head><p>The article proposes a method and a tool for detecting and optimally choosing software architecture design patterns depending on the requirements for the system. The requirements for the software system are presented in the form of quality models of the ISO/IEC 25010 standard. The needs of end users are reflected in the structure of the quality in use model, and the requirements for the system architecture are in the form of an external quality model, according to the procedures proposed in <ref type="bibr" target="#b0">[1]</ref>.</p><p>To implement the method of detection and optimal selection of design patterns, a neural network was built and implemented using the C# language, which takes into account the requirements for the system and the meta description of existing design patterns.</p><p>The tool for detection and optimally selecting design patterns of software architecture of computer systems makes it possible to ensure the efficiency of management of the system development process, and due to automation it provides high productivity and accuracy of decision-making regarding the use of reusable components.</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: Conceptual diagram of the design pattern detection process.</figDesc><graphic coords="4,163.80,85.05,267.80,281.10" 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: The structure of the neural network of the requirements model analyzer.</figDesc><graphic coords="5,85.10,305.75,439.50,171.10" 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: Listing of a neural network construction.</figDesc><graphic coords="6,125.15,280.15,345.05,213.30" type="bitmap" /></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: Listing of neural network training.</figDesc><graphic coords="7,109.25,85.00,376.80,156.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Listing of finding patterns using a neural network.</figDesc><graphic coords="7,132.70,322.45,329.90,81.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Listing of analysis of the resulting vector and pattern finding.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Figure 7 :</head><label>7</label><figDesc>Figure 7: Use Case Diagram "Administrator".</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Figure 8</head><label>8</label><figDesc>Figure 8 provides a diagram of the use cases for users of the software system architecture design pattern selection system.</figDesc><graphic coords="8,152.50,353.55,290.30,274.20" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Figure 8 :</head><label>8</label><figDesc>Figure 8: Use case diagram "End user".</figDesc><graphic coords="9,164.60,85.05,266.10,194.70" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_9"><head>Figure 9 :</head><label>9</label><figDesc>Figure 9: Sequence diagram. The sequence diagram shows 4 main components (objects): user, dialog component, intelligent module, DBMS.</figDesc><graphic coords="9,145.00,403.95,305.30,227.50" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_10"><head>Figure 10 :</head><label>10</label><figDesc>Figure 10: Class diagram.</figDesc><graphic coords="10,108.90,296.30,377.55,165.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_11"><head>Figure 11 :</head><label>11</label><figDesc>Figure 11: Activity diagram.</figDesc><graphic coords="11,172.00,85.05,265.60,351.30" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_12"><head>Figure 12 :</head><label>12</label><figDesc>Figure 12: Formation of software requirement attributes.</figDesc><graphic coords="12,125.80,181.95,363.30,203.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_13"><head>Figure 13 :</head><label>13</label><figDesc>Figure 13: The result of choosing the optimal design pattern for the project. Data from the data set provided by the Onlizer company as part of cooperation and conducting joint scientific research were used for experimental research.As a result, as can be seen from Figure9, the distribution of probabilities regarding the optimal choice of software architecture design patterns is obtained.</figDesc><graphic coords="12,118.85,404.20,536.35,301.05" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Rozrobka ta keruvannya vymohamy do prohramnoho zabezpechennya na osnovi modeli yakosti</title>
		<author>
			<persName><forename type="first">O</forename><surname>Kharchenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Yatsyshyn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Visnyk TDTU</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="page" from="201" to="207" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
	<note>Tom</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">The Method of Quality Management Software</title>
		<author>
			<persName><forename type="first">V</forename><surname>Yatsyshyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">А</forename><surname>Kharchenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">І</forename><surname>Galay</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceeding of the VIIth International Conference &quot;Perspective technologies and methods in MEMS design&quot; 11</title>
				<meeting>eeding of the VIIth International Conference &quot;Perspective technologies and methods in MEMS design&quot; 11<address><addrLine>Polyana, Ukraine</addrLine></address></meeting>
		<imprint>
			<publisher>Publishing House Vezha&amp;Co</publisher>
			<date type="published" when="2011-05">May 2011 -. 2011</date>
			<biblScope unit="page" from="228" to="230" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<idno>ISO/IEC 25010:2011</idno>
		<title level="m">Systems and software engineering -Systems and software Quality Requirements and Evaluation (SQuaRE) -System and software quality models</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<idno>ISO/IEC 14598</idno>
		<title level="m">Information Technology -Software product evaluation. Parts 1 to 6: 1999 -2001</title>
				<meeting><address><addrLine>Geneva</addrLine></address></meeting>
		<imprint>
			<date type="published" when="1999">1999-2001</date>
		</imprint>
	</monogr>
	<note>International Organization for Standardization</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Clean Architecture: A Craftsman&apos;s Guide to Software Structure and Design</title>
		<author>
			<persName><forename type="first">R</forename><surname>Martin</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>Pearson</publisher>
			<biblScope unit="page">420</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<ptr target="https://github.com/jasontaylordev/CleanArchitecture" />
		<title level="m">Clean Architecture Solution Template</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Software tool for productivity metrics measure of relational database management system</title>
		<author>
			<persName><forename type="first">V</forename><surname>Yatsyshyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Pastukh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Zharovskyi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Shabliy</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Mathematical Modeling</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">48</biblScope>
			<biblScope unit="page" from="7" to="17" />
			<date type="published" when="2023">2023</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Development of software for neuromarketing based on artificial intelligence and data science using high-performance computing and parallel programming technologies</title>
		<author>
			<persName><forename type="first">O</forename><surname>Pastukh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Yatsyshyn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Scientific Journal of TNTU. Tern.: TNTU</title>
		<imprint>
			<biblScope unit="volume">113</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="143" to="149" />
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

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