MétaCan
Menu
Back to cohort
Record W4308632560 · doi:10.1145/3550356.3558514

Addressing non-functional requirements of adaptive IoT systems

2022· article· en· W4308632560 on OpenAlexaff
Mirza Rehenuma Tabassum

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsToronto Metropolitan University
Fundersnot available
KeywordsComputer scienceNon-functional requirementScalabilityInteroperabilityContext (archaeology)Requirements engineeringAbstractionModel-driven architectureFunctional requirementUnified Modeling LanguageDistributed computingSoftware systemRisk analysis (engineering)Software engineeringSoftwareDatabase

Abstract

fetched live from OpenAlex

Non-functional requirements (NFR) of IoT systems increase the complexity of system development. The success of such systems also largely depends on dealing with NFRs correctly. However, inter-dependencies among NFRs often introduce conflicts. These conflicts impede implementing the system with all specified NFRs. Furthermore, the heterogeneous nature of IoT systems makes it critical to incorporate NFRs in the early stages of software development. This PhD thesis proposes a model-driven requirements engineering procedure to address different NFRs of adaptive IoT systems. This approach will incorporate non-functional requirements at different levels of abstraction with model-driven techniques to minimize conflicts among elicited NFRs. We are extending use case models, soft goal models, and behavioural models to elicit, analyze, and specify interoperability, scalability, availability, and context-awareness of IoT systems. As interoperability and context-awareness are two NFRs that affect the adaptiveness of IoT systems most, we addressed these two NFRs first. Availability and scalability NFRs will be incorporated as this thesis progresses.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.007
metaresearch head score (Gemma)0.017
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.007
Threshold uncertainty score0.037

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.017
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0010.000
Science and technology studies0.0010.001
Scholarly communication0.0030.003
Open science0.0010.002
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0010.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.240
GPT teacher head0.338
Teacher spread0.098 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2022
Admission routes1
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207