ArticleScientific reports2026
A novel NFR-based conceptual quality framework for modern API industry.
Article in Scientific reports, 2026. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
5 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
The modern software ecosystems employ application programming interface (API) to allow interoperability and integration across various platforms. Non-functional requirements (NFRs) as quality attributes are as vital as functional requirements (FRs) in assuring software quality and user satisfaction. API quality management is a challenge to software industry owing to poor NFRs handling during API development, resulting in cost increase, project failure and dissatisfied customers. The existing standards failed in producing a comprehensive quality framework for APIs. OpenAPI Specification (OAS) focuses on functional aspects, whereas ISO/IEC 25010:2023 emphases on traditional software quality. Hence, this study proposes a novel non-functional requirement quality framework for APIs (NFRQF-API). In compliance with ISO/IEC 25,010, the framework includes key NFRs and their influencing factors to facilitate the development of high-quality APIs. Explanatory sequential mixed-methods design was applied in this study, involving a survey tool. Data were collected using a questionnaire comprising eight Likert-scale items and two open-ended items. Descriptive statistics and reliability testing were applied for quantitative data analysis, while thematic analysis was applied to evaluate the qualitative data, which supports in achieving a comprehensive expert-based justification for the conceptual feasibility and applicability of framework. Based on the experts' survey, analyses results demonstrated the potential effectiveness of the proposed framework in managing the Core, Critical, and Contextual NFRs in the entire API development lifecycle. This study bridges the gap between existing quality models and API quality assurance challenges. The structured expert-refined framework facilitates the enhancement of API quality management and offers KPI-based conceptual quality standards for the industry to design high-quality APIs by effectively handling critical NFR issues.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.