<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM10Schaefer</id>
	<title>WG211/M10Schaefer - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM10Schaefer"/>
	<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M10Schaefer&amp;action=history"/>
	<updated>2026-04-05T20:55:54Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>http://mw.hh.se/wg211/index.php?title=WG211/M10Schaefer&amp;diff=53&amp;oldid=prev</id>
		<title>Admin: 1 revision</title>
		<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M10Schaefer&amp;diff=53&amp;oldid=prev"/>
		<updated>2011-12-12T10:06:24Z</updated>

		<summary type="html">&lt;p&gt;1 revision&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Category:WG211]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;strong&amp;gt;Deductive Verification of Software Product Lines&amp;lt;/strong&amp;gt; by Ina Schaefer&lt;br /&gt;
&lt;br /&gt;
A software product line consists is a family of program variants that &amp;lt;br /&amp;gt;are developed from a common code base. In particular, for &amp;lt;br /&amp;gt;safety-critical or business-critical applications, product quality and &amp;lt;br /&amp;gt;correctness has to be rigorously ensured. Analyzing each product variant &amp;lt;br /&amp;gt;in isolation is in general infeasible, since the number of product &amp;lt;br /&amp;gt;variants is exponential in the number of product features.&amp;lt;br /&amp;gt;&amp;lt;br /&amp;gt;In my talk, I present efficient deductive program verification &amp;lt;br /&amp;gt;techniques for delta-oriented software product lines. Delta-oriented &amp;lt;br /&amp;gt;programming is a modular, yet flexible way to describe a family of &amp;lt;br /&amp;gt;program variants. Besides type-safety of delta-oriented product lines, &amp;lt;br /&amp;gt;our verification techniques consider functional correctness properties &amp;lt;br /&amp;gt;specified using design-by-contract. If product variability is restricted &amp;lt;br /&amp;gt;suitably, compositional family-based verification can establish &amp;lt;br /&amp;gt;correctness of all product variants by analyzing the product line code &amp;lt;br /&amp;gt;base only once. Without any restrictions on product variability, &amp;lt;br /&amp;gt;incremental product-based verification techniques reduce verification &amp;lt;br /&amp;gt;effort by progressing from one verified program variant to the next. In &amp;lt;br /&amp;gt;between both extrems, constraint-based verification techniques provide a &amp;lt;br /&amp;gt;compromise between the family-based and product-based verification &amp;lt;br /&amp;gt;approaches and allow relaxing the restrictions on the admissible product &amp;lt;br /&amp;gt;variability.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>