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

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

2002· other· en· W1503858077 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

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 ; and Courage .

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.000
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.148
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.002
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0020.000
Research integrity0.0010.001
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.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