Search

Software systems are ubiquitously employed in societies, while they can be manipulative and discriminatory. Such systems often appear to misalign with common societal ethics. Our understanding of ethical values, what they mean, and how they are exhibited through software systems is limited. There are hardly any considerations, standards, and procedures to elicit, interpret and design for ethical values during software architecture activities. This study aims to understand ethical aspects in architecting software. We discuss (i) awareness of practitioners about ethical issues, (ii) recognizing stakeholders who may have ethical concerns, (iii) identifying ethical values during architecture design, (iv) difficulties that practitioners face from the ethical point of view, and (v) quantifying and validating ethical values. The goal of the current work is to improve ethical considerations in software architecture design. To this end, we carried out an exploratory focus group with four practicing software architects. Their experiences provided us with preliminary insights on architecting with ethical values.

Yazilim mimarisi tasarimi, yazilim gelistirme surecindeki cok onemli ve zor bir asamadir. Paydaslarin celisen amaclarini yonetmek ve ilgili gereksinimlerden mimari soyutlamalar turetmek onemlidir. Ayrica mevcut cozum alani bilgisi uzerinde temellendirilmis semantik acidan zengin ara urunler (artifact) uretmek dikkat edilmesi gereken bir husustur. Elde edilen mimari ara urunler yazilim gelistirme surecinin geri kalanina kilavuzluk eder ve planlamayi kolaylastirir. Yakin donemde yazilim gelistirme yontemlerinin ve etkinliklerinin eslenebilecegi, yazilim muhendisligine soyut ve genel bir bakis sunan Essence cercevesi onerilmistir. Bu calismada, sentez tabanli yazilim mimarisi tasarimi etkinliklerinin Essence cercevesiyle eslestirilmesi hakkinda bilgi verilmektedir. Boylece, yazilim muhendisliginin soyut ve genel bir modeli kullanilarak yazilim mimarisi tasarim etkinliklerinin aciklanmasi amaclanmistir. Ayrica, sentez tabanli yazilim mimarisi tasarim etkinlikleri icin durum tabanli etkinlik izleme duzenegi onerilmistir. Essence cercevesi ve sentez tabanli mimari tasarimi yaklasimi hakkinda elde edilen deneyim paylasilmaktadir

Предложен подход к выбору базового шаблона программной архитектуры и сопутствующих тактик проектирования, исходя из требуемых параметров качества систем. Проанализированы основные концепты и понятия предметной области, предложена предметная онтология. Рассмотрены связи между основными понятиями, приведены основные шаблоны программных архитектур. Изучено понятие тактик проектирования, а также их связь с шаблонами архитектур. Сформулирована задача построения программной архитектуры с заданными параметрами качества. В качестве решения предложена аналитическая модель выбора на основе минимизации трудоемкости проекта. Приведен подход к выбору базового шаблона архитектуры и тактик проектирования на примере систем класса превентивного обслуживания., The paper presents the approach of selection general architecture pattern and design tactics for the software project. Proposed method is based on the satisfying required software quality attributes. The domain ontology is defined along with the main concepts and structure. Base software architectural patterns and main design tactics were analyzed and as a result the problem of building software architecture with required quality attributes has stated. As a solution, analytical model of selecting necessary tactics has presented. The general approach to select the best software architecture pattern and tactics is defined and described with the example of preventive maintenance systems.

Due to copyright restrictions, the access to the full text of this article is only available via subscription. The increasing size and complexity of software systems has led to an amplified number of potential failures and as such makes it harder to ensure software reliability. Since it is usually hard to prevent all the failures, fault tolerance techniques have become more important. An essential element of fault tolerance is the recovery from failures. Local recovery is an effective approach whereby only the erroneous parts of the system are recovered while the other parts remain available. For achieving local recovery, the architecture needs to be decomposed into separate units that can be recovered in isolation. Usually, there are many different alternative ways to decompose the system into recoverable units. It appears that each of these decomposition alternatives performs differently with respect to availability and performance metrics. We propose a systematic approach dedicated to optimizing the decomposition of software architecture for local recovery. The approach provides systematic guidelines to depict the design space of the possible decomposition alternatives, to reduce the design space with respect to domain and stakeholder constraints and to balance the feasible alternatives with respect to availability and performance. The approach is supported by an integrated set of tools and illustrated for the open-source MPlayer software. Netherlands Ministry of Economic Affairs

