<?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:cvs-server:2002</b:Tag>
<b:SourceType>BookSection</b:SourceType>
<b:City>Augsburg</b:City>
<b:Year>2002</b:Year>
<b:Month>jul</b:Month>
<b:ConferenceName>FM-TOOLS 2002</b:ConferenceName>
<b:Pages>47-52</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>Rittinger</b:Last><b:First>Frank</b:First></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>Haneberg</b:Last><b:First>Dominik</b:First></b:Person>
<b:Person><b:Last>Schellhorn</b:Last><b:First>Gerhard</b:First></b:Person>
<b:Person><b:Last>Reif</b:Last><b:First>Wolfgang</b:First></b:Person>
</b:NameList></b:Editor>
</b:Author>
<b:Title>The CVS-Server Case Study: A Formalized Security Architecture</b:Title>
<b:Comments>CVS is a widely known version management system. Configured in server mode, it can be used for the distributed development of software as well as its distribution from a central database called the repository. In this setting, a number of security mechanisms have to be integrated into the CVS-server architecture. We present an abstract formal model of the access control aspects of a CVS-server architecture enforcing a role-based access control on the data in the repository. This abstract architecture is refined to an implementation architecture, which represents (an abstraction of) a concrete CVS-server configuration running in a POSIX/UNIX environment. Both the abstract as well as the concrete architecture are specified in the language Z. The specification is compiled to HOL-Z, such that refinement proofs for this case study can be done in Isabelle/HOL.</b:Comments>
</b:Source>
</b:Sources>

