<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">63090</controlfield>
        <controlfield tag="005">20171120125810.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="a">10.1109/IRI.2017.64</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">COMPON-2017-0128</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">spa</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="0">0000-0001-5111-8357</subfield>
            <subfield code="a">Requeno Jarabo, José Ignacio</subfield>
            <subfield code="u">Universidad de Zaragoza, España</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">Performance Analysis of Apache Storm Applications using Stochastic Petri Nets</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2017</subfield>
        </datafield>
        <datafield tag="506" ind1=" " ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">Real-time data-processing applications, such as those developed using Apache Storm, need to address highly demanding performance requirements. Engineers should assess these performance requirements while they configure their Storm designs to specific execution contexts, i.e., multi-user private or public cloud infrastructures. To this end, we propose a quality-driven framework for Apache Storm, that covers the following steps. The design with UML, using a novel profile for Apache Storm, allowing performance metrics definition. The transformation of the design into a performance model, con- cretely stochastic Petri nets. Last but not least, the simulation of the performance model and the retrieval of performance results.</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by-nc-nd</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by-nc-nd/3.0/es/</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">Comunicación</subfield>
        </datafield>
        <datafield tag="653" ind1="1" ind2=" ">
            <subfield code="a">Apache Storm; Performance analysis; Petri net</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">0000-0002-8917-6584</subfield>
            <subfield code="a">Merseguer Hernáiz, José Javier</subfield>
            <subfield code="u">Universidad de Zaragoza, España</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="0">0000-0002-2605-6243</subfield>
            <subfield code="a">Bernardi, Simona</subfield>
            <subfield code="u">Centro Universitario de la Defensa, España</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="d">San Diego (USA)</subfield>
            <subfield code="g">The 5th IEEE International Workshop on Formal Methods Integration</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">987724</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/63090/files/iri2017.pdf</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:63090</subfield>
            <subfield code="p">comunicaciones-ponencias</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">COMPON</subfield>
        </datafield>
    </record>

    
</collection>