The importance of Software Architecture design has been acknowledged as a very important factor for a high-quality software development. Different efforts in both industry and academia have produced multiple system development methodologies (SDMs) that include SA design activities. In addition, standardization bodies have defined different recommendations regarding Software Architecture design. However, in industry Software Architecture best practices are currently poorly employed. This fact constrains the benefits that industry can potentially obtain from Software Architecture design in software development. In this paper, we analyze the degree to which the four main recognized SDMs – RUP (Rational Unified Process), MSF (Microsoft Solutions Framework), MBASE (Model-Based System Architecting and Software Engineering), and RUP-SOA (Rational Unified Process for Service-oriented Architecture) - adhere to the best practices of Software Architecture design. Our analysis points out some of the most important strengths and weakness regarding Software Architecture design and highlights some of the most relevant issues of Software Architecture design that need to be incorporated into such methodologies.

This work presents ArchReco, a tool that supports Context Aware Recommendations for Design Patterns while a designer performs a Software Architecture Design. The prototype tool presented in this work takes into consideration the contextual elements that characterize a Software Architecture model and use them for the computation of the most suitable Design Patterns that can be applied during the process of Software Architecture diagram design. The tool currently supports three Context Aware Recommendation methods for the computation of recommendations for the most suitable Design Patterns. © 2015 ACM. 07-11-September-2015 Sponsors: Conference code: 118776

The increased size and complexity of software systems has led to the notion of multiple software product lines (MPLs) in which products are composed from subproducts in separate software product lines. Thus, it is important to identify the proper architectural decomposition of the MPL with respect to the stakeholders' concerns before large organizational resources are committed to the development. Designing MPL architectures is challenging due to the higher level of abstraction and the integration of different product lines. Different architecture analysis approaches have been introduced, but none of these focuses on the evaluation of MPL architectures. We propose the architecture analysis approach for MPL Engineering (Archample), which has been particularly defined for the analysis of MPL architectures. Archample also introduces architectural viewpoints for modeling and documenting MPL and likewise supporting the analysis of the decomposition of an MPL architecture. The approach has been designed and validated within a real industrial context of Aselsan REHI˙S Group (Aselsan REHI˙S), a leading high-technology company in defense systems development in Turkey. © 2014 Elsevier Inc. All rights reserved.

Conference name: 8th European Conference, ECSA 2014 Date of Conference: August 25-29, 2014 Various software architecture viewpoint approaches have been introduced to model the architecture views for stakeholder concerns. To address quality concerns in software architecture views, an important approach is to define architectural perspectives that include a collection of activities, tactics and guidelines that require consideration across a number of the architectural views. Several architectural perspectives have been defined for selected quality concerns. In this paper we propose the Safety Perspective that is dedicated to ensure that the safety concern is properly addressed in the architecture views. The proposed safety perspective can assist the system and software architects in designing, analyzing and communicating the decisions regarding safety concerns. We illustrate the safety perspective for a real industrial case study and discuss the lessons learned. © 2014 Springer International Publishing Switzerland.

During the last decade several architecture design approaches have been introduced. These approaches however have to cope with several obstacles and software architecture design remains a difficult problem. To cope with these obstacles this chapter introduces a novel architecture design approach. The approach is based on the concept of synthesis that is a well-known and effective problem solving technique in traditional engineering disciplines. The approach is illustrated for the design of an atomic transaction architecture for a real industrial project.

Due to copyright restrictions, the access to the full text of this article is only available via subscription. Each software architecture design is the result of a broad set of design decisions and their justifications, that is, the design rationale. Capturing the design rationale is important for a variety of reasons such as enhancing communication, reuse and maintenance. Unfortunately, it appears that there is still a lack of appropriate methods and tools for effectively capturing and managing the architecture design rationale. In this paper we present a feature-based rationale management approach and the corresponding tool environment ArchiRationale for supporting software architecture adaptation. The approach takes as input an existing architecture and captures the design rationale for adapting the architecture for a given quality concern. For this we define a feature model that includes the possible set of architectural tactics to realize the quality concern. The presented approach captures the rationale for deciding on feature selections and for selecting the corresponding architecture design alternatives. ArchiRationale customizes and integrates the Eclipse plugin tools XFeature, ArchStudio and XQuery to provide tool support for capturing, storing and accessing the design rationale. We illustrate the approach for adapting a software architecture for fault tolerance. Embedded Systems Institute ; Netherlands Ministry of Economic Affairs

