MétaCan
Menu
Back to cohort
Record W1508017798 · doi:10.1002/0471028959.sof325

Software Productivity Center Inc.

2002· other· en· W1508017798 on OpenAlexaboutno aff
Wolfgang Strigel

Bibliographic record

VenueEncyclopedia of Software Engineering · 2002
Typeother
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsnot available
Fundersnot available
KeywordsStandardizationProductivityBusinessBest practiceSituatedSoftwareProcess managementProcess (computing)Engineering managementOperations managementMarketingEngineeringKnowledge managementComputer scienceManagement

Abstract

fetched live from OpenAlex

Abstract Software Productivity Center Inc. (SPC) was formed in 1992 as a nonprofit organization promoting the use of best practices and processes to increase the efficiency, reliability, and predictability of the software development process. The SPC is located in Vancouver, BC, Canada. Its clients are situated around the world with the majority in the United States. The goal outlined in the original business plan was for the center to become self‐sustaining in five years. It reached this and privatized in 1997. SPC has a few attributes that set it apart from other leading centers for software process. SPC has a business perspective. SPC advocates best practices that will have the greatest initial impact on the success of the business, while helping to put a structure in place to ensure ongoing learning and advancement of the organization and its staff. SPC has over 100 member companies that enjoy benefits such as discounts on training and products, free monthly seminars, and advice and information from SPC experts. Interaction with these member companies ensures SPC stays current with the challenges and issues facing software organizations each day. Member companies also benefit from SPC's affiliation and participation in international organizations such as the International Organization for Standardization (ISO standards), The Institute of Electrical and Electronics Engineers, Inc. (IEEE), and the Project Management Institute (PMI).

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.001
metaresearch head score (Gemma)0.004
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: Other
Teacher disagreement score0.435
Threshold uncertainty score0.806

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.004
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0040.004
Science and technology studies0.0020.000
Scholarly communication0.0060.004
Open science0.0010.002
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.4350.379

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.008
GPT teacher head0.212
Teacher spread0.204 · 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.

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

Citations3
Published2002
Admission routes1
Has abstractyes

Explore more

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