Component-based software built from reusable software components is being used in a wide range of applications that have high dependability requirements. In order to achieve the required levels of dependability, it is necessary to incorporate into these complex systems means for coping with software faults. However, the problem is exacerbated if we consider the current trend of integrating off-...

Component-based systems built from existing software components are being used in a wide range of applications that have high dependability requirements. In order to achieve the required levels of reliability and availability, it is necessary to incorporate into these complex systems means for coping with software faults. However, the problem is exacerbated if we consider the current trend of i...

Architectural specifications of software systems show them as a collection of interrelated components, and constitute what has been called the Software Architecture level of software design. It is at this level where the description and verification of structural properties of the system are naturally addressed. Besides, the use of explicit descriptions of the architecture of software systems e...

A number of concerns in multi-agent systems (MAS) have a broadly-scoped impact on the system architectural decomposition, which in turn hinder the design of modular MAS architectures. These concerns inherently crosscut the boundaries of several architecture elements, such as components, connectors, and their interfaces. Typical examples of crosscutting concerns in MAS architecture include learn...

As the number of components on a given chip increase in this billion transistor era, System on Chip (SoC) architectures become ever more powerful. Key to this architecture is the ability to integrate multiple heterogeneous components into a single architecture, which requires modularity and abstraction. An integral part of this architectural design is the methods by which the various components...

Software systems that integrate a set of concurrent and possibly distributed components are becoming increasingly common. One architectural style that is often used in such systems is implicit invocation[1, 2]. In this style, a component communicates and passes control by announcing events, and these events are multicast to a set of consuming components that perform actions in response to event...

Our goal is to identify the key architectural and design issues related to Sensor Networks (SNs), evaluate the proposed solutions, and to outline the most challenging research directions. The evaluation has three scopes individual components on SN nodes (processor, communication, storage, sensors, actuators, and power supply), node level and networked system level. The special emphasis is place...

To strengthen the connection between requirements and design during the early stages of architectural design, a designer would like to have notations to help visualize the incremental refinement of an architecture from initially abstract descriptions to increasingly concrete components and interactions, all the while maintaining a clear focus on the relevant requirements at each step. We propos...

With special focus on software architectural issues, we report from the first two major phases of a software development project. Our experience suggests that explicit focus on software architecture in these phases was an important key to success. More specifically: Demands for stability, flexibility and proper work organisation in an initial prototyping phase of a project are facilitated by ha...

SOA is an emerging architectural style to achieve loosely-coupling and high interoperability of soŸware components and systems by using message exchanges via standard public interfaces. In SOAs, soŸware components are exposed as services and typically coordinated by using processes which enable service invocations from corresponding activities. ese processes are described in high-level or low-l...