Dipl.-Inform. Rene Meis
Room BB 918
Tel. : +49 203 379 4503
Fax : +49 203 379 4490
E-Mail : rene.meis[at]uni-due.de

QuickSearch:   Number of matching entries: 0.

YearTitleAuthorJournal/ProceedingsPublisher
2016 Supporting Privacy Impact Assessments using Problem-based Privacy Analysis Meis, R. & Heisel, M. Software Technologies - 10th International Joint Conference, ICSOFT 2015, Revised Selected Papers   Springer  
Abstract: Privacy-aware software development is gaining more and more importance for nearly all information systems that are developed nowadays. As a tool to force organizations and companies to consider privacy properly during the planning and the execution of their projects, some governments advise to perform privacy impact assessments (PIAs). During a PIA, a report has to be created that summarizes the consequence on privacy the project may have and how the organization or company addresses these consequences. As basis for a PIA, it has to be documented which personal data is collected, processed, stored, and shared with others in the context of the project. Obtaining this information is a difficult task that is not yet well supported by existing methods. In this paper, we present a method based on the problem-based privacy analysis (ProPAn) that helps to elicit the needed information for a PIA systematically from a given set of functional requirements. Our tool-supported method shall reduce the effort that has to be spent to elicit the information needed to conduct a PIA in a way that the information is as complete and consistent as possible.
BibTeX:
@inproceedings{CCIS16,
  year = {2016},
  title = {Supporting Privacy Impact Assessments using Problem-based Privacy Analysis},
  booktitle = {Software Technologies - 10th International Joint Conference, {ICSOFT} 2015, Revised Selected Papers},
  author = {Meis, Rene and Heisel, Maritta},
  publisher = {Springer},
  volume = {586},
  series = {Communications in Computer and Information Science},
  pages = {79--98},
  url = {http://dx.doi.org/10.1007/978-3-319-30142-6_5},
  doi = {10.1007/978-3-319-30142-6_5}
}
2016 The Six-Variable Model - Context Modelling Enabling Systematic Reuse of Control Software Ulfat-Bunyadi, N., Meis, R. & Heisel, M. Proceedings of the 11th International Joint Conference on Software Technologies (ICSOFT 2016)   SciTePress  
Abstract: A control system usually consists of some control software as well as sensors and actuators to monitor and control certain quantities in the environment. The context of the control software thus consists of the sensors and actuators it uses and the environment. When starting development of the control software, its context is often not predefined or given. There are contextual decisions the developers can make (e.g. which sensors/actuators/other systems to use). By means of these decisions, the context is defined step by step. Existing approaches (like the Four-Variable Model) call for documenting the environmental quantities (monitored, controlled, input, and output variables) that are relevant after making these contextual decisions. The environmental quantities that have originally been relevant (i.e. before deciding which sensors/actuators/other systems to use) are not documented. This results in problems when the software shall later on be reused in another, slightly different setting (e.g. with additional sensors). Then, it is hard for developers to decide which environmental quantities are still relevant for the software. In this paper, we suggest an extended version of the Four-Variable Model, the Six-Variable Model, and, based on that, a context modelling method, that combines existing approaches. The benefit of our method is that the environmental quantities that are relevant before and after decision making are documented as well as the contextual decisions themselves and the options that were selectable. In this way, later reuse of the software is facilitated.
BibTeX:
@inproceedings{ICSOFT16a,
  year = {2016},
  title = {The Six-Variable Model - Context Modelling Enabling Systematic Reuse of Control Software},
  booktitle = {Proceedings of the 11th International Joint Conference on Software Technologies {(ICSOFT} 2016)},
  author = {Ulfat-Bunyadi, Nelufar and Meis, Rene and Heisel, Maritta},
  publisher = {SciTePress},
  pages = {15--26},
  url = {http://dx.doi.org/10.5220/0005944100150026},
  doi = {10.5220/0005944100150026}
}
2016 Introducing Product Line Engineering in a Bottom-up Approach Ulfat-Bunyadi, N., Meis, R., Mohammadi, N. G. & Heisel, M. Proceedings of the 11th International Joint Conference on Software Technologies (ICSOFT 2016)   SciTePress  
Abstract: The optimal way for introducing a product line is to set up a completely new product line by developing a reuse infrastructure for the whole range of products right from the start. However, in practice, product line engineering is frequently introduced by a company after having developed a number of products separately (i.e. in single system engineering). The challenge then consists of defining the product line based on these existing products, i.e. to a certain extent these products have to be re-engineered. More precisely, two problems need to be solved: first, commonality and variability among the existing products needs to be identified to define a common set of core assets, and, second, the way in which future systems (i.e. products of the product line) will be developed based on this common set of assets needs to be defined. The method we suggest in this paper solves these two problems. Our method focuses on control systems, i.e. systems which monitor/control certain quantities in their environment.
BibTeX:
@inproceedings{ICSOFT16b,
  year = {2016},
  title = {Introducing Product Line Engineering in a Bottom-up Approach},
  booktitle = {Proceedings of the 11th International Joint Conference on Software Technologies {(ICSOFT} 2016)},
  author = {Ulfat-Bunyadi, Nelufar and Meis, Rene and Mohammadi, Nazila Gol and Heisel, Maritta},
  publisher = {SciTePress},
  pages = {146--153},
  url = {http://dx.doi.org/10.5220/0006006001460153},
  doi = {10.5220/0006006001460153}
}
2016 Computer-Aided Identification and Validation of Privacy Requirements Meis, R. & Heisel, M. Information    
Abstract: Privacy is a software quality that is closely related to security. The main difference is that security properties aim at the protection of assets that are crucial for the considered system, and privacy aims at the protection of personal data that are processed by the system. The identification of privacy protection needs in complex systems is a hard and error prone task. Stakeholders whose personal data are processed might be overlooked, or the sensitivity and the need of protection of the personal data might be underestimated. The later personal data and the needs to protect them are identified during the development process, the more expensive it is to fix these issues, because the needed changes of the system-to-be often affect many functionalities. In this paper, we present a systematic method to identify the privacy needs of a software system based on a set of functional requirements by extending the problem-based privacy analysis (ProPAn) method. Our method is tool-supported and automated where possible to reduce the effort that has to be spent for the privacy analysis, which is especially important when considering complex systems. The contribution of this paper is a semi-automatic method to identify the relevant privacy requirements for a software-to-be based on its functional requirements. The considered privacy requirements address all dimensions of privacy that are relevant for software development. As our method is solely based on the functional requirements of the system to be, we enable users of our method to identify the privacy protection needs that have to be addressed by the software-to-be at an early stage of the development. As initial evaluation of our method, we show its applicability on a small electronic health system scenario.
BibTeX:
@article{Information16,
  year = {2016},
  title = {Computer-Aided Identification and Validation of Privacy Requirements},
  author = {Meis, Rene and Heisel, Maritta},
  journal = {Information},
  volume = {7},
  number = {2},
  pages = {28},
  url = {http://www.mdpi.com/2078-2489/7/2/28},
  doi = {10.3390/info7020028}
}
2016 Understanding the Privacy Goal Intervenability Meis, R. & Heisel, M. Trust, Privacy, and Security in Digital Business   Springer  
Abstract: Privacy is gaining more and more attention in society and hence, gains more importance as a software quality that has to be considered during software development. A privacy goal that has not yet been deeply studied is the empowerment of end-users to have control over how their personal data is processed by information systems. This privacy goal is called intervenability. Several surveys have shown that one of end-users’ main privacy concerns is the lack of intervenability options in information systems. In this paper, we refine the privacy goal intervenability into a software requirements taxonomy and relate it to a taxonomy of transparency requirements because transparency can be regarded as a prerequisite for intervenability. The combined taxonomy of intervenability and transparency requirements shall guide requirements engineers to identify the intervenability requirements relevant for the system they consider. We validated the completeness of our taxonomy by comparing it to the relevant literature that we derived based on a systematic literature review.
BibTeX:
@inproceedings{TrustBus16,
  year = {2016},
  title = {Understanding the Privacy Goal Intervenability},
  booktitle = {Trust, Privacy, and Security in Digital Business},
  author = {Meis, Rene and Heisel, Maritta},
  publisher = {Springer},
  volume = {9830},
  series = {LNCS},
  pages = {79--94},
  url = {http://dx.doi.org/10.1007/978-3-319-44341-6_6},
  doi = {10.1007/978-3-319-44341-6_6}
}
2015 A Problem-, Quality-, and Aspect-Oriented Requirements Engineering Method Faßbender, S., Heisel, M. & Meis, R. Software Technologies - 9th International Joint Conference, ICSOFT 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers   Springer  
Abstract: Requirements engineers not only have to cope with the requirements
of various stakeholders for complex software systems, they also have
to consider several software qualities (e.g., performance,
maintainability, security, and privacy) that the system-to-be shall
address. In such a situation, it is challenging for requirements engineers to
develop a complete and coherent set of requirements for the
system-to-be.
Separation of concerns has shown to be one option to handle the
complexity of systems. The problem frames approach address this
principle by decomposing the problem of building the
system-to-be into simpler subproblems. Aspect-orientation aims at
separating cross-cutting functionalities into separate
functionalities, called aspects.
We propose a method called AORE4PF, which shows that
aspect-orientation can be integrated into the problem frames
approach to increase the separation of concerns and to benefit from
several methods that exist on problem frames to develop a complete
and coherent set of requirements. We validated our method with a
small experiment in the field of crisis management.
BibTeX:
@inproceedings{CCIS15a,
  year = {2015},
  title = {A Problem-, Quality-, and Aspect-Oriented Requirements Engineering Method},
  booktitle = {Software Technologies - 9th International Joint Conference, {ICSOFT} 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers},
  author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  volume = {555},
  series = {Communications in Computer and Information Science},
  pages = {291--310},
  url = {http://dx.doi.org/10.1007/978-3-319-25579-8_17},
  doi = {10.1007/978-3-319-25579-8_17}
}
2015 Problem-Based Security Requirements Elicitation and Refinement with PresSuRE Faßbender, S., Heisel, M. & Meis, R. Software Technologies - 9th International Joint Conference, ICSOFT 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers   Springer  
Abstract: Recently published reports on cybercrime indicate an ever-increasing number of
security incidents related to IT systems. Many attacks causing the incidents
abuse (in)directly one or more security defects.
Fixing the security defect once fielded is costly. To avoid the defects and the
subsequent need to fix them, security has to be considered thoroughly when
developing software. The earliest phase to do so is the requirements
engineering, in which security threats should be identified early on and treated
by defining sufficient security requirements.
In a previous paper, we introduced a methodology for
Problem-based Security Requirements Elicitation (PresSuRE).
PresSuRE provides a computer-aided security threat identification. The
identification is based on the functional requirements for a system-to-be.
Still, there is a need for guidance on how to derive security requirements once
the threats are identified. In this work, we provide such guidance extending
PresSuRE and its tool support. We illustrate and validate our approach using a
smart grid scenario provided by the industrial partners of the EU project
NESSoS.
BibTeX:
@incollection{CCIS15b,
  year = {2015},
  title = {Problem-Based Security Requirements Elicitation and Refinement with PresSuRE},
  booktitle = {Software Technologies - 9th International Joint Conference, {ICSOFT} 2014, Vienna, Austria, August 29-31, 2014, Revised Selected Papers},
  author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  volume = {555},
  series = {Communications in Computer and Information Science},
  pages = {311--330},
  url = {http://dx.doi.org/10.1007/978-3-319-25579-8_18},
  doi = {10.1007/978-3-319-25579-8_18}
}
2015 Systematic Identification of Information Flows from Requirements to support Privacy Impact Assessments Meis, R. & Heisel, M. ICSOFT-PT 2015 - Proc. of the 10th Int. Conf. on Software Paradigm Trends   SciTePress  
Abstract: Several countries prescribe or advise government departments and
organizations to perform a privacy impact assessment (PIA) if these
prepare new projects or change existing ones that involve personal
information. A PIA shall summarize what personal information is
collected, processed, stored, and distributed in the context of the
project. But there is only little support for undertaking a PIA and
to create a PIA report, most countries only provide vague guidelines
and simple templates. We present in this paper an extension of the
problem-based privacy analysis (ProPAn) method that derives
information needed to conduct a PIA from a requirements model in
problem frame notation. We provide a formally specified method with
well-defined steps and tool support to reduce the effort to be spent
for eliciting the needed information and to ensure that the needed
information is as complete and coherent as possible to form an
adequate basis for the creation of a PIA report.
BibTeX:
@inproceedings{ICSOFT15,
  year = {2015},
  title = {Systematic Identification of Information Flows from Requirements to support Privacy Impact Assessments},
  booktitle = {{ICSOFT-PT} 2015 - Proc. of the 10th Int. Conf. on Software Paradigm Trends},
  author = {Meis, Rene and Heisel, Maritta},
  publisher = {SciTePress},
  pages = {43-52},
  url = {http://dx.doi.org/10.5220/0005518500430052},
  doi = {10.5220/0005518500430052}
}
2015 A Taxonomy of Requirements for the Privacy Goal Transparency Meis, R., Heisel, M. & Wirtz, R. Trust, Privacy, and Security in Digital Business   Springer  
Abstract: Privacy is a growing concern during software
development. Transparency--in the sense of increasing user's
privacy-awareness--is a privacy goal that is not as deeply studied
in the literature as the properties anonymity and unlinkability. To
be compliant with legislation and standards, requirements engineers
have to identify the requirements on transparency that are relevant
for the software to be developed. To assist the identification
process, we provide a taxonomy of transparency requirements derived
from legislation and standards. This taxonomy is validated using
related research which was identified using a systematic literature
review. Our proposed taxonomy can be used by requirements engineers
as basis to systematically identify the relevant transparency
requirements leading to a more complete and coherent set of
requirements.
BibTeX:
@inproceedings{TrustBus2015,
  year = {2015},
  title = {A Taxonomy of Requirements for the Privacy Goal Transparency},
  booktitle = {Trust, Privacy, and Security in Digital Business},
  author = {Meis, Rene and Heisel, Maritta and Wirtz, Roman},
  publisher = {Springer},
  series = {LNCS 9264},
  pages = {195-209},
  url = {http://dx.doi.org/10.5220/0005518500430052},
  doi = {10.5220/0005518500430052}
}
2014 A Problem-based Approach for Computer Aided Privacy Threat Identification Beckers, K., Faßbender, S., Heisel, M. & Meis, R. Privacy Technologies and Policy   Springer  
Abstract: Recently, there has been an increase of reported privacy threats hitting
large software systems. These threats can originate from stakeholders that are
part of the system. Thus, it is crucial for software engineers to identify these
privacy threats, refine these into privacy requirements, and design solutions that
mitigate the threats.

In this paper, we introduce our methodology named Problem-Based Privacy Analysis (ProPAn). The ProPAn method is an approach for identifying privacy threats during the requirements
analysis of software systems using problem frame models. Our approach does not rely
entirely on the privacy analyst to detect privacy threats, but allows a computer aided privacy
threat identification that is derived from the relations between stakeholders, technology, and personal information in the system-to-be.

To capture the environment of the system, e.g., stakeholders and other IT systems,
we use problem frames, a requirements engineering approach founded on the modeling
of a machine (system-to-be) in its environment (e.g. stakeholders, other software). We define a UML profile for privacy requirements and a reasoning technique that
identifies stakeholders, whose personal information are stored or transmitted in the system-to-be and stakeholders from whom we have to protect this personal information. We illustrate our approach using an eHealth scenario provided by the industrial partners of the EU project NESSoS.

BibTeX:
@inproceedings{APF2012,
  year = {2014},
  title = {A Problem-based Approach for Computer Aided Privacy Threat Identification},
  booktitle = {Privacy Technologies and Policy},
  author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  volume = {8319},
  series = {LNCS},
  pages = {1-16},
  url = {http://dx.doi.org/10.1007/978-3-642-54069-1_1},
  doi = {10.1007/978-3-642-54069-1_1}
}
2014 Aspect-oriented Requirements Engineering with Problem Frames Faßbender, S., Heisel, M. & Meis, R. ICSOFT-PT 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends   SciTePress  
Abstract: Nowadays, the requirements of various stakeholders for a system do not
only increase the complexity of the system-to-be, but also contain different
cross-cutting concerns.
In such a situation, requirements engineers are really challenged to master the
complexity and to deliver a coherent and complete description of the
system-to-be. Hence, they are in need for
methods which reduce
the complexity, handle functional and quality requirements, check
completeness and reveal interactions,
and are tool supported to lower the effort.
One possible option to handle the complexity of a system-to-be is the separation
of concerns. Both, aspect-oriented requirements engineering and the problem
frames approach implement this principle.
Therefore,
we propose a combination of both, the AORE4PF (Aspect-Oriented Requirements
Engineering for Problem Frames) method.
AORE4PF provides guidance for classifying requirements,
separating the different concerns, modeling requirements for documentation and application of completeness and interaction analyses, and weaving
the reusable parts to a complete and coherent system. AORE4PF provides tool
support for most activities.
We exemplify our method using a smart grid case obtained from
the NESSoS project. For validation, the results of a small experiment in the field of
crisis management systems are presented.
BibTeX:
@inproceedings{ICSOFT14Aspects,
  year = {2014},
  title = {Aspect-oriented Requirements Engineering with Problem Frames},
  booktitle = {{ICSOFT-PT} 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends},
  author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {SciTePress},
  pages = {145-156},
  url = {http://dx.doi.org/10.5220/0005001801450156},
  doi = {10.5220/0005001801450156}
}
2014 Functional Requirements Under Security PresSuRE Faßbender, S., Heisel, M. & Meis, R. ICSOFT-PT 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends   SciTePress  
Abstract: Recently, there has been an increase of reported security incidents hitting
large software systems. Such incidents can originate from different
attackers exploiting vulnerabilities of different parts of a system. Hence, there
is a need for enhancing security considerations in software development.
It is crucial for requirements engineers to identify security threats
early on, and to refine the threats into security requirements.
In this paper, we introduce a methodology for Problem-based Security
Requirements Elicitation (PresSuRE). PresSuRE is a method for
identifying security needs during the requirements analysis of
software systems using a problem frame model. Our method does not rely
entirely on the requirements engineer to detect security needs, but
provides a computer-aided security threat identification, and
subsequently the elicitation of security requirements.
The identification is based on the functional requirements for a
system-to-be. We illustrate and validate our approach using a smart grid
scenario provided by the industrial partners of the EU project NESSoS.
BibTeX:
@inproceedings{ICSOFT14Pressure,
  year = {2014},
  title = {Functional Requirements Under Security {PresSuRE}},
  booktitle = {{ICSOFT-PT} 2014 - Proc. of the 9th Int. Conf. on Software Paradigm Trends},
  author = {Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {SciTePress},
  pages = {5-16},
  url = {http://dx.doi.org/10.5220/0005098600050016},
  doi = {10.5220/0005098600050016}
}
2014 Problem-Based Consideration of Privacy-Relevant Domain Knowledge Meis, R. Privacy and Identity Management for Emerging Services and Technologies   Springer  
Abstract: Especially for a privacy analysis, an adequate and accurate
consideration of domain knowledge is needed. Domain knowledge is
often only implicitly given and mainly stored in the minds of
domain experts. It is important to make this implicit knowledge
explicit and to use it in the privacy analysis of a software system.
To our knowledge, no privacy-aware requirements engineering approach
exists yet which explicitly considers the elicitation of
privacy-relevant domain knowledge. This paper presents an extension
of the problem-based privacy analysis (ProPAn) method. The
extension consists of three parts. First, we elicit the relevant
domain knowledge based on questionnaires which are derived from the
stakeholder analysis literature. Second, we present generic patterns
which can be instantiated to represent the elicited knowledge. Last,
we extend the definitions of ProPAn's privacy graphs to take into
account the domain knowledge.
BibTeX:
@incollection{IFIP2013,
  year = {2014},
  title = {{Problem-Based Consideration of Privacy-Relevant Domain Knowledge}},
  booktitle = {Privacy and Identity Management for Emerging Services and Technologies},
  author = {Meis, Rene},
  publisher = {Springer},
  volume = {421},
  series = {IFIP Advances in Information and Communication Technology},
  url = {http://dx.doi.org/10.1007/978-3-642-55137-6_12},
  doi = {10.1007/978-3-642-55137-6_12}
}
2014 Problem-Based Requirements Interaction Analysis Alebrahim, A., Faßbender, S., Heisel, M. & Meis, R. Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ)   Springer  
Abstract: The ability to address the diverse interests of different
stakeholders in a software project in a coherent way is one
fundamental software quality. These diverse and maybe conflicting
interests are reflected by the requirements of each
stakeholder. Thus, it is likely that aggregated
requirements for a software system contain interactions. To avoid unwanted
interactions and improve software quality, we propose a structured
method consisting of three phases to find such interactions.
For our method, we use problem diagrams, which
describe requirements in a structured way. The information represented in the
problem diagrams is translated into a formal Z model.
Then we reduce the number of combinations of
requirements, which might conflict. The reduction of
requirements interaction candidates is crucial to lower the effort of the in
depth interaction analysis. For validation of our method, we use a real-life
example in the domain of smart grid.
BibTeX:
@inproceedings{REFSQ2014,
  year = {2014},
  title = {Problem-Based Requirements Interaction Analysis},
  booktitle = {Proceedings of the International Working Conference on Requirements Engineering: Foundation for Software Quality ({REFSQ})},
  author = {Alebrahim, Azadeh and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  series = {LNCS 8396},
  pages = {200--215},
  url = {http://dx.doi.org/10.1007/978-3-319-05843-6_15},
  doi = {10.1007/978-3-319-05843-6_15}
}
2014 Determining the Probability of Smart Grid Attacks by Combining Attack Tree and Attack Graph Analysis Beckers, K., Heisel, M., Krautsevich, L., Martinelli, F., Meis, R. & Yautsiukhin, A. Smart Grid Security - Second International Workshop, SmartGridSec 2014, Munich, Germany, February 26, 2014, Revised Selected Papers   Springer  
Abstract: Smart grid is an intelligent energy distribution system consisting of multiple information and communication technologies (ICT). One of the challenges for such complex and heterogeneous system as smart grid is to unite security analysis on a high level of abstraction and concrete behavioral attack patterns that exploit low-level vulnerabilities. We provide a structured method that combines the Si* language, which can express attacker motivations as a goal hierarchy, and vulnerability specific attack graphs, which shows every step available for an attacker. We derive system specific information from the low-level representation of the system for a high-level probabilistic analysis.
BibTeX:
@inproceedings{SmartGridSec14,
  year = {2014},
  title = {Determining the Probability of Smart Grid Attacks by Combining Attack Tree and Attack Graph Analysis},
  booktitle = {Smart Grid Security - Second International Workshop, SmartGridSec 2014, Munich, Germany, February 26, 2014, Revised Selected Papers},
  author = {Beckers, Kristian and Heisel, Maritta and Krautsevich, Leanid and Martinelli, Fabio and Meis, Rene and Yautsiukhin, Artisom},
  publisher = {Springer},
  series = {LNCS 8448},
  pages = {30--47},
  url = {http://dx.doi.org/10.1007/978-3-319-10329-7_3},
  doi = {10.1007/978-3-319-10329-7_3}
}
2014 A Structured Approach for Eliciting, Modeling, and Using Quality-Related Domain Knowledge Alebrahim, A., Heisel, M. & Meis, R. Proceedings of the 14th International Conference on Computational Science and Its Applications (ICCSA)   Springer  
Abstract: In requirements engineering, properties of the environment and assumptions about
it, called domain knowledge, need to be captured in addition to
exploring the requirements.
Despite the recognition of the significance of capturing and using the
required domain knowledge, it might be missing, left implicit, or be
captured inadequately during the software development. This results in an
incorrect specification. Moreover, the software might fail to achieve its
quality objectives because of ignored required constraints and assumptions.
In order to analyze software quality properly, we
propose a structured approach for eliciting, modeling, and using domain
knowledge. We investigate what kind of quality-related domain knowledge is
required for the early phases of quality-driven software development and how
such domain knowledge can be systematically elicited and explicitly modeled to
be used for the analysis of quality requirements. Our method aims at improving
the quality of the requirements engineering process by facilitating the
capturing and using of implicit domain knowledge.
BibTeX:
@incollection{SQ2014,
  year = {2014},
  title = {A Structured Approach for Eliciting, Modeling, and Using Quality-Related Domain Knowledge},
  booktitle = {Proceedings of the 14th International Conference on Computational Science and Its Applications (ICCSA)},
  author = {Alebrahim, Azadeh and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  series = {LNCS 8583},
  pages = {370--386},
  url = {http://dx.doi.org/10.1007/978-3-319-09156-3_27},
  doi = {10.1007/978-3-319-09156-3_27}
}
2014 Privacy-Aware Cloud Deployment Scenario Selection Beckers, K., Faßbender, S., Gritzalis, S., Heisel, M., Kalloniatis, C. & Meis, R. Trust, Privacy, and Security in Digital Business   Springer  
Abstract: Nowadays, IT-resources are often out-sourced to clouds to reduce
administration and hardware costs of the own IT
infrastructure. There are different deployment scenarios for clouds
that heavily differ in the costs for deployment and maintenance, but
also in the number of stakeholders involved in the cloud and the
control over the data in the cloud. These additional stakeholders
can introduce new privacy threats into a system. Hence, there is a
trade-off between the reduction of costs and addressing privacy
concerns introduced by clouds. Our contribution is a structured
method that assists decision makers in selecting an appropriate
cloud deployment scenario. Our method is based on the privacy
requirements of the system-to-be. These are analyzed on basis of the
functional requirements using the problem-based privacy threat
analysis (ProPAn). The concept of clouds is integrated into the
requirements model, which is used by ProPAn to automatically generate
privacy threat graphs.
BibTeX:
@inproceedings{TrustBus2014,
  year = {2014},
  title = {Privacy-Aware Cloud Deployment Scenario Selection},
  booktitle = {Trust, Privacy, and Security in Digital Business},
  author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Gritzalis, S. and Heisel, Maritta and Kalloniatis, C. and Meis, Rene},
  publisher = {Springer},
  series = {LNCS 8647},
  pages = {94-105},
  url = {http://dx.doi.org/10.1007/978-3-319-09770-1_9},
  doi = {10.1007/978-3-319-09770-1_9}
}
2012 Pattern-based Context Establishment for Service-Oriented Architectures Beckers, K., Faßbender, S., Heisel, M. & Meis, R. Software Service and Application Engineering   Springer  
Abstract: A context description of a software system and its environment is essential
for any given software engineering process. Requirements define statements
about the environment (according to Jackson's terminology). The context
description of a Service-Oriented Architecture is difficult to provide,
because of the variety of technical systems and stakeholders involved. We
present two patterns for SOA systems and support their instantiation with a
structured method. In addition, we show how the pattern can be used in a
secure service development life-cycle.
BibTeX:
@inproceedings{sdps2012,
  year = {2012},
  title = {Pattern-based Context Establishment for Service-Oriented Architectures},
  booktitle = {Software Service and Application Engineering},
  author = {Beckers, Kristian and Fa{\ss}bender, Stephan and Heisel, Maritta and Meis, Rene},
  publisher = {Springer},
  series = {LNCS 7365},
  pages = {81-101},
  url = {http://dx.doi.org/10.1007/978-3-642-30835-2_7},
  doi = {10.1007/978-3-642-30835-2_7}
}

Created by JabRef on 21/10/2016.