Non-functional requirements in model-driven development of service-oriented architectures

Ameller, David; Burgués, Xavier; Costal, Dolors; Farré, Carles; Franch, Xavier

doi:10.1016/j.scico.2018.08.001

Cited by 12 publications

(5 citation statements)

References 29 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Several research approaches have been proposed to deal with NFRs in MDD. The common approach, in the state of the art, is to add NFRs to models by using UML profiles and, in fewer cases, NFRs are added directly to the UML models (e.g., as a comment) or by providing a whole metamodel designed for this objective [29]. The earliest contributions appeared at the beginning of the 2000s in the domain of performance validation (e.g., the Workshop on Software and Performance [30]).…”

Section: Non-functional Requirements In Mddmentioning

confidence: 99%

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: Non-functional Requirements In Mddmentioning

confidence: 99%

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

“…Dealing with NFRs is a major challenge in software development [1]. Analyzing conflicts in NFRs is a major task in large software systems development projects [6].…”

Section: Discussionmentioning

confidence: 99%

“…Any software organization needs to consider non-functional requirements (NFRs) in order to deliver a system that complies with its stakeholder expectations [1]. Practical impact of NFRs has not only been acknowledged by the research community but also has been documented in many studies conducted in industry [1]- [3]. Neglecting NFRs during software development is a top-ten risk, and errors in considering them are the most expensive and difficult to correct [4], [5].…”

Section: Introductionmentioning

confidence: 99%

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

Zhang

Wang

2019

IEEE Access

View full text Add to dashboard Cite

The need for particular software non-functional requirements (NFRs) leads a project team to use specific design strategies to fulfill these NFRs. However, some of the strategies may cause deficiencies in other software NFRs. These strategies are called conflicting strategies. Making the tradeoff decision of these conflicting strategies for NFRs is crucial. Therefore, a conflicting NFRs tradeoff framework (CNTF) and the corresponding method are proposed. Firstly, the NFRs are obtained from stakeholders. Fuzzy set theory is used to express stakeholder assessments on the importance of each NFR. The assessment results are ranked using a fuzzy ranking method. Then, adapting from production theory in microeconomics, the degree of satisfaction by which NFRs are affected by conflicting strategies are plotted as tradeoff curves. Borrowing the concept from the linear programming in management science, a tradeoff method is presented to help software project teams make the best tradeoff decision for conflicting NFRs. Finally, feasibility and limitations of the CNTF are elaborated in a case study. INDEX TERMS Non-functional requirement, conflict, production theory, linear programming, tradeoff.

show abstract

“…SOA is a software architecture and design styles that entails the use of services as its main building component [23]. A service (as a software component), is a technique that allows access to several capabilities.…”

Section: Service Oriented Architecture (Soa)mentioning

confidence: 99%

A Critical Analysis of Topics in Software Architecture and Design

Bishung¹,

Koyejo²,

Okezie³

et al. 2019

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

Software architecture and design is an important component in the software engineering field. This aspect of software engineering covers the functional and non-functional requirements of any system being proposed to be developed, while software architecture deals with non-functional requirements, software design entails the functional requirements. The objective of this paper is to critically analyze current topics in Software architecture and design. The method of analysis involved the use of inclusion and exclusion criteria of papers published in journals and conferences. These papers were accessed from digital libraries like ScienceDirect, and IEEE explore, with a quantitative approach of analysis been imbibed. From the analysis, the result showed that, of 35 papers used in analysis, 34.3% discussed stakeholders' involvement and decisions in software design. 17.1% for design quality, 20% examined software reuse while 11.4% discussed software evaluation and 8.6% of papers reviewed discussed software management, evolution and software development life cycle each which should be more focused as it is the fundamentals of software design and architecture. From the analysis derived, stakeholder's involvement and decision in software design is an integral part in software building for effective use. Thereby making researchers dwell more on the topic. The least discussed topics was due to the expectations of researchers. Expecting readers to have a fore knowledge of the fundamentals of design which includes software management, evolution and software development life cycle.

show abstract

Non-functional requirements in model-driven development of service-oriented architectures

Cited by 12 publications

References 29 publications

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

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

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

A Critical Analysis of Topics in Software Architecture and Design

Contact Info

Product

Resources

About