MétaCan
Menu
Back to cohort
Record W1971467631 · doi:10.1109/6294.918216

Package-oriented software engineering: a generic architecture

2001· article· en· W1971467631 on OpenAlexaff
Giancarlo Succi, Witold Pedrycz, E. Liu, Jason Yip

Bibliographic record

VenueIT Professional · 2001
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsSoftware engineeringComputer scienceReference architectureResource-oriented architectureSoftware developmentSoftware architectureSoftware architecture descriptionDomain engineeringArchitecture tradeoff analysis methodComponent-based software engineeringApplications architectureSoftware constructionSoftwareProgramming language

Abstract

fetched live from OpenAlex

New methodologies and better techniques are the rule in software engineering, and users of large and complex methodologies benefit greatly from specialized software support tools. However, developing such tools is both difficult and expensive, because developers must implement a lot of functionality in a short time. A promising solution is component-based software development, in particular package-oriented programming (POP). POP fails, however, to satisfy all the requirements of large, complex software engineering tasks. A more generic POP architecture would better serve the development of software engineering environments for large and complex methodologies. Such an architecture emerged from our development experiences with two software engineering research tools: Holmes, a domain analysis support tool; and Egidio, a unified-modeling-language-based business modeling tool. We found this particular architecture simple to understand, easy to implement, and a natural candidate for a generic POP architecture. Our generic architecture satisfies the additional requirements we deem important for larger, more complex software engineering activities. Our experiences show that the strength of this architecture lies in its simplicity and ability to work with multiple users and quickly integrate a wide variety of applications. It is not perfect, but we present it as a first step toward a more general package-oriented architecture to encourage further research in this area.

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.004
metaresearch head score (Gemma)0.005
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.006
Threshold uncertainty score0.021

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.005
Meta-epidemiology (narrow)0.0010.002
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0030.003
Science and technology studies0.0020.007
Scholarly communication0.0060.009
Open science0.0030.004
Research integrity0.0040.005
Insufficient payload (model declined to judge)0.0040.004

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.030
GPT teacher head0.291
Teacher spread0.261 · 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 designTheoretical or conceptual
Domainnot available
GenreMethods

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

Citations13
Published2001
Admission routes1
Has abstractyes

Explore more

Same venueIT ProfessionalSame topicAdvanced Software Engineering MethodologiesFrench-language works237,207