Date of Conference: 15-18 Aug. 2011 Global Software Development (GSD) can be considered as the coordinated activity of software development that is not localized and central but geographically distributed. Designing an appropriate software architecture of a GSD system is important to meet the requirements for the communication, coordination and control of the distributed GSD teams. A common practice in software architecture design is to apply architectural views to model the design decisions for the various stakeholder concerns. Unfortunately, existing architectural viewpoint approaches are general-purpose and not directly dedicated towards GSD projects. In this paper we propose six architectural viewpoints that have been specifically defined to model GSD systems. The architectural viewpoints are based on a meta-model that has been derived after a thorough domain analysis of the GSD literature. © 2011 IEEE.

Date of Conference: September 13-16, 2011 Conference name: 5th European Conference, ECSA 2011 A common practice in software architecture design is to apply architectural views to model the design decisions for the various stakeholder concerns. When dealing with quality concerns, however, it is more difficult to address these explicitly in the architectural views. This is because quality concerns do not easily match the architectural elements that seem to be primarily functional in nature. As a result, the communication and analysis of these quality concerns becomes more problematic in practice. We introduce a general and practical approach for supporting architects to model quality concerns by extending the architectural viewpoints of the so-called V&B approach. We illustrate the approach for defining recoverability and adaptability viewpoints for an open source software architecture. © 2011 Springer-Verlag.

This work contributes in bridging the gap between software design and implementation of component-based systems using software architectures at the modelling/design level and the coordination paradigm at the implementation level. Exploiting the improvements realized by the latest version of UML, we present a methodology for automating the transition from software architecture design of component-based systems described in UML 2.0 to coordination code. The presented methodology is further enhanced with a code generation tool that fully automates the production of the complete code implementing the coordination-communication part of software systems modelled with UML 2.0. 861 866 Cited By :2

Since the architecture of a software system constrains the quality attributes, the decisions taken during architectural design have a large impact on the resulting system. An architectural design method is presented that employs iterative evaluation and transformation of the software architecture in order to satisfy the quality requirements. Architecture evaluation is performed by using scenarios, simulation, mathematical modelling and experience-based reasoning. The architecture can be transformed by imposing an architectural style, imposing an architectural pattern, using a design pattern, converting a quality requirement to functionality and by distributing quality requirements. The method has evolved through its application in several industrial projects.

Software architecture design as an engineering field has evolved greatly during the last 15 years, which is evident by the number of methods, styles, patterns, and guidelines available for its practitioners in industry. This paper takes a closer look at the purposes behind this field to reveal the level of discrepancy in pursued purposes between industrial practitioners and published methods for software architecture design. In our research surveys of architecture design methods and of purposes at a number of industrial practitioners resulted in two sets of purposes which were eventually compared and the level of discrepancy identified. Mjukvarudesign är ett område inom mjukvaruindustrin som utvecklats omfattande under de senaste 15 åren, vilket synliggjorts av de nya metoder, designstilar, designmönster och paradigmer som gjorts tillgängliga för mjukvaruutvecklare idag. Den här uppsatsen gör en djupgranskning av syftena bakom detta arbetsområde för att upptäcka eventuella skillnader mellan de syften som framhålls av befintliga arkitekturmetoder och de syften som åtsträvas av utövare inom mjukvaruindustrin.

During the last decade several architecture design approaches have been introduced. These approaches however have to cope with several obstacles and software architecture design remains a difficult problem. To cope with these obstacles this chapter introduces a novel architecture design approach. The approach is based on the concept of synthesis that is a well-known and effective problem solving technique in traditional engineering disciplines. The approach is illustrated for the design of an atomic transaction architecture for a real industrial project.