Valuing Historic Places: Traditional and Contemporary Approaches

Decisions about which older buildings, structures, and places should be conserved are fundamental to the practice of architectural conservation. Conservation professionals use the interrelated concepts of integrity, authenticity, and historical value to determine which historic places are worthy of importance. Traditionally, these concepts are predicated on preserving the object rather than conserving the meaning and values associated with the object. In other works, the goal is to benefit the object and not the people who value the object. This method, which has roots in antiquated nineteenth-century Western scientific traditions, deprecates the importance of people, processes, and meanings in how places are valued and conserved. Thus, conservation professionals produce “objective” meanings for other conservators, but not for everyday people. The net result is a failure to understand how local populations actually value their historic places. A recent movement in architectural conservation is to emphasize the role of contemporary social, cultural, and personal meanings in valuing historic places and the processes in which places develop these values overtime. This pluralistic perspective recognizes that different populations and cultures will have diverse ways of valuing historic places. Ultimately, for places such as Iraq, we have very little, if any, data to support conservation decisions that understand and respect local cultures and tradition. The danger is in applying traditional, Western, concepts that still dominate the conservation profession to non-Western contexts. There is a tremendous learning opportunity to engage in the cross-pollination of ideas from the perspectives of the Western and Eastern traditions and to learn how the citizens of Iraq value their cultural heritage. This information, once gathered, can then inform how to best approach the conservation of Iraqi urban centers

A Pattern Language for High-Performance Computing Resilience

High-performance computing systems (HPC) provide powerful capabilities for modeling, simulation, and data analytics for a broad class of computational problems. They enable extreme performance of the order of quadrillion floating-point arithmetic calculations per second by aggregating the power of millions of compute, memory, networking and storage components. With the rapidly growing scale and complexity of HPC systems for achieving even greater performance, ensuring their reliable operation in the face of system degradations and failures is a critical challenge. System fault events often lead the scientific applications to produce incorrect results, or may even cause their untimely termination. The sheer number of components in modern extreme-scale HPC systems and the complex interactions and dependencies among the hardware and software components, the applications, and the physical environment makes the design of practical solutions that support fault resilience a complex undertaking. To manage this complexity, we developed a methodology for designing HPC resilience solutions using design patterns. We codified the well-known techniques for handling faults, errors and failures that have been devised, applied and improved upon over the past three decades in the form of design patterns. In this paper, we present a pattern language to enable a structured approach to the development of HPC resilience solutions. The pattern language reveals the relations among the resilience patterns and provides the means to explore alternative techniques for handling a specific fault model that may have different efficiency and complexity characteristics. Using the pattern language enables the design and implementation of comprehensive resilience solutions as a set of interconnected resilience patterns that can be instantiated across layers of the system stack.Comment: Proceedings of the 22nd European Conference on Pattern Languages of Program

Analysing the Design of Privacy-Preserving Data-Sharing Architecture

Privacy has become an essential software quality to consider in a software system. Privacy practices should be adopted from the early stages of the system design to safeguard personal data from privacy violations. Privacy patterns are proposed in industry and academia as reusable design solutions to address different privacy issues. However, the diverse types and granularity of the patterns lead to difficulty for the practitioner to select and adopt them in the architecture. First, the fragmented information about the system actors in the patterns does not align with the regulatory entities and interactions between them. Second, these privacy patterns lack architectural perspectives that could help weave patterns into concrete software designs. Third, the consequences of applying the patterns have not covered the impacts on software quality attributes. This thesis aims to provide guidance to software architects and practitioners for considering and applying privacy patterns in their design, by adding new perspectives to the existing patterns. First, the research provides an analysis of the relationships between regulatory entities and their responsibility in adopting the patterns in a software design. Then, the research reports studies that were conducted using architectural-level modelling-based approaches, to analyse the architectural views of privacy patterns. The analyses aim to improve understanding of how privacy patterns are applied in software designs and how such a design affects software quality attributes, including privacy, performance, and modifiability. Finally, in an effort to harmonise and unite the extended view of privacy patterns that have a close relation to system architecture, this research proposes an enhanced pattern catalogue and a systematic privacy-by-design (PbD) pattern-selection model that aims to aid and guide software architects in pattern selection during software design. The enhanced pattern catalogue offers consolidated information on the extended view of privacy patterns. The selection model provides a structured way for the practitioner to know when and how to use the pattern catalogue in the system-design process. Two industry case studies are used to evaluate the proposed pattern catalogue and selection model. The findings demonstrate how the proposed frameworks are applicable to different types of data-sharing software systems and their usability in supporting pattern selection decisions in the privacy design

