Resumen
This article focuses on the need to find requirements about software attributes. 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. Requirement traceability is the ability to describe and follow the life of a requirement, forward and backward. This would be done by defining and maintaining relationship to various artifacts created during system development, such as stakeholder needs, architectural or design elements, or source code. Analyzing requirements using software attributes can make conflicts and cooperation instances more obvious, because changes in quality often cause certain functional changes that in turn affect other quality attributes. For example, it is known that checking user inputs increases correctness but also increases costs and decreases performance. INSET: Related Work.