<?xml version="1.0" encoding="UTF-8"?>

<modsCollection xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd">
<mods version="3.3">

<genre>conference paper</genre>

<titleInfo><title>Automatized Derivation of Comprehensive Specifications for Black-box Services</title></titleInfo>





<name type="personal">
  <namePart type="given">Simon</namePart>
  <namePart type="family">Schwichtenberg</namePart>
  <role><roleTerm type="text">author</roleTerm> </role><identifier type="local">13235</identifier></name>







<name type="corporate">
  <namePart></namePart>
  <identifier type="local">66</identifier>
  <role>
    <roleTerm type="text">department</roleTerm>
  </role>
</name>





<name type="corporate">
  <namePart>SFB 901</namePart>
  <role><roleTerm type="text">project</roleTerm></role>
</name>
<name type="corporate">
  <namePart>SFB 901 - Subprojekt B1</namePart>
  <role><roleTerm type="text">project</roleTerm></role>
</name>
<name type="corporate">
  <namePart>SFB 901 - Project Area B</namePart>
  <role><roleTerm type="text">project</roleTerm></role>
</name>



<abstract lang="eng">Today, cloud vendors host third party black-box services, whose developers usually provide only textual descriptions or purely syntactical interface specifications. Cloud vendors that give substantial support to other third party developers to integrate hosted services into new software solutions would have a unique selling feature over their competitors. However, to reliably determine if a service is reusable, comprehensive service specifications are needed. Characteristic for comprehensive in contrast to syntactical specifications are the formalization of ontological and behavioral semantics, homogeneity according to a global ontology, and a service grounding that links the abstract service description and its technical realization. Homogeneous, semantical specifications enable to reliably identify reusable services, whereas the service grounding is needed for the technical service integration. In general, comprehensive specifications are not availableand have to be derived. Existing automatized approaches are restricted to certain characteristics of comprehensiveness. In my PhD, I consider an automatized approach to derive fully-fledged comprehensive specifications for black-box services. Ontological semantics are derived from syntactical interface specifications. Behavioral semantics are mined from call logs that cloud vendors create to monitor the hosted services. The specifications are harmonized over a global ontology. The service grounding is established using traceability information. The approach enables third party developers to compose services into complex systems and creates new sales channels for cloud and service providers.</abstract>

<relatedItem type="constituent">
  <location>
    <url displayLabel="217-sig-alternate.pdf">https://ris.uni-paderborn.de/download/217/1516/217-sig-alternate.pdf</url>
  </location>
  <physicalDescription><internetMediaType>application/pdf</internetMediaType></physicalDescription>
</relatedItem>
<originInfo><dateIssued encoding="w3cdtf">2016</dateIssued>
</originInfo>
<language><languageTerm authority="iso639-2b" type="code">eng</languageTerm>
</language>



<relatedItem type="host"><titleInfo><title>Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)</title></titleInfo><identifier type="doi">10.1145/2889160.2889271</identifier>
<part><extent unit="pages">815-818</extent>
</part>
</relatedItem>


<extension>
<bibliographicCitation>
<bibtex>@inproceedings{Schwichtenberg_2016, title={Automatized Derivation of Comprehensive Specifications for Black-box Services}, DOI={&lt;a href=&quot;https://doi.org/10.1145/2889160.2889271&quot;&gt;10.1145/2889160.2889271&lt;/a&gt;}, booktitle={Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)}, author={Schwichtenberg, Simon}, year={2016}, pages={815–818} }</bibtex>
<ama>Schwichtenberg S. Automatized Derivation of Comprehensive Specifications for Black-box Services. In: &lt;i&gt;Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)&lt;/i&gt;. ; 2016:815-818. doi:&lt;a href=&quot;https://doi.org/10.1145/2889160.2889271&quot;&gt;10.1145/2889160.2889271&lt;/a&gt;</ama>
<mla>Schwichtenberg, Simon. “Automatized Derivation of Comprehensive Specifications for Black-Box Services.” &lt;i&gt;Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)&lt;/i&gt;, 2016, pp. 815–18, doi:&lt;a href=&quot;https://doi.org/10.1145/2889160.2889271&quot;&gt;10.1145/2889160.2889271&lt;/a&gt;.</mla>
<short>S. Schwichtenberg, in: Proceedings of the 38th International Conference on Software Engineering Companion (ICSE), 2016, pp. 815–818.</short>
<chicago>Schwichtenberg, Simon. “Automatized Derivation of Comprehensive Specifications for Black-Box Services.” In &lt;i&gt;Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)&lt;/i&gt;, 815–18, 2016. &lt;a href=&quot;https://doi.org/10.1145/2889160.2889271&quot;&gt;https://doi.org/10.1145/2889160.2889271&lt;/a&gt;.</chicago>
<ieee>S. Schwichtenberg, “Automatized Derivation of Comprehensive Specifications for Black-box Services,” in &lt;i&gt;Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)&lt;/i&gt;, 2016, pp. 815–818.</ieee>
<apa>Schwichtenberg, S. (2016). Automatized Derivation of Comprehensive Specifications for Black-box Services. In &lt;i&gt;Proceedings of the 38th International Conference on Software Engineering Companion (ICSE)&lt;/i&gt; (pp. 815–818). &lt;a href=&quot;https://doi.org/10.1145/2889160.2889271&quot;&gt;https://doi.org/10.1145/2889160.2889271&lt;/a&gt;</apa>
</bibliographicCitation>
</extension>
<recordInfo><recordIdentifier>217</recordIdentifier><recordCreationDate encoding="w3cdtf">2017-10-17T12:41:34Z</recordCreationDate><recordChangeDate encoding="w3cdtf">2022-01-06T06:55:11Z</recordChangeDate>
</recordInfo>
</mods>
</modsCollection>
