The Infona portal uses cookies, i.e. strings of text saved by a browser on the user's device. The portal can access those files and use them to remember the user's data, such as their chosen settings (screen view, interface language, etc.), or their login data. By using the Infona portal the user accepts automatic saving and using this information for portal operation purposes. More information on the subject can be found in the Privacy Policy and Terms of Service. By closing this window the user confirms that they have read the information on cookie usage, and they accept the privacy policy and the way cookies are used by the portal. You can change the cookie settings in your browser.
While the functions of Business Process Management (BPM) tools are already studied and standardized, new challenges regarding the architecture of such type of tools are emerging including the need for more scalability to support increasing demands, and more resilience of the overall solution to detect and avoid third-party code problems, that can causes failure of all the system. In this paper we...
Dynamic software architectures are those that describe how components and connectors can be created, interconnected, and/or removed during system execution. Most existing architecture description languages (ADLs) provide a limited support to expressively describe these architectures and entail architectural mismatches and inconsistencies between architecture and implementation due to their decoupling...
Systems-of-Systems (SoS) result from associating independent, complex systems for fulfilling given missions. In particular, SoS require software architectures that can cope with their dynamic, critical nature. Selecting adequate Architecture Description Languages (ADLs) for representing such architectures contributes for a better communication, analysis, and evolution of these systems. Nonetheless,...
The emergence of socio-technical systems characterized by significant user collaboration poses a new challenge for system adaptation. People are no longer just the “users” of a system but an integral part. Traditional self-adaptation mechanisms, however, consider only the software system and remain unaware of the ramifications arising from collaboration interdependencies. By neglecting collective...
In practice, inconsistencies between architectural documentation and the code might arise due to improper implementation of the architecture or the separate, uncontrolled evolution of the code. Several approaches have been proposed to detect inconsistencies between the architecture and the code but these tend to be limited for capturing inconsistencies that might occur at runtime. We present a runtime...
C&C view of Software architecture is one of the modelling languages to describe and analyze runtime architecture of a software system. However, it is not sufficient to describe runtime architectural behaviours with only C&C view because C&C view architecture does not provide a sequence and state-chart of a software system. On the other side, we would use Finite State Process (FSP) model...
An increasingly important requirement for software system is the capability to evolve dynamically at runtime according to the users' requirements and computing environments. From the angle of software architecture, in this paper, a framework of supporting dynamic evolution based on reflective aspect-oriented software architecture-RAOSA is proposed and software architecture is reified as an explicit...
Resource adapter is connector software that can be deployed in application servers so that an enterprise application can connect to a backend enterprise information system (EIS) in a seamless manner. Typically resource adapters conform to JCA (J2EE Connector Architecture) specification, and plug into application servers to provide connectivity between the EIS and the enterprise applications. A resource...
There is a growing trend to develop open world software with the forthcoming of the pervasive computing era.Traditional research on software architecture, components,and connectors is not geared towards the characteristics of open world software, and are not easily used in open world environments. In this paper, we present an extensible knowledge base called SACoCo (Semantic Architectural styles,...
Large, complex and long-lived software need to be upgraded at runtime. Addition, removal and replacement of a software component are the elementary evolution operations that have to be supported. Yet, dynamic changes are errorprone as it is difficult to guarantee that the new system will still work and that all functionalities and quality are preserved. Few existing work on ADLs fully support component...
Certain design fragments in software architectures can have a negative impact on system maintainability. In this paper, we introduce the concept of architectural "bad smells," which are frequently recurring software designs that can have non-obvious and significant detrimental effects on system lifecycle properties. We define architectural smells and differentiate them from related concepts,...
Complex and long-lived software need to be upgraded at runtime. Replacing a software component with a newer version is the basic evolution operation that has to be supported. It is error-prone as it is difficult to guarantee the preservation of functionalities and quality. Few existing work on ADLs fully support a component replacement process from its description to its test and validation. The main...
A key aspect of the design of any software system is its architecture. From the perspective of dependability, an effective architecture aims to build fault-free systems, i.e. ensuring fault avoidance. At the architecture level, fault avoidance is achieved by formally describing the structure and behaviour of software systems enabling to check their correctness. Therefore, a software architecture description...
Set the date range to filter the displayed results. You can set a starting date, ending date or both. You can enter the dates manually or choose them from the calendar.