Privacy Requirements: Findings and Lessons Learned in Developing a Privacy Platform

Information practices and systems that make use of personal and health-related information are governed by European laws and regulations to prevent unauthorized use and disclosure. Failure to comply with these laws and regulations results in huge monetary sanctions, which both private companies and public administrations want to avoid. How to comply with these laws, requires understanding the privacy requirements imposed on information systems. A holistic approach to privacy requirements specification calls for understanding not only the requirements derived from law, but also citizens' needs with respect to privacy. In this paper, we report on our experience in conducting privacy requirements engineering as part of a H2020 European Project, namely VisiOn (Visual Privacy Management in User Centric Open Requirements) for the development of a privacy platform to improve the interaction between Public Administrations (PA) and citizens, while guarding the privacy of the latter. Specifically, we present the process for eliciting, classifying, prioritizing, and validating privacy requirements for the two types of users, namely PA and citizen. The process is applied to different cases spanning from healthcare to other e-governmental initiatives, with the active involvement of the corresponding PAs. We report on findings and lessons learned from this experience.

[1]  Agusti Solanas,et al.  The pursuit of citizens' privacy: a privacy-aware smart city is possible , 2013, IEEE Communications Magazine.

[2]  Haralambos Mouratidis,et al.  Secure Tropos: a Security-Oriented Extension of the Tropos Methodology , 2007, Int. J. Softw. Eng. Knowl. Eng..

[3]  Rebecca Herold,et al.  HIPAA Privacy Rule , 2014 .

[4]  Stefanos Gritzalis,et al.  Addressing privacy requirements in system design: the PriS method , 2008, Requirements Engineering.

[5]  A. Cavoukian Privacy by Design: Origins, Meaning, and Prospects for Assuring Privacy and Trust in the Information Era , 2012 .

[6]  Zahir Irani,et al.  E-government adoption: architecture and barriers , 2005, Bus. Process. Manag. J..

[7]  A. Herrmann,et al.  Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[8]  Nicolas Mayer,et al.  Model-based Management of Information System Security Risk , 2012 .

[9]  Ian Sommerville,et al.  Software Engineering, 8. Auflage , 2007, it : Informatik.

[10]  Lorrie Faith Cranor,et al.  Engineering Privacy , 2009, IEEE Transactions on Software Engineering.

[11]  Gan Wang,et al.  Reuse in Systems Engineering , 2010, IEEE Systems Journal.

[12]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[13]  Anthony Finkelstein,et al.  Proceedings of the Conference on The Future of Software Engineering , 2000, ICSE 2000.

[14]  Nicola Zannone A requirements engineering methodology for trust, security, and privacy , 2007 .

[15]  A. Andrews,et al.  4 Requirements Prioritization , .

[16]  Didar Zowghi,et al.  Requirements Elicitation: A Survey of Techniques, Approaches, and Tools , 2005 .

[17]  K. Pripuzic,et al.  Implementing web-surveys for software requirements elicitation , 2005, Proceedings of the 8th International Conference on Telecommunications, 2005. ConTEL 2005..

[18]  R. P. Srivastava,et al.  A conceptual framework and belief‐function approach to assessing overall information quality , 2003, Int. J. Intell. Syst..

[19]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[20]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[21]  Richard Y. Wang,et al.  Data quality assessment , 2002, CACM.

[22]  Benjamin Gerber,et al.  Conceptualizing privacy , 2010, CSOC.

[23]  Annie I. Antón,et al.  Analyzing Regulatory Rules for Privacy and Security Requirements , 2008, IEEE Transactions on Software Engineering.

[24]  Markus Helfert,et al.  Proactive data quality management for data warehouse systems , 2002, DMDW.

[25]  Alessandro Acquisti,et al.  Is There a Cost to Privacy Breaches? An Event Study , 2006, WEIS.

[26]  Claes Wohlin,et al.  Requirements Engineering: Setting the Context , 2005 .

[27]  Paolo Giorgini,et al.  Modelling and reasoning about security requirements in socio-technical systems , 2015, Data Knowl. Eng..

[28]  Ashish Garg,et al.  Quantifying the financial impact of IT security breaches , 2003, Inf. Manag. Comput. Secur..

[29]  Paolo Giorgini,et al.  Modeling and Reasoning About Information Quality Requirements , 2015, REFSQ.

[30]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[31]  A. Terry Bahill,et al.  Requirements development, verification, and validation exhibited in famous failures , 2005, Syst. Eng..

[32]  Michael Jackson,et al.  The World and the Machine , 1995, 1995 17th International Conference on Software Engineering.