MétaCan
Menu
Back to cohort
Record W1605645998

Experience in using business scenarios to assess COTS components in integrated solutions

2005· article· en· W1605645998 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

VenueConference of the Centre for Advanced Studies on Collaborative Research · 2005
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of TorontoIBM (Canada)
Fundersnot available
KeywordsIBMSoftware engineeringSystems engineeringComputer scienceComponent (thermodynamics)Variety (cybernetics)Business requirementsCorporationProcess (computing)SoftwareSystem integrationCommercial off-the-shelfBusiness processEngineering managementManufacturing engineeringEngineeringDatabaseWork in processOperating systemOperations managementBusiness
DOInot available

Abstract

fetched live from OpenAlex

Constructing software by integrating commercial off-the-shelf (COTS) components is widely practised, particularly in the IT service industry. For vendors of COTS components, requirements engineering is particularly challenging. To continually improve their products, vendors must identify and analyze problems that occur when their components are used in a wide variety of integrated solutions, and they must anticipate new applications in which their components could be used. In this paper, we describe a scenario-based framework developed at the Software Group division of IBM Corporation (IBM SWG) The framework mimics the solution integration process for new business opportunities, allowing the development teams to evaluate their components, discover and re-solve integration issues, and to surface new requirements for future releases. This paper describes the framework, gives an example of its use in a business scenario, discusses the experience of using this framework at IBM SWG, and relates the lessons learned.

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.013
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.531
Threshold uncertainty score0.995

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.013
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.005
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.001
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.522
GPT teacher head0.487
Teacher spread0.035 · 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