ACM Transactions on Software Engineering and Methodology (TOSEM)
A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification
IEEE Transactions on Software Engineering
Proceedings of the 17th international conference on Software engineering
Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
Practical software requirements: a manual of content and style
Practical software requirements: a manual of content and style
Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Transactions on Software Engineering
Managing inconsistent specifications: reasoning, analysis, and action
ACM Transactions on Software Engineering and Methodology (TOSEM)
Managing Requirements Inconsistency with Development Goal Monitors
IEEE Transactions on Software Engineering
Handling Obstacles in Goal-Oriented Requirements Engineering
IEEE Transactions on Software Engineering - special section on current trends in exception handling—part II
Reconciling requirements: a method for managing interference, inconsistency and conflict
Annals of Software Engineering
Overlaps in Requirements Engineering
Automated Software Engineering
A Reference Model for Requirements and Specifications
IEEE Software
Predicate Logic for Software Engineering
IEEE Transactions on Software Engineering
Surfacing Root Requirements Interactions from Inquiry Cycle Requirements Documents
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
A Methodological Framework for Viewpoint-Oriented Conceptual Modeling
IEEE Transactions on Software Engineering
Towards automatic problem decomposition: an ontology-based approach
Proceedings of the 2006 international workshop on Advances and applications of problem frames
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
What's in a feature: a requirements engineering perspective
FASE'08/ETAPS'08 Proceedings of the Theory and practice of software, 11th international conference on Fundamental approaches to software engineering
Building business process description and reasoning meta-model Mbp in a-prolog
SPW/ProSim'06 Proceedings of the 2006 international conference on Software Process Simulation and Modeling
Hi-index | 0.00 |
Viewpoint-based Requirements Engineering (VBRE) is based on the fact that there is a multiplicity of stakeholders that take part in any requirements process. This will inevitably lead to conflicts and inconsistencies that, if adequately managed, can be used to improve the process, as they are sources of requirements. There comes a time in every VBRE process when different viewpoints need to be compared to fin discrepancies (conflicts, inconsistencies). But in Requirements Engineering (RE) we also deal with other categories of statements, apart from "requirements", like domain descriptions and interface specifications. We could use this categorization to (i) internally classify the contents of each viewpoint by categories; (ii) compare the contents of one viewpoint against another, taking into account that this comparison should only be made between elements of the same category; (iii) classify the discrepancies by the affected categories and (iv) generate resolutions for the discrepancies according to this classification. In this paper, we present a VBRE method based on this approach, which is not constrained to a particular representation formalism. The proposed framework includes discrepancy detection and classification and solution generation.