Assisting software architects in architectural decision-making using Quark
David Ameller,Xavier Franch +1 more
Reads0
Chats0
TLDR
Quark is presented, a method to assist software architects in architectural decision-making, and the conceptualization of the relationship between NFRs and ADs defined in Arteon, an ontology to represent and manage architectural knowledge is conceptualized.Abstract:
Non-Functional Requirements (NFRs) and constraints are among the principal drivers of architectural decision-making NFRs are improved or damaged by architectural decisions (ADs), while constraints directly include or exclude parts of the architecture (eg, logical components or technologies) We may determine the impact of an AD, or which parts of the architecture are aected by a constraint, but at the end it is hard to know if we are respecting the NFRs and the imposed constraints with all the ADs made In the usual approach, architects use their own experience to produce software architectures that comply with the NFRs and imposed constraints, but at the end, especially for crucial decisions, the architect has to deal with complex trade-os between NFRs and juggle with possible incompatibilities raised by the imposed constraints In this paper we present Quark, a method to assist software architects in architectural decision-making, and the conceptualization of the relationship between NFRs and ADs defined in Arteon, an ontology to represent and manage architectural knowledge Finally, we provide an overview of the Quark and Arteon implementation, the ArchiTech toolread more
Citations
More filters
Journal ArticleDOI
Quality attributes use in architecture design decision methods: research and practice
TL;DR: A systematic literature review is conducted to study the importance and impact of the relationships between quality attributes and architecture design decisions and to what extent existing architecture knowledge management methods and tools deal with the decisions that affect the quality of a system.
Book ChapterDOI
Analysis of Enterprise Architecture Evolution Using Markov Decision Processes
TL;DR: This paper designs, present and analyze an approach supporting EA model evolution, and defines EA artifacts dependencies and model their corresponding evolutions during change, using a feedback control schema to fully inform the EA design decisions.
Journal ArticleDOI
Quality-aware Architectural Model Transformations in Adaptive Mashups User Interfaces
Javier Criado,Silverio Martínez-Fernández,David Ameller,Luis Iribarne,Nicolás Padilla,Andreas Jedlitschka +5 more
TL;DR: The final publication is available at IOS Press through http://dx.doi.org/10.3233/FI-2016-0000.
Book ChapterDOI
A Risk-Based Approach Supporting Enterprise Architecture Evolution
Khaled Gaaloul,Sérgio Guerreiro +1 more
TL;DR: This paper rationalizes on a set of design decisions that are mapped on a non deterministic finite automaton, which is then evaluated by Markov decision processes, and considers risk as a correctness factor to choose the best alternative.
Proceedings ArticleDOI
Improving Software Architecture Design Decision by Selecting Set of Solutions
TL;DR: This paper proposes an approach that helps the software architects to thoroughly define and trace the architectural design decision significantly and systematically and claims that the approach would achieve better results in ADDs.
References
More filters
Journal ArticleDOI
Optimization by Simulated Annealing
TL;DR: There is a deep and useful connection between statistical mechanics and multivariate or combinatorial optimization (finding the minimum of a given function depending on many parameters), and a detailed analogy with annealing in solids provides a framework for optimization of very large and complex systems.
Journal ArticleDOI
Toward principles for the design of ontologies used for knowledge sharing
TL;DR: The role of ontology in supporting knowledge sharing activities is described, and a set of criteria to guide the development of ontologies for these purposes are presented, and it is shown how these criteria are applied in case studies from the design ofOntologies for engineering mathematics and bibliographic data.
Book
Software Architecture in Practice
TL;DR: This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Book ChapterDOI
On Non-Functional Requirements in Software Engineering
TL;DR: This chapter reviews the state of the art on the treatment of non-functional requirements (hereafter, NFRs), while providing some prospects for future directions.
Book
MDA Explained: The Model Driven Architecture¿: Practice and Promise
TL;DR: Insight is given in what MDA means and what you can achieve, both today and in the future, thereby raising the level of maturity of the IT industry.