Negotiating requirements is one of the first steps in any software system life cycle, but its results have probably the most significant impact on the system's value. However...
As new software components become available for an existing system, we can evolve not only the system itself but also its requirements based on the new components. In this paper, ...
In order to make requirements comprehensible to humans and as unambiguous as possible, a glossary and/or domain model is needed for defining the terminology used. Unless these are...
Katharina Wolter, Michal Smialek, Daniel Bildhauer...
In this paper, both a UML model of requirement and a UML model of a design are defined as a pair of class diagram and a family of sequence diagrams. We then give an unified semant...
In this work, we propose a framework for quantifying non-functional requirements (NFRs). This framework uses quality characteristics of the execution domain, application domain an...