<?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">Traffic Flows System Development for Smart City</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Iryna</forename><surname>Krislata</surname></persName>
							<email>irynakrislata@gmail.com1</email>
						</author>
						<author>
							<persName><forename type="first">Anatoliy</forename><surname>Katrenko</surname></persName>
							<email>anatolii.v.katrenko@lpnu.ua2</email>
						</author>
						<author>
							<affiliation key="aff0">
								<address>
									<addrLine>]2, Vasyl Lytvyn, -0180]3, Victoria Vysotska [0000-0001-6417-3689]4, Burov</addrLine>
									<postCode>0000-0001-7142-6576, 0000-0002-9676, 0000-0001-6124-3995]</postCode>
									<settlement>Yevhen</settlement>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff1">
								<orgName type="institution">Lviv Polytechnic National University</orgName>
								<address>
									<settlement>Lviv</settlement>
									<country key="UA">Ukraine</country>
								</address>
							</affiliation>
						</author>
						<author>
							<affiliation key="aff2">
								<orgName type="department">Department of fixing violations Traffic Management Department Public Transport Management Department</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Traffic Flows System Development for Smart City</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">EBB87365468A53502EFA18C0E07EE89F</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T01:29+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>Traffic flow management</term>
					<term>information system</term>
					<term>information technologies</term>
					<term>management system</term>
					<term>transport network</term>
					<term>vehicles</term>
					<term>road quality</term>
					<term>traffic congestion</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The work is devoted to the development of an information system, where the movement of vehicles is a central element. Another key element is research and development of theoretical and methodological foundations and mathematical tools for performing all kinds of tasks for managing these flows, improving the transport network and maintaining good quality of the roads. To achieve this, the following questions were raised in this document: analysis of existing methods of solving various problems related to the traffic of a large city; development of a formalized approach to solving this class of problems; development of algorithm for optimization of these tasks; implementation of developed algorithms in the complex traffic management program. As a result, specific practical problems regarding managing the traffic flow of a large city were solved, the adequacy of developed models and algorithms was proved, and the usefulness of their use was shown.</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>Transport infrastructure is one of the most important infrastructures that provide the life of cities, villages, regions, regions, and even countries <ref type="bibr" target="#b0">[1]</ref><ref type="bibr" target="#b1">[2]</ref><ref type="bibr" target="#b2">[3]</ref><ref type="bibr" target="#b3">[4]</ref><ref type="bibr" target="#b4">[5]</ref><ref type="bibr" target="#b5">[6]</ref><ref type="bibr" target="#b6">[7]</ref>. According to the definition, it is a collection of certain objects (enterprises) involved in the construction, repairing, as well as the maintenance of the roads, bridges etc. The transport infrastructure ensures the availability and preservation of transport routes in proper condition. It includes railways, railway stations and stations, highways, public transport, streets, airlines and airports, river routes and ports, seaports, bus stations, tram lines, etc. In recent years, many major cities have completely exhausted the potential of transport networks development. That is why optimal planning of transport  The main goal of the development of the main goal is the analysis of the external and internal environment of the system, assessment of its resources and capabilities. At the second stage we will make a decomposition of the main goal of the system for the purpose of the second level (aspects of the general purpose). Formation of the objectives of the second level (aspects) in the directions is in line with the main strategic goal, which should guarantee its implementation. Such aspects in this case are: analysis of primary information and vehicle management, analysis and efficient management of the transport network, analysis of constraints and solving problems. Aspects of general purpose characterize the specialized directions of activity and functioning of the system. Each direction represents a clearly defined sphere of specialized activity of the system. In the third stage, we decompose the objectives of the second level (aspects of the general purpose) in accordance with the specific tasks (subaspects of the general purpose). For the first aspect, when decomposing, there are new exits: data collection and monitoring of quantitative and qualitative transport composition, data collection and optimization of public transport; for the second -analysis and optimization of traffic lights, data collection on the condition of highway in different weather conditions, monitoring of the state of roads; and accordingly, for the third, data collection and raising financial capital, an overview of reporting and solving the problem of corruption, receiving information from the police about the violation and minimizing it. At the next stage, the decompositions describe the "leaves" of the tree, which are the criteria for achieving the goal. As shown in Fig. <ref type="figure" target="#fig_0">1</ref> the following criteria for achieving the main goal of the information system of traffic flows of a large city in accordance with the sub-aspects of the general goal are: the number of cameras that meet the requirements, optimization of the interval of public transport, efficiency of informing about the arrival of transport, the effective operation of traffic lights, the speed of calling vehicles for cleaning roads , effective schedules of carrying out of repair works, optimization of tariffs for transport services, efficiency of informing drivers about traffic jams, optimal routes of traffic collapse, optimal number of police, maximization of penalties. The interaction of the system with elements of the environment with sufficient completeness will be reflected within the notation of the DFD (flowcharts) using the context diagram, and the detailing -by constructing the DFD hierarchy of the following levels. Data Flow Diagrams (DFDs) depict the flow of information for any process or system. They use symbols such as rectangles, circles and arrows, as well as short text labels to show incoming and outgoing data, storage points and routes (information transfer) between each destination <ref type="bibr" target="#b8">[9]</ref>. These charts can be used to analyze an existing system or create a new one.</p><p>The data flowchart may become more detailed by levels. Levels DFD are numbered 0, 1 or 2, and sometimes you can go to level 3 or go beyond its limits. The required level of detail depends on the amount of what they are trying to achieve. The level of DFD 0, also called the context diagram, is depicted in Fig. <ref type="figure" target="#fig_1">2</ref>. This is a basic overview of the entire traffic information system of a large city to be analyzed and modeled. It is designed for clarity and in order to display the system as a single high-level system, with its interconnections and external objects. The context diagram is easily understood by a wide audience, including stakeholders, business analysts and developers. This context diagram depicts only one main process "to en-sure the management of traffic flows (cities)" and the following external entities: "traffic flows", "elements of the transport network", "the department of fixing violations", "the department of control of traffic jams," the department of public management transport "," traffic lights management department "and" road control department ", which will provide stream management. Level DFD 1, shown in Fig. <ref type="figure">3</ref>, provides a more detailed breakdown of parts of the context chart. Here are the main functions performed by the system, by separating the system of high level on its subprocesses.  From this diagram it is clear that at this stage, according to the standard, there are no new entities, but only duplicates those that were on the context. In addition, there are new processes (subprocesses) and data warehouses.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Funds</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Address</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Cars</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Інформація про особу Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Accident information Traffic violation information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Routes Personnel Message</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Address</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Scoreboard information</head><note type="other">Management</note><p>The sub-processes in this chart are "collect information about vehicles", "fix violations", "solve problems with congestion", "optimize the traffic of public transport", "ensure the proper use of traffic lights", "monitor the state of roads", "conduct road traffic control "and" provide payment for transport services ". In addition, there are 7 data warehouses on the chart: "vehicle information", "transport service information", "violation reporting", "traffic lights information", "table information and characteristics", "maps" and "reporting on conducting repair works". At this stage, the diagram describes in more detail the essence of the system. However, in my opinion, it can be decomposed more in order to describe in detail some of the subprocesses. As a result we get DFD 2 level. DFD level 2 are divides into more parts the 1st level graph. In order to achieve the required level of detail about the functioning of the system, a more detailed description of the system will be required. To begin with, consider the process of "collecting information about vehicles" (Fig. <ref type="figure">4</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Install surveillance cameras</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Identify locations with no surveillance cameras</head><p>Information about traffic flows Address Video </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Photo</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 4. Detailing the process of collecting information on vehicles</head><p>As you can see, the diagram shows new processes: "to determine places with no observation cameras", "to install surveillance cameras", "to recognize machine numbers and other characteristics". The results of these processes will be recorded in the data store "vehicle information", which will be used in the future by the system in the execution of other processes.</p><p>Next we decompose the process of "fixing violations" (Fig. <ref type="figure">5</ref>). We see that in this second level diagram there are new processes: "fixing traffic accidents", "fixing traffic offenses", "delaying the offender", "imposing a punishment", "calling police officers", "calling for ambulance if necessary". The external essence of the "Department for fixing violations" will send information and collect all the results.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Report traffic violations Fix an accident Accident information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Traffic violation information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2.1">2.2.2</head><p>Detain the offender</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.2.5</head><p>To impose a measure of punishment</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.2.6</head><p>Call the police</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.2.3</head><p>Call an ambulance if necessary</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.2.4</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Management</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Person information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Person information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Person information</head><p>Data on the nature of the violation Challenge Challenge Personnel Personnel Fig. <ref type="figure">5</ref>. Detailing the process of fixing violations And all recorded violations and road accidents with information about place, time, date, person and the actual violation and punishment for it will be stored in the data warehouse "reporting of violations", which the police will also use to review the frequency of relevant events committed by that or another person to determine the penalties for this person. This data storage is depicted on a higher level chart. The process of solving the problem with congestion is extremely relevant and at the same time quite complicated. It includes several subprocesses with much entities and data storage. How this issue will be solved by the information system is shown below (Fig. <ref type="figure">6</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Send police officers</head><p>Analyze the density of congestion </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Message</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Routes</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>GPS information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 6. Detailing the process of solving problem with congestion</head><p>When the cameras observe an excessive accumulation of vehicles on one or another section of the transport network, a signal with this information is sent to the traffic control unit. Accordingly, the unit assigns the task of solving this problem to the following processes: "to send police officers", "analyze the density of the trick," "to consider possible options for a detour", which are taken from the data warehouse "maps", "send directions to GPS", "send message on the radio station", "adjust the pace of work of the traffic light "and, of course, "solve the problems with traffic jams" When fixing the camera of the observation of excessive replenishment of vehicles in one or another department of the transport network, signal with the information is sent to the department of traffic jam management. As a result, he refuses to solve the problem of the following processes: "breaking the bottlenecks", "analyze the integrity", "expand the possible options for exchange", which are displayed with the data warehouses "maps", "dispatch sending to GPS", "sending messages". message on the radio station "," prepare the pace of work of the traffic lights ", usually" solve problems with the traffic jam". If we describe in detail the process of optimizing public transport, then several new processes will appear in the diagram (Fig. <ref type="figure">7</ref>). Among them: "analyze the population at stops," "determine the required amount of each transport," "determine the required frequency of vehicles," set the scoreboard, "send data with the arrival time on the scoreboard" and "calculate the failure." In my opin-ion, with the help of these data, the traffic of taxis, trams, trolleybuses and other vehicles people will be much more satisfied, since all possible factors for comfortable movement of people and informed expectations will be taken into account. Edited data</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Scoreboard information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 7. Detailing the process of optimization of public transport</head><p>Next we consider the process of "ensuring the proper use of traffic lights", or rather its decomposition (Fig. <ref type="figure">8</ref>). </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Information about traffic lights</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Management</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>High density Low density</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Management</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>New traffic light</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Disconnect information</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 8. Decomposition of the process of using traffic lights</head><p>Here the managing link is the external essence of the "traffic lights management department". The diagram also shows the processes "analyze the density of the road at a certain hour of the day", as a result of which the following processes will be performed depending on the results: "turn off the traffic light", "put an additional traffic light" or "adjust the light speed". All results of the above actions are stored in the data store "information about traffic lights", which is also used to read current data of a given traffic light and further work with it. Fig. <ref type="figure" target="#fig_4">9</ref> depicts the process of "monitoring the state of roads". This chart is managed by the "road control department", as it provides information about a specific address and requests the processes of "constructing a new road" and "checking the state of the roads." The funds for such actions are partly received as a result of the process of "ensuring payment for transport services". The results of the construction are recorded in the already mentioned card data repository. After checking, if necessary, there is a process of "drawing up a schedule of repairs" and "carrying out repairs", the results of which are reduced to "reporting on the repair work." This data warehouse is also analyzed in the process of checking the state of roads for a decision on the need for the start of repair. The next process, which we will decompose, is "to provide payment for transport services" (Fig. <ref type="figure" target="#fig_0">10</ref>).  To raise funds</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Road status information</head><note type="other">Address</note></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>2.8.3</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Funds</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 10. Detailing the process of ensuring payment for transport services</head><p>The processes that perform the function of ensuring payment for transport services: "to gather information about transport services", "to establish optimal tariffs", "to raise funds". Funds are collected from drivers of vehicles, some of which are transported for the construction and reconstruction of roads. All information on tariffs and collected funds is stored in the "transport service information" repository. The final process that we will decompose is to "control the weather on the highways" (Fig. <ref type="figure" target="#fig_0">11</ref>). The external essence of this process is the "Department of Road Weather Monitoring". The processes in this chart are "to analyze weather conditions" and "send cars to clear roads". In general, the system can be further elaborated to 3.4 and further levels, but going beyond Level 3 can lead to significant complexities as the model may become less comparable and effective. Therefore, at this stage, we will stop.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Send road cleaning machines</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Analyze weather conditions</head><note type="other">Address Challenge Cars</note><p>According to the definition, description and rules, the DFD diagram of the information system of traffic flows of a large city was built, which is a generalized intellectual transport system. Let's take a closer look at what it is. Intelligent Transport Systems (ITS) are advanced applications that, without the intelligence as such, are aimed at providing innovative services related to different modes of transport and traffic management and allow different users to be more informed and make transport networks safer, coordinated and "smarter" <ref type="bibr" target="#b9">[10]</ref>. Intelligent transport systems differ in applied technology, from basic control systems such as automotive navigation; traffic light control systems; container management systems; automatic speed detection for monitoring applications such as video surveillance systems; and more advanced applications that integrate real-time data and feedback systems from a number of other sources such as parking systems and other information systems; weather information, etc. In addition, prognostic methods are developed to make modern simulations progress in comparison with historical data.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Building a Hierarchy of Tasks</head><p>This information system consists of many tasks that can be represented hierarchically (Fig. <ref type="figure" target="#fig_1">12</ref>). From the figure, we see that the main task, located at the top of the hierarchy, is "the task of regulating traffic flows." It breaks up into 8 sub-tasks, which, in turn, also have several tasks at their lower levels. Including:</p><p>1) "task of collecting information on vehicles", which includes the "task of installing surveillance cameras" and "the task of recognizing the machine number";</p><p>2) "task of fixing violations", which is divided into 2 subtasks -"task of fixing violations of traffic rules" and "task of fixing an accident". For them, the lowest level of the hierarchy will be "the task of delinquent offender";</p><p>3) the "problem of solving the problem with congestion", which includes the "task of collecting information about the jam" and "the problem of analysis of the density of the flood", which also branch out to "the problem of considering possible alternatives to detour", "the task of adjusting the pace of the traffic light "And" the task of calling police officers "; 4) "task of optimization of public transport", which includes the "task of setting the table" and "task of determining the frequency of vehicles." The latter includes the "task of sending data to the scoreboard" and "task of calculating failures"; 5) "the task of ensuring the proper use of traffic lights", which includes the "problem of analyzing the density of the road at a certain hour of the day" and "the task of collecting information about current traffic lights", which also branch out to the "task of turning off the traffic light", "the task of installing additional traffic lights" and "the task of setting the pace of change of light"; 6) "task of collecting fees for transport services", which include "the task of collecting information about transport services" and "the task of optimizing tariffs". They in turn, at the lower level of the hierarchy, have a "task of raising funds"; 7) "task of monitoring the state of roads", which is divided into "the task of constructing a new road" and "the task of checking the state of roads". The latter also has a lower level of "the task of scheduling repair work" and "the task of repair"; 8) "task of monitoring the weather on highways" includes the "task of collecting information on the availability of appropriate equipment" and "the task of weather analysis", which in turn include the "task of sending cars to clear roads".  </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Description of the Created Software</head><p>Let's launch the program and select the required characteristics. We select the number of cars and press the start button. Let's see how cars ride without starting a congestion drive algorithm (Fig. <ref type="figure" target="#fig_0">13</ref>). Next, we will switch to the mode of using the required algorithm (Fig. <ref type="figure" target="#fig_0">14</ref>). We see that the paths of some cars differ considerably in these modes, and in the mode with the algorithm traffic is not formed. Now let's consider and compare the timelines of unmanned vehicle fares with initial data and algorithm (Fig. <ref type="figure" target="#fig_0">15</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 13. The movement of cars with the initial data</head><p>We see that taking into account the algorithm used, the time of travel of some cars has significantly decreased, and for the rest of the cars remained almost unchanged (difference to 0.5 s). So, the program is workable and the goal is achieved. For this pur-pose, the most active part of it was chosen, which creates the greatest discomfort for the participants of the traffic movement. In particular, a program implementing one of the methods for solving congestion problems was developed. Motivation of the driver's actions determines the place, time and way of movement. Each driver individually decides whether he needs to go this or that way, or whether he relies on minimizing fuel costs or time. Therefore, to avoid the influence of the human factor on the movement of vehicles, this program works with unmanned cars. When planning a route to your destination, an unmanned car determines the shortest path. However, with obstacles such as traffic jams, this path may cause significant delays. The program is also designed to schedule commuting trains, minimizing the time for which the vehicle will arrive at destination. The program works with Unity, where we set the number of vehicles that will move, and the locations of their movement and destination will be read from the statistics stored in the database of the traffic information system of the big city. Then the cars are moving according to the traffic rules, and taking into account the traffic lights. When detecting a significant number of vehicles at an intersection (intersection), the car according to the Dijkstra algorithm is looking for a shorter route, bypassing the overloaded road. Vehicle movement stops when the planned place is reached. The program is called by executing executable file (with extension .exe). The input data is the number of cars that will move on the map (the starting points and destinations of each of the cars are indicated in Unity) and the choice of motion algorithm or not. The starting point is the actual traffic of cars on the map, which shows the fastest route itself.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusion</head><p>The work of predecessors was highlighted and issues remained unpublished and those that require further research. Then a systematic analysis of the functioning of the system was performed, the purpose of the system was specified by constructing a goal tree, the main variants of its achievement were given by decomposition to aspects, sub-aspects and criteria for evaluating the quality of implementation. Next, a hierarchy of data flow diagrams was constructed, which, with a sufficient degree of detail, describes the processes of the functioning of the IP, the links between them and the information necessary for the successful operation in the context of the selected type of IP. On the basis of DFD a task hierarchy is constructed taking into account the sequence of their execution. The main characteristics, methods of problem solving, methods of presentation of knowledge, software, system and auxiliaries, which are used in work for construction of mechanisms of choice of the optimal route of a detour passage, are given. The description and analysis of methods for solving the problem with congestion is presented, as well as for the implementation of the C # language and the Unity tool for developing a graphical interface for working with the map and unmanned cars. The composition, structure, content and functions of the developed software and the processes of their joint operation were described. The reference example confirms the working capacity of the development, and the results of the system's operation correspond to the task. As a result of this work an information system was developed, the main element of which is the traffic flows of a large city. The theoretical and methodological provisions and mathematical tools for performing various types of tasks for managing these flows and improving the transport network and supporting the state of roads were also researched and developed.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. Goal tree of the information system of traffic flows of a large city 2.3. Roads monitoring 2.3.1. Effective schedules of repair work 3.1. Data collection and raising financial capital 3.1.1. Optimization of tariffs for transport services 3.2. Reporting overview and troubleshooting 3.2.1. The promptness of informing drivers about traffic jams 3.2.2. Optimal congestion routes 3.3. Obtaining and minimizing information from police about violations 3.3.1. The optimal number of police 3.3.2. Maximizing sentencingThe main goal of the development of the main goal is the analysis of the external and internal environment of the system, assessment of its resources and capabilities. At the second stage we will make a decomposition of the main goal of the system for the purpose of the second level (aspects of the general purpose). Formation of the objectives of the second level (aspects) in the directions is in line with the main strategic goal, which should guarantee its implementation. Such aspects in this case are: analysis of primary information and vehicle management, analysis and efficient management of the transport network, analysis of constraints and solving problems. Aspects of general purpose characterize the specialized directions of activity and functioning of the system. Each direction represents a clearly defined sphere of specialized activity of the system. In the third stage, we decompose the objectives of the second level (aspects of the general purpose) in accordance with the specific tasks (subaspects of the general purpose). For the first aspect, when decomposing, there are new exits: data collection and monitoring of quantitative and qualitative transport composition, data collection and optimization of public transport; for the second -analysis and optimization of traffic lights, data collection on the condition of highway in different weather conditions, monitoring of the state of roads; and accordingly, for the</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Context diagram of the information system of traffic flows of a large city</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 3 . 1 -</head><label>31</label><figDesc>Fig. 3. Flowchart of the data of the first level Databases: 1 -Vehicle information; 2 -Reporting of violations; 3 -Traffic light information; 4 -Report on repair work; 5 -Cards; 6 -Transport service information; 7 -Information about the characteristics of the scoreboard. Processes: 1.1 -Collect vehicle information from surveillance cameras; 1.2 -Fix violations; 1.3 -Solve congestion issues; 1.4 -Ensure proper use of traffic lights; 1.5 -Optimize public transport; 1.6 -Check the condition of the roads; 1.7 -Check the weather on the roads; 1.8 -Provide payment for transport services.From this diagram it is clear that at this stage, according to the standard, there are no new entities, but only duplicates those that were on the context. In addition, there are new processes (subprocesses) and data warehouses.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 9 .</head><label>9</label><figDesc>Fig. 9. Detailing the process of monitoring the state of roads</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>1 Fig. 11 .</head><label>111</label><figDesc>Fig. 11. Detailing the process of monitoring the weather on the highways</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>Fig. 12 . 1 -</head><label>121</label><figDesc>Fig. 12. Hierarchy of tasks of the information system of transport flows of a large city Tasks: 1 -Management of city traffic flows; 1.1 -Information about vehicles; 1.1.1 -Installation of data collection from chamber storage; 1.1.2 -Machine number recognition; 1.2 -Commit message; 1.2.1 -Fix traffic messages; 1.2.2 -Fixing of an accident; 1.3 -Traffic congestion management; 1.3.1 -Collection of congestion information; 1.3.2 -A real congestion; 1.4 -Optimization of public transport traffic; 1.4.1 -Propose machine speeds; 1.4.2 -Installation of a simple scoreboard; 1.5 -Specially protected light of traffic lights; 1.5.1 -Analysis of the reliability of expensive at a certain hour of acquisition; 1.5.2 -Collection of information about current traffic lights; 1.6 -Complete set of payment for transport services; 1.6.1 -Information on transport services; 1.6.2 -Tariff optimization; 1.7 -Existing roads are observed;</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Fig. 14 .Fig. 15 .</head><label>1415</label><figDesc>Fig. 14. Movement of cars according to the algorithm</figDesc><graphic coords="13,169.45,285.85,256.20,143.15" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="1,0.00,190.95,595.32,460.02" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Dynamic urban surveillance video stream processing using fog computing</title>
		<author>
			<persName><forename type="first">N</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>You</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Ling</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Liang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Zimmermann</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE second international conference on multimedia big data (BigMM)</title>
				<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="105" to="112" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<author>
			<persName><forename type="first">G</forename><surname>Ermacora</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Toma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Bona</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Chiaberge</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Silvagni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Gaspardone</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Antonini</surname></persName>
		</author>
		<title level="m">A cloud robotics architecture for an emergency management and monitoring service in a smart city environment</title>
				<meeting><address><addrLine>Turin, Italy</addrLine></address></meeting>
		<imprint>
			<publisher>Tech. Rep</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Monitoring urban structure types as spatial indicators with CIR aerial photographs for a more effective urban environmental management</title>
		<author>
			<persName><forename type="first">E</forename><surname>Banzhaf</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Hofer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Journal of Selected Topics in Applied Earth Observations and Remote Sensing</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="129" to="138" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<author>
			<persName><forename type="middle">Henry</forename><surname>Dr</surname></persName>
		</author>
		<author>
			<persName><surname>Lieu</surname></persName>
		</author>
		<title level="m">Transportation Research Board (TRB) Special Report 165</title>
				<imprint>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
	<note>Traffic Flow Theory</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Hoogendoorn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Knoop</surname></persName>
		</author>
		<title level="m">Traffic flow theory and modeling</title>
				<imprint>
			<publisher>Edward Eldar Publishing</publisher>
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Decoding the species composition of forest plantations according to satellite imagery Sentinel-2</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">I</forename><surname>Georgian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">V</forename><surname>Myroniuk</surname></persName>
		</author>
		<ptr target="http://nbuv.gov.ua/UJRN/licgoc_2017_11_6" />
	</analytic>
	<monogr>
		<title level="m">Forestry and landscape gardening</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">The overview of green building sector in Slovakia</title>
		<author>
			<persName><forename type="first">J</forename><surname>Golej</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Adamuscin</surname></persName>
		</author>
		<idno type="DOI">10.4108/eai.13-7-2018.158874</idno>
		<ptr target="https://eudl.eu/pdf/10.4108/eai.13-7-2018.158874" />
	</analytic>
	<monogr>
		<title level="j">EAI Endorsed Transactions on Energy Web</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">23</biblScope>
			<biblScope unit="page">e8</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Topographic structure from motion: a new development in photogrammetric measurement</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Fonstad</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">T</forename><surname>Dietrich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><forename type="middle">C</forename><surname>Courville</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">L</forename><surname>Jensen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">E</forename><surname>Carbonneau</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Earth Surface Processes and Landforms</title>
		<imprint>
			<biblScope unit="volume">38</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="421" to="430" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<author>
			<persName><forename type="first">V</forename><surname>Hahanov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Gharibi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Litvinova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Chumachenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Ziarmand</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><forename type="middle">, .</forename><surname>Englesi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Khakhanova</surname></persName>
		</author>
		<title level="m">Cloud-Driven Traffic Monitoring and Control Based on Smart Virtual Infrastructure</title>
				<imprint>
			<date type="published" when="2017">2017. 0092. 2017</date>
			<biblScope unit="page">1</biblScope>
		</imprint>
	</monogr>
	<note type="report_type">SAE Technical Paper</note>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Mobile Post-Emergency Monitoring System for Nuclear Power Plants</title>
		<author>
			<persName><forename type="first">A</forename><surname>Sachenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Kochan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Kharchenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Roth</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Yatskiv</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">, .</forename><surname>Chernyshov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Fesenko</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ICTERI</title>
		<imprint>
			<biblScope unit="page" from="384" to="398" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<title level="m" type="main">Autonomous Vehicles for Safer Driving</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">K</forename><surname>Jurgen</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2013">2013</date>
			<publisher>SAE International</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<ptr target="https://ukurier.gov.ua/uk/news/skanuvannya-derev-dopomozhe-yih-zvazhuvati-ta-viya/" />
		<title level="m">Scanning trees will help them weigh and detect carbon content</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<ptr target="http://texty.org.ua/pg/blog/nartext/read/76201/Jak_big_data_i_drony_mozhut_vratuvaty" />
		<title level="m">How big data and drones can save Ukrainian forests</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Smart urban surveillance using fog computing</title>
		<author>
			<persName><forename type="first">N</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Chen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Song</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">T</forename><surname>Huang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Ye</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE/ACM Symposium on Edge Computing (SEC)</title>
				<imprint>
			<date type="published" when="2016">2016. 2016</date>
			<biblScope unit="page" from="95" to="96" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">An Application Development for Recognizing of View in Order to Control the Mouse Pointer</title>
		<author>
			<persName><forename type="first">P</forename><surname>Zdebskyi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vysotska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Demchuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Krylyshyn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">2386</biblScope>
			<biblScope unit="page" from="55" to="74" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Intelligent system of a smart house</title>
		<author>
			<persName><forename type="first">V</forename><surname>Lytvyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vysotska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Mykhailyshyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Kohut</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3rd International Conference on Advanced Information and Communications Technologies</title>
				<imprint>
			<publisher>AICT</publisher>
			<date type="published" when="2019">2019</date>
			<biblScope unit="page" from="282" to="287" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Preface: Modern Machine Learning Technologies and Data Science (MoMLeT&amp;DS</title>
		<author>
			<persName><forename type="first">M</forename><surname>Emmerich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Lytvyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Yevseyeva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">B</forename><surname>Fernandes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Dosyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vysotska</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="volume">2386</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Preface: Computational Linguistics and Intelligent Systems (COLINS</title>
		<author>
			<persName><forename type="first">V</forename><surname>Lytvyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Sharonova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hamon</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Cherednichenko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Grabar</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Kowalska-Styczen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vysotska</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="volume">2362</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<analytic>
		<title level="a" type="main">Development of mobile application for choreographic productions creation and visualization</title>
		<author>
			<persName><forename type="first">L</forename><surname>Chyrun</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Gozhyj</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Stefanchuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Oborska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Lozynska</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Mykich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Basyuk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Rzheuskyi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CEUR Workshop Proceedings</title>
				<imprint>
			<date type="published" when="2019">2019</date>
			<biblScope unit="volume">2386</biblScope>
			<biblScope unit="page" from="340" to="358" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<analytic>
		<title level="a" type="main">Information Encryption Based on the Synthesis of a Neural Network and AES Algorithm</title>
		<author>
			<persName><forename type="first">V</forename><surname>Lytvyn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Peleshchak</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vysotska</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">3rd International Conference on Advanced Information and Communications Technologies</title>
				<imprint>
			<date type="published" when="2019">2019. 2019</date>
			<biblScope unit="page" from="447" to="450" />
		</imprint>
	</monogr>
</biblStruct>

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