Designing service-based applications in the presence of non-functional properties: A mapping study

Neto, Plácido A. Souza; Vargas-Solar, Genoveva; Costa, Umberto Souza da; Musicante, Martin A.

doi:10.1016/j.infsof.2015.09.004

Cited by 7 publications

(2 citation statements)

References 177 publications

(396 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Accordingly, different sources can be interpreted differently to be or not classified as a GL type. For instance, while Neto et al [SS54] considered Ph.D. and master theses as a peerreviewed source, the study of Rodríguez-Pérez et al [SS83] did not consider this to be so. The same conflict was found in interpreting books and book chapters as GL types (e.g., [SS56]) or not (e.g., [SS97]).…”

Section: Challenges For Dealing With Grey Literaturementioning

confidence: 99%

Grey Literature in Software Engineering: A Critical Review

Kamei

Wiese

Lima

et al. 2021

Preprint

View full text Add to dashboard Cite

Context: Grey Literature (GL) recently has grown in Software Engineering (SE) research since the increased use of online communication channels by software engineers. However, there is still a limited understanding of how SE research is taking advantage of GL.Objective: This research aimed to understand how SE researchers use GL in their secondary studies. Method: We conducted a tertiary study of studies published between 2011 and 2018 in high-quality software engineering conferences and journals. We then applied qualitative and quantitative analysis to investigate 446 potential studies. Results: From the 446 selected studies, 126 studies cited GL but only 95 of those used GL to answer a specific research question representing almost 21% of all the 446 secondary studies. Interestingly, we identified that few studies employed specific search mechanisms and used additional criteria for assessing GL. Moreover, by the time we conducted this research, 49% of the GL URLs are not working anymore. Based on our findings, we discuss some challenges in using GL and potential mitigation plans. Conclusion: In this paper, we summarized the last 10 years of software engineering research that uses GL, showing that GL has been essential for bringing practical new perspectives that are scarce in traditional literature. By drawing the current landscape of use, we also raise some awareness of related challenges (and strategies to deal with them).

show abstract

Section: Challenges For Dealing With Grey Literaturementioning

confidence: 99%

Grey Literature in Software Engineering: A Critical Review

Kamei

Wiese

Lima

et al. 2021

Preprint

View full text Add to dashboard Cite

show abstract

“…However, measuring software quality attributes is a major challenge for software engineers as they are qualitative and measurement requires quantitative metrics. It has been found that quality attributes are primarily addressed in a general form without any empirical model or specific quantifiable approach [1] that may help in integrating quality attributes in the development process.…”

Section: Introductionmentioning

confidence: 99%

Software Coupling and Cohesion Model for Measuring the Quality of Software Components

Alzamil

2023

CMC

View full text Add to dashboard Cite

Measuring software quality requires software engineers to understand the system's quality attributes and their measurements. The quality attribute is a qualitative property; however, the quantitative feature is needed for software measurement, which is not considered during the development of most software systems. Many research studies have investigated different approaches for measuring software quality, but with no practical approaches to quantify and measure quality attributes. This paper proposes a software quality measurement model, based on a software interconnection model, to measure the quality of software components and the overall quality of the software system. Unlike most of the existing approaches, the proposed approach can be applied at the early stages of software development, to different architectural design models, and at different levels of system decomposition. This article introduces a software measurement model that uses a heuristic normalization of the software's internal quality attributes, i.e., coupling and cohesion, for software quality measurement. In this model, the quality of a software component is measured based on its internal strength and the coupling it exhibits with other component(s). The proposed model has been experimented with nine software engineering teams that have agreed to participate in the experiment during the development of their different software systems. The experiments have shown that coupling reduces the internal strength of the coupled components by the amount of coupling they exhibit, which degrades their quality and the overall quality of the software system. The introduced model can help in understanding the quality of software design. In addition, it identifies the locations in software design that exhibit unnecessary couplings that degrade the quality of the software systems, which can be eliminated.

show abstract

QoS-Based Elasticity for Service Chains in Distributed Edge Cloud Environments

Cardellini

Grbac

Nardelli

et al. 2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

With the emerging IoT and Cloud-based networked systems that rely heavily on virtualization technologies, elasticity becomes a dominant system engineering attribute for providing QoS-aware services to their users. Although the concept of elasticity can introduce significant QoS and cost benefits, its implementation in real systems is full of challenges. Indeed, nowadays systems are mainly distributed, built upon several layers of abstraction, and with centralized control mechanisms. In such a complex environment, controlling elasticity in a centralized manner might strongly penalize scalability. To overcome this issue, we can conveniently split the system in autonomous subsystems that implement elasticity mechanisms and run control policies in a decentralized manner. To efficiently and effectively cooperate with each other, the subsystems need to communicate among themselves to determine elasticity decisions that collectively improve the overall system performance. This new architecture calls for the development of new mechanisms and efficient policies. In this chapter, we focus on elasticity in IoT and Cloud-based systems, which can be geo-distributed also at the edge of the networks, and discuss its engineering perspectives along with various coordination mechanisms. We focus on the design choices that may affect the elasticity properties and provide an overview of some decentralized design patterns related to the coordination of elasticity decisions.

show abstract

Designing service-based applications in the presence of non-functional properties: A mapping study

Cited by 7 publications

References 177 publications

Grey Literature in Software Engineering: A Critical Review

Grey Literature in Software Engineering: A Critical Review

Software Coupling and Cohesion Model for Measuring the Quality of Software Components

QoS-Based Elasticity for Service Chains in Distributed Edge Cloud Environments

Contact Info

Product

Resources

About