The main success metric of a software system is the degree to which it achieves its purpose. Therefore, identifying this purpose must be one of the main activities in the development of software systems. At the same time, wide range of inconsistencies can arise during requirements engineering. Because requirements and goals are elicited from different stakeholders. Resolving such inconsistencies sooner is a necessary condition for successful development of the software. This paper proposes an enhanced fuzzy based GORE approach to handle the requirements conflict problem in GORE.
Introduction
Requirements Engineering (RE), is the first step of software engineering that deals with all process of software systems requirements like elicitation, validation, analysis, etc. Requirements engineering must address the reasons why a software system is needed, the functionalities that the system must provide to achieve its purpose and the constraints on how the software must be designed and implemented [2].
One of the great challenges of requirements engineering is …show more content…
Robinson has provided that many inconsistencies come from conflicting goals; therefore, inconsistency management should proceed at the goal level [7]. Reasoning about inconsistencies needs methods for representing overlapping descriptions and inconsistency relationships. Also, a viewpoint mechanisms have been proposed for recording independent descriptions into modular structures; such structures are related by consistency rules and linked to specific stakeholders participated in the elicitation process [8, 9]. An approach like in [7] for identifying conflicts at requirements level and stamping them as differences at goal level. Accordingly, solved differences are down propagated to the requirements level. Also [10] proposed a model in which all stakeholders, their goals and conflicts between goals are
Introduction
Requirements Engineering (RE), is the first step of software engineering that deals with all process of software systems requirements like elicitation, validation, analysis, etc. Requirements engineering must address the reasons why a software system is needed, the functionalities that the system must provide to achieve its purpose and the constraints on how the software must be designed and implemented [2].
One of the great challenges of requirements engineering is …show more content…
Robinson has provided that many inconsistencies come from conflicting goals; therefore, inconsistency management should proceed at the goal level [7]. Reasoning about inconsistencies needs methods for representing overlapping descriptions and inconsistency relationships. Also, a viewpoint mechanisms have been proposed for recording independent descriptions into modular structures; such structures are related by consistency rules and linked to specific stakeholders participated in the elicitation process [8, 9]. An approach like in [7] for identifying conflicts at requirements level and stamping them as differences at goal level. Accordingly, solved differences are down propagated to the requirements level. Also [10] proposed a model in which all stakeholders, their goals and conflicts between goals are