A survey on quality attributes in service-based systems

Ameller, David; Galster, Matthias; Avgeriou, Paris; Franch, Xavier

doi:10.1007/s11219-015-9268-4

Cited by 41 publications

(28 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We have only found one study reporting the majority of the respondents to consider NFRs and functionalities at the same level of importance [50]. Interestingly, they found a statistically significant relationship between the importance given to NFRs and their implicit or explicit nature in the project.…”

Section: What Benefits Can the Management Of Nfrs Bring To Companies mentioning

confidence: 83%

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Ameller

Franch

Gómez

et al. 2021

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Managing Non-Functional Requirements (NFRs) in software projects is challenging, and projects that adopt Model-Driven Development (MDD) are no exception. Although several methods and techniques have been proposed to face this challenge, there is still little evidence on how NFRs are handled in MDD by practitioners. Knowing more about the state of the practice may help researchers to steer their research and practitioners to improve their daily work. Objective: In this paper, we present our findings from an interview-based survey conducted with practitioners working in 18 different companies from 6 European countries. From a practitioner's point of view, the paper shows what barriers and benefits the management of NFRs as part of the MDD process can bring to companies, how NFRs are supported by MDD approaches, and which strategies are followed when (some) types of NFRs are not supported by MDD approaches. Results: Our study shows that practitioners perceive MDD adoption as a complex process with little to no tool support for NFRs, reporting productivity and maintainability as the types of NFRs expected to be supported when MDD is adopted. But in general, companies adapt MDD to deal with NFRs. When NFRs are not supported, the generated code is sometimes changed manually, thus compromising the maintainability of the software developed. However, the interviewed practitioners claim that the benefits of using MDD outweight the extra effort required by these manual adaptations. Conclusion: Overall, the results indicate that it is important for practitioners to handle NFRs in MDD, but further research is necessary in order to lower the barrier for supporting a broad spectrum of NFRs with MDD. Still, much conceptual and tool implementation work seems to be necessary to lower the barrier of integrating the broad spectrum of NFRs in practice.

show abstract

Section: What Benefits Can the Management Of Nfrs Bring To Companies mentioning

confidence: 83%

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Ameller

Franch

Gómez

et al. 2021

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…However, this is due to the fact that our survey targeted a very specific population and required participants with experience with AUTOSAR. The participation of this study (51 participants) compared to other empirical studies in software architecture is similar [1]. In [1], the authors analyze the sampling of four studies with the following participation: 56 participants, 11 software companies, 53 industrial software architects, and 22 students.…”

Section: External Validitymentioning

confidence: 99%

A Survey on the Benefits and Drawbacks of AUTOSAR

Martínez‐Fernández

Ayala

Franch

et al. 2015

Proceedings of the First International Workshop on Automotive Software Architecture

Self Cite

View full text Add to dashboard Cite

The use of software reference architectures plays a fundamental role in software development, as it could bring several benefits such as providing means to design applications' software architectures with higher productivity and quality. However, many organizations still find scarce the existing empirical evidence about the benefits and drawbacks of software reference architectures. Organizations need such evidence to make informed decisions whether or not to adopt a software reference architecture for the development and maintenance of software applications. In this context, this paper aims to gather evidence on AUTOSAR, a mature and accepted software reference architecture for automotive applications used worldwide by more than 180 organizations. We designed and executed a web-based survey addressed to practitioners with experience in using AUTOSAR. We obtained 51 valid responses. The survey results indicate that the most popular benefits of AUTOSAR are standardization (88%), reuse (80%) and interoperability (51%) whereas its most important drawbacks are complexity (65%), initial investment (59%) and learning curve (51%). The respondents of the survey also gave directions to handle the major drawbacks of AUTOSAR, such as the need of a tool environment to improve its usability and handle its complexity, and the need of more stable releases of AUTOSAR to decrease the cost of migrating among versions.

show abstract

“…There are three phases included in the stage, i.e., service performance measurement, service analysis, and optimization, and service improvement. Services dependability can be used to measure and evaluate the system's performance from the internal systems perspective [34], while services quality can be used to measure the performance from the external perspective [32], [35].…”

Section: Introductionmentioning

confidence: 99%

Evaluating Services Computing Systems Engineering Framework using An Acceptance Model

Kurniawan¹,

Suhardi²,

Bandung³

et al. 2019

Int. J. Adv. Sci. Eng. Inf. Technol.

View full text Add to dashboard Cite

The gap between business services and IT services becomes a major concern in services computing. As an approach for service-based IT solution, services computing systems are promised to be able to bridge the gap between these services. The implementation will require an engineering framework as a guide to building the systems. The framework needs to be evaluated to provide important feedback to the framework development. This paper outlines the evaluation of SCSE framework through an acceptance model. The study develops an acceptance model based on the experiences of a group of engineers after using the framework to build smart campus services systems. A survey involving 54 systems engineers with various engineering backgrounds was conducted to assess the experiences of the engineers in using the framework. The results of the acceptance model show that both perceived ease of use, represented by the level of agreement (υ1) and perceived usefulness, represented by the level of importance (υ2) deliver good results almost for the entire stages of the proposed framework. In addition, the user experiences of using the proposed framework are in the acceptable levels. The contribution of this paper is an enrichment of the engineering methodologies for the service-oriented system from the perspective of services computing.

show abstract

A survey on quality attributes in service-based systems

Cited by 41 publications

References 40 publications

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

Dealing with Non-Functional Requirements in Model-Driven Development: A Survey

A Survey on the Benefits and Drawbacks of AUTOSAR

Evaluating Services Computing Systems Engineering Framework using An Acceptance Model

Contact Info

Product

Resources

About