Deriving Empirically Grounded NFR Specifications from Practitioner Discourse: A Validated Methodology Applied to Trustworthy APIs in the AI Era
Information · 22.03.2026 · 17 (3) · 304
DOI: 10.3390/info17030304 ↗Kurz gefasst
Fachartikel in der Zeitschrift Information, online erschienen am 22.03.2026. Verfasst von Apitchaka Singjai. Die Arbeit wurde bisher 1-mal zitiert (Crossref) und nennt 48 Literaturangaben. Der Volltext ist frei zugänglich (Open Access, CC BY 4.0). Gefördert von: Chiang Mai University.
Abstract (Originalsprache)
Specifying non-functional requirements (NFRs) for rapidly evolving domains such as trustworthy APIs in the AI era is challenging as best practices emerge through practitioner discourse faster than traditional requirements engineering can capture them. We present a systematic methodology for deriving prioritized NFR specifications from multimedia practitioner discourse combining AI-assisted transcript analysis, grounded theory principles, and Theme Coverage Score (TCS) validation. Our five-task approach integrates purposive sampling, automated transcription with speaker diarization, grounded theory coding extracting stakeholder-specific themes with TCS quantification, MoSCoW prioritization using empirically derived thresholds (Must Have ≥85%, Should Have 65–84%, Could Have 45–64%, and Won’t Have
Förderung
- Chiang Mai University
Zitieren
APA
Singjai, A. (2026). Deriving Empirically Grounded NFR Specifications from Practitioner Discourse: A Validated Methodology Applied to Trustworthy APIs in the AI Era. Information, 17(3), 304. https://doi.org/10.3390/info17030304
Vancouver
Singjai A. Deriving Empirically Grounded NFR Specifications from Practitioner Discourse: A Validated Methodology Applied to Trustworthy APIs in the AI Era. Information. 2026;17(3):304. doi:10.3390/info17030304
BibTeX
@article{Singjai2026,
author = {Singjai, Apitchaka},
title = {Deriving Empirically Grounded NFR Specifications from Practitioner Discourse: A Validated Methodology Applied to Trustworthy APIs in the AI Era},
journal = {Information},
year = {2026},
volume = {17},
number = {3},
pages = {304},
doi = {10.3390/info17030304}
}
EUVIMED