betaFeedback

WorksComputer Science

Systematic Mapping Protocol. Generative AI-Augmented Requirements Engineering: A Systematic Mapping Study of Practices, Specifications, and Reuse in Software Development

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.

Systematic Mapping Protocol

Introduction

Requirements engineering (RE) is widely recognized as one of the most critical phases of software development, since defects introduced in requirements propagate to every subsequent activity and become increasingly costly to correct [1] [2]. RE comprises the elicitation, analysis, negotiation, specification, validation, and management of requirements, and its main work products, notably specifications, constitute the basis on which systems are designed, built, and tested [2] [3] [4].

Since the emergence of large language models capable of generating text from a small number of examples [5], generative artificial intelligence (GenAI) has been increasingly applied across software engineering [6]. RE, being largely based on natural language, has been one of the areas where this adoption has been most visible, continuing a long research tradition on natural language processing for RE [7]. Several secondary studies have recently mapped or reviewed this literature [8] [9] [10] [11], showing a strong concentration on early RE activities, such as elicitation and analysis, and on prompting strategies and evaluation methods.

At the same time, industry practice has begun to promote specification-driven development (SDD), in which structured specifications are used as the primary input for AI-assisted design, code generation, and testing [12]. This shift raises a question that the existing secondary studies do not address as their main focus: to what extent does GenAI-augmented RE produce specifications that are sufficiently precise, structured, verifiable, traceable, and reusable to serve as a reliable basis for subsequent activities of the software life cycle?

This study addresses that question by means of a systematic mapping study (SMS), following the guidelines of Petersen et al. [13] [14] and Kitchenham et al. [15]. Its central premise is that RE is the core of the process under study, and that specifications must be characterized both by their relationship to the needs they express and by their use in guiding development, testing, and reuse. Accordingly, the study does not aim to describe the use of AI throughout the life cycle in general, but to map how GenAI is used to improve RE and how RE work products are exploited downstream.

The expected contributions of the study are:

  • a classified map of research on GenAI-augmented RE, organized by RE activity, process organization, work product, representation, AI integration approach, downstream use, quality control mechanism, and research type;

  • a classified catalog of the practices reported in the literature;

  • the identification of research concentrations and gaps, particularly regarding the downstream use of specifications;

  • a foundation for future systematic literature reviews and for the design of an integrated GenAI-augmented RE process.

This protocol is structured as follows. Section 2 summarizes the background of the study. Section 3 reviews related secondary studies. Section 4 describes the research method, including the research questions, search strategy, study selection, data extraction, data analysis, and tool support. Section 5 discusses threats to validity and their mitigation. Section 6 defines the scope limitations. Section 7 describes how protocol amendments are handled. Section 8 describes the supplementary material and Section 9 concludes.

Background

Requirements engineering

RE is the subfield of software engineering concerned with discovering, documenting, analyzing, validating, and managing the requirements of a system throughout its life cycle [1] [2] [3]. ISO/IEC/IEEE 29148 [4] defines the characteristics of well-formed requirements, both for individual requirements (necessary, appropriate, unambiguous, complete, singular, feasible, verifiable, correct, and conforming) and for sets of requirements (complete, consistent, feasible, comprehensible, and able to be validated). This study adopts these characteristics as the reference set of quality attributes, complemented by traceability.

Generative artificial intelligence

GenAI refers to models capable of producing new content, such as text, code, or models, from instructions expressed in natural language. Large language models, trained on extensive corpora and adaptable to new tasks through instructions with or without examples [5], are the most widespread form of GenAI in software engineering [6]. They can be integrated into RE through different approaches, including direct prompting, chain-of-thought prompting, retrieval-augmented generation, fine-tuning, and agent-based architectures [9] [16].

Specification-driven development

Specification-driven development (SDD), also referred to as spec-driven development, is an emerging industrial approach in which structured specifications act as the primary artifact from which AI assistants derive plans, code, and tests [12]. Because the term originated in industry and has limited academic presence, this study does not restrict itself to that label: it includes any RE approach whose work products are used as a source, constraint, or validation criterion for subsequent activities.

Related work

A preliminary search identified the following secondary studies related to the scope of this SMS (Table 1). They were used to refine the research questions and search terms, and their primary studies will contribute to the control set used to validate the search strings (§ 12).

StudyTypePeriod and studiesMain focus
Zhao et al. (2021) [7]SMS1983–2019; 404 studiesNatural language processing for RE, prior to the widespread adoption of GenAI
Hou et al. (2024) [6]SLR2017–2024; 395 studiesLLMs across software engineering tasks, including RE
Cheng et al. (2025) [8]SLR2019–2024; 105 studies (extended to 238 studies up to 2025 in a later version)GenAI applications across RE phases, models and techniques used, and implementation challenges
Zadenoori et al. (2025) [9]SLR2023–2024; 74 studiesLLMs for RE: publication trends, supported RE activities, prompting strategies, and evaluation methods
Hemmat et al. (2025) [10]SRNot stated hereResearch directions for NLP and LLMs in software requirements engineering
Lourenço et al. [11]SMS2020–2025; 51 studiesQuality evaluation of functional requirements generated by LLMs

