<?xml version="1.0" encoding="UTF-8"?>
<b:Sources SelectedStyle="" xmlns:b="http://schemas.openxmlformats.org/officeDocument/2006/bibliography"  xmlns="http://schemas.openxmlformats.org/officeDocument/2006/bibliography" >
<b:Source>
<b:Tag>brucker.ea:ocl-null:2009</b:Tag>
<b:SourceType>BookSection</b:SourceType>
<b:City>Heidelberg</b:City>
<b:Publisher>Springer-Verlag</b:Publisher>
<b:Year>2009</b:Year>
<b:ConferenceName>Models in Software Engineering</b:ConferenceName>
<b:Issue>6002</b:Issue>
<b:Pages>261-275</b:Pages>
<b:Author>
<b:Author><b:NameList>
<b:Person><b:Last>Brucker</b:Last><b:First>Achim</b:First><b:Middle>D</b:Middle></b:Person>
<b:Person><b:Last>Krieger</b:Last><b:First>Matthias</b:First><b:Middle>P</b:Middle></b:Person>
<b:Person><b:Last>Wolff</b:Last><b:First>Burkhart</b:First></b:Person>
</b:NameList></b:Author>
<b:Editor><b:NameList>
<b:Person><b:Last>Gosh</b:Last><b:First>Sudipto</b:First></b:Person>
</b:NameList></b:Editor>
</b:Author>
<b:Title>Extending OCL with Null-References</b:Title>
<b:Comments>From its beginnings, OCL is based on a strict semantics for undefinedness, with the exception of the logical connectives of type Boolean that constitute a three-valued propositional logic. Recent versions of the OCL standard added a second exception element, which, similar to the null references in object-oriented programming languages, is given a non-strict semantics. Unfortunately, this extension has been done in an ad hoc manner, which results in several inconsistencies and contradictions. In this paper, we present a consistent formal semantics (based on our HOL-OCL approach) that includes such a non-strict exception element. We discuss the possible consequences concerning class diagram semantics as well as deduction rules. The benefits of our approach for the specification-pragmatics of design level operation contracts are demonstrated with a small case-study.</b:Comments>
</b:Source>
</b:Sources>

