MétaCan
Menu
Back to cohort
Record W2897142836 · doi:10.1109/modre.2018.00010

Model-Based Development with Distributed Cognition

2018· article· en· W2897142836 on OpenAlexaff
Karan Singh Hundal, Gunter Mussbacher

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsMcGill University
Fundersnot available
KeywordsMetamodelingComputer scienceModel-driven architectureSoftware engineeringKey (lock)Process (computing)Bridge (graph theory)Requirements elicitationModeling languageFormal specificationModel transformationRequirements engineeringSystems engineeringUnified Modeling LanguageSoftwareArtificial intelligenceProgramming languageEngineering

Abstract

fetched live from OpenAlex

Model Driven Engineering (MDE) allows a system to be defined using a series of models. It can refine higher level models into lower level models using model transformations, thereby automating the building of a concrete model and the software development process. This is particularly useful for Requirements Engineering since MDE can bridge the gap between early requirements models, late requirements models, and architectural models. However, requirements elicitation techniques have received little attention in terms of MDE. A major reason is the lack of a formal modelling language for some of these techniques. The definition of a metamodel is an essential step for the specification of a formal modeling language, which is a key prerequisite for Model Driven Engineering (MDE). We introduce a metamodel for Distributed Cognition, a well-known requirements elicitation technique, using the key concepts present in the framework's literature with the aim to integrate Distributed Cognition into MDE. Furthermore, we report on a preliminary case study on a software XP team to validate our metamodel.

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.003
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.004
Threshold uncertainty score0.015

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.005
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0010.001
Science and technology studies0.0010.002
Scholarly communication0.0030.002
Open science0.0020.004
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0040.001

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.018
GPT teacher head0.227
Teacher spread0.209 · 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 designTheoretical or conceptual
Domainnot available
GenreEmpirical

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

Citations1
Published2018
Admission routes1
Has abstractyes

Explore more

Same topicModel-Driven Software Engineering TechniquesFrench-language works237,207