Architectural mismatch tolerance

The integrity of complex software systems built from existing components is becoming more dependent on the integrity of the mechanisms used to interconnect these components and, in particular, on the ability of these mechanisms to cope with architectural mismatches that might exist between components. There is a need to detect and handle (i.e. to tolerate) architectural mismatches during runtime because in the majority of practical situations it is impossible to localize and correct all such mismatches during development time. When developing complex software systems, the problem is not only to identify the appropriate components, but also to make sure that these components are interconnected in a way that allows mismatches to be tolerated. The resulting architectural solution should be a system based on the existing components, which are independent in their nature, but are able to interact in well-understood ways. To find such a solution we apply general principles of fault tolerance to dealing with arch itectural mismatche

Resolving Architectural Mismatches of COTS Through Architectural Reconciliation

The integration of COTS components into a system under development entails architectural mismatches. These have been tackled, so far, at the component level, through component adaptation techniques, but they also must be tackled at an architectural level of abstraction. In this paper we propose an approach for resolving architectural mismatches, with the aid of architectural reconciliation. The approach consists of designing and subsequently reconciling two architectural models, one that is forward-engineered from the requirements and another that is reverse-engineered from the COTS-based implementation. The final reconciled model is optimally adapted both to the requirements and to the actual COTS-based implementation. The contribution of this paper lies in the application of architectural reconciliation in the context of COTS-based software development. Architectural modeling is based upon the UML 2.0 standard, while the reconciliation is performed by transforming the two models, with the help of architectural design decisions.

Landscape History and Theory: from Subject Matter to Analytic Tool

This essay explores how landscape history can engage methodologically with the adjacent disciplines of art history and visual/cultural studies. Central to the methodological problem is the mapping of the beholder � spatially, temporally and phenomenologically. In this mapping process, landscape history is transformed from subject matter to analytical tool. As a result, landscape history no longer simply imports and applies ideas from other disciplines but develops its own methodologies to engage and influence them. Landscape history, like art history, thereby takes on a creative cultural presence. Through that process, landscape architecture and garden design regain the cultural power now carried by the arts and museum studies, and has an effect on the innovative capabilities of contemporary landscape design

Enforcing Architectural Styles in Presence of Unexpected Distributed Reconfigurations

Architectural Design Rewriting (ADR, for short) is a rule-based formal framework for modelling the evolution of architectures of distributed systems. Rules allow ADR graphs to be refined. After equipping ADR with a simple logic, we equip rules with pre- and post-conditions; the former constraints the applicability of the rules while the later specifies properties of the resulting graphs. We give an algorithm to compute the weakest pre-condition out of a rule and its post-condition. On top of this algorithm, we design a simple methodology that allows us to select which rules can be applied at the architectural level to reconfigure a system so to regain its architectural style when it becomes compromised by unexpected run-time reconfigurations.Comment: In Proceedings ICE 2012, arXiv:1212.345

Some issues in the 'archaeology' of software evolution

During a software project's lifetime, the software goes through many changes, as components are added, removed and modified to fix bugs and add new features. This paper is intended as a lightweight introduction to some of the issues arising from an `archaeological' investigation of software evolution. We use our own work to look at some of the challenges faced, techniques used, findings obtained, and lessons learnt when measuring and visualising the historical changes that happen during the evolution of software

Some issues in the 'archaeology' of software evolution

During a software project's lifetime, the software goes through many changes, as components are added, removed and modified to fix bugs and add new features. This paper is intended as a lightweight introduction to some of the issues arising from an `archaeological' investigation of software evolution. We use our own work to look at some of the challenges faced, techniques used, findings obtained, and lessons learnt when measuring and visualising the historical changes that happen during the evolution of software

Celebrating the generation of architectural ideas : tracing the lineage of Southeast Asian temples

From its early beginnings in the fifth century, the Brahmanic/Hindu tradition created a rich body of temples which spread across India and influenced temple building in Southeast Asia. The legacy of this ancient diasporic movement remains celebrated today in the admiration of Southeast Asian monuments such as Angkor Wat and Prambanan. However this architecture evolved over time through a process of long experimentation with philosophies, world-views, and methods. The architectural forms of such monuments have obvious Indian antecedents but the process of their development into distinctive indigenous forms remains difficult to ascertain. This is due both to the lack of textual accounts from the earliest Southeast Asian civilisations and because their architectural remains are fragmented or heavily eroded. This paper draws on a research project that pieces together fragments of evidence from diagrams and canonical descriptions to photogrammetry of temples in India and Southeast Asia. The intention of this is to establish the degree to which Southeast Asian temples are attributable to Brahmanic/Hindu lineage and influence. It will focus on the role of the early Southeast Asian temple site of Sambor Prei Kuk (lsanapura) in Cambodia. Comparing the relationships between cosmology, geometry and physical form in this earlier sites with both Indian and developed Southeast Asian models, it is intended that its generative role within Southeast Asian architectural historiography can be clarified and more fully celebrated