A Decision Support System for Software Architecture-Style Selection

Moaven, Shahrouz; Habibi, Jafar; Ahmadi, Hamed; Kamandi, Ali

doi:10.1109/sera.2008.26

Cited by 23 publications

(11 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The results can be seen. since have complex requirements and non-deterministic changing environments; face with challenges in its con figuration and also cover requirements in maintenance and run time [25], [26]. We reviewed variety of performed works and existing challenges in this field; however they demonstrated that a complete solution has not been provided yet.…”

Section: Case Studymentioning

confidence: 99%

Towards a Dynamic Model for Requirements Handling in Software Architecture Configuration Management

Alidoosti¹,

Moaven²,

Habibi³

et al. 2016

LNSE

Self Cite

View full text Add to dashboard Cite

Abstract-Nowadays the role of software architecture is obvious. Both complex requirements and non-deterministic chang ing environments lead software architecture to face with problems for coverage of requirements and environments. Consequently, the configuration of the software architec ture is faced with challenges even in run-time. Being able to deal with such problems requires new techniques to be used. In spite of variety of related works performed in this domain, improvements are required in some aspects such as consideration of overlap and contradictory require ments and also effects in dynamic environments. In this paper, a dynamic model is presented for handling chang ing requirements which makes use of the configuration management concepts such as versioning, composition, consistency, construction, and selection; hence the possibility of configuring software architecture in overlapped and contradictory requirements and dynamic environ ments has been provided in the proposed model. The model includes change management and versioning activities for software architecture and its artefacts. The results of performing the proposed model on a case are reported in this paper.Index Terms-Dynamic model, software architecture, requirements handling, configuration management. I. INTRODUCTIONToday the need for interoperability of software systems is of importance more than ever ‫‬ . ‫‬ Therefore satisfaction of special requirements of this domain requires solutions that include identifying and handling quality attributes such as availability, flexibility, etc. One of the most important requirements is the run-time configuration management considered as the most prominent requirement of dynamic environments. Adaptable soft-ware architecture is able to be adjusted in variable environmental conditions [1].Changes can occur at different times, such as: design time, before implementation, or at run-time [2]. Various factors lead to changes in the software architecture, e.g. changing customer needs, need to create new software faster, adding new software features and modifying soft-ware faults during maintenance phase [3]- [5]. That order to fix these changes making use of configuration management and its concepts.The architecture has been integrated with the require ments in such a way that it is impossible to judge which of them Manuscript received November 10, 2014; revised January 7, 2015 came earlier than other [4]. Although there is a relationship between architecture and software requirements, but there are different opinions on the nature of this relationship [3]. In fact, requirements are description of problem but software architecture represents the struc ture of software system that solves the problem with its main elements such as components and connectors. In fact, because of the different nature of the two, there is a gap between them.Despite much work performed in identifying and meeting requirements in the area of configuration management of software architecture, there is still no perfect proven solution...

show abstract

Section: Case Studymentioning

confidence: 99%

Towards a Dynamic Model for Requirements Handling in Software Architecture Configuration Management

Alidoosti¹,

Moaven²,

Habibi³

et al. 2016

LNSE

Self Cite

View full text Add to dashboard Cite

show abstract

“…Moaven et al [10] propose a multi-criteria decision support system for the selection of architectural styles using fuzzy Choquet integral. The last approach requires that quality attributes like flexibility and maintainability for each of the architectural styles (pipes & filters, layered, etc.)…”

Section: Related Workmentioning

confidence: 99%

Supporting architectural decision making for systems-of-systems design under uncertainty

Lytra

Zdun

2013

Proceedings of the First International Workshop on Software Engineering for Systems-of-Systems

View full text Add to dashboard Cite

For the design and integration of complex systems-of-systems, various architectural decisions for recurring design problems need to be made. This requires that the software architects consider various design issues and alternatives, make trade-offs for competing requirements, and adapt the decisions to specific technologies and systems. Documentations of reusable architectural design decisions (ADDs), e.g., pattern-based decisions, provide rather informal guidelines for making recurring ADDs. These and other factors introduce many sources of uncertainty in the architectural decision making process. Existing approaches do not consider this inherent uncertainty of architectural decision making, which has been until now largely ad hoc and informal, without explicit, automated support. Apart from that, the design rationale for repeated ADDs often remains undocumented, leading to loss of architectural knowledge. To address these problems we propose to provide semi-automated support for decision making and documentation of reusable ADDs under uncertainty using a fuzzy logic expert system. We motivate our approach using a systems-ofsystems example from the industry automation area in which our approach has been applied.

show abstract

“…In this method, the existing inaccuracies are represented as mathematical models and an appropriate tool is produced for the actual problems. For implementing fuzzy logic on the problem of evaluating software architecture styles [8], the input of supporting system is the significance of quality features and the output of the system is the amount of support each architecture for different quality features. In this method, after evaluation, a software producer needs a supporting system for prioritizing architecture styles but this supporting is not accessible to the public.…”

Section: Introductionmentioning

confidence: 99%

Evaluating software architectural styles based on quality features through hierarchical analysis and Fuzzy Integral (FAHP)

Elahi

Babamir

2015

2015 7th Conference on Information and Knowledge Technology (IKT)

View full text Add to dashboard Cite

nowadays, software development processes are usually based on methods which use styles of software architecture. Indeed, software development styles differently support different quality features. In architecture styles, tactics are used for achieving quality features. Stakeholders usually request several quality features simultaneously. In this paper, a framework has been proposed in which tactics are first used to evaluate and compare the architectures with regard to only one quality feature. Then, the Analytical Hierarchy Process of Fuzzy Integral used to enhance architecture selection accuracy which is based on all the requests of Stakeholders. Using the fuzzy hierarchical process, we considered the Stakeholders' requests for quality features in the process of selecting the desirable style based on 4 factors: (1) dependency between the features in determining their weight, (2) contrast between the features (by a negative impact), (3) interaction between the features (by a positive impact), and (4) sorting out ambiguities (clarifying ambiguous and unknown values). Since Stakeholders are highly sensitive to the quality features of their requirements, our contribution in this paper is a method to select the architecture styles based on the features.

show abstract

A Decision Support System for Software Architecture-Style Selection

Cited by 23 publications

References 6 publications

Towards a Dynamic Model for Requirements Handling in Software Architecture Configuration Management

Towards a Dynamic Model for Requirements Handling in Software Architecture Configuration Management

Supporting architectural decision making for systems-of-systems design under uncertainty

Evaluating software architectural styles based on quality features through hierarchical analysis and Fuzzy Integral (FAHP)

Contact Info

Product

Resources

About