Requirements prioritization is a fundamental activity during software system maintenance. Prioritize requirements, in fact, means to determine the ordering in which requirements have to be considered in a given planning or maintenance activity. Most of the existing requirements prioritization techniques and tools focus on user and non/functional requirements, while only few attempt exists to consider how requirements are actually implemented, if they are implemented. In this demonstration paper, we present a tool that prioritizes (change) requirements by using artifacts traceability information, to locate the requirements implementation, and a set of code-based metrics, to measure several properties (e.g., coupling, size, scattering) of the requirements implementation. The tool, hence, determines the requirement ordering with respect to how these requirements are implemented in a subject software system. © 2013 IEEE.
Maintainability-based requirements prioritization by using artifacts traceability and code metrics / Asghar, M. W.; Marchetto, A.; Susi, A.; Scanniello, G.. - (2013), pp. 417-420. (Intervento presentato al convegno 17th European Conference on Software Maintenance and Reengineering, CSMR 2013 tenutosi a Genova, ita nel 2013) [10.1109/CSMR.2013.62].
Maintainability-based requirements prioritization by using artifacts traceability and code metrics
Marchetto A.;
2013-01-01
Abstract
Requirements prioritization is a fundamental activity during software system maintenance. Prioritize requirements, in fact, means to determine the ordering in which requirements have to be considered in a given planning or maintenance activity. Most of the existing requirements prioritization techniques and tools focus on user and non/functional requirements, while only few attempt exists to consider how requirements are actually implemented, if they are implemented. In this demonstration paper, we present a tool that prioritizes (change) requirements by using artifacts traceability information, to locate the requirements implementation, and a set of code-based metrics, to measure several properties (e.g., coupling, size, scattering) of the requirements implementation. The tool, hence, determines the requirement ordering with respect to how these requirements are implemented in a subject software system. © 2013 IEEE.I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione