MétaCan
Menu
Back to cohort
Record W4417131598 · doi:10.1109/ms.2025.3640399

DevSecOps for Secure and Scalable Citizen Development

2025· article· W4417131598 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Software · 2025
Typearticle
Language
FieldComputer Science
TopicOpen Source Software Innovations
Canadian institutionsHEC Montréal
Fundersnot available
KeywordsLeverage (statistics)Process (computing)ScalabilityGermanShadow (psychology)Development (topology)

Abstract

fetched live from OpenAlex

Citizen development enables business users to create and modify applications using low-code development platforms, which enhances efficiency and reduces reliance on IT departments. However, citizen development needs to be practiced with clear oversight and guardrails, rather than treated as an open-ended sandbox. Uncontrolled citizen development can introduce challenges such as unmonitored shadow IT, data security gaps, and maintenance risks. This article presents a structured DevSecOps process for citizen development in enterprise environments, based on 42 projects involving more than 100 citizen developers at a large German financial institution. The tailored process balances innovation and collaboration with robust security measures and provides actionable insights for organizations to safely leverage citizen development.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.858
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.002
Science and technology studies0.0020.000
Scholarly communication0.0010.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.017
GPT teacher head0.272
Teacher spread0.255 · 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