Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help
Authors:
- 8 November 2004
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 21 (6) , 50-58
Abstract
Requirements about software attributes have numerous complex and nontrivial interdependencies. Requirements conflict with each other when they make contradicting statements about common software attributes, and they cooperate when they mutually enforce such attributes. Because software developers rarely apply formal requirements specification techniques in practice, and because reliable techniques for natural language understanding aren't available, it's generally infeasible to automatically identify conflicts and cooperation among requirements. In software development and maintenance, identifying conflicts and cooperation among requirements is challenging. Fortunately, quality attributes can help. In addition, automated traceability techniques can eliminate falsely identified conflicts and cooperation efficiently.Keywords
This publication has 10 references indexed in Scilit:
- Rule-based generation of requirements traceability relationsJournal of Systems and Software, 2004
- Bridging models across the software lifecycleJournal of Systems and Software, 2003
- A scenario-driven approach to trace dependency analysisIEEE Transactions on Software Engineering, 2003
- An analysis of the requirements traceability problem2002
- Automating requirements traceability: Beyond the record & replay paradigm2002
- Aspect-oriented programmingCommunications of the ACM, 2001
- Toward reference models for requirements traceabilityIEEE Transactions on Software Engineering, 2001
- Non-Functional Requirements in Software Engineering2000
- Architectural Design to Meet Stakeholder Requirements1999
- Identifying quality-requirement conflictsIEEE Software, 1996