English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Current day software development relies heavily on the use of servicearchitectures and on agile iterative development methods to design, implement,and deploy systems. These practices result in systems made up of multipleservices that introduce new data flows and evolving designs that escape thecontrol of a single designer. Academic privacy engineering literature typicallyabstracts away such conditions of software production in order to achievegeneralizable results. Yet, through a systematic study of the literature, weshow that proposed solutions inevitably make assumptions about softwarearchitectures, development methods and scope of designer control that aremisaligned with current practices. These misalignments are likely to pose anobstacle to operationalizing privacy engineering solutions in the wild.Specifically, we identify important limitations in the approaches thatresearchers take to design and evaluate privacy enhancing technologies whichripple to proposals for privacy engineering methodologies. Based on ouranalysis, we delineate research and actions needed to re-align research withpractice, changes that serve a precondition for the operationalization ofacademic privacy results in common software engineering practices.

Privacy Engineering Meets Software Engineering. On the Challenges of Engineering Privacy ByDesign