No abstract

Good software architecture is critically important for successful software development. The software architecture can be defined as a set of architectural design decisions. However, the effort for acquiring good software architecture currently lacks of interest and experience in architectural design decisions. For this reason, during acquiring good software architecture, it is difficult to evaluate the architectural designs and make changes to the architecture that is relevant for the required changes. Therefore, this paper proposes a model of architectural design decisions for making architectural design decisions more explicit. Based on the proposed model, this paper also proposes an integrated approach for acquiring good software architecture with respect to its requirements, which is called AQUA. Namely, the AQUA defines decision centric process of finding, evaluating, and changing the decisions. During the decision-centric process, the AQUA involves works of architectural evaluation and transformation. The AQUA provides software architects with a means for achieving software quality attributes through acquiring good software.

No abstract

No abstract

Abstract. Architecture-based software development plays an important role in successfully developing and managing large and complex software systems. Recently, there have been a number of studies for designing, evaluating, or transforming architectures. However, there is not much work being done for closely connecting an architectural evaluation with an architectural transformation in order to achieve quality attributes during the architecture-based software development. For this reason, it is still difficult to achieve consistently quality attributes at the architectural level. This paper presents an approach to quality achievement in architecture-based software development, which is called AQUA. The AQUA involves two distinctive activities, which are architectural evaluation and transformation, but these activities can be seamlessly combined through producing relevant artifacts based on the design decisions that led to the architecture. Due to the proposed approach, we can expect to achieve quality attributes in architecture-based software development.