Proactive Empirical Assessment of New Language Feature Adoption via Automated Refactoring: The Case of Java 8 Default Methods

Programming languages and platforms improve over time, sometimes resulting in new language features that offer many benefits. However, despite these benefits, developers may not always be willing to adopt them in their projects for various reasons. In this paper, we describe an empirical study where we assess the adoption of a particular new language feature. Studying how developers use (or do not use) new language features is important in programming language research and engineering because it gives designers insight into the usability of the language to create meaning programs in that language. This knowledge, in turn, can drive future innovations in the area. Here, we explore Java 8 default methods, which allow interfaces to contain (instance) method implementations. Default methods can ease interface evolution, make certain ubiquitous design patterns redundant, and improve both modularity and maintainability. A focus of this work is to discover, through a scientific approach and a novel technique, situations where developers found these constructs useful and where they did not, and the reasons for each. Although several studies center around assessing new language features, to the best of our knowledge, this kind of construct has not been previously considered. Despite their benefits, we found that developers did not adopt default methods in all situations. Our study consisted of submitting pull requests introducing the language feature to 19 real-world, open source Java projects without altering original program semantics. This novel assessment technique is proactive in that the adoption was driven by an automatic refactoring approach rather than waiting for developers to discover and integrate the feature themselves. In this way, we set forth best practices and patterns of using the language feature effectively earlier rather than later and are able to possibly guide (near) future language evolution. We foresee this technique to be useful in assessing other new language features, design patterns, and other programming idioms

Software architectures and Open Source Software: Where can research leverage the most?

Software architectures have been playing a central role in software engineering research for some years now. They are considered of pivotal importance in the success of complex software systems development. However, with the emergence of Open Source Software (OSS) development, a new opportunity for studying architectural issues arises. In this paper, we introduce accepted notions of software architectures (Section 2), discuss some of the known issues in OSS (Section 3), resulting in a set of aspects we consider to be relevant for future research (Section 4)

Historic Preservation and its Cultured Despisers: Reflections on the Contemporary Role of Preservation Law in Urban Development

The past years have seen widely noticed critiques of historic preservation by “one of our leading urban economists,” Edward Glaeser, and by star architect Rem Koolhaas. Glaeser, an academic economist specializing in urban development, admits that preservation has value. But he argues in his invigorating book, Triumph of the City, and in a contemporaneous article, Preservation Follies, that historic preservation restricts too much development, raises prices, and undermines the vitality of the cities. Koolhaas is a Pritzker Prize-winning architect and oracular theorist of the relation between architecture and culture. In his New York exhibit, Cronocaos, he argued that preservation lacks an organizing theory, imposes inauthentic consumer-friendly glosses on older structures, and inhibits architectural creativity. Although these critiques are as different as the cultural spaces inhabited by their authors (although both are professors at Harvard), both seemed to strike nerves, suggesting an underlying unease about how large a role preservation has come to play in urban development. This article assesses these critiques as part of an ongoing effort to make sense of historic preservation law. This article proceeds as follows: First, it presents Glaeser’s critique in detail, placing it within the context of his larger argument about what makes cities attractive and dynamic. Grappling with the strengths and weaknesses of Glaeser’s critique leads to a discussion of how preservation regulation actually works and clarification of some of the benefits it confers. Second, this Article will attempt to specify Koolhaas’s critique, connecting it to similar complaints about preservation by more linear thinkers. Weighing objections to the coherence or authenticity of preservation leads to further discussion of the role that preservation plays in the larger culture. This article concludes with a call for future research