Identifying quality-requirement conflicts
- 1 March 1996
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 13 (2) , 25-35
- https://doi.org/10.1109/52.506460
Abstract
No abstract availableKeywords
This publication has 6 references indexed in Scilit:
- Software requirements as negotiated win conditionsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- SAAM: a method for analyzing the properties of software architecturesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Using non-functional requirements to systematically support changePublished by Institute of Electrical and Electronics Engineers (IEEE) ,2002
- Software requirements negotiation and renegotiation aidsPublished by Association for Computing Machinery (ACM) ,1995
- Handling conflict between domain descriptions with computer-supported negotiationKnowledge Acquisition, 1991
- Theory-W software project management principles and examplesIEEE Transactions on Software Engineering, 1989