Pith. sign in

REVIEW 1 cited by

Requirement Tracing using Term Extraction

Not yet reviewed by Pith; the record is open.

This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.

SPECIMEN: schema-true, not a live event

T0 review · schema-true

One-sentence machine reading of the paper's core claim.

pith:XXXXXXXX · record.json · timestamp

arxiv 1506.08789 v1 pith:YQT3SSOW submitted 2015-06-29 cs.SE cs.CLcs.IR

classification cs.SEcs.CLcs.IR
keywords requirementsmethodtraceabilitycandidatedataextractionfrequencymetrics
verification ladder T0 review T1 audit T2 compute T3 formal
0 comments
read the original abstract

Requirements traceability is an essential step in ensuring the quality of software during the early stages of its development life cycle. Requirements tracing usually consists of document parsing, candidate link generation and evaluation and traceability analysis. This paper demonstrates the applicability of Statistical Term Extraction metrics to generate candidate links. It is applied and validated using two data sets and four types of filters two for each data set, 0.2 and 0.25 for MODIS, 0 and 0.05 for CM1. This method generates requirements traceability matrices between textual requirements artifacts (such as high-level requirements traced to low-level requirements). The proposed method includes ten word frequency metrics divided into three main groups for calculating the frequency of terms. The results show that the proposed method gives better result when compared with the traditional TF-IDF method.

Discussion (0). Continue with ORCID to comment.

Forward citations

Cited by 1 Pith paper

Reviewed papers in the Pith corpus that reference this work. Sorted by Pith novelty score. Full citation record

  1. Three-Phase Evaluation of AI-Assisted Software Development Life Cycle

    cs.SE 2026-07 conditional novelty 5.5 of 10

    In a sequential three-phase pilot, higher AI autonomy and AWS Kiro versus GitHub Copilot were associated with fewer development hours, higher RITM scores, and lower mental demand, with modestly higher frustration.

Pith tools