REVIEW 2 cited by
NALABS: Detecting Bad Smells in Natural Language Requirements and Test Specifications
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
read the original abstract
In large-scale embedded system development, requirement and test specifications are often expressed in natural language. In the context of developing such products, requirement review is performed in many cases manually using these specifications as a basis for quality assurance. Low-quality specifications can have expensive consequences during the requirement engineering process. Especially, if feedback loops during requirement engineering are long, leading to artifacts that are not easily maintainable, are hard to understand, and are inefficient to port to other system variants. We use the idea of smells to specifications expressed in natural language, defining a set of specifications for bad smells. We developed a tool called NALABS (NAtural LAnguage Bad Smells), available on https://github.com/eduardenoiu/NALABS and used for automatically checking specifications. We discuss some of the decisions made for its implementation, and future work.
Forward citations
Cited by 2 Pith papers
-
Investigating the Performance of Small Language Models in Detecting Test Smells in Manual Test Cases
Small language models with a targeted prompting scheme detect seven test-smell types in natural-language Ubuntu manual tests, with pass@2 scores of 90-97% across three models.
-
SmartDelta Methodology: Automated Quality Assurance and Optimization for Incremental System Engineering
The paper introduces a six-stage SmartDelta Methodology for quality assurance across software versions and variants and illustrates it with seven project tools, but does not empirically validate the methodology.
Discussion (0). Continue with ORCID to comment.