MétaCan
Menu
Back to cohort
Record W4234542976 · doi:10.1504/ijbis.2019.10024674

Developers' views on the adoption and benefits of software process improvement programs in Canadian software development firms

2019· article· en· W4234542976 on OpenAlexaffabout
Gerald Grant, Delroy A. Chevers

Bibliographic record

VenueInternational Journal of Business Information Systems · 2019
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsCarleton University
Fundersnot available
KeywordsSoftware developmentSoftware development processComputer sciencePersonal software processSoftwareProcess (computing)Software qualityPackage development processQuality (philosophy)Team software processProcess managementSoftware engineeringSoftware peer reviewSoftware quality controlSoftware constructionEngineering managementBusinessEngineering

Abstract

fetched live from OpenAlex

For decades software developers have struggled in their attempts to deliver high quality software products. Against this background, software process improvement (SPI) programs are viewed as one of the solutions to overcome the problem of delivering low quality software products. This study utilised a two-phase approach to ascertain the state of SPI adoption and the determinants of information systems (IS) quality and success in Canadian software development firms. The study found a moderate adoption rate of SPI programs and it was felt that user training and technical support could positively impact the success of information systems projects. Based on these arguments a proposed research model was presented with the hope of it being validated in future studies.

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.009
metaresearch head score (Gemma)0.038
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.087
Threshold uncertainty score0.629

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0090.038
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0040.006
Science and technology studies0.0090.004
Scholarly communication0.0060.001
Open science0.0010.002
Research integrity0.0010.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.029
GPT teacher head0.247
Teacher spread0.218 · 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 designQualitative
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

Citations0
Published2019
Admission routes2
Has abstractyes

Explore more

Same venueInternational Journal of Business Information SystemsSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207