<?xml version="1.0" encoding="UTF-8"?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-08-14T23:53:08Z</responseDate>
  <request identifier="811" metadataPrefix="oai_dc" verb="GetRecord">https://drops.dagstuhl.de/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:drops-oai.dagstuhl.de:811</identifier>
        <datestamp>2024-03-06T10:28:19Z</datestamp>
        <setSpec>ddc:004</setSpec>
        <setSpec>open_access</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Experiences from Industrial WCET Analysis Case Studies</dc:title>
          <dc:creator>Ermedahl, Andreas</dc:creator>
          <dc:creator>Gustafsson, Jan</dc:creator>
          <dc:creator>Lisper, Björn</dc:creator>
          <dc:description>Static Worst-Case Execution Time (WCET) analysis&#13;
is currently taking a step from research to industrial&#13;
use. We present a summary of three case studies&#13;
where static WCET analysis has been used to analyse&#13;
production code for embedded real-time systems. The&#13;
primary purpose has not been to test the accuracy of&#13;
the obtained WCET estimates, but rather to investigate&#13;
the practical and methodological difficulties that&#13;
arise when applying current WCET analysis methods&#13;
to these particular kind of systems.&#13;
In particular, we have been interested in how laborintensive&#13;
the analysis becomes, for instance by estimating&#13;
the efforts to study the analysed code in detail, and&#13;
measuring the number of manual annotations necessary&#13;
to perform the analysis. From these observations, we&#13;
draw some conclusions about what would be needed to&#13;
turn static WCET analysis into a useful tool for embedded&#13;
and real-time systems software development.</dc:description>
          <dc:publisher>Schloss Dagstuhl – Leibniz-Zentrum für Informatik</dc:publisher>
          <dc:contributor>Andreas Ermedahl and Jan Gustafsson and Björn Lisper</dc:contributor>
          <dc:date>2007</dc:date>
          <dc:relation>Is Part Of OASIcs, Volume 1, 5th International Workshop on Worst-Case Execution Time Analysis (WCET'05) (2007)</dc:relation>
          <dc:type>InProceedings</dc:type>
          <dc:type>Text</dc:type>
          <dc:type>doc-type:ResearchArticle</dc:type>
          <dc:type>publishedVersion</dc:type>
          <dc:format>application/pdf</dc:format>
          <dc:identifier>doi:10.4230/OASIcs.WCET.2005.811</dc:identifier>
          <dc:identifier>urn:nbn:de:0030-drops-8118</dc:identifier>
          <dc:identifier>https://drops.dagstuhl.de/entities/document/10.4230/OASIcs.WCET.2005.811</dc:identifier>
          <dc:language>eng</dc:language>
          <dc:rights>https://creativecommons.org/licenses/by-nc-nd/3.0/legalcode</dc:rights>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
