MétaCan
Menu
Back to cohort
Record W1503858077 · doi:10.1002/0471028959.sof112

Extreme Programming (<scp>XP</scp>)

2002· other· en· W1503858077 on OpenAlexaff
Will Tracz

Bibliographic record

VenueEncyclopedia of Software Engineering · 2002
Typeother
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsExtreme programmingSoftware engineeringExtreme programming practicesSoftware developmentComputer scienceUser storyCode refactoringSoftware development processScheduleDocumentationIterative and incremental developmentSoftwareProgramming languageOperating system

Abstract

fetched live from OpenAlex

Abstract eXtreme Programming (XP) is a lightweight software development methodology based on the widely recognized and effective paradigms of code inspections, iterative spiral development, integrated product development teams (i.e., full‐time customer involvement), frequent builds, programmer teams (i.e., pair programming), design patterns, refactoring, coding standards, risk analysis, and regression testing. XP emerged from the object‐oriented programming community. XP is “extreme” in the sense that it diverges from “traditional” software development methodologies in several ways. In particular, it discourages documentation and encourages a willingness to throw code away. The XP approach to software development is targeted at systems with vague and changing requirements, a short delivery schedule, and limited resources. XP is based on four “values” that are assumed to be embraced by those participating in the software development process:Communication;Simplicity;Feedback; andCourage.

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.002
metaresearch head score (Gemma)0.008
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: Other · Consensus signal: none
Teacher disagreement score0.120
Threshold uncertainty score0.400

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0020.008
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.004
Science and technology studies0.0010.001
Scholarly communication0.0050.003
Open science0.0020.003
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.1200.076

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.014
GPT teacher head0.215
Teacher spread0.201 · 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
GenreOther

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
Published2002
Admission routes1
Has abstractyes

Explore more

Same venueEncyclopedia of Software EngineeringSame topicSoftware Engineering Techniques and PracticesFrench-language works237,207