MétaCan
Menu
Back to cohort
Record W2541607800 · doi:10.1109/step.2002.1267597

A technical review of the software construction knowledge area in the SWEBOK guide

2004· review· en· W2541607800 on OpenAlexaff
F. Robert, Alain Abran, P. Bourque

Bibliographic record

Venuenot available
Typereview
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsÉcole de Technologie Supérieure
Fundersnot available
KeywordsComputer sciencePerspective (graphical)Knowledge engineeringStrengths and weaknessesBody of knowledgeSoftware engineeringSoftwareCurriculumData scienceKnowledge managementWorld Wide WebArtificial intelligence

Abstract

fetched live from OpenAlex

In May 2001, of the Guide to the Software Engineering Body of Knowledge (SWEBOK) was released in a Web format and, in December 2001, in book format with the intent to collect comments and possible improvements. Up to now, feedback received confirmed the usefulness of the guide for all documented knowledge areas, with the exception of the software construction knowledge area, for which the content does not map easily to industry practices or to actual academic curricula. After analysis of this specific SWEBOK knowledge area, some issues were identified, such as inconsistencies between the textual descriptions and the visual representations. Furthermore, analysis of this chapter using the Vincenti classification of engineering knowledge types allowed us to identify some additional weaknesses and provided us with guidance on how the structure of this chapter could be improved. This paper proposes a revised breakdown of topics that is more aligned with an engineering perspective.

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.007
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.010
Threshold uncertainty score0.021

Distilled classifier scores by category (both heads)

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

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.045
GPT teacher head0.350
Teacher spread0.304 · 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 designNot applicable
Domainnot available
GenreReview

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

Citations9
Published2004
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207