MétaCan
Menu
Back to cohort
Record W2729160685

Architecture-Based Software Evolution: A Multi-Dimensional Approach

2007· article· en· W2729160685 on OpenAlexfundno aff
Huan Wang

Bibliographic record

VenueMacSphere (McMaster University) · 2007
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsnot available
FundersNatural Sciences and Engineering Research Council of CanadaMcMaster University
KeywordsComputer scienceSoftwareSoftware evolutionArchitectureSoftware engineeringSoftware systemGeographyProgramming languageSoftware construction
DOInot available

Abstract

fetched live from OpenAlex

Software Evolution is unavoidable because software systems are subject to continuous change, continuing growth and increasing complexity. As software systems become mission-critical and large in size, the complexity in software development is now focused on software evolution rather than construction. In this work, we view a software system as an entity that is evolving throughout its lifetime, during development and maintenance. Based on a broad survey of software evolution approaches, we propose an architecture-based solution for software evolution, which is defined in terms of evolution specific operations on architectural elements, that is, adding, removing, replacing components and (or) connectors, transforming configurations according to the required changes. In our view of software architectures, connectors are more likely to change since they are the architectural elements which reflect business rules. This work is focused on the evolution of connectors in architectures describing detailed design. Coordination contracts are introduced by Fiadeiro et al. as a realization of connectors at this detailed architecture level, which enables a three-layer architecture to separate concerns of components, connectors and configuration during evolution. Furthermore, to constrain the evolution in a predictable direction, we have established a matching scheme for justifying behavioral relationships between coordination contracts by specification matching based on pre- and postconditions of contracts and methods. A number of specification matches, with various degrees of similarity between the evolved and evolving contracts, have been developed for system behaviors after evolution operations. Case studies are exhibited give a better understanding of these matches.

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 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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.567
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.028
GPT teacher head0.229
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 teacher head, not a consensus.

Study designSimulation or modeling
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

Citations0
Published2007
Admission routes1
Has abstractyes

Explore more

Same venueMacSphere (McMaster University)Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207