-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
49 lines (38 loc) · 2.13 KB
/
index.html
File metadata and controls
49 lines (38 loc) · 2.13 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
<!DOCTYPE html>
<html>
<head>
<style>
p.abstractClass{
margin: 2cm 4cm 1cm 4cm;
}
</style>
<title>Reducing Tactic Latency Uncertainty for Self-Adaptive Systems</title>
</head>
<body bgcolor=#fdf7ef>
<h1 align="center" style="font-family:Arial">Reducing Tactic Latency Uncertainty for Self-Adaptive Systems</h1>
<br>
<br>
<br>
<br>
<p class="abstractClass"style="font-size:20px" align="justify">
Tactic latency is the time between when a tactic is started and when its effect is produced. Fortunately, many self-adaptive techniques are beginning to account for latency in their decision-making process. These adaptation processes consider tactic latency to be a static, human defined value. Unfortunately, many tactics have a volatile latency value; one that may be constantly changing. In this work, we present a Latency Volatility Aware (LVA) adaptation process. We achieved positive results evaluating LVA in several environments against a baseline process that only considers static latency values. We found that accounting for latency volatility can have a positive impact on the adaptation decision process, specifically by making the system more resilient to large variations in tactic latency. To support the evaluation of LVA, we created <i>TacSim</i>, a tool which enables us to quickly simulate multiple adaptation decisions while accounting for uncertainty in tactic latency. This paper advances the self-adaptive decision-making process by reducing tactic latency uncertainty. Our discoveries can serve as a foundation for future work in reducing uncertainty through understanding and accounting for tactic latency volatility.
</p>
<!--
<br>
<br>
<h3 align="center"> Data 1 goes here</h3>
<h3 align="center"> Data 2 goes here</h3>
<h3 align="center"> Data 3 goes here</h3>
<h3 align="center"> Data 4 goes here</h3>
<br>
<br>
<br>
-->
<div style="text-align: center">
<footer>
<a href="https://www.se.rit.edu" target="_blank" ><img src="seLogo.png" width=40 height=40 align="center"></a>
</div>
<p align="center">© Department of Software Engineering. <b>RIT</b></p>
</footer>
</body>
</html>