
<mods xmlns="http://www.loc.gov/mods/v3" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-4.xsd">
    
    <titleInfo>
        <title>End-User Regression Testing for Privacy</title>
    </titleInfo>
    <name type="personal" ID="sks2142">
        <namePart type="family">Sheth</namePart>
        <namePart type="given">Swapneel Kalpesh</namePart>
        <role>
            <roleTerm type="text">author</roleTerm>
        </role>
        <affiliation>Columbia University. Computer Science</affiliation>
    </name>
    <name type="personal" ID="gek1">
        <namePart type="family">Kaiser</namePart>
        <namePart type="given">Gail E.</namePart>
        <role>
            <roleTerm type="text">author</roleTerm>
        </role>
        <affiliation>Columbia University. Electrical Engineering</affiliation>
    </name>
    <name type="corporate">
        <namePart>Columbia University. Computer Science</namePart>
        <role>
            <roleTerm type="text">originator</roleTerm>
        </role>
        <role>
            <roleTerm type="text">contributor</roleTerm>
        </role>
    </name>
    <typeOfResource>text</typeOfResource>
    <genre>Technical reports</genre>
    
    <originInfo>
        <place>
            <placeTerm type="text">New York</placeTerm>
        </place>
        <publisher>Department of Computer Science, Columbia University</publisher>
        <dateIssued encoding="w3cdtf" keyDate="yes">2012</dateIssued>
    </originInfo>
    <abstract>Privacy in social computing systems has become a major concern. End-users of such systems find it increasingly hard to understand complex privacy settings. As software evolves over time, this might introduce bugs that breach users&apos; privacy. Further, there might be system-wide policy changes that could change users&apos; settings to be more or less private than before. We present a novel technique that can be used by end-users for detecting changes in privacy, i.e., regression testing for privacy. Using a social approach for detecting privacy bugs, we present two prototype tools. Our evaluation shows the feasibility and utility of our approach for detecting privacy bugs. We highlight two interesting case studies on the bugs that were discovered using our tools. To the best of our knowledge, this is the first technique that leverages regression testing for detecting privacy bugs from an end-user perspective.</abstract>
    <subject>
        <topic>Computer science</topic>
    </subject>
    <relatedItem type="series" ID="r.1">
        <titleInfo>
            <title>Columbia University Computer Science Technical Reports</title>
            <partNumber>CUCS-015-12</partNumber>
        </titleInfo>
    </relatedItem>
    <relatedItem>
        <location>
            <url></url>
        </location>
    </relatedItem>
    <identifier type="hdl">http://hdl.handle.net/10022/AC:P:14776</identifier>

    <language>
        <languageTerm type="text">English</languageTerm>
    </language>
    
    <location>
        <physicalLocation authority="marcorg">NNC</physicalLocation>
    </location>
    
    <recordInfo>
        <recordContentSource authority="marcorg">NNC</recordContentSource>
        <recordCreationDate encoding="w3cdtf">2012-09-26 13:43:57 -0400</recordCreationDate>
        <recordChangeDate encoding="w3cdtf">2012-09-26 13:48:02 -0400</recordChangeDate>
        <recordIdentifier>8784</recordIdentifier>
        <languageOfCataloging>
            <languageTerm authority="iso639-2b">eng</languageTerm>
        </languageOfCataloging>
    </recordInfo>
    
</mods>
