MétaCan
Menu
Back to cohort
Record W4241081215 · doi:10.48009/4_iis_2021_117-133

DEVOPS PARADIGM -A PEDAGOGICAL APPROACH TO MANAGE AND IMPLEMENT IT PROJECT

2021· article· en· W4241081215 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

VenueIssues in Information Systems · 2021
Typearticle
Languageen
FieldSocial Sciences
TopicEducation and Digital Technologies
Canadian institutionsKwantlen Polytechnic University
Fundersnot available
KeywordsDevOpsComputer scienceEngineering managementSoftware engineeringProcess managementEngineeringSoftware deployment

Abstract

fetched live from OpenAlex

DevOps, the widely used term in software industry, integrates the Development and IT Operations activities to frequently deliver, deploy, and release quality software features. DevOps approach emphasizes collaboration among Developments and IT operations teams throughout System Development Life Cycle (SDLC). The DevOps process is supported by wide variety of tool chains for various phases of SDLC. There exist many DevOps models. However, in this paper authors use a simple four phase pedagogical models to demonstrate principles of DevOps. In this paper authors attempt to show how DevOps principles can effectively be used to manage and implement business problems in classroom setting. Specifically, DevOps methodology is applied to manage develop and implement a small web application. This pedagogical approach is specially aimed at students who do not have prior experiences and skillsets in applying DevOps methodology and associated toolsets to every stages of SDLC. At the conclusion of the project, students gained valuable insights on how to apply DevOps principles to business problems and to select and use commonly used state of the arts tools to plan, manage, build, test, monitor, deploy tasks at every stages of DevOps. The authors also discuss the limitations and practical issues related to implementing DevOps within classroom settings.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.913
Threshold uncertainty score0.422

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
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.163
GPT teacher head0.441
Teacher spread0.277 · 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