國立虎尾科技大學 |

Problem-Based Privacy Analysis (ProPAn) : = A Computer-aided Privacy Requirements Engineering Method.

Record Type:	Language materials, manuscript : Monograph/item
Title/Author:	Problem-Based Privacy Analysis (ProPAn) :/
Reminder of title:	A Computer-aided Privacy Requirements Engineering Method.
Author:	Meis, Rene.
Description:	1 online resource (509 pages)
Notes:	Source: Dissertations Abstracts International, Volume: 80-08, Section: B.
Contained By:	Dissertations Abstracts International80-08B.
Subject:	Computer engineering. -
Online resource:	click for full text (PQDT)
ISBN:	9781392778708

Problem-Based Privacy Analysis (ProPAn) : = A Computer-aided Privacy Requirements Engineering Method.
Meis, Rene.

Problem-Based Privacy Analysis (ProPAn) :A Computer-aided Privacy Requirements Engineering Method. - 1 online resource (509 pages)

Source: Dissertations Abstracts International, Volume: 80-08, Section: B.

Thesis (Ph.D.)--Universitaet Duisburg-Essen (Germany), 2018.

Includes bibliographical references

With the advancing digitalization in almost all parts of our daily life, e.g., electronic health records and smart homes, and the outsourcing of data processing, e.g., data storage in the cloud and data analysis services, computer-based systems process more and more data these days. Often the processed data originate from natural persons (called data subjects) and are hence personal data possibly containing sensitive information about the individuals. Privacy in the context of personal data processing means that personal data are protected, e.g., against unwanted access and modification, that data subjects are aware about the processing practices of the controller that processes their data, and that data subjects keep control over the processing of their personal data. Privacy regulations, such as the EU GeneralData Protection Regulation (GDPR), aim at protecting data subjects by empowering them with rights and by putting obligations on controllers processing personal data. Not only administrative fines defined in regulations are a driver for the consideration of privacy in the development of a software-based system, also several data breaches occurred in the last years have shown that a poor consideration of privacy during the system and software development mayultimately lead to a loss of trust in and reputation of the controller. To avoid the occurrence of data breaches and to be compliant with privacy regulations, privacy should to be considered in system and software development as a software quality from the beginning. This approach is also known as privacy-by-design. There are several challenges for privacy-by-design methods that are still not fully addressed by existing methods. First, diverse notions of privacy exist. Most of these privacy notions are non-technical and have to berefined to more technical privacy requirements that can be related to the system. Second, the system has to be analyzed for its personal data processing behavior. That is, it has to be determined which personal data are collected, stored, and provided to others by the system. Third, the privacy requirements have to be elicited that are actually relevant for the system. Fourth, the privacy risks imposed by or existing in the system have to be identified and evaluated. Fifth, measures that implement the privacy requirements and mitigatethe privacy risks of the system have to be selected and integrated into the system. Sixth, privacy regulations mandate to assess the impact of the personal data processing on the data subjects. Such a privacy impact assessment (PIA) may be performed as part of a privacy-by-design method. Seventh, the conduction of a privacy-by-design method should be supported as good as possible, e.g., by asystematic method, supportive material, and computer support. In this thesis, I propose the privacy requirements engineering method Problem-based Privacy Analysis (ProPAn). The ProPAn method aims to address the aforementioned challenges starting with a system's functional requirements as input. As part of ProPAn, I provide a privacy requirements taxonomy that I derived from and mapped to various other privacy notions. This privacy requirements taxonomy addresses the first challenge mentioned above. The ProPAnmethod is the main contribution of my thesis and addresses the second to seventh challenge mentioned above. To address the fifth challenge in the ProPAn method, I propose an aspect-oriented requirements engineering framework that allows to modelcross-cutting functionalities and to modularly integrate them into a system's functional requirements. The seventh challenge is addressed by ProPAn's computer support for the execution of the method and the documentation and validation of the method's artifacts in a machine-readable model.

Electronic reproduction.
Ann Arbor, Mich. :
ProQuest,
2024

Mode of access: World Wide Web

ISBN: 9781392778708Subjects--Topical Terms:

569006
Computer engineering.
Subjects--Index Terms:

PrivacyIndex Terms--Genre/Form:

554714
Electronic books.

