2013Unpublished venueRequires access

Maintainability-Based Requirements Prioritization by Using Artifacts Traceability and Code Metrics

Mehrina Asghar, Alessandro Marchetto, Angelo Susi, Giuseppe Scanniello

Open publisher page 8 citations

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.

About this research paper

What this paper is about

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.

Why it matters

OpenAlex reports 8 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available 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.

Key concepts: Requirement prioritization, Requirements traceability, Computer science, Non-functional testing, Traceability, Maintainability, Requirements management, Requirements analysis

Related papers

Back to paper searchBrowse research topicsOriginal source
Maintainability-Based Requirements Prioritization by Using Artifacts Traceability and Code Metrics — Research Paper | ScholarLens