Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Managing Conflicts in Goal-Driven Requirements Engineering
IEEE Transactions on Software Engineering
Annals of Software Engineering
Reconciling requirements: a method for managing interference, inconsistency and conflict
Annals of Software Engineering
To Be and Not to Be: On Managing Inconsistency in Software Development
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
A comedy of errors: the London Ambulance Service case study
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Knowledge and Information Systems
Explicit domain modelling in video games
Proceedings of the 6th International Conference on Foundations of Digital Games
| Hi-index | 0.00 |
Management of requirements inconsistency is key to the development of trustworthy software systems. But at present, although there are a lot of work on this topic, most of them are limited in treating inconsistency at the syntactic level. We still lack a systematical method for managing requirements inconsistency at the semantic level. This paper first proposes a requirements refinement model, which suggests that interactions between software agents and their ambiences are essential to capture the semantics of requirements. We suppose that the real effect of these interactions is to make the states of entities in the ambiences changed. So, we explicitly represent requirements of a software agent as a set of state transition diagrams, each of which is for one entity in the ambiences. We argue that, based on this model, the mechanism to deal with the inconsistency at the semantic level. A domain ontology is used as an infrastructure to detect, diagnose and resolve the inconsistency.