<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="https://puma.ub.uni-stuttgart.de/tag/cloud-computing%20explainability"><owl:Ontology rdf:about=""><rdfs:comment>PUMA publications for /tag/cloud-computing%20explainability</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="https://puma.ub.uni-stuttgart.de/bibtex/29196fbbfb4275c103f46d3bb625ace20/klinaku"><owl:sameAs rdf:resource="/uri/bibtex/29196fbbfb4275c103f46d3bb625ace20/klinaku"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><owl:sameAs rdf:resource="https://doi.org/10.1145/3578245.3584728"/><swrc:date>Mon Jan 13 13:33:26 CET 2025</swrc:date><swrc:address>New York, NY, USA</swrc:address><swrc:booktitle>Companion of the 2023 ACM/SPEC International Conference on Performance Engineering</swrc:booktitle><swrc:month>4</swrc:month><swrc:pages>277–282</swrc:pages><swrc:publisher><swrc:Organization swrc:name="Association for Computing Machinery"/></swrc:publisher><swrc:series>ICPE &#039;23 Companion</swrc:series><swrc:title>Hitchhiker&#039;s Guide for Explainability in Autoscaling</swrc:title><swrc:year>2023</swrc:year><swrc:keywords>autoscaling cloud-computing elasticity explainability </swrc:keywords><swrc:day>15</swrc:day><swrc:abstract>Cloud-native applications force increasingly powerful and complex autoscalers to guarantee the applications&#039; quality of service. For software engineers with operational tasks understanding the autoscalers&#039; behavior and applying appropriate reconfigurations is challenging due to their internal mechanisms, inherent distribution, and decentralized decision-making. Hence, engineers seek appropriate explanations. However, engineers&#039; expectations on feedback and explanations of autoscalers are unclear. In this paper, through a workshop with a representative sample of engineers responsible for operating an autoscaler, we elicit requirements for explainability in autoscaling. Based on the requirements, we propose an evaluation scheme for evaluating explainability as a non-functional property of the autoscaling process and guide software engineers in choosing the best-fitting autoscaler for their scenario. The evaluation scheme is based on a Goal Question Metric approach and contains three goals, nine questions to assess explainability, and metrics to answer these questions. The evaluation scheme should help engineers choose a suitable and explainable autoscaler or guide them in building their own.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="9798400700729" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="Coimbra, Portugal" swrc:key="location"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1145/3578245.3584728" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Floriment Klinaku"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Sandro Speth"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Markus Zilch"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Steffen Becker"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description><foaf:Group rdf:about="https://puma.ub.uni-stuttgart.de/tag/cloud-computing%20explainability"><foaf:name>cloud-computing explainability</foaf:name><description>Community for tag(s) cloud-computing explainability</description></foaf:Group></rdf:RDF>