-
Notifications
You must be signed in to change notification settings - Fork 1
/
cfp.html
147 lines (140 loc) · 8.94 KB
/
cfp.html
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
<!DOCTYPE html>
<!--
Template Name: Sparked
Author: <a href="http://www.os-templates.com/">OS Templates</a>
Author URI: http://www.os-templates.com/
Licence: Free to use under our free template licence terms
Licence URI: http://www.os-templates.com/template-terms
-->
<html>
<head>
<title>WASPI'18 | Call for Papers</title>
<meta charset="utf-8">
<link href="layout/styles/layout.css" rel="stylesheet" type="text/css" media="all">
</head>
<body id="top">
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<div class="wrapper row1">
<nav id="mainav" class="clear">
<!-- ################################################################################################ -->
<ul class="clear">
<li><a href="index.html">Home</a></li>
<li class="active"><a href="cfp.html">CFP</a></li>
<li><a href="dates.html">Important Dates</a></li>
<li><a href="submission.html">Submissions</a></li>
<li><a href="organization.html">Organization</a></li>
</ul>
<!-- ################################################################################################ -->
</nav>
</div>
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<div class="wrapper row2">
<header id="header" class="clear">
<!-- ################################################################################################ -->
<div id="logo">
<h1><a href="index.html">Workshop on<br/>Automated Specification Inference<br/>(WASPI)</a></h1>
<p>Friday, November 9, 2018 - co-located with <a href="https://conf.researchr.org/home/fse-2018">ESEC/FSE 2018</a></p>
</div>
<!-- ################################################################################################ -->
</header>
</div>
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<div class="wrapper row4">
<main id="container" class="clear">
<!-- container body -->
<!-- ########################################################################################## -->
<h1>The 1<sup>st</sup> International Workshop on Automated Specification Inference</h1>
<p>Specifications provide programmers with the confidence their implementations are correct. Formal specifications can even automatically verify the code and specification are consistent, providing additional guarantees. However, most programmers do not write such specifications as it is either too hard, too time consuming, or requires expertise not widely available. Tools and techniques have been developed over time to (semi)automate the generation of such specifications, to varying success.</p>
<p>The International Workshop on Automated Specification Inference (WASPI) provides a venue for researchers and practitioners to come together and discuss the current state of the art of and challenges to specification inference techniques and tools. For example, how do we infer more complex and usable specifications? How do we increase the accuracy of the inference techniques? How do we encourage practitioners to use the inference tools and techniques more than they currently do? The goal of this workshop is to identify the most pressing open problems facing specification inference researchers and provide a solid direction toward solving those problems.</p>
<h2>Important Dates</h2>
<table>
<tr><th style="text-align: right;">Submissions due:</th><td><del>July 27, 2018</del> August 8, 2018</td></tr>
<tr><th style="text-align: right;">Author Notification:</th><td><del>August 24, 2018</del></td></tr>
<tr><th style="text-align: right;">Camera-ready due:</th><td>September 14, 2018</td></tr>
</table>
<h2>Topics</h2>
<p>Topics of interest include, but are not limited to:</p>
<ul>
<li>tools and techniques for automatically inferring:
<ul>
<li>behavioral interface specifications</li>
<li>hoare-style specifications</li>
<li>informal specifications (documentation)</li>
<li>information-flow specifications</li>
<li>model-based specifications</li>
<li>temporal specifications</li>
</ul>
</li>
<li>static specification inference techniques</li>
<li>dynamic specification inference techniques</li>
<li>automatic verification of inferred specifications</li>
<li>mining software repository approaches to inference</li>
<li>machine-learning approaches to inference</li>
<li>inferring specifications from big data</li>
</ul>
<h2>Submission Information</h2>
<p>WASPI 2018 invites novel contributions in the form of either <b>4-page short papers</b> or <b>2-page position papers</b> from both researchers and practitioners. Submissions can be research papers, practice papers, position papers, demo papers, or experience reports. All submissions should describe unpublished work and must have been neither previously accepted for publication nor concurrently submitted for review in another journal, book, conference, or workshop. Submissions are peer-reviewed and accepted papers will appear in the workshop proceedings.</p>
<p>Papers should be submitted electronically at: <a href="https://easychair.org/conferences/?conf=waspi2018">https://easychair.org/conferences/?conf=waspi2018</a></p>
<p>Submissions must follow the <a href="https://2018.fseconference.org/attending/Submission+Policies">ESEC/FSE submission policies</a> and be no more than 2 or 4 pages (including references).</p>
<h2>Program Committee</h2>
<ul>
<li>Mehdi Bagherzadeh, Oakland University</li>
<li>Robert Dyer, Bowling Green State University</li>
<li>Vasant Honavar, Penn. State University</li>
<li>Suresh Jagannathan, Purdue University</li>
<li>Miryung Kim, UCLA</li>
<li>Yu David Liu, SUNY at Binghamton</li>
<li>Santosh Nagarakatte, Rutgers</li>
<li>Hoan Anh Nguyen, Iowa State University</li>
<li>Tien N. Nguyen, University of Texas, Dallas</li>
<li>Hridesh Rajan, Iowa State University</li>
</ul>
<h2>Organizers</h2>
<ul>
<li>Robert Dyer, Bowling Green State University</li>
<li>Vasant Honavar, Penn. State University</li>
<li>Gary T. Leavens, University of Central Florida</li>
<li>Hoan Anh Nguyen, Iowa State University</li>
<li>Tien N. Nguyen, University of Texas, Dallas</li>
<li>Hridesh Rajan, Iowa State University</li>
</ul>
<!-- ########################################################################################## -->
<!-- / container body -->
<div class="clear"></div>
</main>
</div>
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<div class="wrapper row5">
<footer id="footer" class="clear">
<!-- ################################################################################################ -->
<div class="clear">
Contact: <span class="icon-envelope-alt"></span> <script type="text/javascript"><!--
document.write('<a href="mailto:' + (['rdyer', 'bgsu.edu'].join('@'))
+ '">' + (['rdyer', 'bgsu.edu'].join('@')) + '<\/a>');
// --></script>
<ins><noscript><div><code>rdyer (at) bgsu (dot) edu</code></div></noscript></ins>
</div>
<!-- ################################################################################################ -->
</footer>
</div>
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<!-- ################################################################################################ -->
<div class="wrapper row6">
<div id="copyright" class="clear">
<!-- ################################################################################################ -->
<p class="fl_left">Copyright © 2018 - All Rights Reserved</p>
<p class="fl_right">Template by <a target="_blank" href="http://www.os-templates.com/" title="Free Website Templates">OS Templates</a></p>
<!-- ################################################################################################ -->
</div>
</div>
</body>
</html>