Problem-Based Privacy Analysis (ProPAn) : = A Computer-aided Privacy Requirements Engineering Method.
LDR:09536ntm a22003977 4500 001 1143940
005 20240531084149.5
006 m o d
007 cr mn ---uuuuu
008 250605s2018 xx obm 000 0 eng d
020 $a 9781392778708
035 $a (MiAaPQ)AAI13844395
035 $a (MiAaPQ)Duisburg_00047797
035 $a AAI13844395
040 $a MiAaPQ $b eng $c MiAaPQ $d NTU
100 1 $a Meis, Rene. $3 1468758
245 1 0 $a Problem-Based Privacy Analysis (ProPAn) : $b A Computer-aided Privacy Requirements Engineering Method.
264 0 $c 2018
300 $a 1 online resource (509 pages)
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
500 $a Source: Dissertations Abstracts International, Volume: 80-08, Section: B.
500 $a Advisor: Heisel, Maritta.
502 $a Thesis (Ph.D.)--Universitaet Duisburg-Essen (Germany), 2018.
504 $a Includes bibliographical references
520 $a With the advancing digitalization in almost all parts of our daily life, e.g., electronic health records and smart homes, and the outsourcing of data processing, e.g., data storage in the cloud and data analysis services, computer-based systems process more and more data these days. Often the processed data originate from natural persons (called data subjects) and are hence personal data possibly containing sensitive information about the individuals. Privacy in the context of personal data processing means that personal data are protected, e.g., against unwanted access and modification, that data subjects are aware about the processing practices of the controller that processes their data, and that data subjects keep control over the processing of their personal data. Privacy regulations, such as the EU GeneralData Protection Regulation (GDPR), aim at protecting data subjects by empowering them with rights and by putting obligations on controllers processing personal data. Not only administrative fines defined in regulations are a driver for the consideration of privacy in the development of a software-based system, also several data breaches occurred in the last years have shown that a poor consideration of privacy during the system and software development mayultimately lead to a loss of trust in and reputation of the controller. To avoid the occurrence of data breaches and to be compliant with privacy regulations, privacy should to be considered in system and software development as a software quality from the beginning. This approach is also known as privacy-by-design. There are several challenges for privacy-by-design methods that are still not fully addressed by existing methods. First, diverse notions of privacy exist. Most of these privacy notions are non-technical and have to berefined to more technical privacy requirements that can be related to the system. Second, the system has to be analyzed for its personal data processing behavior. That is, it has to be determined which personal data are collected, stored, and provided to others by the system. Third, the privacy requirements have to be elicited that are actually relevant for the system. Fourth, the privacy risks imposed by or existing in the system have to be identified and evaluated. Fifth, measures that implement the privacy requirements and mitigatethe privacy risks of the system have to be selected and integrated into the system. Sixth, privacy regulations mandate to assess the impact of the personal data processing on the data subjects. Such a privacy impact assessment (PIA) may be performed as part of a privacy-by-design method. Seventh, the conduction of a privacy-by-design method should be supported as good as possible, e.g., by asystematic method, supportive material, and computer support. In this thesis, I propose the privacy requirements engineering method Problem-based Privacy Analysis (ProPAn). The ProPAn method aims to address the aforementioned challenges starting with a system's functional requirements as input. As part of ProPAn, I provide a privacy requirements taxonomy that I derived from and mapped to various other privacy notions. This privacy requirements taxonomy addresses the first challenge mentioned above. The ProPAnmethod is the main contribution of my thesis and addresses the second to seventh challenge mentioned above. To address the fifth challenge in the ProPAn method, I propose an aspect-oriented requirements engineering framework that allows to modelcross-cutting functionalities and to modularly integrate them into a system's functional requirements. The seventh challenge is addressed by ProPAn's computer support for the execution of the method and the documentation and validation of the method's artifacts in a machine-readable model.
520 $a Mit der fortschreitenden Digitalisierung in beinah allen Bereichen unseres taglichen Lebens, z.B. elektronische Patientenakten und Smart Homes, und dem Outsourcing von Datenverarbeitung, z.B. Datenspeicherung in der Cloud und Datenanalysediensten, verarbeiten computerbasierte Systeme immer mehr Daten. Haufig stammen die verarbeiteten Daten von naturlichen Personen (betroffenen Personen) und sind daher personenbezogene Daten, die moglicherweisesensible Informationen uber die einzelnen Personen enthalten. ImKontext der Verarbeitung personenbezogener Daten heist Privacy, dass personenbezogene Daten geschutzt werden, z.B. gegen ungewollten Zugriff und Anderung, dass betroffene Personen sich uber die Verarbeitung der personenbezogenen Daten bewusst sind, und dass die betroffenen Personen die Kontrolle uber die Verarbeitung ihrer Daten behalten. Datenschutzregularien,wie die EU Datenschutz-Grundverordnung (DSGVO), verfolgen das Ziel betroffene Personen zu starken, indem ihnen Rechte gegeben werden, und Verantwortlichen, die personenbezogene Daten verarbeiten, Pflichten auferlegt werden. Nicht nur Geldbusen, die in Regularien definiert sind, sind ein Treiber fur die Berucksichtigung von Privacy bei der Entwicklung von softwarebasierten System, auch einige Verletzungen des Schutzes personenbezogener Daten in den letztenJahren haben gezeigt, dass eine unzureichende Berucksichtigung von Privacy wahrend der System- und Softwareentwicklung letztlich zu einem Verlust von Vertrauen in den Verantwortlichen und dessen Ansehen fuhren konnen. Um Verletzungen des Schutzes personenbezogener Daten zu vermeiden und konform zu Datenschutzregularien zu sein, sollte Privacy von Anfang an wahrend der System- und Softwareentwicklung als Softwarequalitat berucksichtigt werden. Dieser Ansatz ist auch als Privacy-by-Design bekannt. Es gibt einige Herausforderung fur Privacy-by-Design-Methoden, die noch nicht vollstandig von existierenden Methoden adressiert werden. Erstens gibt es verschiedenstePrivacybegriffe. Die meisten dieser Begriffe sind nicht-technisch und mussen zu technischeren Privacyanforderungen verfeinert werden, die zu dem System in Bezug gesetzt werden konnen. Zweitens muss das System bezuglicher seiner Verarbeitung von personenbezogenen Daten untersucht werden. Das heist, dass festgestellt werdenmuss, welche personenbezogenen Daten vom System gesammelt, gespeichert, und an Andere weitergegeben werden. Drittens mussen die Privacyanforderungen erhoben werden, die tatsachlich fur das System relevant sind. Viertens mussen die Risiken bezuglich Privacy, die das System verursacht oder beinhaltet, identifiziert und evaluiert werden. Funftens, mussen Masnahmen, die Privacyanforderungen implementieren und Risiken bezuglich Privacy reduzieren, ausgewahlt und in das System integriert werden. Sechstens schreiben Datenschutzregularien vor, die Folgen der Verarbeitung personenbezogener Daten auf die betroffenen Personen zu untersuchen. Eine solche Datenschutz-Folgenabschatzung kann als Teil einer Privacy-by-Design-Methode durchgefuhrt werden. Siebtens sollte die Durchfuhrung einer Privacy-by-Design-Methode so gut wie moglich unterstutzt werden, z.B. durch eine systematische Methode, unterstutzendes Material, und Computerunterstutzung. In meiner Dissertation stelle ich die Anforderungsanalysemethode Problembasierte Privacy Analyse (ProPAn) vor, in der die Berucksichtigung von Privacy integriert ist. Die ProPAn-Methode verfolgt das Ziel, die zuvor genannten Herausforderungen zu adressieren, beginnend mit den funktionalen Anforderungen des Systems als Eingabe. Als Teil der ProPAn-Methode stelle icheine Privacyanforderungstaxonomie bereit, die ich aus verschiedenenPrivacybegriffen abgeleitet habe und zu diesen in Beziehungsetze. Die ProPAn-Methode ist der Hauptbeitrag meiner Dissertation und adressiert die zweite bis siebte zuvor genannte Herausforderung. Um die funfte Herausforderung zu adressieren, prasentiere ich ein aspektorientiertes Anforderungsanalyseframework, das es erlaubt Querschnittsanforderungen zu modellieren und modular in die funktionalen Anforderungen eines Systems zu integrieren. Die siebte Herausforderung wird von ProPAns Computerunterstutzungfur die Anwendung der Methode, und der Dokumentation und Validierung der Methodenartefakte in einem maschinenlesbaren Modells adressiert.
533 $a Electronic reproduction. $b Ann Arbor, Mich. : $c ProQuest, $d 2024
538 $a Mode of access: World Wide Web
650 4 $a Computer engineering. $3 569006
650 4 $a Computer science. $3 573171
650 4 $a Information science. $3 561178
653 $a Privacy
653 $a Requirements
653 $a Engineering
655 7 $a Electronic books. $2 local $3 554714
690 $a 0984
690 $a 0464
690 $a 0723
710 2 $a ProQuest Information and Learning Co. $3 1178819
710 2 $a Universitaet Duisburg-Essen (Germany). $3 1468759
773 0 $t Dissertations Abstracts International $g 80-08B.
856 4 0 $u http://pqdd.sinica.edu.tw/twdaoapp/servlet/advanced?query=13844395 $z click for full text (PQDT)