The starting point for software evolution is usually a change request, expressing the new or updated requirements on the delivered system. The requirements specified in a change ...
Filippo Ricca, Marco Torchiano, Mariano Ceccato, P...
High-level software artifacts, such as requirements, domain-specific requirements, and so on, are an important source of information that is often neglected during the reverse- an...
Jane Huffman Hayes, Giuliano Antoniol, Yann-Ga&eum...
Posing speculative questions about a software system is an important yet often unsupported activity. Current impact analysis techniques tend to focus upon the functionality of the...
Jane Cleland-Huang, Carl K. Chang, Gaurav Sethi, K...
Scenarios and goals are effective and popular techniques for requirements definition. Validation is essential in order to ensure that they represent what stakeholders actually wan...
This paper discusses the requirements and a generic framework for the integration of architectural and codebased reengineering tools. This framework is needed because there is a l...
Rick Kazman, Steven S. Woods, S. Jeromy Carri&egra...