Software Requirements Conflict Identification: Review and Recommendations

Aldekhail, Maysoon; Chikh, Azzedine; Ziani, Djamal

doi:10.14569/ijacsa.2016.071044

Cited by 17 publications

(18 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The literature is rich with approaches that rely on textually specified requirements to identify conflicts between them. A comprehensive overview of these approaches is found in [4]. In what follows, we discuss the approaches that consider security or privacy as part of their supported concepts.…”

Section: Other Conflict Detection Approachesmentioning

confidence: 99%

A semi-automated BPMN-based framework for detecting conflicts between security, data-minimization, and fairness requirements

et al. 2020

View full text Add to dashboard Cite

Requirements are inherently prone to conflicts. Security, data-minimization, and fairness requirements are no exception. Importantly, undetected conflicts between such requirements can lead to severe effects, including privacy infringement and legal sanctions. Detecting conflicts between security, data-minimization, and fairness requirements is a challenging task, as such conflicts are context-specific and their detection requires a thorough understanding of the underlying business processes. For example, a process may require anonymous execution of a task that writes data into a secure data storage, where the identity of the writer is needed for the purpose of accountability. Moreover, conflicts not arise from trade-offs between requirements elicited from the stakeholders, but also from misinterpretation of elicited requirements while implementing them in business processes, leading to a non-alignment between the data subjects' requirements and their specifications. Both types of conflicts are substantial challenges for conflict detection. To address these challenges, we propose a BPMN-based framework that supports: (i) the design of business processes considering security, data-minimization and fairness requirements, (ii) the encoding of such requirements as reusable, domain-specific patterns, (iii) the checking of alignment between the encoded requirements and annotated BPMN models based on these patterns, and (iv) the detection of conflicts between the specified requirements in the BPMN models based on a catalog of domain-independent anti-patterns. The security requirements were reused from SecBPMN2, a security-oriented BPMN 2.0 extension, while the fairness and data-minimization parts are new. For formulating our patterns and anti-patterns, we extended a graphical query language called SecBPMN2-Q. We report on the feasibility and the usability of our approach based on a case study featuring a healthcare management system, and an experimental user study.

show abstract

Section: Other Conflict Detection Approachesmentioning

confidence: 99%

A semi-automated BPMN-based framework for detecting conflicts between security, data-minimization, and fairness requirements

et al. 2020

View full text Add to dashboard Cite

show abstract

“…Another technique used to identify the conflicts is known as the negotiation method. Here, the stakeholders and software engineers discuss the project orally and analyze the requirements as well as the conflicts that the project could be facing [5].…”

Section: Related Workmentioning

confidence: 99%

Towards Detecting and Mitigating Conflicts for Privacy and Security Requirements

Alkubaisy

Cox

Mouratidis

2019

2019 13th International Conference on Research Challenges in Information Science (RCIS)

View full text Add to dashboard Cite

requirement engineering live in a world were contradiction is the norm. Hence, development of software engineering is usually an adjustable and upgrading cyclical process. We found in the literature that some requirements conflict with other requirements. We will focus in this study on identification and resolution of conflicts between security and privacy requirements. Although, most the recent studies focus on identifying conflicts without proposing a solution to resolve it. This paper presents an approach to identifying and resolving conflicting privacy and security requirements as patterns. By using patterns to describe the problem we can propose a solution for each conflict.

show abstract

“…Bendjenna [11] states the importance of dealing with conflictive situations during Requirements Engineering, considering the variety of stakeholders with the common objective of obtaining a unique system. Aldekhail [12] presents a literature review related to requirements conflicts. Some publications have presented requirements conflict management in a web-based collaborative environment.…”

Section: Related Workmentioning

confidence: 99%

Conflict Management in the Collaborative Description of a Domain Language (S)

Litvak

Rossi

Antonelli

2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

The identification and specification of the requirements of a software system is a difficult task that has the goal of obtaining requirements as correct and complete as possible. It is extremely important that Requirements Engineers understand a domain language in order to write high-quality requirements. Moreover, they must describe (and discuss) the language in a collaborative way in order to consider the different points of view of all stakeholders to assure that the resulting requirements will have more chances to meet their needs. However, collaborative construction implies the occurrence of conflicts that are unavoidable because of ambiguity, overlapping and misunderstanding natural language descriptions. This article relies on the Language Extended Lexicon in order to describe the application domain. Although it is a semi-structured glossary and this characteristic helps to reduce the conflicts, our experience shows that conflicts arise anyway. Thus, in order to mitigate this problem, this article presents a catalogue with a set of conflicts that could appear during a collaborative construction of the Language Extended Lexicon and proposes alternatives for their resolution.

show abstract

Software Requirements Conflict Identification: Review and Recommendations

Cited by 17 publications

References 24 publications

A semi-automated BPMN-based framework for detecting conflicts between security, data-minimization, and fairness requirements

A semi-automated BPMN-based framework for detecting conflicts between security, data-minimization, and fairness requirements

Towards Detecting and Mitigating Conflicts for Privacy and Security Requirements

Conflict Management in the Collaborative Description of a Domain Language (S)

Contact Info

Product

Resources

About