Table 1. Related secondary studies

These studies show that GenAI-augmented RE has been characterized mainly in terms of supported activities, models, and prompting strategies. Zadenoori et al. [9] report that code, test, and traceability artifacts account for a small share of the work products addressed in the literature. None of the studies takes as its main focus the specifications produced by GenAI-augmented RE and their use in subsequent activities. This gap justifies the present SMS, whose distinctive axes are the work products of RE (RQ3) and their downstream use, including SDD and reuse (RQ5).

Research method

The study follows the guidelines for systematic mapping studies in software engineering of Petersen et al. [13] [14] and Kitchenham et al. [15], the snowballing guidelines of Wohlin [17], and the procedure applied by the authors in a previous SMS [18] [19] [20]. Figure 1 summarizes the search and selection process.

Search and selection process

Figure 1. Search and selection process

Objective

This study aims to identify and classify research on requirements engineering (RE) augmented by generative artificial intelligence (GenAI). The mapping covers the activities, practices, process organization, work products, notations, and forms of AI integration reported in the literature.

Particular attention is given to specifications and to their use as input for subsequent activities, namely specification-driven development (SDD), design and code generation, test derivation, verification, and reuse.

The resulting map is intended to:

  • identify areas of research concentration and gaps;

  • build a classified catalog of reported practices;

  • inform future systematic literature reviews and the design of an integrated GenAI-augmented RE process.

The following guiding principle governs the formulation of the research questions and the application of the selection criteria:

Requirements engineering is the core of the process under study. Specifications are among its principal work products, and this study characterizes them both by their relationship to the needs they express and by their use in guiding software development, testing, and reuse.

Research and publication questions

A set of research questions (RQ) has been designed to accomplish this goal (Table 3), which were designed after applying the PICOC approach (Table 2).

Table 2. PICOC

RQ#Research questionDescription
RQ1Which RE activities do the studies address and which practices do they report?• Activity: elicitation, analysis, negotiation, specification, validation, management, traceability, evolution, or reuse.<br>• Practice type: traditional practice augmented by AI, adapted traditional practice, or emerging practice.
RQ2How is the RE process organized in the reported approaches?• Structure: single task, sequential workflow, iterative workflow, or multi-agent system.<br>• Degree of automation: assistance, collaboration, supervised autonomy, or full autonomy.<br>• Point of human intervention: definition, review, approval, or correction.
RQ3Which work products are generated, transformed, or related?• Artifact: user stories, use cases, functional and non-functional requirements, acceptance criteria, business rules, conceptual and domain models, data dictionaries, or structured specifications.<br>• Level of formalization: informal, semi-structured, structured, or formal.
RQ#Research questionDescription
RQ4Which notations, AI models, integration approaches, and tools are reported?• Notation or format: unconstrained natural language, template-based natural language, UML, BPMN, SysML, formal language, or structured format.<br>• Model family: by provider and by availability (proprietary or open).<br>• Integration approach: zero-shot prompting, few-shot prompting, chain-of-thought prompting, retrieval-augmented generation, fine-tuning, or agent-based approaches.<br>• Tools and integration with repositories.
RQ5For which downstream activities are RE work products used?• Use: specification-driven development, design generation, code generation, test derivation, conformance verification, or reuse of requirements, models, or components.<br>• Traceability: whether it is reported, and between which artifacts.
RQ6Which requirements quality attributes do the studies consider, and through which mechanisms are they controlled?• Attribute, following ISO/IEC/IEEE 29148: characteristics of individual requirements (necessary, appropriate, unambiguous, complete, singular, feasible, verifiable, correct, conforming) and of sets of requirements (complete, consistent, feasible, comprehensible, able to be validated), complemented by traceability. Mechanism: human review, automated verification, metrics, testing, or regeneration.<br>• Mechanism: human review, automated verification, metrics, testing, or regeneration.
RQ7Which research types and validation methods are reported?• Research type, following Wieringa et al. [21]: solution proposal, validation research, evaluation research, philosophical paper, opinion paper, or experience paper.<br>• Method: experiment, case study, survey, proof of concept, or none.<br>• Setting: academic, industrial, or mixed.<br>• Benefits and limitations: recorded as stated by the authors, without appraisal.

Table 3. Research questions

