Metrics for Transparency

Transparency is a novel non-functional requirement for software systems. It is acclaimed to improve the quality of service since it gives users access to information concerning the system’s processes, clarifying who is responsible if something goes wrong. Thus, it is believed to support people’s right to a secure and private processing of their personal data. We define eight quality metrics for transparency and we demonstrate the usage and the effectiveness of the metrics by assessing transparency on the Microsoft HealthVault, an on-line platform for users to collect, store, and share medical records.

[1]  C. Zarcadoolas,et al.  The simplicity complex: exploring simplified health messages in a complex world. , 2011, Health promotion international.

[2]  Joseph R. Spiegel,et al.  Readability analysis of patient information on the American Academy of Otolaryngology–Head and Neck Surgery website , 2009, Otolaryngology--head and neck surgery : official journal of American Academy of Otolaryngology-Head and Neck Surgery.

[3]  Eric Bauer,et al.  Reliability and Availability of Cloud Computing: Bauer/Cloud Computing , 2012 .

[4]  Norman F. Schneidewind,et al.  Methodology For Validating Software Metrics , 1992, IEEE Trans. Software Eng..

[5]  Martin Glinz,et al.  On Non-Functional Requirements , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[6]  David R. Hansberry,et al.  Readability Assessment of Patient Education Materials on Major Otolaryngology Association Websites , 2012, Otolaryngology--head and neck surgery : official journal of American Academy of Otolaryngology-Head and Neck Surgery.

[7]  Gabriele Lenzini,et al.  Patient-Centred Transparency Requirements for Medical Data Sharing Systems , 2016, WorldCIST.

[8]  Carlo Batini,et al.  Information Systems for eGovernment - A Quality-of-Service Perspective , 2010 .

[9]  Cem Kaner,et al.  Software Engineering Metrics: What Do They Measure and How Do We Know? , 2004 .

[10]  Stefan Berthold,et al.  Crime and Punishment in the Cloud Accountability, Transparency, and Privacy , 2013 .

[11]  Victor R. Basili,et al.  Identifying and qualifying reusable software components , 1991, Computer.

[12]  Martin Cutts.  Oxford Guide to Plain English , 2004 .

[13]  Jean Anderson Eloy,et al.  Readability Assessment of Patient Education Materials from the American Academy of Otolaryngology—Head and Neck Surgery Foundation , 2012, Otolaryngology--head and neck surgery : official journal of American Academy of Otolaryngology-Head and Neck Surgery.

[14]  Eric Bauer,et al.  Reliability and Availability of Cloud Computing , 2012 .

[15]  Bruce McMillin,et al.  Software engineering: What is it? , 2018, 2018 IEEE Aerospace Conference.

[16]  Paul W. Oman,et al.  Using metrics to evaluate software system maintainability , 1994, Computer.

[17]  Rudolf Franz Flesch.  How to Write Plain English , 1981 .

[18]  Norman F. Schneidewind,et al.  IEEE Standard For A Software Quality Metrics Methodology Revision And Reaffirmation , 1997, Proceedings of IEEE International Symposium on Software Engineering Standards.

[19]  Lothar Litz,et al.  A measure for transparency in net based control algorithms , 1999, IEEE SMC'99 Conference Proceedings. 1999 IEEE International Conference on Systems, Man, and Cybernetics (Cat. No.99CH37028).

[20]  Julio Cesar Sampaio do Prado Leite,et al.  Software Transparency , 2010, Bus. Inf. Syst. Eng..

[21]  Barry P. Mulcahy,et al.  Trust-terms ontology for defining security requirements and metrics , 2010, ECSA '10.

[22]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[23]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[24]  Tony Gorschek,et al.  Quality Requirements in Practice: An Interview Study in Requirements Engineering for Embedded Systems , 2009, REFSQ.