“Lazy” consistency: a basis for cooperative software development
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification
IEEE Transactions on Software Engineering
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
Decentralised process enactment in a multi-perspective development environment
Proceedings of the 17th international conference on Software engineering
Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Formal methods for verification and validation of partial specifications: a case study
Journal of Systems and Software - Special issue on formal methods technology transfer
Guest Editorial: Introduction to the Special Section
IEEE Transactions on Software Engineering
IEEE Software
Restructuring Requirements Specifications For Managing Inconsistency And Change: A Case Study
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Validating Requirements for Fault Tolerant Systems using Model Checking
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
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
xlinkit: a consistency checking and smart link generation service
ACM Transactions on Internet Technology (TOIT)
Requirements, domain and specifications: a viewpoint-based approach to requirements engineering
Proceedings of the 24th International Conference on Software Engineering
Metadata and Cooperative Knowledge Management
CAiSE '02 Proceedings of the 14th International Conference on Advanced Information Systems Engineering
A Foolish Consistency: Technical Challenges in Consistency Management
DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Journal of Systems and Software
ViewPoints: meaningful relationships are difficult!
Proceedings of the 25th International Conference on Software Engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
The Complexity of TRMCS-like Spiral Specification
IWSSD '00 Proceedings of the 10th International Workshop on Software Specification and Design
Static Consistency Checking for Distributed Specifications
Proceedings of the 16th IEEE international conference on Automated software engineering
Proceedings of the 2003 ACM symposium on Document engineering
A Survey of Software Refactoring
IEEE Transactions on Software Engineering
A Methodological Framework for Viewpoint-Oriented Conceptual Modeling
IEEE Transactions on Software Engineering
Priority Assessment of Software Requirements from Multiple Perspectives
COMPSAC '04 Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01
Managing inconsistent repositories via prioritized repairs
Proceedings of the 2004 ACM symposium on Document engineering
Pragmatic Consistency Management in Industrial Requirements Specifications
SEFM '05 Proceedings of the Third IEEE International Conference on Software Engineering and Formal Methods
Proceedings of the 28th international conference on Software engineering
Problem-based analysis of organisational change: a real-world example
Proceedings of the 2006 international workshop on Advances and applications of problem frames
Model refactorings through rule-based inconsistency resolution
Proceedings of the 2006 ACM symposium on Applied computing
Identifying Acceptable Common Proposals for Handling Inconsistent Software Requirements
FORTE '07 Proceedings of the 27th IFIP WG 6.1 international conference on Formal Techniques for Networked and Distributed Systems
A Language-Theoretic View on Guidelines and Consistency Rules of UML
ECMDA-FA '09 Proceedings of the 5th European Conference on Model Driven Architecture - Foundations and Applications
From requirements negotiation to software architecture decisions
Information and Software Technology
MaDe4IC: an abstract method for managing model dependencies in inter-organizational cooperations
Service Oriented Computing and Applications
Improving requirements quality using essential use case interaction patterns
Proceedings of the 33rd International Conference on Software Engineering
Learning to adapt requirements specifications of evolving systems (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Engineering mathematical knowledge
MKM'05 Proceedings of the 4th international conference on Mathematical Knowledge Management
Ontology-Based inconsistency management of software requirements specifications
SOFSEM'05 Proceedings of the 31st international conference on Theory and Practice of Computer Science
Measuring inconsistency in requirements specifications
ECSQARU'05 Proceedings of the 8th European conference on Symbolic and Quantitative Approaches to Reasoning with Uncertainty
Delegation modeling with paradigm
COORDINATION'05 Proceedings of the 7th international conference on Coordination Models and Languages
From inconsistency handling to non-canonical requirements management: A logical perspective
International Journal of Approximate Reasoning
An ontology-based framework for domain-specific modeling
Software and Systems Modeling (SoSyM)
Hi-index | 4.11 |
Software engineers make use of many descriptions, including analysis models, specifications, designs, program code, user guides, test plans, change requests, style guides, schedules, and process models. But since different developers construct and update these descriptions at various times during development, maintaining consistency among descriptions presents several problems.Descriptions tend to vary considerably. Individual descriptions can be illformed or self-contradictory and frequently evolve throughout the life cycle at different rates. Also, checking the consistency of a large, arbitrary set of descriptions is computationally expensive.The authors assert that maintaining consistency at all times is counterproductive. In many cases, it may be desirable to tolerate or even encourage inconsistency to facilitate distributed team-work and prevent premature commitment to design decisions. They advocate using inconsistency to highlight problem areas, using it as a tool to improve the development team's shared understanding, direct the process of requirements elicitation, and assist with verification and validation.