• Corpus ID: 232104883

Automatically detecting the conflicts between software requirements based on finer semantic analysis

@article{Guo2021AutomaticallyDT,
  title={Automatically detecting the conflicts between software requirements based on finer semantic analysis},
  author={Weize Guo and Li Zhang and Xiaoli Lian},
  journal={ArXiv},
  year={2021},
  volume={abs/2103.02255}
}
Context: Conflicts between software requirements bring uncertainties to product development. Some great approaches have been proposed to identify these conflicts. However, they usually require the software requirements represented with specific templates and/or depend on other external source which is often uneasy to build for lots of projects in practice. Objective: We aim to propose an approach Finer Semantic Analysis-based Requirements Conflict Detector (FSARC) to automatically detecting the… 

Figures and Tables from this paper

Identifying the requirement conflicts in SRS documents using transformer-based sentence embeddings

This study aims to identify the conflicts in requirements by analyzing their semantic compositions and contextual meanings with the help of sentence embeddings and cosine similarity measures, and proposes an approach for automatic con flict detection, which consists of two phases: identifying conﷂict candidates based on textual similarity, and using semantic analysis to detect them.

Requirements Conflict Detection and Resolution in AREM Using Intelligence System Approach

The success of the method in detecting and resolving conflicts in the model is able to overcome the problem of inconsistencies and incompleteness in the requirements model.

A Prompt-based Few-shot Learning Approach to Software Conflict Detection

A software requirement specification (SRS) document is an essential part of the software development life cycle which outlines the requirements that a software program in development must sat-isfy.

A framework for improving the process of discovering potential errors at the requirements engineering stage

This paper has been working on providing a comprehensive framework that enables software developers to focus on the underlying errors in an organized documentation manner, as well as to be supportive and complementary to the various processes of validation and testing, by focusing on the requirements validation process.

References

SHOWING 1-10 OF 48 REFERENCES

Towards Development of Complete and Conflict-Free Requirements

This work introduces a tool called ASSERT (Analysis of Semantic Specifications and Efficient generation of Requirements-based Tests) for capturing requirements, backed by a formal requirements analysis engine, and provides explainable and automated formal analysis, something important for a tool's adoptability in industry.

Requirements Management with Semantic Technology: An Empirical Study on Automated Requirements Categorization and Conflict Analysis

Major results were that OntRep provides reasonable capabilities for the automated categorization of requirements, was when compared to a manual approach considerably more effective to identify conflicts, and produced less false positives with similar effort.

Detection of conflicting functional requirements in a use case-driven approach

A formal interpretation of use case models consisting of UML use case, activity, and collaboration diagrams is proposed, which allows to make precise the notions of conflict and dependency between functional requirements expressed by different use cases.

Reasoning with contextual requirements: Detecting inconsistency and conflicts

Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help

Quality attributes can help identify conflicts and cooperation among requirements in software development and maintenance, and automated traceability techniques can eliminate falsely identified conflicts and cooperate efficiently.

Managing Consistency between Textual Requirements, Abstract Interactions and Essential Use Cases

A traceability approach with visualization capability is embedded into a light-weight automated tracing tool in order to allow users to capture their requirements and generate Essential Use Case models of these requirements automatically.

An ontological framework to manage the relative conflicts between security and usability requirements

  • Dewi MairizaD. Zowghi
  • Computer Science
    2010 Third International Workshop on Managing Requirements Knowledge
  • 2010
The sureCM framework to manage these conflicts is described; the security-usability conflicts ontology is summarized; and it is demonstrated how the ontology will be used as a basis to assist analysts in managing conflicts between security and usability requirements.

A Formalization Method to Process Structured Natural Language to Logic Expressions to Detect Redundant Specification and Test Statements

This paper proposes a formalization process for requirements specification and test statements, allowing us to detect redundant statements and thus reduce the efforts for specification and validation.

Easy Approach to Requirements Syntax (EARS)

A small set of structural rules was developed to address eight common requirement problems including ambiguity, complexity and vagueness and was applied whilst extracting aero engine control system requirements from an airworthiness regulation document.