<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[JSS Editor’s Selection - Medium]]></title>
        <description><![CDATA[Selected Papers and Other Material from Elsevier’s Journal of Systems and Software - Medium]]></description>
        <link>https://medium.com/jss-editors-selection?source=rss----773a35967154---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>JSS Editor’s Selection - Medium</title>
            <link>https://medium.com/jss-editors-selection?source=rss----773a35967154---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:33:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/jss-editors-selection" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Best Reviewers for 2020]]></title>
            <link>https://medium.com/jss-editors-selection/best-reviewers-for-2020-eea836a9ed83?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/eea836a9ed83</guid>
            <dc:creator><![CDATA[Vadim Zaytsev]]></dc:creator>
            <pubDate>Mon, 08 Mar 2021 13:28:04 GMT</pubDate>
            <atom:updated>2021-03-08T13:28:04.327Z</atom:updated>
            <content:encoded><![CDATA[<h3>Best Reviewers for JSS 2020</h3><p>In the context of a journal, unlike a traditional conference, reviewers contribute <em>substantially</em> to the ultimate quality of papers that are published. Their often copious feedback is taken seriously and addressed. In many ways they become the secret co-authors of these papers and the best reviewers deserve recognition from the community. That is why today, like every year, we celebrate the best reviewers for JSS in the past year. These reviewers have each contributed <strong>at least 8 reviews</strong>, all of high quality, and thus have improved the quality of the papers that you will read and cite in the coming months and years. This is one of our favorite awards, as these selfless contributions represent the heart of our research community.</p><p>The winners for 2020 are:</p><p>😎 <a href="https://dardin88.github.io/"><strong>Dario Di Nucci</strong></a></p><p>Assistant professor at the Jheronimus Academy Data and Engineering Lab of the Jheronimus Academy of Data Science, a collaboration between Tilburg University and Eindhoven Technical University</p><p><a href="https://fpalomba.github.io/?section=1"><strong>Fabio Palomba</strong></a></p><p>Assistant Professor at the Software Engineering (SeSa) Lab of the University of Salerno</p><p>✍️ <a href="https://www.lboro.ac.uk/departments/compsci/staff/academic-teaching/lin-guan/"><strong>Lin Guan</strong></a></p><p>Senior Lecturer in the Department of Computer Science at Loughborough University</p><p>☁️ <a href="http://www.eecs.qmul.ac.uk/~fcuadrado/index.html"><strong>Félix Cuadrado</strong></a></p><p>Senior Lecturer in Networks in the School of Electronic Engineering and Computer Science of Queen Mary University of London</p><p>⏱️ <a href="http://retis.sssup.it/~luca/"><strong>Luca Abeni</strong></a></p><p>Associate Professor at the ReTiS (Real Time Systems) Lab of Scuola Superiore S. Anna, Pisa</p><p>😉 <a href="http://www.mysmu.edu/faculty/lxjiang/"><strong>Lingxiao Jiang</strong></a></p><p>Associate Professor in the School of Computing and Information Systems of Singapore Management University</p><p>💪 <a href="https://mitschi.github.io/"><strong>Christian Macho</strong></a></p><p>Postdoc (tenure track) in the Software Engineering Group (SERG) led by Prof. Martin Pinzger at the University of Klagenfurt.</p><p>😐 <a href="https://baolingfeng.github.io/"><strong>Lingfeng Bao</strong></a></p><p>Lecturer in Zhejiang University</p><p>🍕 <a href="http://pages.di.unipi.it/soldani/"><strong>Jacopo Soldani</strong></a></p><p>Assistant Professor (RTDa) in the Department of Computer Science of the University of Pisa</p><p>Please tweet your congratulations to these deserving reviewers!</p><p>All the best,<br>👹 <a href="http://www.cs.rug.nl/~paris/">Paris Avgeriou</a><br>🤪 <a href="https://davidshepherd.weebly.com/">David C. Shepherd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eea836a9ed83" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/best-reviewers-for-2020-eea836a9ed83">Best Reviewers for 2020</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MIP Finalists for 2020]]></title>
            <link>https://medium.com/jss-editors-selection/mip-finalists-for-2020-b54a2b650301?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/b54a2b650301</guid>
            <dc:creator><![CDATA[Vadim Zaytsev]]></dc:creator>
            <pubDate>Sat, 06 Mar 2021 15:57:12 GMT</pubDate>
            <atom:updated>2021-03-06T16:11:35.041Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to announce that four papers have been selected for our Most Influential Paper Finalist Award. These papers are:</p><p><strong>🐛 A systematic and comprehensive investigation of methods to build and evaluate fault prediction models</strong></p><p>Erik Arisholm, Lionel C. Briand, Eivind B. Johannessen</p><p>(<a href="https://medium.com/jss-papers-of-the-year/about-a-systematic-and-comprehensive-investigation-of-methods-to-build-and-evaluate-fault-364942cb8a35">Blog</a>) (<a href="https://www.sciencedirect.com/science/article/pii/S0164121209002295">Paper</a>) (<a href="https://www.simula.no/sites/default/files/publications/Simula.SE.315.pdf">Green OA</a>)</p><p><strong>👪 A family of code coverage-based heuristics for effective fault localization</strong></p><p>W.Eric Wong, Vidroha Debroy, Byoungju Choi</p><p>(<a href="https://medium.com/jss-papers-of-the-year/a-family-of-code-coverage-based-heuristics-for-effective-fault-localization-373b50a17ed5">Blog</a>) (<a href="https://www.sciencedirect.com/science/article/pii/S0164121209002465">Paper</a>) (<a href="https://personal.utdallas.edu/~ewong/SE6367/01-Project/08-SFL-papers/07-Family-of-Code-Coverage-based.pdf">Green OA</a>)</p><p><strong>🧪 Adaptive Random Testing: The ART of test case diversity</strong></p><p>Tsong Yueh Chen, Fei-Ching Kuo, Robert G. Merkel, T.H.Tse</p><p>(<a href="https://medium.com/jss-papers-of-the-year/diversity-diversity-diversity-e972cec64acd">Blog</a>) (<a href="https://www.sciencedirect.com/science/article/pii/S0164121209000405">Paper</a>) (<a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.150.4003">Green OA</a>)</p><p><strong>🏛️ A comparative study of architecture knowledge management tools</strong></p><p>Antony Tang, Paris Avgeriou, Anton Jansen, Rafael Capilla, Muhammad Ali Babar</p><p>(<a href="https://medium.com/jss-papers-of-the-year/architectural-knowledge-management-tools-7c8fdb3a2c88">Blog</a>) (<a href="https://www.sciencedirect.com/science/article/pii/S0164121209002295">Paper</a>) (<a href="https://ulir.ul.ie/bitstream/handle/10344/2101/2009_Tang.pdf?sequence=2">Green OA</a>)</p><p>In order to determine the <strong>MIP Grand Prize Winner</strong>, we will be taking into account your “claps”. Each author has written a blog post, linked above. If you feel that this paper should be awarded as the Grand Prize Winner, please “<strong><em>clap</em></strong>” for it using Medium’s clap feature. We will be taking these claps into consideration when making the final decision. Hurry, you only have a few weeks before the final decision!</p><p>🏆🏆🏆🗳️🗳️🏆🏆🏆<br><strong>Vote for your favorite!<br></strong>🏆🏆🏆🗳️🗳️🏆🏆🏆</p><p>All the best,<br><a href="https://davidshepherd.weebly.com/">David C. Shepherd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b54a2b650301" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/mip-finalists-for-2020-b54a2b650301">MIP Finalists for 2020</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best Papers JSS 2020]]></title>
            <link>https://medium.com/jss-editors-selection/best-papers-jss-2020-20839e096a2c?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/20839e096a2c</guid>
            <dc:creator><![CDATA[Vadim Zaytsev]]></dc:creator>
            <pubDate>Mon, 01 Mar 2021 15:22:40 GMT</pubDate>
            <atom:updated>2021-03-01T15:22:40.747Z</atom:updated>
            <content:encoded><![CDATA[<p>Each year <a href="https://www.journals.elsevier.com/journal-of-systems-and-software/">JSS</a> receives well over 1000 submissions, and 2020 was no exception. From these submissions we like to, each year, honor a few of the best submissions. In 2020, the papers we would like to honor as our official <strong><em>“Best Paper Award Winners”</em></strong> are:</p><p>🥇 <strong>Are unit and integration test definitions still valid for modern Java projects? An empirical study on open-source projects</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S0164121219301955">https://www.sciencedirect.com/science/article/pii/S0164121219301955</a></blockquote><p>🥇 <strong>CrossRec: Supporting software developers by recommending third-party libraries</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S0164121219302341">https://www.sciencedirect.com/science/article/pii/S0164121219302341</a></blockquote><p>🥇 <strong>Exploring onboarding success, organizational fit, and turnover intention of software professionals</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S016412121930216X">https://www.sciencedirect.com/science/article/pii/S016412121930216X</a></blockquote><p>🥇 <strong>Understanding coordination in global software engineering: A mixed-methods study on the use of meetings and Slack</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S0164121220301564">https://www.sciencedirect.com/science/article/pii/S0164121220301564</a></blockquote><p>🥇 <strong>The long and winding road: MBSE adoption for functional avionics of spacecraft</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S0164121219302274">https://www.sciencedirect.com/science/article/pii/S0164121219302274</a></blockquote><p>From among these excellent papers, which already represent the top five from over one thousand submissions, we would like to further distinguish our two <strong><em>“Diamond Best Paper Awards”</em></strong>. These two papers, listed below, represent some of the best work submitted to JSS in the past year. For anyone looking to submit to JSS, consider looking to these papers as examples!</p><p>🏆🥇 <strong>CrossRec: Supporting software developers by recommending third-party libraries</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S0164121219302341">https://www.sciencedirect.com/science/article/pii/S0164121219302341</a></blockquote><p>🏆🥇 <strong>Exploring onboarding success, organizational fit, and turnover intention of software professionals</strong></p><blockquote><a href="https://www.sciencedirect.com/science/article/pii/S016412121930216X">https://www.sciencedirect.com/science/article/pii/S016412121930216X</a></blockquote><p>Congratulations to the authors on a job well done!</p><p>All the best,<br> <a href="http://www.cs.rug.nl/~paris/">‪Paris Avgeriou‬</a><br> <a href="https://davidshepherd.weebly.com/">David C. Shepherd</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20839e096a2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/best-papers-jss-2020-20839e096a2c">Best Papers JSS 2020</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diversity, Diversity, Diversity:]]></title>
            <link>https://medium.com/jss-editors-selection/diversity-diversity-diversity-ed96828f2aeb?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/ed96828f2aeb</guid>
            <dc:creator><![CDATA[T.H. Tse]]></dc:creator>
            <pubDate>Fri, 26 Feb 2021 11:10:40 GMT</pubDate>
            <atom:updated>2023-02-26T04:06:29.923Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Three Words that Summarize the Impacts of Adaptive Random Testing</strong></h3><figure><img alt="Adaptive Random Testing: The ART of Diversity in Test Cases, Technology, and Applications" src="https://cdn-images-1.medium.com/max/1024/1*MxV4KKeGG426YLjI2ZvUag.jpeg" /></figure><p>When we consider real estate, we know that “There are three things that matter in property: location, location, location” — a statement attributed to Lord Harold Samuel in 1944.</p><p>The article titled “Adaptive random testing: The ART of test case diversity” by T.Y. Chen, F.-C. Kuo, R.G. Merkel, and T.H. Tse was published in <em>Journal of Systems and Software</em> in 2010. We would like to mimic Lord Samuel and summarize the impacts and influences of our paper in three words: “diversity, diversity, diversity”. Intuitively speaking, the most effective way to reveal software failures is through the design of diversified test cases, because programmers may make all kinds of mistakes.</p><p>On the one hand, the impacts of the ART 2010 paper are at the fundamental level. It has enhanced the foundations of software testing, and opened up new research directions. On the other hand, the 2010 paper has also strongly influenced researchers to work on new ART algorithms, and motivated practitioners to apply ART to real-life software testing. These impacts have become apparent in the decade following the publication of the ART 2010 paper, as illustrated in this blog entry.</p><h3><strong>1. Adaptive Random Testing: The ART of Diversity in Test Cases</strong></h3><p>Random testing (RT) has been recognized as important in software quality assurance. It attempts to exercise a diversified choice of test cases through random selection. However, it has been criticized for insufficiently effective as it does not make use of any available information to guide the selection of test cases. Adaptive random testing (ART) was proposed by T.Y. Chen in the late 1990s to enhance random diversification of test cases by algorithmically spreading them more evenly.</p><p>The ART 2010 paper published in <em>Journal of Systems and Software</em> was a reflection on adaptive random testing after a decade of its inception. The article discussed the importance of test case diversity, justified by research results demonstrating that the simple notion of even spreading across the input domain can significantly enhance failure detection capability in software testing.</p><p>The concept of “even spreading across the input domain” is easily understood by any person, but is difficult to describe precisely. The difficulty lies in the fact that there are many perspectives to achieve such a phenomenon. Hence, numerous ART algorithms have been developed from various approaches or intuitions. For instance, the first and most popular ART algorithm, FSCS-ART, is based on the approach to choosing the farthest among a set of potential candidates as the next test case in order to achieve this phenomenon.</p><p>Thus, adaptive random testing has evolved into a large family of enhanced random testing methods built on the very simple notion of diversity and even spreading. This notion leverages on the phenomenon that neighboring inputs are more likely to behave similarly, because most programs mimic our daily lives, which are rarely stochastic.</p><h3><strong>2. Adaptive Random Testing: The ART of Diversity in Techniques</strong></h3><figure><img alt="Histogram showing the cumulative no. of papers on ART techniques and applications since 2010" src="https://cdn-images-1.medium.com/max/1024/1*trf_rIqYWM4TizxpP_Hzgw.jpeg" /><figcaption>Cumulative No. of Papers on ART Techniques and Applications since 2010</figcaption></figure><p>Recognizing the limitations in efficiency of the initial techniques, numerous papers have been published since 2010, proposing improved ART algorithms. Some notable examples are ant colony optimization [4], ART by bisection [1], ART by exclusion through test profile [15], ART4SQLi [25], ARTsum [3], category selection-based ART [27], clustering [23], code coverage [7], divide and conquer [9], distance-aware forgetting strategy [17], dynamic partitioning [10], KD-ART [22], KDFC-ART [18], OMISS-ART [5], randomized quasi-random testing [14], and static mirror adaptive random testing [21]. For instance, ART by exclusion [15] is based on the concept of predefining a criterion and taking the first candidate that satisfies this criterion as the next test case. The ART algorithms by partitioning [10] are sparked by the intuition that the next test case should be selected from a partition without test cases.</p><p>In particular, ART by bisection [1] and RBCVT-Fast using clustering by centroidal Voronoi tessellations [23] are linear-time algorithms for numeric programs. ARTsum [3] and category selection-based ART [26] are linear-time algorithms for nonnumeric programs. Two independent projects are currently working on linear-time algorithms for object-oriented programs.</p><p>Different ART methodologies have different favorable and unfavorable testing scenarios. Given the large family of techniques, the good news is that you can choose a cost-effective ART algorithm for the particular program under test. The bad news is that there is no free lunch — you need to understand ART techniques as well as the basic characteristics of the program under test before you can select the most appropriate one.</p><p>In addition to motivating the development of more effective and efficient algorithms, the ART 2010 paper has also suggested new insights, interpretations, and research directions. Most notably, the use of failure patterns, such as the distribution of failure-causing inputs, has given rise to the novel research direction of failure-based software testing [20]. Given such knowledge, we may successfully construct adversarial attacks of machine learning systems to test their robustness. Another example of failure patterns is the conceived geometry of the failure areas. This allows us to utilize any minimal information on hand to compare the effectiveness of software testing approaches, without the need to know the detailed algorithms or procedures.</p><p>Random ordering and random sequences have been commonly used as benchmarks for comparing test sequences generated by various algorithms in different problem contexts. Following ART, the new concept of adaptive random sequences [6][26] has evolved as a more effective alternative than random sequences.</p><h3><strong>3. Adaptive Random Testing: The ART of Diversity in Applications</strong></h3><figure><img alt="Pie chart showing the distribution of applications of adaptive random testing" src="https://cdn-images-1.medium.com/max/1024/1*GBWv3GHM4j9MuiCOFOTyxg.jpeg" /><figcaption>Distribution of Applications of Adaptive Random Testing</figcaption></figure><p>ART has been adopted in numerous application domains. A plausible reason is that RT can be used alone or with other testing methods. It does not need the source code. As ART is an alternative to RT, it can be adopted in many application domains as well. The only limitation is the need for test oracles. With the increasing acceptance of metamorphic testing [8] as an effective means to alleviate the oracle problem, the applicability of RT and ART can be extended to the domains involving oracle problems.</p><p>Huawei has applied ART to an industrial case study involving 50 million test cases [27]. Originally, it took 50 days to test and analyze. It was necessary to reduce the number of test cases while revealing more failures. At the same time, control flow, data flow, or code instrumentation could not be applied for reasons of privacy and safety. Based on the linear time algorithm ARTsum [3], category selection-based ART (CSBART) was proposed, where partial categories were selected to compute test case distances. Experimentation showed that CSBART outperformed a more complex K-means clustering strategy.</p><p>Simula Research Laboratory has successfully applied ART to an industrial real-time embedded system [2][13][19]. Despite Simula’s initial observation regarding the inefficiency of ART, the findings from the industrial system were positive. “Results on artificial problems and one industrial case study show that Adaptive Random Testing performs best.” [13] “One main advantage of ART and SBT is that [they] can be tailored to whatever time and resources are available for testing: when resources are expended and time is up, we can simply stop their application without any side effect.” [2] “Adaptive random output diversity algorithm is able to identify different failure types better than the search-based algorithms when test suites are above a certain size.” [19]</p><p>Other notable practical applications include object-oriented programs [5], web services [24], configurable systems [3][7], mobile applications [16], database applications [25], regression testing [6], combinatorial testing [12], and mutation testing [22].</p><p>Furthermore, based on the new research direction proposed in the 2010 paper, a collaborative project between the industry and the academia is being conducted to study how failure patterns can help detect obstacle perception problems in automatic driving systems.</p><h3><strong>4. Support, Support, Support: Three Further Things that Matter in ART</strong></h3><p>There are three further things that matter in adaptive random testing: your support, your support, your support.</p><p>- If you are a researcher, we need your support in proposing better ART approaches and empirically evaluating the family of such techniques.</p><p>- If you are a practitioner, we need your support in applying various ART methodologies to large-scale industrial applications and sharing your experience with us.</p><p>- In either case, we need your immediate support in clicking the “applause” button at the end of the blog entry.</p><p><strong>References</strong></p><p>[1] Mao, C., Quan, M., Chen, Z., and Chen, T.Y., 2020. Adaptive random testing by bisection and comprehensive distance. In: Miao, H., Tan, C., Liu, S., and Duan, Z. (Eds.), Structured Object-Oriented Formal Language and Method, Lecture Notes in Computer Science, vol. 12028. Springer, Cham, Germany, pp. 328–344.</p><p>[2] Arcuri, A., Iqbal, M.Z., Briand, L., 2010. Black-box system testing of real-time embedded systems using random and search-based testing. In: Testing Software and Systems: Proceedings of the 22nd IFIP WG 6.1 International Conference (ICTSS 2010), Lecture Notes in Computer Science, vol. 6435. Springer, Berlin, Germany, pp. 95–110.</p><p>[3] Barus, A.C., Chen, T.Y., Kuo, F.-C., Liu, H., Merkel, R.G., Rothermel, G., 2016. A cost-effective random testing method for programs with non-numeric inputs. IEEE Transactions on Computers 65 (12), 3509–3523.</p><p>[4] Bidgoli, A.M., Haghighi, H., 2020. Augmenting ant colony optimization with adaptive random testing to cover prime paths. Journal of Systems and Software 161, 110495.1–110495.17.</p><p>[5] Chen, J., Kuo, F.-C., Chen, T.Y., Towey, D., Su, C., Huang, R., 2017. A similarity metric for the inputs of OO programs and its application in adaptive random testing. IEEE Transactions on Reliability 66 (2), 373–402.</p><p>[6] Chen, J., Zhu, L., Chen, T.Y., Towey, D., Kuo, F.-C., Huang, R., Guoa, Y., 2018. Test case prioritization for object-oriented software: An adaptive random sequence approach based on clustering. Journal of Systems and Software 135, 107–125.</p><p>[7] Chen, T.Y., Kuo, F.-C., Liu, H., Wong, W.E., 2013. Code coverage of adaptive random testing. IEEE Transactions on Reliability 62 (1), 226–237.</p><p>[8] Chen, T.Y., Kuo, F.-C., Liu, H., Poon, P.-L., Towey, D., Tse, T.H., Zhou, Z.Q., 2018. Metamorphic testing: A review of challenges and opportunities. ACM Computing Surveys 51 (1), 4:1–4:27.</p><p>[9] Chow, C., Chen, T.Y., Tse, T.H., 2013. The ART of divide and conquer: An innovative approach to improving the efficiency of adaptive random testing. In: Proceedings of the 13th International Conference on Quality Software (QSIC 2013), IEEE Computer Society, Los Alamitos, CA, 268–275.</p><p>[10] Huang, R., Liu, H., Xie, X., Chen, J., 2015. Enhancing mirror adaptive random testing through dynamic partitioning. Information and Software Technology 67, 13–29.</p><p>[11] Huang, R., Sun, W., Xu, Y., Chen, H., Towey, D., Xia, X., 2019. A survey on adaptive random testing. IEEE Transactions on Software Engineering. DOI: <a href="https://doi.org/10.1109/TSE.2019.2942921.">https://doi.org/10.1109/TSE.2019.2942921.</a></p><p>[12] Huang, R., Xie, X., Chen, T.Y., Lu, Y., 2012. Adaptive random test case generation for combinatorial testing. In: Proceedings of the IEEE 36th Annual International Computer Software and Applications Conference (COMPSAC 2012). IEEE Computer Society, Los Alamitos, CA, pp. 52–61.</p><p>[13] Iqbal, M.Z.Z., Arcuri, A., Briand, L.C., 2011. Automated system testing of real-time embedded systems based on environment models. Technical Report 2011–19, Simula Research Laboratory, Lysaker, Norway.</p><p>[14] Liu, H., Chen, T.Y., 2016. Randomized quasi-random testing. IEEE Transactions on Computers 65 (6), 1896–1909.</p><p>[15] Liu, H., Xie, X., Yang, J., Lu, Y., Chen, T.Y., 2010. Adaptive random testing by exclusion through test profile. In: Proceedings of the 10th International Conference on Quality Software (QSIC 2010). IEEE Computer Society, Los Alamitos, CA, pp. 92–101.</p><p>[16] Liu, Z., Gao, X., Long, X., 2010. Adaptive random testing of mobile application. In: Proceedings of the 2nd International Conference on Computer Engineering and Technology (ICCET 2010), vol. 2. IEEE, Piscataway, NJ, pp. 297–301.</p><p>[17] Mao, C., Chen, T.Y., Kuo, F.-C., 2017. Out of sight, out of mind: A distance-aware forgetting strategy for adaptive random testing. Science China Information Sciences 60, 092106:1–092106:21.</p><p>[18] Mao, C., Zhan, X., Tse, T.H., Chen, T.Y., 2019. KDFC-ART: a KD-tree approach to enhancing Fixed-size-Candidate-set Adaptive Random Testing. IEEE Transactions on Reliability 68 (4), 1444–1469.</p><p>[19] Matinnejad, R., Nejati, S., Briand, L.C., Bruckmann, T., 2015. Effective test suites for mixed discrete-continuous Stateflow controllers. In: Proceedings of the 10th Joint Meeting on Foundations of Software Engineering (ESEC/FSE-10). ACM, New York, NY, pp. 84–95.</p><p>[20] Merkel, R.G., Kuo, F.-C., Chen, T.Y., 2011. An analysis of failure-based test profiles for random testing. In: Proceedings of the 35th Annual International Computer Software and Applications Conference (COMPSAC 2011). IEEE Computer Society, Los Alamitos, CA, pp. 68–75.</p><p>[21] Omari, M., Chen, J., Ackah-Arthur, H., Kudjo, P.K., 2019. Elimination by linear association: An effective and efficient static mirror adaptive random testing. IEEE Access 7, 71038–71060.</p><p>[22] Patrick, M., Jia, Y., 2017. KD-ART: Should we intensify or diversify tests to kill mutants? Information and Software Technology 81, 36–51.</p><p>[23] Shahbazi, A., Tappenden, A.F., Miller, J., 2013. Centroidal Voronoi tessellations: A new approach to random testing. IEEE Transactions on Software Engineering 39 (2), 163–183.</p><p>[24] Tappenden, A.F., Miller, J., 2014. Automated cookie collection testing. ACM Transactions on Software Engineering and Methodology 23 (1), 3:1–3:40.</p><p>[25] Zhang, L., Zhang, D., Wang, C., Zhao, J., Zhang, Z., 2019. ART4SQLi: The ART of SQL injection vulnerability discovery. IEEE Transactions on Reliability 68 (4), 1470–1489.</p><p>[26] Zhang, X., Xie, X., Chen, T.Y., 2016. Test case prioritization using adaptive random sequence with category-partition-based distance. In: Proceedings of the 2016 IEEE International Conference on Software Quality, Reliability and Security (QRS 2016). IEEE Computer Society, Los Alamitos, CA, pp. 374–385.</p><p>[27] Zhang, Z., Wang, Y., Wang, Z., Qian, J., 2019. How to effectively reduce tens of millions of tests: An industrial case Study on adaptive random testing. IEEE Transactions on Reliability 68 (4), 1429–1443.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed96828f2aeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/diversity-diversity-diversity-ed96828f2aeb">Diversity, Diversity, Diversity:</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collective Executions: Coordinating Joint Device Behavior in the Fog]]></title>
            <link>https://medium.com/jss-editors-selection/collective-executions-coordinating-joint-device-behavior-in-the-fog-d8d7c6764b1b?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/d8d7c6764b1b</guid>
            <category><![CDATA[collective-execution]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[programming-model]]></category>
            <category><![CDATA[fog-computing]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[Niko Makitalo]]></dc:creator>
            <pubDate>Thu, 17 Sep 2020 07:14:53 GMT</pubDate>
            <atom:updated>2020-09-17T07:14:53.232Z</atom:updated>
            <content:encoded><![CDATA[<p>The contemporary computing environment has shifted from single node computing to increasingly distributed computing as the number of interconnected devices has grown. Despite of this shift in the computing paradigm, the way we think about software has not dramatically changed over the time: Software application is yet considered to be solely executed by a single entity at the time — one entity possibly coordinating the others.</p><h4>The interconnected entities can together be considered as the runtime environment.</h4><p>With our novel concept of Collective Executions we have taken the first steps towards new kind of computing paradigm and programming model where multiple devices dynamically, at the same time form the runtime environment where multiple devices are at the same time executing the same piece of software. The devices — as well as other entities, like humans and services — are then assigned to certain roles in the execution. Underneath a novel framework takes care of forming this runtime that enables such collective software execution by taking care of things like state synchronization, device coordination etc.</p><h3>Coalescence and disintegration — Novel way of thinking the application state</h3><p>In the very core of this model is the concept of coalescence and disintegration. In physics, these concepts describe the phenomena where two water drops merge into each other, or split. The analogy in our approach is that the software instances running on different entities can be merged as well into one instance. Then the state synchronization between the newly joined devices begins. Similarly, when disintegration takes place, the state synchronization ends.</p><p>The coalescence and disintegration take place when the distance between the executing entities meets certain thresholds in <em>n</em>-dimensional space. For example, the distance can be physical distance — like the proximity of other devices executing the same application, or it can be for instance the social distance: the family members, friends or people having some other certain social relationship may cause the application instances to coalescence and jointly start executing the same application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoY3IzGnI5CZLflK310p5g.png" /><figcaption><em>Figure 1: Coalescence and Disintegration of Collective Executions</em></figcaption></figure><p>The distance can also be measured in the virtual world, where today common interests connect millions of people: People liking the same video game trailers could then jointly start a multiple player game.</p><p>More formally, we define the distance for two collective execution instances:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wpYM4OhPbNYnIhreyuIU5w.png" /></figure><p>Where <em>p </em>and <em>q </em>are the instances of the Collective Execution <em>E </em>and dist𝑖<em> </em>is their mutual distance along the dimension of <em>i</em>. As the value of the distance is the maximum, it is the so-called Chebyshev distance between the instances.</p><h3>An Example Application</h3><p>To illustrate how the Collective Executions work in practice, let’s consider the following PhotoSharing example: A group of people has gathered together. The group consists of friends and family members, so the distance in the social world is short. This can act as a trigger that their PhotoSharing executions are enabled to coalescence.</p><p>From the user’s perspective, the idea of the PhotoSharing is to initiate discussion among the people that have gathered together. Hence while the PhotoSharing is running, it also notices that the physical distance is under the threshold value that is being used for proactively suggest viewing their most recent and previously un-shared photos related to specific topic, like recent trips to abroad or family life for instance. (Common interests, distance in the virtual world). The Collective Execution then forms the state by synchronizing the unseen photos and the currently shown photo among the participating devices. One device at the time acts as a coordinator and coordinates the other to show certain photo. Other devices act as screens, showing the same selected photo at the same time. This has been depicted in Figure 2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X0IgWB_DAu0xFA_AJigLFQ.png" /><figcaption><em>Figure 2: PhotoSharing Collective Execution coordinating entities.</em></figcaption></figure><h3>Future Work</h3><p>It’s obvious, that there are numerous privacy and security concerns in such proactive approach. Hence plenty of research would be required for instance to make sure that no personal and intimate data will leak into wrong hands. Also, user experience perspective on the security should not be overlooked to make sure that the users a) understand how and by whom their data is being used, and b) not to burden the user with constant interruptions for regarding the data usage or proactive invocation of the activities.</p><h3>Acknowledgements</h3><p>This blog post is based on our articles in <a href="https://doi.org/10.1016/j.jss.2019.110391">JSS</a> and <a href="https://doi.ieeecomputersociety.org/10.1109/MS.2017.4541037">IEEE Software</a> that we from the department of Computer Science, University of Helsinki, Finland have co-authored with our colleagues at the departments of Electronics and Communications Engineering and Pervasive Computing, Tampere University, Finland.</p><h3>References</h3><p>Mäkitalo, N., Aaltonen, T., Raatikainen, M., Ometov, A., Andreev, S., Koucheryavy, Y., &amp; Mikkonen, T. (2019). Action-Oriented Programming Model: Collective Executions and Interactions in the Fog. <em>Journal of Systems and Software</em>, <em>157</em>, 110391. DOI: <a href="https://doi.org/10.1016/j.jss.2019.110391">https://doi.org/10.1016/j.jss.2019.110391</a></p><p>Mäkitalo, N., Ometov, A., Kannisto, J., Andreev, S., Koucheryavy, Y., &amp; Mikkonen, T. (2017). Safe, secure executions at the network edge: coordinating cloud, edge, and fog computing. <em>IEEE Software</em>, <em>35</em>(1), 30–37. DOI: <a href="http://doi.org/10.1109/MS.2017.4541037">http://doi.org/10.1109/MS.2017.4541037</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8d7c6764b1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/collective-executions-coordinating-joint-device-behavior-in-the-fog-d8d7c6764b1b">Collective Executions: Coordinating Joint Device Behavior in the Fog</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to Update Systematic Literature Reviews in Software Engineering]]></title>
            <link>https://medium.com/jss-editors-selection/when-to-update-systematic-literature-reviews-in-software-engineering-d74ea836d286?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/d74ea836d286</guid>
            <category><![CDATA[systematic-review]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Marcos Kalinowski]]></dc:creator>
            <pubDate>Tue, 01 Sep 2020 07:35:06 GMT</pubDate>
            <atom:updated>2020-09-01T07:35:06.488Z</atom:updated>
            <content:encoded><![CDATA[<p>by Emilia Mendes, Claes Wohlin, Katia Felizardo and Marcos Kalinowski</p><p>The following blog post briefly describes the main findings and implications of our Journal of Systems and Software (JSS) article, which provides recommendations on <strong>when to update systematic literature reviews </strong>to the software engineering research community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/965/1*UkXKBjpG_-NmBT-7yjhfhA.png" /></figure><h3>The Need for Well-Justified Updates</h3><p>During our investigations, we found a total of 436+ SLRs published in Software Engineering (SE), within the period from January 2004 to May 2016. Furthermore, we identified 20 updated SLRs. These searches provide evidence that many SLRs in SE are potentially outdated; thus affecting our current aggregated understanding of the state-of-the-art in those SLRs’ research topics.</p><p>When new evidence is added as part of updating SLRs, different findings and conclusions from those reported initially may be identified. Therefore, updating SLRs may contribute to different purposes. For example, (a) providing a continuous update of the state-of-the-art on a research topic; and (b) identifying how that particular research topic is evolving.</p><p>How to keep SLRs current, more specifically concerning how and when to update SLRs, has also been a topic of discussion in other fields, such as medicine and environmental sciences. Within the context of SE, SLRs also need updating; however, the discussion on this important topic was rather limited, which led us to conduct this investigation to provide recommendations for our research community.</p><h3>Recommendations on When to Update SLRs</h3><p>To propose guidance on when to update SLRs in SE, we have investigated existing decision frameworks and detailed guidelines in other more mature disciplines with respect to SLRs. We put forward that the decision framework proposed in (Garner <em>et al.</em>, 2016) — 3PDF henceforth, can be used as a basis to guide the decision of when to update SLRs in SE.</p><p>To reach this conclusion, we conducted a literature review of SLR updates in SE and contacted the authors to obtain their feedback relating to the usefulness of the 3PDF within the context of SLR updates in SE. Second, we used these authors’ feedback to see whether the framework needed any adaptation; none was suggested. Third, we applied the 3PDF to the SLR updates identified in our literature review. The 3PDF showed that 14 of the 20 SLRs did not need updating.</p><p>These findings reinforce the importance of using a decision support mechanism (such as the 3PDF) to help the SE community decide when to update SLRs, allowing them to properly justify the need for updates and avoiding wasting scientific effort with SLRs that do not need to be updated. The 3PDF is shown in below, and further details on how it can be applied within the SE context can be found in our paper.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*vWiu42Lk34mN9wpx_0FwSA.png" /><figcaption><strong>Decision framework to assess SLRs for updating (</strong><a href="https://doi.org/10.1136/bmj.i3507"><strong>Gartner et al., 2016</strong></a><strong>).</strong></figcaption></figure><h3>Implications for the Software Engineering Research Community</h3><p>In our paper, we provided recommendations on when to update SLRs in SE. We put forward that these recommendations should be followed by researchers active in the community when updating SLRs to assess and justify the need for updating.</p><p>We believe that one of the several takeaway messages for the SE research community is that the ‘maturation’ time between the publication of the original/previous SLR and its update should be longer than two years, although exceptions exist. Such a suggestion does not however bypass the need to apply the 3PDF to assess whether an SLR update is genuinely needed. Our results show that many resources are wasted in carrying out updates that did not need to be conducted.</p><p>Another important aspect that has been brought to light is that, whenever SLR updates do not include new relevant methods, they should at least provide results that reflect a change in findings, conclusions, or credibility, when compared to the original SLR. The point here is that the effort to carry out an SLR update should be justified by some novelty, in either the methods used, new findings or conclusions, or increased credibility. If nothing has changed, those SLRs should not be accepted for publication, as one may as well rely on the findings already presented in the original SLR.</p><p>The implications also reach out to newly starting Ph.D. students, i.e., they should not waste any effort to carry out an SLR update if such an update is not justified by a novelty in some manner. And the justification for the decision to not update (or to update) an existing SLR can be based upon applying the 3PDF to the original SLR, and additionally supported by the evidence and recommendations provided in our paper.</p><p>Furthermore, based on the evidence, we believe that an additional take away message on “How ” to update would be to employ the same mechanisms used in the original SLR being updated. To complement our suggestions regarding “How” to update SLRs in SE, we have made recommendations <a href="https://www.sciencedirect.com/science/article/pii/S095058491930223X?via%3Dihub">elsewhere</a> as to what search strategies to employ when updating SE SLRs.</p><p><strong>We expect these findings to help the SE research community to optimize their efforts when employing SLR methodology to provide a current aggregated understanding of the state-of-the-art on relevant SE research topics.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d74ea836d286" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/when-to-update-systematic-literature-reviews-in-software-engineering-d74ea836d286">When to Update Systematic Literature Reviews in Software Engineering</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Towards the definitive evaluation framework for cross-platform app development approaches]]></title>
            <link>https://medium.com/jss-editors-selection/towards-the-definitive-evaluation-framework-for-cross-platform-app-development-approaches-4be425031d37?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/4be425031d37</guid>
            <category><![CDATA[cross-platform]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[app-development-framework]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[evaluation]]></category>
            <dc:creator><![CDATA[Christoph Rieger]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 14:26:01 GMT</pubDate>
            <atom:updated>2020-07-27T14:26:01.218Z</atom:updated>
            <content:encoded><![CDATA[<p>Christoph Rieger and Tim A. Majchrzak</p><p>The following describes how our Journal of Systems and Software (JSS) article <em>Towards the definitive evaluation framework for cross-platform app development approaches</em> has been developed, what its main findings are, and which implications we think it has.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*CTAXql4fogHL7SQtI-AEzg.png" /></figure><h3>Getting started: what are we doing here?</h3><p>Most people nowadays own smartphones. Many also own a tablet. And quite likely their TVs, wearables, maybe even their cars are powered by a mobile platform. We call this <em>app-enabled</em>. The typical expectation is that a given app — for example, a social media client — will run on any of these in a comparable quality, with a comparable user experience, and using common user interfaces of the respective platform.</p><p>Unfortunately, this means that several apps need to be developed. This is complicated since the two dominating smartphone platforms — Android and iOS — are not compatible regarding app development. Even worse, a developer needs to consider the differences of all the implementations of a platform — particularly one Android implementation is not necessarily fully compatible with another one.</p><p>Cross-platform app development approaches promise to solve this problem. There are different approaches towards cross-platform development, ranging on a kind of interval between apps built purely with Web technology to native apps. Selecting the appropriate framework is not easy and reaches beyond technical considerations, particularly if this is not a single-project decision, but a strategic one that you take for many projects, probably enterprise-wide.</p><p>We have built a catalogue of criteria, which we propose in our paper. We distinguish development by four perspectives: infrastructure, development, app, and usage perspective. Altogether we distinguish 33 criteria, allowing for a fine-grained assessment of approaches. Moreover, we propose a weighting framework, allowing one assessment to be used for decision making for different applications, e.g. for apps specifically for tablets, wearables, or smart home usage.</p><h3>Foundations: Towards the first article</h3><p>One of us, Tim, started to work toward cross-platform apps back in 2011. Then a postdoc at the University in Münster, he engaged in a project with the local chamber of commerce to explore the possibilities of what we named <em>business apps</em>. Only four years after the release of the first iPhone, the smartphone landscape was quite different to what it was today. It was not common that nearly any business that offered a Web site would also offer an app (or typically <em>several</em> apps); many apps for smartphones where limited. Smartphone were not the primary way of accessing the Internet for many people. Data plans were expensive, and the computational capabilities let alone the possibilities of sensors were limited. However, enterprises noticed that there was a demand to provide customers with apps for specific pieces of functionality that would reasonably be used from a smartphone.</p><p>The project had a quite curious setup. We worked with regional industry, doing interviews and talking to developers, but the subject of study was really global. Unsurprisingly, we could publish a paper on the project reporting results that were perceived noteworthy [MaHe13]. In the meantime, we had engaged in various activities on the topic, which we found to be underrepresented in research. Our approach of tackling it followed a path typical for new research topics: we started by working exemplarily on case studies [ZiMa12], covered broader topics [HMRW13], and eventually set out to contribute to the theory [HKM15].</p><p>In parallel, we wanted to work practically on the problem of cross-platform app development, but with scientific rigour in mind. Cross-platform app development can essentially follow two approaches. Either they use a runtime environment, or they are generative. Generative approaches yield truly native apps but use source code for one app only. Runtime based approaches provide a layer between app and mobile platform; such approaches are available with varying sophistication, from such that are more or less Webapps to such that use the native GUI elements through a self-contained runtime. Approaches developed and favoured by industry are based on runtime environments because of the availability of programmers with related experience (e.g. JavaScript). As computer scientists (or rather information systems people who like computer science methods), we favoured the generative approaches, which would in theory yield “cleaner” results and offer many benefits regarding semantic analysis and performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIoELfccVJ6Z3lRyzOXbxw.png" /><figcaption>Continuum of cross-platform development approaches</figcaption></figure><p>A few transpilers were available, but their performance was not satisfying. A transpiler takes code written in one language for one platform and transforms it to code written in another language for another platform. Due to platform and language idiosyncrasies, particularly when it comes to the GUI, this is very hard. Therefore, we favoured a model-based approach: instead of instruction how an app should work, we set out to ask developers to merely specify what an app should be capable off in a concise and platform-neutral representation. Work on our prototype MD2 proved to be very fruitful, although it remained an academic prototype [HMK13]. Learning that cross-platform app development ought to follow software engineering best practices, be theoretically sound, yet industrially producible made us think. Platform fragmentation, device heterogeneity and rapid release cycles made (and make) it hard for developers. Therefore, through a Bachelor thesis we had a student analyse these early cross platform app development frameworks. The results seemed so promising that we invited him to work with us in turning their results into a scientific framework and revising it further. The work proved even more relevant than we had anticipated. The article from 2013 [HHM13] has been cited more than 330 times.</p><h3>Work: Getting the article done</h3><p>After serving as deputy professor in Cologne, Tim started as tenured associate professor at the University of Agder in 2015. He set out to enable a second research tier, becoming a member of CIEM (Centre for Integrated Emergency Management) — societal support had always been a theme Tim was interested in. However, collaboration continued with the group in Münster, where Christoph started as PhD student in 2015. One stream of research focused on extending previous cross-platform approaches towards novel mobile devices such as smartwatches and voice-based smart personal assistants. Therefore, a graphical notation called MAML [Ri17] was built on top of MD2 to demonstrate the transferability of abstracted functionality to heterogeneous devices.</p><p>Motivated by the success of the first evaluation paper from 2013, Christoph and Tim decided to update the original paper. Despite its impact, it offered room for improvement. First, it had become dated due to the unprecedented progress in the field with platforms and frameworks frequently occurring and disappearing. Moreover, with Progressive Web Apps (PWAs), a new contender recently entered the scene and recent frameworks needed to be addressed [BMG18]. Second, it did not cater for the different application areas of mobile platforms — now not limited to smartphones anymore but spanning for example entertainment electronics, vehicles, and wearables [RiKu18]. Third, observation of the application of the original research indicated that with the evolution of the field in practice, the theoretic base could be refined and the framework slightly tweaked to flexibly accommodate the unique requirements of cross-platform projects.</p><p>The first step to achieving this goal was to offer a weighting framework on top of the revised original framework [RiMa16]. Since we got encouraging feedback when presenting our ideas at a conference, we decided that our work finally was ripe to contribute to theory. The idea for the JSS paper was born in September 2016. A journal paper, particularly one that builds on a broad base of literature and seeks to theorize, takes some time to write. After more than two years and many internal revisions, our article was handed in on 20 November 2018. Thanks to the quick JSS review process, we soon received comprehensive feedback. Much to our relief, the time we had taken was honoured and most comments tried to push us even further, e.g., for thoroughly linking our extensive set of criteria to the scientific body of knowledge. On 25 February 2019 we uploaded our revision and received the acceptance notification on 1 April 2019 — it was not an April fool’s joke!</p><h3>Conclusion: Where we hope this to be going</h3><p>To give a better idea of our framework, the following table shows an exemplary set of weights for different device categories as described in detail in the paper. Consider it a snapshot and really exemplary to illustrate the evaluation of one of the various. The evaluated platforms have since then been developed further, some more, some less. Moreover, categories of novel app-enabled devices (like vehicles) are quickly evolving and would need to be updated. However, the weights always need to be decided individually anyway, since the framework is meant to be adjusted to the needs and preconditions of developers, the companies they work for, their customers, and possible end-customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*C32fLoV7cP_4mOOeTae3Wg.png" /><figcaption>Exemplary weight profiles and framework evaluation</figcaption></figure><p>Despite being published in JSS, our article has not yet been cited as much as the first evaluation article from 2013 had. We hope that it has been noticed in practice for its comprehensiveness, though. The need of developing interoperable functionality in a cross-platform fashion keeps being there, although modern Web-based development frameworks and Progressive Web Apps (PWAs) have likely shifted the focus toward Web technologies in many cases.</p><p>Research on the underlying topics is ongoing. However, it has become much more specific. For example, the performance of cross-platform app development technologies is now studied in detail which is reflected in the latest evolution of frameworks towards hybrids of runtime and generative approaches. In addition, research institute Gartner predicts that “multiexperience” apps with immersive interaction modes such as chat, voice, wearable, and augmented reality experiences will become much more common in the near future [Ga19]. Further software engineering research is mandated to boost the efficiency of app development and cope with the plethora of heterogeneous devices.</p><p>Our further journey with this topic is yet undecided. Whereas Christoph closely follows recent developments in the field of mobile app development, he has completed his PhD and left academia to work on technology-related topics in the private sector. Tim stayed and still engages in topics in app development. From our observations, the convergence of technologies might become the next roadblock on the path towards improving cross-platform app development — both challenging and interesting at the same time. Mobile computing, the Internet-of-Things and cyber-physical systems (CPS) share an increasing number of constituting elements. It may be that they soon also share platforms and means of development much stronger than they do now.</p><p>Interested researches and practitioners will find good venues for their work on the intersection of Web technology, mobile computing, IoT, and recently also cyber-physical systems in the HICSS minitrack on Software Development for Mobile Devices, the Internet-of-Things, and Cyber-Physical Systems as well as on the SAC track on Web technologies, which Tim both co-chairs.</p><h3>References</h3><p>[BMG18] Biørn-Hansen, A., Majchrzak, T. A., and Grønli, T.-M. (2018): Progressive Web Apps for the Unified Development of Mobile Applications. In: Majchrzak, T. A., Traverso, P., Krempels, K.-H., and Monfort, V., eds.: Revised Selected Papers WEBIST 2017, Lecture Notes in Business Information Processing (LNBIP), 322, 64–86, Springer</p><p>[Ga19] Gartner, Inc. (2019). Gartner Says the Future of App Development Is Multiexperience. https://www.gartner.com/en/newsroom/press-releases/2019-04-04-gartner-says-the-future-of-app-development-is-multiex</p><p>[HHM13] Heitkötter, H., Hanschke, S., and Majchrzak, T. A. (2013): Evaluating Cross-Platform Development Approaches for Mobile Applications. In: Cordeiro, J. and Krempels, K.-H., eds.: Revised Selected Papers WEBIST 2012, Lecture Notes in Business Information Processing (LNBIP), 140, 120–138, Springer</p><p>[HMK13] Heitkötter, H., Majchrzak, T. A., and Kuchen, H. (2013): Cross-Platform Model-Driven Development of Mobile Applications with MD² In: Proc. of the 28th ACM Symp. on Applied Computing (SAC), 526–533, ACM</p><p>[HKM15] Heitkötter, H., Kuchen, H., and Majchrzak, T. A. (2015): Extending a Model-Driven Cross-Platform Development Approach for Business Apps. Science of Computer Programming (SCP), 97(1): 31–36</p><p>[HMRW13] Heitkötter, H., Majchrzak, T. A., Ruland, B., and Weber, T. (2013): Evaluating Frameworks for Creating Mobile Web Apps. In: Proc. 9th International Conference on Web Information Systems and Technologies (WEBIST), 209–221, SciTePress</p><p>[MaHe13] Majchrzak, T. A. and Heitkötter, H. (2013): Development of Mobile Applications in Regional Companies: Status Quo and Best Practices. In: Proc. 9th International Conference on Web Information Systems and Technologies (WEBIST), 335–346, SciTePress</p><p>[Ri17] Rieger, C. (2017) Business apps with MAML: a model-driven approach to process-oriented mobile app development. In: SAC: 1599–1606</p><p>[RiKu18] Rieger, C. and Kuchen, H. (2018) Towards Model-Driven Business Apps for Wearables. MobiWIS 2018: 3–17</p><p>[RiMa16] Rieger, C. and Majchrzak, T. A. (2016): Weighted Evaluation Framework for Cross-Platform App Development Approaches. In Stanislaw Wrycza, ed.: Proc. of the 9th SIGSAND/PLAIS EuroSymposium on Systems Analysis and Design Information Systems, Lecture Notes in Business Information Processing (LNBIP), 18–39, Springer</p><p>[ZiMa12] Zibula, A. and Majchrzak, T. A. (2012): Developing a Cross-Platform Mobile Smart Meter Application Using HTML5, jQuery Mobile, and PhoneGap. In: Proc. 8th International Conference on Web Information Systems and Technologies (WEBIST), 13–23, SciTePress</p><h3>Author Biographies</h3><p>Christoph Rieger received BSc and MSc degrees in Information Systems from the University of Münster, Germany. By contributing to MD2 framework during his Master’s thesis, he combined his interests on mobile devices and software engineering which became focal areas of his later work as a research assistant in Münster. In particular, model-driven software development and domain-specific languages for several application areas are central topics of his research which was published in renowned conferences and journals including Journal of Systems and Software (JSS) and Empirical Software Engineering (EMSE). After receiving his PhD in economics (Dr. rer. pol.), he now pursues his interests in technology-related topics as a consultant.</p><p>Tim A. Majchrzak is professor in Information Systems at the University of Agder (UiA) in Kristiansand, Norway. He also is a member of the Centre for Integrated Emergency Management (CIEM) at UiA. Tim received BSc and MSc degrees in Information Systems and a PhD in economics (Dr. rer. pol.) from the University of Münster, Germany. His research comprises both technical and organizational aspects of Software Engineering, typically in the context of Mobile Computing. He has also published work on diverse interdisciplinary Information Systems topics, most notably targeting Crisis Prevention and Management. Tim’s research projects typically have an interface to industry and society. He is a senior member of the IEEE and the IEEE Computer Society, and a member of the Gesellschaft für Informatik e.V.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4be425031d37" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/towards-the-definitive-evaluation-framework-for-cross-platform-app-development-approaches-4be425031d37">Towards the definitive evaluation framework for cross-platform app development approaches</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The $3,9 Trillion Dollar Challenge: How Enterprise Architecture Improves the Quality of IT…]]></title>
            <link>https://medium.com/jss-editors-selection/the-3-9-trillion-dollar-challenge-how-enterprise-architecture-improves-the-quality-of-it-bcfac202718e?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/bcfac202718e</guid>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[science]]></category>
            <dc:creator><![CDATA[Martin van den Berg]]></dc:creator>
            <pubDate>Mon, 22 Jun 2020 12:01:01 GMT</pubDate>
            <atom:updated>2020-06-22T12:01:01.648Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The $3,9 Trillion Dollar Challenge: How Enterprise Architecture Improves the Quality of IT Investment Decisions</strong></h3><p><a href="https://www.linkedin.com/in/mjbkvandenberg/">Martin van den Berg</a></p><p>$3,9 Trillion dollar. That’s an enormous amount of money. You might wonder where all this money goes? This is the amount that companies and consumers worldwide expect to spend on IT in 2020, according to research firm <a href="https://www.gartner.com/en/newsroom/press-releases/2020-01-15-gartner-says-global-it-spending-to-reach-3point9-trillion-in-2020">Gartner</a>. However, companies do not spend this money just like that. Before they do that, they make decisions about what they spend, why, when and how. Let me give you some examples of IT decisions: are we going to invest in digitizing our customer service? When are we going to replace our logistics system and what investment is needed? What projects are needed in the context of our digital transformation? Where do we want to apply artificial intelligence?</p><p>An important decision is whether or not to start a large IT project. Before the management of a company approves such a project, it wants to know what the project will cost, what it will deliver, when it will be ready, etcetera. Such an IT investment decision is difficult and risky. IT projects regularly fail. Look at the <a href="https://curiousmatic.com/colossal-failed-government-projects/">headlines</a>.</p><p>According to the <a href="https://www.standishgroup.com/">Standish group</a>, which is a research firm that researches IT projects, in 2017 only 33% of the projects were successful, 19% failed and 48% were challenged, which means that there was something wrong with these projects in terms of time, money or customer satisfaction. For all these projects a decision was made to start them. The question is what we can do to improve these IT investment decisions, so that we get more successful projects.</p><p>In my case, I investigated how enterprise architecture (EA) can help. My research question is: how can enterprise architecture be used as an instrument to improve IT decisions?</p><p>But you will probably wonder: what is EA? I’m going to try to explain it by drawing a parallel with urban planning. What you see on the figure is the so-called Merwedekanaal area in Utrecht, the Netherlands, and my hometown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cZMI8GieWuK8QUaKTqdQMg.png" /></figure><p>This is a former defence site, once used by the Dutch army. There are now <a href="https://www.utrecht.nl/bestuur-en-organisatie/publicaties/bestemmingsplannen/omgevingsvisie-merwedekanaalzone">plans</a> to redevelop the area from a vision of healthy, urban living. Together with other disciplines and interested parties, urban planners developed concepts and designs. You can imagine that when redeveloping such an area, many choices have to be made, such as the destination, how to finance the development, how to connect to the infrastructural facilities of the city, how to connect to all other plans of the municipality of Utrecht, etcetera. Various plans have been made for this purpose, such as an environmental vision, a zoning plan and an urban development plan. These plans make it possible to make well-considered investment decisions about the development of this area. Urban planning is an indispensable discipline in this respect. An urban planner carries out research into the existing and new urban areas, designs the public space, and draws up principles and rules for building. It is unthinkable that such an area could be redeveloped without the involvement of the urban planner. Surely it would be crazy to simply start building a shopping centre anywhere in this area?</p><p>You can compare the redevelopment of the Merwedekanaal area with a change in the strategy of a company. Let me give you an example: a bank wants to proactively make offers to its customers on the basis of their payment behaviour. It would be crazy to just start building an IT system. A plan is needed for the management of this bank to make a well-considered decision about this change of strategy. This plan should make clear what the bank wants to achieve with the strategy change, how to finance this change, which changes in processes and IT systems are needed, which organisational changes are needed, what the privacy consequences are etcetera. EA, just like urban planning, should be an indispensable discipline when drawing up such a plan. After all, enterprise architects such as myself, do research into existing and new processes and IT systems, design them and draw up principles and rules for their construction. Enterprise architects are therefore a kind of urban planners of their company.</p><p>Unlike urban planning, EA is not yet generally accepted as a discipline that is indispensable in large transformations. One explanation is that the profession is not that mature compared to urban planning, and that enterprise architects are not always seen as advisors to management. Another explanation is that it is not so easy to translate principles and diagrams into useful insights for decision-makers. That is the reason I started to research how EA can improve IT decisions, and in particular IT investment decisions. In 2019 I received my PhD based on this <a href="https://research.vu.nl/en/publications/improving-it-decisions-with-enterprise-architecture">research</a>.</p><p>One the most interesting results of my research is published in the <a href="https://www.sciencedirect.com/science/article/pii/S0164121219300433">JSS article</a>. In this study I wanted to find out how EA can improve the quality of IT investment decisions. A quantitative research approach was chosen, in which data were collected from a survey of 142 participants. These data were used to perform a comparative analysis between top and bottom quartile organizations on 1) the EA maturity, 2) the use of EA artifacts in the preparation of IT investments, and 3) the key insights that EA provides in preparation of IT investments.</p><p>The study reveals that top quartile organizations (organizations with the highest quality outcomes of their IT investment decisions) apply EA differently compared to bottom quartile organizations (organizations with the smallest quality outcomes of their IT investment decisions). What distinguishes these former organizations from the latter, is a higher EA maturity on all EA maturity areas. Furthermore, top quartile organizations make more use of EA artifacts in the preparation of IT investment decisions, in particular heat maps, policies, roadmaps, business capability models and landscape diagrams. In these organizations EA artifacts are not limited to artifacts that only provide insight and oversight but have evolved to more diagnostic and actionable EA artifacts. Heatmaps and roadmaps are typical examples of diagnostic respectively actionable EA artifacts. A heatmap shows which business capabilities need to be redesigned by means of colours. A roadmap shows which steps need to be taken to realize a design. The figure (taken from the <a href="https://www.sciencedirect.com/science/article/pii/S0164121219300433">JSS article</a>) shows the differences between top and bottom quartile organizations with regard to the EA artifacts that these organizations use in the preparation of IT investment decision</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXRgtnkAwzOHtwihWFwhDQ.png" /></figure><p>It is also in the top quartile organizations where the EA function provides more strategic insights during the preparation of IT investment decisions, especially whether IT investments fit with the business strategy, the relationship with future and past investments and the risks of IT investments.</p><p>These findings are important given the large amounts invested in IT and the risks associated with these investments. The right EA approach can help organizations to become more successful in their IT investments. With my research, I wish to help enterprise architects get more and better involved in IT investment decisions, resulting in more successful IT projects. So that in the end the 3,9 trillion dollars is better spent.</p><p>Read the full paper at the <a href="https://www.sciencedirect.com/science/article/pii/S0164121219300433">Journal of Systems and Software</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcfac202718e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/the-3-9-trillion-dollar-challenge-how-enterprise-architecture-improves-the-quality-of-it-bcfac202718e">The $3,9 Trillion Dollar Challenge: How Enterprise Architecture Improves the Quality of IT…</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FogBus: A Blockchain-based Lightweight Framework for Edge and Fog Computing]]></title>
            <link>https://medium.com/jss-editors-selection/fogbus-a-blockchain-based-lightweight-framework-for-edge-and-fog-computing-cd91a146e388?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/cd91a146e388</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[fog-computing]]></category>
            <category><![CDATA[internet-of-things]]></category>
            <category><![CDATA[edge-computing]]></category>
            <dc:creator><![CDATA[Md Redowan Mahmud]]></dc:creator>
            <pubDate>Tue, 19 May 2020 13:58:23 GMT</pubDate>
            <atom:updated>2020-05-19T13:58:23.364Z</atom:updated>
            <content:encoded><![CDATA[<p>The Cloud Computing and Distributed Systems (CLOUDS) Laboratory, the University of Melbourne has been one of the pioneer research organizations in developing various resource and application management policies for Edge and Fog computing environments. From the CLOUDS Lab, 40+ articles have already been published on Edge and Fog computing in different high impact journals, conferences and book series. In 2017, the CLOUDS Lab launched “iFogSim” toolkit for modeling and simulation of resource management policies in the Internet of Things (IoT), Edge and Fog computing environments. Additionally, with a view to supporting end-to-end integration of Edge-Fog and Cloud infrastructure for Internet of Things (IoT) applications, the CLOUDS Lab has recently developed a real-world framework named “FogBus”. The research article entitled “FogBus: A Blockchain-based Lightweight Framework for Edge and Fog Computing”, co-authored by Shreshth Tuli, Redowan Mahmud, Shikhar Tuli, and Rajkumar Buyya, has been published in the Journal of Systems and Software (JSS), Elsevier in 2019. It has also received the “Top Ten Downloaded Article of 2019 Award” from the editorial board of JSS.</p><p>The requirement of executing latency-sensitive and computing-intensive IoT applications across the Edge-Fog and Cloud infrastructure sets the motivation for developing the FogBus framework. Like FogBus, there exist other frameworks that integrate Edge-Fog and Cloud infrastructure. However, they</p><ol><li>barely support simultaneous execution of multiple applications and platform independence</li><li>offer limited scope to application developers and users to tune them framework according to individual requirements</li><li>apply centralized techniques that eventually increase management time and service delay</li><li>and consider only a few security aspects.</li></ol><p>On the other hand, <strong>FogBus</strong></p><ol><li>simplifies the integration of Edge-Fog and Cloud infrastructure so that edge and remote resources can be harnessed according to application requirements</li><li>applies Blockchain to ensure data integrity while transferring confidential data</li><li>supports platform-independent application execution and node-to-node interaction architecture to overcome the resource heterogeneity within an integrated Edge-Fog and Cloud environment.</li><li>provides a scope to integrate customized Edge-Fog resource management policies.</li></ol><p>FogBus considers Edge computation as a subset of Fog computing. The hardware that FogBus deals with are:</p><p><strong>IoT devices:</strong> Perceive the external environment and convert any given command to physical actions. FogBus allows IoT devices to connect with proximate gateways via wireless or wired communication protocols.</p><p><strong>Fog Gateway Nodes (FGN):</strong> Through FGNs, the FogBus framework offers user interfaces of applications so that the users can set authentication credentials, access the backend program, convey service expectations, receive service outcome, manage IoT devices, and request resources from computing infrastructure according to their affordability. They use either the Constrained Application Protocol (CoAP) or Simple Network Management Protocol (SNMP) for communication.</p><p><strong>Fog Computational Nodes (FCN):</strong> In FogBus framework, they are classified as Broker nodes, Repository nodes and General Computing nodes (GCNs). They perform resource management operations, data storage, and application execution.</p><p><strong>Cloud datacenters: </strong>FogBus extends resources from Cloud datacenters to execute back-end applications. In association with Fog repository nodes, it facilitates extensive data storage and distribution so that access and processing of data become location independent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XfeETCn-uSDCmf55rtzkSw.png" /><figcaption><em>Figure 1: High-level view of integrating IoT, Edge-Fog and Cloud through FogBus framework</em></figcaption></figure><p>The software components of FogBus include:</p><p><strong>Broker Service:</strong> It looks after the security of decision-making entities, manages the data flow, provisions resources for application execution and connects Cloud to Fog infrastructure.</p><p><strong>Repository Service:</strong> It archives the user and infrastructure credentials, stores the data from IoT devices, mirrors the application catalog and extends the Cloud storage to support data management operations.</p><p><strong>Computing Service:</strong> It manages the security aspects of computing entities, executes the applications, monitors the resource usage during application execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DiIGFLIvbmM9zh1_He-8_A.png" /><figcaption><em>Figure 2: Interaction of different software components within FogBus</em></figcaption></figure><p>Moreover, the network structure of FogBus works in Master-Worker basis where the Brokers are the masters and other nodes are the workers. The software components of FogBus is developed in PHP and Java programming language for their cross-platform assistance. HTTP Restful APIs are used to manage the communication among different hardware in FogBus enabled integrated computing environments. The Blockchain feature of FogBus is implemented in Java in association with SHA256 algorithm. The hash value is created using the corresponding data, the index of the block in the chain, the timestamp of the data reception and the hash of its previous block within the chain. The Cloud plugin is created with the <a href="http://www.manjrasoft.com/aneka_architecture.html">Aneka Cloud Application Platform</a> software developed by Manjra soft and <a href="http://www.cloudbus.org/">CLOUDS Lab</a>.</p><p>To illustrate the efficacy of FogBus, it has been used to develop a prototype for Sleep Apnea data analysis. The configurations of hardware used in this prototype are:</p><ul><li>IoT Device: Jumper JPD-500F Finger Pulse Oximeter, 1.5V, Bluetooth Low Energy v4.2 (BLE), UTF-8 data encoding.</li><li>Gateway: Smartphone, Oppo A73 CPH1725, Android 7.1.1.</li><li>Broker/Master Node: Dell Latitude D630 Laptop, Intel(R) Core (TM)2 Duo CPU E6550@2.33GHz 2GB DDR2 RAM, 32-bit, Windows 7, Apache HTTP Server 2.4.34, Java SE Runtime Environment (JRE) 1.6, MySQL 5.6, .net 3.5, Aneka 3.1.</li><li>Other FCN/Worker Node: Raspberry Pi 3 B+, ARM Cortex- A53 quad-core SoC CPU @ 1.4GHz 1GB LPDDR2 SDRAM, IEEE 802.11, 64-bit, Raspbian Stretch, Apache HTTP Server 2.4.34, JRE 1.6, MySQL 5.6.</li><li>Public Cloud: Microsoft Azure B1s Machine, 1vCPU, 1GB RAM, 2GB SSD, Windows Server 2016, .NET 3.5, Aneka 3.1.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8h-3cRxoTH8YTp8CsY7hA.png" /><figcaption><em>Figure 3: FogBus framework enabled system model for Sleep Apnea analysis</em></figcaption></figure><p>Additionally, FogBus provides significant scope to conduct future research in the following directions.</p><ol><li>Fog infrastructure virtualization: In-depth exploration is required to virtualize the Fog infrastructure in FogBus</li><li>Application placement techniques: Different application placement techniques can also be added to the software stack of FogBus.</li><li>Artificial Intelligence: FogBus does not support any artificial intelligence techniques for controlling the operations. The inclusion of Artificial Intelligence techniques can be a significant contribution to FogBus.</li><li>Runtime application migration: Migration of applications during runtime is very crucial if any anomaly is predicted. Different runtime application migration strategies for FogBus can be developed to handle such uncertain events.</li><li>Lightweight security features: Existing security features of FogBus require comparatively higher computational assistance. This consequently affects service delivery latency, energy, and network usage. Therefore, lightweight but effective features can be helpful for further enhancement of FogBus.</li></ol><p><em>In summary, it can be claimed that FogBus is a very important contribution to the state of the art. Building on FogBus framework, 30+ research articles have already been published. Moreover, both iFogSim simulator and FogBus framework, developed by the CLOUDS Lab, pave the way for systematic research on resource management in Edge-Fog computing environments. iFogSim assists in conceptualizing a resource management policy, whereas, FogBus facilitates its physical deployment and evaluation. Many researchers and organizations all around the world are following this approach. The CLOUDS Lab expects its faster growth in the upcoming years.</em></p><p>FogBus software is released in open source and it can be accessed from:<br><a href="http://cloudbus.org/fog/">http://cloudbus.org/fog/</a> or <a href="https://github.com/Cloudslab/FogBus">https://github.com/Cloudslab/FogBus</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd91a146e388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/fogbus-a-blockchain-based-lightweight-framework-for-edge-and-fog-computing-cd91a146e388">FogBus: A Blockchain-based Lightweight Framework for Edge and Fog Computing</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing the JSS Happy Hour (May 29th)]]></title>
            <link>https://medium.com/jss-editors-selection/announcing-the-jss-happy-hour-may-29th-36cf9cf92f3c?source=rss----773a35967154---4</link>
            <guid isPermaLink="false">https://medium.com/p/36cf9cf92f3c</guid>
            <category><![CDATA[science]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Philipp Leitner]]></dc:creator>
            <pubDate>Wed, 13 May 2020 07:25:21 GMT</pubDate>
            <atom:updated>2020-05-29T11:37:18.496Z</atom:updated>
            <content:encoded><![CDATA[<p>To fill the void left by ICSE’s cancellation, we are planning on hosting a JSS Happy Hour on May 29th. This happy hour will be streamed via <a href="https://www.twitch.tv/">Twitch.tv</a>, ensuring high quality audio and video, and will feature:</p><ul><li><strong>SHORT video summaries</strong> of selected papers <em>(3 min or less, 10 papers or less)</em></li><li><strong>Banter from our expert panel </strong>of <a href="http://www.cs.rug.nl/~paris/">Paris Avgeriou</a>, <a href="https://www2.dmst.aueb.gr/dds/">Diomidis Spinellis</a>, and <a href="https://kstolee.github.io/">Katie Stolee</a> after each video <em>(e.g., “If your result needs a statistician then you should design a better experiment”)</em></li><li><strong>Interactive crowd voting </strong>on key JSS issues via <a href="https://www.mentimeter.com/">Menti.com</a> <em>(e.g., the goatee, which JSS co-EiC wears it better?)</em></li></ul><p>We want to ensure this event captures some of the valuable community-building that is always a part of ICSE, and so we have some guidelines for watching. They are:</p><ol><li><strong>Be interactive</strong> — One of the best parts of conferences is interacting with a large number of your peers and collaborators. Thus, we encourage you to engage fully during the broadcast. There will be three ways to engage: by chatting on Twitch.tv’s built-in chat (you’ll need an account), by answering questions on Menti.com, and by tweeting <a href="https://twitter.com/search?q=%23jssOnTwitch">#jssOnTwitch</a>.</li><li><strong>Watch with Friends </strong>— Twitch.tv is a broadcast-only medium (i.e., broadcasters cannot hear you). While we will solicit your feedback in the Twitch chat, via Menti.com, and on Twitter, it is simply not the same as interacting directly with friends. Thus, we encourage you to host watch parties. That is, set up a Zoom meeting or Google Hangout session and watch the Twitch.tv stream together with 3–6 of your best conference buddies. It’s a chance to reconnect!*</li><li><strong>Be respectful</strong> — This event is centered around community-building. Before you tweet, chat, or answer on Menti, ask yourself, would I say this in person? Is this comment constructive? We encourage you to have fun, but not at the expense of others.</li></ol><p>* PSA — use headphones to avoid echos during the meeting.</p><p>We hope you will join us for this fun event! All you need to do to join is visit <a href="https://twitch.tv/davidcshepherd">https://twitch.tv/davidcshepherd</a> on <strong>May 29th at 10am EST </strong>(4pm Amsterdam time/CET DST/UTC+2). For those not in these time zones we apologize! Note that the broadcast will be publicized on Twitter for your convenience.</p><p>All the best,</p><p>David C. Shepherd</p><p>Paris Avgeriou</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36cf9cf92f3c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jss-editors-selection/announcing-the-jss-happy-hour-may-29th-36cf9cf92f3c">Announcing the JSS Happy Hour (May 29th)</a> was originally published in <a href="https://medium.com/jss-editors-selection">JSS Editor’s Selection</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>