Examination of the software architecture change characterization scheme using three empirical studies

Williams, Byron; Carver, Jeffrey C.

doi:10.1007/s10664-012-9223-y

Cited by 8 publications

(2 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The work in [16] uses a systematic literature review to characterize architecture changes from existing literatures. As part of the Software Architecture Change Characterization Scheme (SACCS), a general classification of causes of architecture changes presented in [16] and another work [17] by the same authors can be used as the basic categorization of the causes of architecture changes in the two OSS projects in this study, which is elaborated in Section III. The work in [18] analyzes group interviews in various workshops for different levels of participants, e.g., developers, testers, and architects in five companies.…”

Section: A Cause Of Architecture Changementioning

confidence: 99%

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Ding¹,

Liang²,

Tang³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Section: A Cause Of Architecture Changementioning

confidence: 99%

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Ding¹,

Liang²,

Tang³

et al. 2015

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

“…The work in [17] uses a systematic literature review to characterize architecture changes from existing literatures. As part of the Software Architecture Change Characterization Scheme (SACCS), a general classification of causes of architecture changes presented in [17] and another work [18] by the same authors can be used as the basic categorization of the causes of architecture changes in the two OSS projects in this study, which is elaborated in Section 3. The work in [19] analyzes group interviews in various workshops for different levels of participants, e.g., developers, testers, and architects in five companies.…”

Section: Cause Of Architecture Changementioning

confidence: 99%

Understanding the Causes of Architecture Changes Using OSS Mailing Lists

Ding

Liang

Tang

et al. 2015

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

The causes of architecture changes can tell about why architecture changes, and this knowledge can be captured to prevent architecture knowledge vaporization and architecture degeneration. But the causes are not always known, especially in open source software (OSS) development. This makes it very hard to understand the underlying reasons for the architecture changes and design appropriate modifications. Architecture information is communicated in development mailing lists of OSS projects. To explore the possibility of identifying and understanding the causes of architecture changes, we conducted an empirical study to analyze architecture information (i.e., architectural threads) communicated in the development mailing lists of two popular OSS projects: Hibernate and ArgoUML, verified architecture changes with source code, and identified the causes of architecture changes from the communicated architecture information. The main findings of this study are: (1) architecture information communicated in OSS mailing lists does lead to architecture changes in code; (2) the major cause for architecture changes in both Hibernate and ArgoUML is preventative changes, and the causes of architecture changes are further classified to functional requirement, external quality requirement, and internal quality requirement using the coding techniques of grounded theory; (3) more than 45% of architecture changes in both projects happened before the first stable version was released. * This paper is an enhanced version of our previous paper "Causes of Architecture Changes: An Empirical

show abstract

Metrics in automotive software development: A systematic literature review

Vogel

Knapik

Cohrs

et al. 2020

J Software Evolu Process

View full text Add to dashboard Cite

Software is an integrated part of new features within the automotive sector, car manufacturers, the Hersteller Initiative Software (HIS) consortium defined metrics to determine software quality. Yet, problems with assigning metrics to quality attributes often occur in practice. The specified boundary values lead to discussions between contractors and clients as different standards and metric sets are used. This paper studies metrics used in the automotive sector and the quality attributes they address. The HIS, ISO/IEC 25010:2011, and ISO/IEC 26262:2018 are utilized to draw a big picture illustrating (i) which metrics and boundary values are reported in literature, (ii) how the metrics match the standards, (iii) which quality attributes are addressed, and (iv) how the metrics are supported by tools. Our findings from analyzing 38 papers include a catalog of 112 metrics of which 17 define boundary values and 48 are supported by tools. Most of the metrics are concerned with source code, are generic, and not specifically designed for automotive software development. We conclude that many metrics exist, but a clear definition of the metrics' context, notably regarding the construction of flexible and efficient measurement suites, is missing.

show abstract

Examination of the software architecture change characterization scheme using three empirical studies

Cited by 8 publications

References 31 publications

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Causes of Architecture Changes: An Empirical Study through the Communication in OSS Mailing Lists

Understanding the Causes of Architecture Changes Using OSS Mailing Lists

Metrics in automotive software development: A systematic literature review

Contact Info

Product

Resources

About