@Baccthesis{Themessl2013,
  author    = {Patrick Themessl},
  title     = {Incremental Consistency Checking with SPARQL (Bachelor's Thesis)},
  year      = {2013},
  abstract  = {Incremental consistency checking is a method of increasing the performance
	of the evaluation of UML consistency rules at design-time. It works
	by determining and then keeping a list of model elements in memory
	for every consistency rule, the so called change impact scope, and
	re-evaluating the rule only when the user performs a modification
	of one of those model elements in the list. This method has been
	shown to work if the consistency rules are evaluated by an interpreter
	that is under our control so that we can observe their evaluation.
	In this paper we assume the software model to be stored in RDF and
	the consistency rules to be expressed in SPARQL. We develop a method
	to determine the change impact scope by transforming the queries
	in a way that the scope is contained in the result set of the modified
	query. We show that it is possible to port incremental consistency
	checking to systems where the evaluation of consistency rules is
	black-boxed, which renders the previous approach of tracing the execution
	of an (OCL) interpreter inapplicable. Since (legacy) consistency
	rules are typically expressed in OCL, in the second part of this
	paper I am introducing my approach to determine a set of model elements
	that are required to calculate the result of an OCL rule executed
	against a software model stored in RDF in order to allow a pre-fetching
	of those elements in situations where the execution of single SPARQL
	queries comes with a constant, high time penalty.},
  file      = {:BSc Theses\\2013 Patrick Themessl\\Themessl - Incremental Consistency Checking with SPARQL-preprint.pdf:PDF},
  owner     = {AK117794},
  timestamp = {2015.09.21},
}