MétaCan
Menu
Back to cohort
Record W2923156901 · doi:10.1049/iet-sen.2019.0040

Implementing ISO/IEC 29110 to reinforce four very small entities of Mexico under an agile approach

2019· article· en· W2923156901 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

VenueIET Software · 2019
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsAgile software developmentScrumContext (archaeology)Engineering managementSoftware qualitySoftwareProcess managementSoftware engineeringSoftware developmentQuality (philosophy)Computer scienceSoftware development processEngineeringAgile Unified ProcessSystems engineering

Abstract

fetched live from OpenAlex

Very small entities (VSEs) of software development have had a significant demand and economic impact in recent years, because most of them are the software producers for medium and big companies in order to satisfy the growing demand of software. In this context, it is important to ensure that they produce quality software to successfully meet the market needs. This task relies on having the knowledge and the experience to implement proven practices, which are contained in quality models and standards, to be able to develop quality software, while increasing their productivity and keeping or reducing their costs. A description of the implementation of ISO/IEC 29110 in Mexico, specifically at Zacatecas State is presented. This implementation was done as a strategy to increase the competitiveness of them. The study includes both, the strategy established to deploy the knowledge and the method followed to implement the ISO/IEC 29110 in four VSEs that uses scrum methodology as agile approach. The results show that the implementation of ISO/IEC 29110 was easy and with a high acceptance due to the benefits detected in the reinforcement of the VSEs’ processes without changing the way they work and solving their problems.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.714
Threshold uncertainty score0.788

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.0010.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.029
GPT teacher head0.262
Teacher spread0.233 · 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