Abstract:The architecture of a software-intensive system can be defined as the set of relevant design decisions that affect the qualities of the overall system functionality; therefore, architectural decisions are eventually crucial to the success of a software project. The software engineering literature describes several techniques to choose among architectural alternatives, but it gives no clear guidance on which technique is more suitable than another, and in which circumstances. As such, there is no systematic way… Show more
“…Architectural design decisions tend to be driven by technological requirements and constraints [21], which also emphasizes the effect of technology on business-IT alignment. A process for integration architecture design is proposed in [31]. It relies on a model that captures the relationships between systems, their desired properties and qualities, and the design decisions.…”
Section: Methodologies Of Systems Integrationmentioning
Abstract. Information systems integration is an essential instrument for organizations to attain advantage in today's growing and fast changing business and technology landscapes. Integration solutions generate added value by combining the functionality and services of heterogeneous and diverse systems. Existing integration environments tend to rely heavily on technical, platformdependent skills. Consequently, the solutions that they enable are not optimally aligned with the envisioned business goals of the organization. Furthermore, the gap between the goals and the solutions complicates the task of evaluating the quality of integration solutions. To address these challenges, we propose a quality-driven, model-driven methodology for designing and developing integration solutions. The methodology spans organizational and systems design details, providing a holistic view of the integration solution and its underlying business goals. A multi-view meta-model provides the basis for the integration design. Quality factors that affect various aspects of the integration solution guide and inform the progress of the methodology. An example business case is presented to demonstrate the application of the methodology.
“…Architectural design decisions tend to be driven by technological requirements and constraints [21], which also emphasizes the effect of technology on business-IT alignment. A process for integration architecture design is proposed in [31]. It relies on a model that captures the relationships between systems, their desired properties and qualities, and the design decisions.…”
Section: Methodologies Of Systems Integrationmentioning
Abstract. Information systems integration is an essential instrument for organizations to attain advantage in today's growing and fast changing business and technology landscapes. Integration solutions generate added value by combining the functionality and services of heterogeneous and diverse systems. Existing integration environments tend to rely heavily on technical, platformdependent skills. Consequently, the solutions that they enable are not optimally aligned with the envisioned business goals of the organization. Furthermore, the gap between the goals and the solutions complicates the task of evaluating the quality of integration solutions. To address these challenges, we propose a quality-driven, model-driven methodology for designing and developing integration solutions. The methodology spans organizational and systems design details, providing a holistic view of the integration solution and its underlying business goals. A multi-view meta-model provides the basis for the integration design. Quality factors that affect various aspects of the integration solution guide and inform the progress of the methodology. An example business case is presented to demonstrate the application of the methodology.
“…y N 3 = (3,3,3,3,6,6,5,5,7,5,4,8,5,6,5,5,7,6,8), (25) y N 4 = (4,4,4,4,6,6,7,7,5,9,5,5,7,8,7,6,5,7,7).…”
Section: Obtaining Values Of the Metricsmentioning
confidence: 99%
“…As a result, we have obtained four the following vector estimates: y1 = (1,6,8,7,8,8,7,8,9,8,7,6,8,7), (15) y2 = (2,7,6,6,7,7,8,6,7,7,7,7,6,7), (16) y3 = (3,6,5,7,5,4,8,5,6,5,5,7,6,8), (17) y4 = (4,6,7,5,9,5,5,7,8,…”
Section: Preference Relationsmentioning
confidence: 99%
“…A number of techniques have been proposed to assist software architects in making architecture decisions [3,4]. There are several groups of such techniques, where some of them focused on architecture trade-off analysis, quality evaluation model analysis, performance optimization and some others well-known techniques [5,6,7,8,9,10,11,12,13,14,15].…”
Architectural decisions have a significant impact on the development process as well as on the quality of applied systems. On the other hand, it would be desirable to rely on mature solutions and proven experience when making such decisions. Partially this problem could be solved with the use of architectural patterns. Such solution for the same task can be implemented using different sets of patterns. As a result, there is a problem of choosing and evaluating the software architecture that is build using a number of patterns and that meets the system requirements. In this paper, the technique that allows selecting the optimal software architecture for applied software is proposed. This selection technique is reduced to the criteria importance theory problem. For applying it, we need to pick up a set of metrics that assess the characteristics of the software architecture. Next, we need to determine metrics scale and information about their importance. The results allow us making conclusions about usefulness of the proposed technique during architecture design phase for applied software.
“…Our method takes as input decision models that correspond to those already produced by other requirements engineering and architecture methods [22,45,47,49]. The only other required inputs are probability distributions modelling the decision makers uncertainty about the model parameters.…”
Uncertainty complicates early requirements and architecture decisions and may expose a software project to significant risk. Yet software architects lack support for evaluating uncertainty, its impact on risk, and the value of reducing uncertainty before making critical decisions. We propose to apply decision analysis and multi-objective optimisation techniques to provide such support. We present a systematic method allowing software architects to describe uncertainty about the impact of alternatives on stakeholders' goals; to calculate the consequences of uncertainty through Monte-Carlo simulation; to shortlist candidate architectures based on expected costs, benefits and risks; and to assess the value of obtaining additional information before deciding. We demonstrate our method on the design of a system for coordinating emergency response teams. Our approach highlights the need for requirements engineering and software cost estimation methods to disclose uncertainty instead of hiding it.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.