ElementDefinition
PopulationStudies on software requirements engineering.
InterventionUse of GenAI (large language models and foundation models) in RE activities.
ComparisonNot applicable.
OutcomeReported practices, process organization, work products, representations, downstream uses, quality control mechanisms, and research types.
ContextSoftware development in academic and industrial settings.

Table 11.

Each research question is associated with a classification scheme that defines the fields of the data extraction form.

RQ6 records what the studies report about the quality of the requirements they produce; it does not assess the quality of the studies themselves. Likewise, RQ7 records the reported benefits and limitations as stated by the authors, without appraisal.

In addition, the publication questions in Table 4 characterize the bibliographic and demographic landscape of the field.

PQ#Publication questionDescription
PQ1In which language were the studies published?To know the distribution of studies by language: English, Spanish or Portuguese.
PQ2Where have the studies been published?To know the distribution of studies by type of venue: conference, journal or workshop.
PQ3How has the quantity of studies evolved over time?Publications per year.
PQ4What are the authors’ affiliations?Classify the affiliations into three categories: academy, industry or both. We will consider the affiliations of all the authors.
PQ5Which countries are the most active?Considering the author’s affiliations (all authors).

Table 4. Publication questions

Search strategy

The selected search strategy includes two approaches to look for the primary studies. The first one is an automatic search on the most important online sources for scientific studies (digital libraries and databases). The second one, used in order to ensure the completeness of our set of studies, is the snowballing technique. It comprises the following activities, represented in Figure 1:

  1. Build control set. A set of known relevant primary studies is compiled from the related secondary studies (Table 1) and from the researchers' knowledge. It is used to verify that the search strings retrieve the studies they are expected to retrieve.

  2. Select sources. The digital libraries and complementary sources are confirmed, and access and export formats are verified.

  3. Design the search string. Search strings (Table 5) are built from the PICOC (Table 2) and adapted to the syntax of each source.

