With today's ever increasing demands on software, software developers must produce
software that can be changed without the risk of degrading the software architecture. One …

A software architecture manifests the major early design decisions. These early decisions
determine the system's development, deployment and evolution. Thus, making better …

Our approach to creating self-healing systems is based on software architecture, where
repairs are done at the level of a software system's components and connectors. In our …

Autonomous or semi-autonomous systems are deployed in environments where contact with
programmers or technicians is infrequent or undesirable. To operate reliably, such systems …

Architectural knowledge has played a role in discussions on design, reuse, and evolution for
over a decade. Over the past few years, the term has significantly increased in popularity …

Empirical evaluation of software systems in actual usage situations is critical in software
engineering. Prototyping, beta testing, and usability testing are widely used to refine system …

To operate reliably in environments where interaction with an operator is infrequent or
undesirable, an autonomous system should be capable of both determining how to achieve …

Autonomous systems operate in an unpredictable world, where communication with those
people responsible for its software architecture may be infrequent or undesirable. If such a …

Self-adaptive software continually evaluates and modifies its own behavior to meet
changing demands. One of the key issues in constructing such software is that of planning …

As management of architectural knowledge becomes vital for improving an organization's
architectural capabilities, support for (semi-) automating this management is required. There …