An overview of formal and informal methods of conflict detection in software requirements

Successful software development requires a set of complete, compatible, and clear requirements. A wide range of different stakeholders with different requirements andbackgrounds participate in the requirements engineering process. Accordingly, it is difficult to fully meet the needs of each stakeholder. It is the job of the requirements engineer to exchange the needs of the stakeholders with the resources and constraints of the project. One of the most essential processes in the software project life cycle is the requirements engineering process because it allows the software product to be determined. These specifications should be as coherent as possible because it allows the effort required to obtain the final product to be estimated in an appropriate manner. We extracted the software requirements from various sources that were selected and grouped based on quality characteristics, and worked on modifying them by identifying the contradictions between these requirements and introducing solutions to them. In this article, we reviewed formal and informal methods such as artificial intelligence to systematically detect conflicts between different software requirements, andfinally examined modern and useful techniques.

Keywords:

Engineering requirements , software requirements , stakeholders , conflict detection , formal method