SourceSearch string
ScopusTITLE-ABS-KEY("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements validation" OR "requirements management" OR "requirements traceability" OR "software requirement*" OR "user stor*" OR "use case specification*" OR "use case model*" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development") AND TITLE-ABS-KEY("generative AI" OR "generative artificial intelligence" OR "large language model*" OR llm* OR gpt* OR chatgpt OR "foundation model*" OR gemini OR llama OR claude OR copilot OR deepseek OR mistral OR palm)
IEEE Xplore("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements validation" OR "requirements management" OR "requirements traceability" OR "software requirements" OR "user stories" OR "user story" OR "use case specification" OR "use case model" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development") AND ("generative AI" OR "generative artificial intelligence" OR "large language model" OR "large language models" OR LLM OR LLMs OR GPT OR chatgpt OR "foundation model" OR "foundation models" OR gemini OR llama OR claude OR copilot OR deepseek OR mistral OR palm)
ACM DL(Title:("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements validation" OR "requirements management" OR "requirements traceability" OR "software requirements" OR "user stories" OR "user story" OR "use case specification" OR "use case model" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development") OR Abstract:("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements validation" OR "requirements management" OR "requirements traceability" OR "software requirements" OR "user stories" OR "user story" OR "use case specification" OR "use case model" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development") OR Keyword:("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements
SourceSearch string
validation" OR "requirements management" OR "requirements traceability" OR "software requirements" OR "user stories" OR "user story" OR "use case specification" OR "use case model" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development")) AND (Title:("generative AI" OR "generative artificial intelligence" OR "large language model" OR "large language models" OR LLM OR LLMs OR GPT OR ChatGPT OR "foundation model" OR "foundation models" OR Gemini OR LLaMA OR Claude OR Copilot OR DeepSeek OR Mistral OR PaLM) OR Abstract:("generative AI" OR "generative artificial intelligence" OR "large language model" OR "large language models" OR LLM OR LLMs OR GPT OR ChatGPT OR "foundation model" OR "foundation models" OR Gemini OR LLaMA OR Claude OR Copilot OR DeepSeek OR Mistral OR PaLM) OR Keyword:("generative AI" OR "generative artificial intelligence" OR "large language model" OR "large language models" OR LLM OR LLMs OR GPT OR ChatGPT OR "foundation model" OR "foundation models" OR Gemini OR LLaMA OR Claude OR Copilot OR DeepSeek OR Mistral OR PaLM))
Springer Link("requirements engineering" OR "requirements elicitation" OR "requirements analysis" OR "requirements specification" OR "requirements validation" OR "requirements management" OR "requirements traceability" OR "software requirements" OR "user stories" OR "user story" OR "use case specification" OR "use case model" OR "acceptance criteria" OR "specification-driven development" OR "spec-driven development") AND ("generative AI" OR "generative artificial intelligence" OR "large language model" OR "large language models" OR LLM OR LLMs OR GPT OR ChatGPT OR "foundation model" OR "foundation models" OR Gemini OR LLaMA OR Claude OR Copilot OR DeepSeek OR Mistral OR PaLM)
SOL("requirements engineering" OR "requirements elicitation" OR "requirements specification" OR "software requirements" OR "user stories" OR "engenharia de requisitos" OR "elicitação de requisitos" OR "especificação de requisitos" OR "requisitos de software" OR "histórias de usuário") AND ("generative AI" OR "large language model" OR "large language models" OR LLM OR ChatGPT OR GPT OR "inteligência artificial generativa" OR "IA generativa" OR "modelos de linguagem")
SciELO("requirements engineering" OR "requirements elicitation" OR "requirements specification" OR "software requirements" OR "user stories" OR "ingeniería de requisitos" OR "ingeniería de requerimientos" OR "especificación de requisitos" OR "especificación de requerimientos" OR "requisitos de software" OR "requerimientos de software" OR "historias de usuario" OR "engenharia de requisitos" OR "especificação de requisitos" OR "histórias de usuário") AND ("generative AI" OR "large language model" OR "large language models" OR LLM OR ChatGPT OR GPT OR "inteligencia artificial generativa" OR "IA generativa" OR "modelos de lenguaje" OR
SourceSearch string
"inteligência artificial generativa" OR "modelos de linguagem" OR Gemini OR LLaMA OR Claude OR Copilot OR DeepSeek OR Mistral OR PaLM)

Table 5. Search strings

  1. Run pilot search. The strings are run with no time restriction to verify the retrieval of the control set and to establish the starting year. If the strings are inadequate, they are redesigned.

  1. Run the searches. The final strings are run in all sources, with the starting year applied, and the original exports are preserved.

Digital libraries

The automated search is conducted in four digital libraries frequently used in software engineering secondary studies: Scopus, IEEE Xplore, ACM Digital Library, and Springer Link. To capture studies published in Spanish and Portuguese, two complementary sources are also searched: SBC OpenLib (SOL), which hosts the proceedings of the Workshop on Requirements Engineering (WER) and other Brazilian software engineering venues, and SciELO. Search strings are adapted to the syntax of each source and, for the complementary sources, translated into Spanish and Portuguese.

Duplicates are resolved as follows: for works with an extended version, the most recent version is retained; for exact duplicates, the record is retained according to the source priority Scopus, IEEE Xplore, Springer Link, ACM Digital Library, SOL, and SciELO.

Search strings

Each string combines two blocks of terms with AND: block A covers RE and its work products, including SDD; block B covers GenAI. The term “use case” is restricted to “use case specification” and “use case model” to avoid noise from expressions such as “use cases of LLMs”. In ACM Digital Library, the search is restricted to title, abstract, and keywords. Table 5 presents the strings, which will be validated and, if necessary, adjusted in the pilot search; any adjustment will be recorded as a protocol amendment.

In Springer Link, which searches full text, the content-type filter (article and conference paper) and the discipline filter (Computer Science) are applied and recorded. For IEEE Xplore, SOL, and SciELO, the pilot search verifies that the strings comply with the term limits and Boolean syntax supported by each source; where a string is not supported, it is split into documented partial searches.

Pilot search

A pilot search is run with no time restriction to identify the earliest evidence of the object of this study. That evidence is defined as the earliest study that addresses at least one RE activity using GenAI and is not excluded by criteria EC7 to EC9. The publication year of that study is adopted as the starting year. The pilot search also computes the proportion of the control set retrieved by the strings. The pilot search, the identified study, the control set recall, and the resulting decisions are recorded and reported.

Study selection

Exclusion criteria

A study is included if it meets none of the exclusion criteria which are presented in Table 6.

EC#Description
EC1The study is not written in English, Spanish or Portuguese.
EC2The study is not peer-reviewed. Preprints are accepted only when their acceptance at a peer-reviewed venue can be verified; if the published version is available, it is retained instead of the preprint.
EC3The study is a short paper (five pages or fewer).
EC#Description
EC4The study was published before the year of the earliest evidence of GenAI-augmented RE, as established by the pilot search.
EC5A more recent extended version of the same work exists.
EC6The study is a secondary or tertiary study. Such studies are considered as related work.
EC7The study does not address any RE activity.
EC8GenAI is not part of the proposed approach, its application, or its evaluation. This includes studies that rely exclusively on non-generative AI techniques.
EC9The study focuses on design, code, or testing without explicitly describing requirements or specifications as a source, constraint, or validation criterion.

Table 6. Exclusion criteria.

Reviewer calibration

Before screening, all reviewers independently assess a common sample of studies. Agreement is measured using Cohen's kappa [22] (two reviewers) or Fleiss' kappa [23] (more than two). Screening begins only when kappa reaches at least 0.61, which corresponds to substantial agreement [24]. Otherwise, the reviewers jointly analyze the disagreements and record written interpretation notes for the criteria, without modifying them, and calibration is repeated with a new sample. Agreement is measured again at the end of title and abstract screening and reported.

Screening and conflict resolution

Each study is assessed by at least two reviewers, independently and in blind mode, first on the basis of its title and abstract and then on its full text. Each reviewer classifies the study as include, uncertain, or exclude, indicating the applicable criterion as the exclusion reason. Disagreements are resolved according to the matrix proposed by Petersen et al. [13] (Table 7).

Table 7. Criteria to resolve disagreements.

Researcher 1
IncludeUncertainExclude
Researcher 2IncludeA: includedB: includedD: full reading
UncertainB: includedC: full readingE: excluded
ExcludeD: full readingE: excludedF: excluded

Table 12.

Studies in cases C and D are read in full and reassessed until they reach case A, B, E, or F. The studies included at the end of full-text screening constitute the seed set for snowballing.

Snowballing

Backward snowballing (references) and forward snowballing (citations) are applied to the seed set, following Wohlin [17]. Citationchaser [25] is used as the primary tool and Scopus as a complement to improve coverage of software engineering venues. Each seed is processed individually, and the originating seed, direction, iteration, tool, and query date are recorded for each candidate. Candidates are deduplicated against the entire corpus and screened as described in § 14 to § 16. Studies included in an iteration become the seeds of the next one, and the process ends when an iteration yields no new included studies.

Data extraction form

Data are extracted from each primary study into the data extraction form (DEF) presented in Table 8 and Table 9. The values listed are the initial classification schemes; they may be refined through keywording (§ 19), and any category added is recorded and applied to all studies. Fields marked as multiple accept more than one value. Each study is extracted by one researcher and verified by a second researcher.

FieldRQAccepted values
Study identifier—S### (automated search), SB### (snowballing); DOI
RE activity (multiple)RQ1Elicitation; analysis; negotiation; specification; validation; management; traceability; evolution; reuse
Practice typeRQ1Traditional practice augmented by AI; adapted traditional practice; emerging practice
Practice descriptionRQ1Free text: objective, activities, inputs, outputs, and context of application

Table 8. Data extraction form for research questions

FieldPQAccepted values
LanguagePQ1English; Spanish; Portuguese
Venue namePQ2Name of the conference, workshop, or journal
YearPQ3Year of publication
AffiliationPQ4Academia; industry; both
Countries (multiple)PQ5Countries of all authors' affiliations

Table 9. Data extraction form for publication questions

FieldRQAccepted values
Process structureRQ2Single task; sequential workflow; iterative workflow; multi-agent system; not reported
Degree of automationRQ2Assistance; collaboration; supervised autonomy; full autonomy; not reported
Point of human intervention (multiple)RQ2Definition; review; approval; correction; none; not reported
Artifact (multiple)RQ3User stories; use cases; functional requirements; non-functional requirements; acceptance criteria; business rules; conceptual or domain models; data dictionaries; structured specifications; other
Level of formalizationRQ3Informal; semi-structured; structured; formal
Notation or format (multiple)RQ4Unconstrained natural language; template-based natural language; UML; BPMN; SysML; formal language; structured format; other
Model (multiple)RQ4Model name and version; provider; availability (proprietary or open)
Integration approach (multiple)RQ4Zero-shot prompting; few-shot prompting; chain-of-thought prompting; retrieval-augmented generation; fine-tuning; agent-based; other
ToolsRQ4Free text: tools and integration with repositories
Downstream use (multiple)RQ5Specification-driven development; design generation; code generation; test derivation; conformance verification; reuse of requirements; reuse of models; reuse of components; none
TraceabilityRQ5Reported (yes or no); linked artifacts
Quality attributes (multiple)RQ6Individual requirement: necessary; appropriate; unambiguous; complete; singular; feasible; verifiable; correct; conforming. Set of requirements: complete; consistent; feasible; comprehensible; able to be validated. Additional: traceable. Other; not reported
Control mechanism (multiple)RQ6Human review; automated verification; metrics; testing; regeneration; other; not reported

Table 13 (PDF p. 17).

FieldRQAccepted values
Research typeRQ7Solution proposal; validation research; evaluation research; philosophical paper; opinion paper; experience paper [21]
Empirical methodRQ7Experiment; case study; survey; proof of concept; none
SettingRQ7Academic; industrial; mixed
Reported benefitsRQ7Free text, as stated by the authors
Reported limitationsRQ7Free text, as stated by the authors
Notes—Free text: extraction remarks and doubts

Table 14 (PDF p. 18).

Data analysis

The analysis is descriptive, as is appropriate for a mapping study [13]. The initial classification schemes are refined through keywording of abstracts [14]: when the extracted data reveal recurring concepts not covered by the schemes, new categories are proposed, agreed upon by two researchers, recorded, and applied to all studies.

For each dimension, frequencies and percentages are reported. Relationships between dimensions are presented through cross-tabulations and bubble plots, in particular:

  • RE activity (RQ1) by downstream use (RQ5);

  • artifact type (RQ3) by level of formalization (RQ3) and notation (RQ4);

  • integration approach (RQ4) by RE activity (RQ1);

  • quality attributes and control mechanisms (RQ6) by artifact type (RQ3);

  • research type (RQ7) by RE activity (RQ1) and by year (PQ2).

Publication questions are presented through distributions by venue type, language, year, affiliation, and country. Gaps are identified as combinations of dimensions with few or no studies, particularly between RE work products and their downstream use.

Tool support

Each phase of the study is supported by a designated tool (Table 10). Tool versions and access dates are recorded in the study's traceability dataset.

PhaseToolPurpose
Protocol definitionParsifalProtocol design and registration.
SearchesScopus, IEEE Xplore, ACM Digital Library, Springer Link, SOL, SciELOAutomated search.
Deduplication and screeningRayyanDeduplication, independent blind screening, and conflict resolution; exclusion criteria configured as exclusion reasons.
SnowballingCitationchaser, complemented by ScopusBackward and forward snowballing.
Data extractionParsifalData extraction form.

Table 10. Tool support

PhaseToolPurpose
Reference managementZoteroManagement of the final set of studies and citation in the report.
TraceabilitySpreadsheetConsolidated traceability dataset.

Use of generative AI: GenAI tools may support search string design, translation, data extraction, and analysis. All AI-assisted outputs are verified and adjusted by a researcher. Inclusion and exclusion decisions are made exclusively by researchers. Relevance predictions offered by screening tools are not consulted during independent screening. Every use of AI is logged, recording the tool and model version, date, phase, instruction, output, and verification. The log is published as supplementary material.

Threats to validity

In order to minimize the impact of the validity threats categorized by Petersen et al. [13] that could affect our study, we present them with the corresponding mitigation actions:

Descriptive validity

Descriptive validity concerns the extent to which observations are described objectively and accurately.

  • Data are recorded in a structured data extraction form with predefined accepted values (Table 8 and Table 9).

  • An initial meeting is held with all researchers to unify concepts and criteria and to demonstrate the extraction process with examples.

  • Each extraction is verified by a second researcher.

  • The data extraction form and the extracted data are published.

Theoretical validity

Theoretical validity concerns the ability to capture what is intended to be captured.

  • Search coverage. Search strings are tailored to six sources, including two complementary sources for Spanish and Portuguese, and are validated against a control set of known studies during the pilot search.

  • Combined search methods. Automated search and iterative backward and forward snowballing are combined to reduce the risk of missing relevant studies [26].

  • Terminological variability. GenAI terminology evolves rapidly and SDD has limited academic presence. Block B includes generic and model-specific terms, and SDD is included only as an alternative term within block A.

  • Snowballing coverage. Citationchaser relies on Lens.org, whose coverage of software engineering venues may be incomplete; Scopus is used as a complement.

  • Selection bias. Exclusion criteria are explicit and operational; reviewers are calibrated with a kappa threshold of 0.61; each study is reviewed independently and in blind mode by at least two researchers; and disagreements are resolved with a predefined matrix.

  • Language bias. Studies in English, Spanish, and Portuguese are included; studies in other languages are excluded, which may have a minor impact.

  • Publication bias and recency. The field evolves rapidly and many studies first appear as preprints. Only preprints with verifiable peer-reviewed acceptance are included, which may omit the most recent work; this is acknowledged as a limitation.

  • Use of GenAI by the researchers. AI support may introduce errors in extraction or translation. All AI-assisted outputs are verified by a researcher, selection decisions are made exclusively by researchers, and every use is logged and reported.

Generalizability

Generalizability concerns the ability to generalize the results to the domain.

  • The research questions and classification schemes are general enough to classify studies regardless of application domain, model, or industry [27].

  • However, because GenAI models evolve rapidly, results reflect the state of research at the time of the search, which is recorded and reported.

Interpretive validity

Interpretive validity is achieved when conclusions are reasonable given the data.

  • Every conclusion is validated by at least two researchers.

  • Researchers with experience in RE and in GenAI participate in the interpretation of data.

  • New classification categories emerging from keywording are agreed upon by two researchers and applied to all studies.

Repeatability

The research process must be detailed enough to be repeated.

  • This protocol is published before the study is conducted.

  • Search strings, search dates, filters, and original exports are preserved for each source.

  • The traceability dataset records every decision, its rationale, and the reviewers involved.

  • Tools, versions, and the log of AI use are reported.

  • Any deviation from the protocol is recorded as an amendment (§ 28).

Scope limitations

Consistent with the nature of a mapping study, the following are outside the scope of this study:

  • quality assessment of primary studies;

  • synthesis of the effectiveness of practices;

  • design of the integrated RE process, which is proposed as future work building on the resulting map.

Protocol amendments

Deviations from this protocol that arise during the study, such as adjustments to the search strings after the pilot search, the starting year, interpretation notes for the exclusion criteria, or new classification categories, are recorded in an amendment log with their date, description, rationale, and affected phase. The amendment log is published together with the final report.

Supplementary material

The following material will be made publicly available in an open repository: this protocol and its amendments; search strings, dates, and the number of results per source; the traceability dataset; reviewer agreement values; the data extraction form and extracted data; the snowballing records; and the log of AI use.

Conclusion

This protocol defines the procedure for a systematic mapping study on generative AI-augmented requirements engineering. Unlike existing secondary studies, which focus on the RE activities supported and the prompting strategies used, this study places the work products of RE, and particularly specifications, at the center of the mapping, and examines how they are used in subsequent activities such as specification-driven development, design and code generation, test derivation, verification, and reuse.

The protocol specifies seven research questions with explicit classification schemes, a search strategy across six sources in three languages validated through a pilot search and a control set, a selection procedure based on operational exclusion criteria, reviewer calibration, and blind independent screening, iterative backward and forward snowballing, a data extraction form, and a descriptive analysis approach. It also defines the tool support, including the controlled use of GenAI by the researchers, and the mitigation of threats to validity.

The resulting map is expected to reveal where research on GenAI-augmented RE is concentrated, which gaps remain between RE work products and their downstream use, and which practices may form the basis of an integrated RE process whose specifications serve as a reliable foundation for the rest of the software life cycle.

References

References

  1. [1]B. Nuseibeh and S. Easterbrook, “Requirements engineering: a roadmap,” in Proceedings of the Conference on The Future of Software Engineering, Limerick Ireland: ACM, May 2000, pp. 35–46. doi: 10.1145/336512.336523.DOI
  2. [2]K. E. Wiegers and J. Beatty, Software requirements, Third edition. Redmond, Washington: Microsoft Press, a division of Microsoft corporation, 2013.
  3. [3]Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), Version 4.0a. IEEE Computer Society, 2025.
  4. [4]Systems and software engineering — Life cycle processes — Requirements engineering, ISO/IEC/IEEE 29148:2018, Geneva., Nov. 2018. doi: 10.1109/IEEESTD.2018.8559686.DOI
  5. [5]T. B. Brown et al., “Language Models are Few-Shot Learners,” in Advances in Neural Information Processing Systems, Curran Associates, Inc., 2020, pp. 1877–1901.arxiv.org/abs/2005.14165
  6. [6]X. Hou et al., “Large Language Models for Software Engineering: A Systematic Literature Review,” ACM Transactions on Software Engineering and Methodology, vol. 33, no. 8, pp. 1–79, Dec. 2024. doi: 10.1145/3695988.DOI
  7. [7]L. Zhao et al., “Natural Language Processing (NLP) for Requirements Engineering: A Systematic Mapping Study,” ACM Computing Surveys, vol. 54, no. 3, 2021.
  8. [8]H. Cheng et al., “Generative AI for Requirements Engineering: A Systematic Literature Review,” Softw Pract Exp, vol. 56, no. 2, pp. 141–170, Feb. 2026, doi: 10.1002/spe.70029.DOI
  9. [9]M. A. Zadenoori, J. Dąbrowski, W. Alhoshan, L. Zhao, and A. Ferrari, “Large Language Models (LLMs) for Requirements Engineering (RE): A Systematic Literature Review,” Sep. 14, 2025, arXiv: arXiv:2509.11446. doi: 10.48550/arXiv.2509.11446.
  10. [10]A. Hemmat, M. Sharbaf, S. Kolahdouz-Rahimi, K. Lano, and S. Y. Tehrani, “Research directions for using LLM in software requirement engineering: a systematic review,” Front. Comput. Sci., vol. 7, p. 1519437, Mar. 2025, doi: 10.3389/fcomp.2025.1519437.
  11. [11]L. M. Lourenço, C. Bezerra, and A. P. Marques, “Quality Evaluation of Software Functional Requirements Generated by LLMs: A Systematic Mapping Study,” in Anais do Simpósio Brasileiro de Sistemas de Informação (SBSI), May 2026, pp. 161–180. doi: https://doi.org/10.5753/sbsi.2026.248317.
  12. [12]“GitHub Spec Kit.” [Online]. Available: https://github.com/github/spec-kit
  13. [13]K. Petersen, S. Vakkalanka, and L. Kuzniarz, “Guidelines for conducting systematic mapping studies in software engineering: An update,” Information and Software Technology, vol. 64, pp. 1–18, Aug. 2015. doi: 10.1016/j.infsof.2015.03.007.DOI
  14. [14]K. Petersen, R. Feldt, S. Mujtaba, and M. Mattsson, “Systematic Mapping Studies in Software Engineering,” presented at the 12th International Conference on Evaluation and Assessment in Software Engineering (EASE), Jun. 2008. doi: 10.14236/ewic/EASE2008.8.DOI
  15. [15]B. A. Kitchenham, D. Budgen, and P. Brereton, Evidence-Based Software Engineering and Systematic Reviews. Chapman and Hall/CRC, 2015. doi: 10.1201/b19467.DOI
  16. [16]A. Vogelsang and J. Fischbach, “Using Large Language Models for Natural Language Processing Tasks in Requirements Engineering: A Systematic Guideline,” May 15, 2024, arXiv: arXiv:2402.13823. doi: 10.48550/arXiv.2402.13823.arxiv.org/abs/2402.13823
  17. [17]C. Wohlin, “Guidelines for snowballing in systematic literature studies and a replication in software engineering,” in Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering, London England United Kingdom: ACM, May 2014, pp. 1–10. doi: 10.1145/2601248.2601268.DOI
  18. [18]J. L. Barros-Justo, F. Pinciroli, S. Matalonga, and N. Martínez-Araujo, “What software reuse benefits have been transferred to the industry? A systematic mapping study,” Information and Software Technology, vol. 103, pp. 1–21, Nov. 2018, doi: 10.1016/j.infsof.2018.06.003.
  19. [19]F. Pinciroli, J. L. Barros Justo, and R. Forradellas, “Systematic mapping study: On the coverage of aspect-oriented methodologies for the early phases of the software development life cycle,” Journal of King Saud University - Computer and Information Sciences, vol. 34, no. 6, pp. 2883–2896, Jun. 2022, doi: 10.1016/j.jksuci.2020.10.029.
  20. [20]F. Pinciroli, L. Antonelli, and Á. T. Bermúdez, “Systematic mapping study: on agile strategies for software project management according to complexity factors,” Innovations Syst Softw Eng, vol. 22, no. 1, p. 9, Jun. 2026, doi: 10.1007/s11334-026-00626-8.DOI
  21. [21]R. Wieringa, N. Maiden, N. Mead, and C. Rolland, “Requirements engineering paper classification and evaluation criteria: a proposal and a discussion,” Requirements Eng, vol. 11, no. 1, pp. 102–107, Mar. 2006, doi: 10.1007/s00766-005-0021-6.DOI
  22. [22]J. Cohen, “A Coefficient of Agreement for Nominal Scales,” Educational and Psychological Measurement, vol. 20, no. 1, pp. 37–46, Apr. 1960, doi: 10.1177/001316446002000104.DOI
  23. [23]J. L. Fleiss, “Measuring nominal scale agreement among many raters.,” Psychological Bulletin, vol. 76, no. 5, pp. 378–382, Nov. 1971, doi: 10.1037/h0031619.DOI
  24. [24]J. R. Landis and G. G. Koch, “The Measurement of Observer Agreement for Categorical Data,” Biometrics, vol. 33, no. 1, p. 159, Mar. 1977, doi: 10.2307/2529310.DOI
  25. [25]N. R. Haddaway, M. J. Grainger, and C. T. Gray, “Citationchaser: A tool for transparent and efficient forward and backward citation chasing in systematic searching,” Research Synthesis Methods, vol. 13, no. 4, pp. 533–545, Jul. 2022, doi: 10.1002/jrsm.1563.DOI
  26. [26]D. Badampudi, C. Wohlin, and K. Petersen, “Experiences from using snowballing and database searches in systematic literature studies,” in Proceedings of the 19th International Conference on Evaluation and Assessment in Software Engineering, Nanjing China: ACM, Apr. 2015, pp. 1–10. doi: 10.1145/2745802.2745818.DOI
  27. [27]K. Petersen and C. Gencel, “Worldviews, Research Methods, and their Relationship to Validity in Empirical Software Engineering Research,” in 2013 Joint Conference of the 23rd International Workshop on Software Measurement and the 8th International Conference on Software Process and Product Measurement, Ankara, Turkey: IEEE, Oct. 2013, pp. 81–89. doi: 10.1109/IWSM-Mensura.2013.22.DOI

Paper details

vlnc:W_dz9uz5t2
Version
v1 · latest
Published
Fresh — added to the Hub within the last 30 days
Added
License
CC BY 4.0
Usage

views · 10

downloads · 0

A view counts once per browser per day, a download each time the PDF is requested.

  • Computer Science

Not recorded for this paper

View statement
Looking for related papers…
Contents