AI & ML
Systematic Mapping Protocol. Generative AI-Augmented Requirements Engineering: A Systematic Mapping Study of Practices, Specifications, and Reuse in Software Development
arXiv cs.SE0 views
arXiv:2611.23349v1 Announce Type: new Abstract: Generative artificial intelligence (GenAI), particularly large language models (LLMs), is rapidly being adopted in requirements engineering (RE). Existing secondary studies have characterized which RE activities are supported and which prompting strategies are used, but little is known about the specifications that GenAI-augmented RE produces and how they are used in subsequent activities such as specification-driven development (SDD), design and code generation, test derivation, verification, and reuse. This document presents the protocol of a systematic mapping study (SMS) that will identify and classify research on GenAI-augmented RE, with particular attention to the work products it generates and their downstream use. The protocol defines the research questions and their classification schemes, the search strategy, the study selection procedure, the data extraction form, the analysis approach, the tool support, and the threats to validity. It is published in advance to establish a prior commitment and to support the transparency and repeatability of the study.
Source:https://arxiv.org/abs/2611.23349PreviousRootSink: Reproducible C/C++ Crashes with Tested Repair SitesNextIdempotency Is Not Recovery: A Fault-Injection Study of Language-Model Agent Tool Actions
Related posts
Thống kê hiệu suất Al Ahli vs Al Nassr: Phép thử cực đại cho hàng công chủ nhà
0dev.to Data
Phân tích số liệu vòng 10 Bundesliga: Thách thức chiến thuật của FC Koln trước Bayern Munich
0dev.to Data
Dấu ấn chiến thuật của Hansi Flick: Biến số Frenkie de Jong giúp Barcelona ngược dòng trước Atletico Madrid
0dev.to Data
PMO Support Services in the UAE: What Effective Program Governance Actually Requires
0dev.to News
The draft is not the send
0dev.to Discuss

My First GitHub Issue & My First Forem (DEV.to) Issue 🚀
0dev.to Discuss