Software Ecosystems' Architectural Health: Another View

Amorim, Simone da Silva; McGregor, John D.; Almeida, Eduardo Santana de; Chávez, Christina

doi:10.1109/jsos.2017.15

Cited by 5 publications

(3 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In previous work, we proposed the idea to study one part of this health -the portion concerning the impact of the software architecture on the health. With this in mind, we advocate that the architectural health of software ecosystems "is composed of the parts of the ecosystem health influenced by architectural issues" [3]. This definition is supported by the belief that the creation and maintenance of the software architecture "weigh" directly on the behavior of the health indicators.…”

Section: Architectural Health Of Software Ecosystemsmentioning

confidence: 99%

“…Moreover, these practices face specific parts of the problem inside established limits, allowing to measure the success of their application [11]. Even more, the use of a practice causes impact in different parts of the ecosystem, including contributions positive or negative to the state of the health indicators [3]. Degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions Performance Efficiency Performance relative to the amount of resources used under stated conditions Compatibility Degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment Usability Degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use Reliability Degree to which a system, product or component performs specified functions under specified conditions for a specified period Security Degree to which a product or system protects information and data so that persons or other products or systems have the data access appropriate to their types and levels of authorization Maintainability Degree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers Portability Degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another…”

Section: Architectural Health Of Software Ecosystemsmentioning

confidence: 99%

“…The interview scope covered important topics of Software Architecture. The set of questions encompassed 7 key areas related to architectural health, as defined in our previous work [3]. The interview was semi-structured and had 30 open-ended questions.…”

Section: Data Collectionmentioning

confidence: 99%

See 2 more Smart Citations

Tailoring the NFR Framework for Measuring Software Ecosystems Health

Amorim

Andrade²,

McGregor

et al. 2018

Anais Do WER18 - Workshop Em Engenharia De Requisitos

View full text Add to dashboard Cite

A healthy software ecosystem is capable of maintaining productivity and attractiveness, even in the face of problems and disruptions. Some studies have used software metrics to measure the health of a software ecosystem; however, there is little agreement on how to measure those aspects related to software architecture nor how to weigh their influence on the health state of the ecosystem. This paper introduces an approach to measuring and assessing the state of a software ecosystem's health that is aware of the architectural practices used. The approach uses a variation of the softgoal interdependence graph belonging to NFR (Non-Functional Requirements) framework on goal modeling. The key idea is to model and estimate influences of architectural practices on the health indicators. This research carried out an exploratory case study in the KDE ecosystem. KDE architectural practices were identified and analyzed with the support of our proposed practice-aware approach. The findings present the measurable influences that can be used to support decision-making processes related to architectural practices.

show abstract

Section: Architectural Health Of Software Ecosystemsmentioning

confidence: 99%

Section: Architectural Health Of Software Ecosystemsmentioning

confidence: 99%

See 1 more Smart Citation

Tailoring the NFR Framework for Measuring Software Ecosystems Health

Amorim

Andrade²,

McGregor

et al. 2018

Anais Do WER18 - Workshop Em Engenharia De Requisitos

View full text Add to dashboard Cite

show abstract

Software Visualization Tool for Evaluating API Usage in the Context of Software Ecosystems: A Proof of Concept

Avancini

Silveira

Guerra

et al. 2020

Computational Science and Its Applications – ICCSA 2020

View full text Add to dashboard Cite

Software Ecosystem (SECO) is a consolidated research area in software engineering, emerging as a paradigm for understanding dynamics and relationships among software systems that collaborate with each other to achieve their goals. Understanding the ecosystem and how its elements interact is essential for software evolution, especially for those that provide functions and services for other systems, such as software APIs. Once an API is being used by different software, future changes need to be made in a systematic and appropriate manner, considering the whole ecosystem. However, there is a lack of formal and effective ways for APIs evaluation in the context of SECO. Thus, in this paper, we present Ecolyzer, a prototype tool that aims to support the analysis of API usage considering its ecosystem through interactive visualization. To demonstrate the feasibility of our tool, we conducted a proof of concept (PoC) using an open-source platform API. The results obtained with Ecolyzer are useful and show that the prototype meets the goals described for the accomplishment of this work.

show abstract