Architectural design in object-z

We present a process for introducing an object-oriented architecture into an abstract functional specification written in Object-Z. Since the design is derived from the specification, correctness concerns are addressed as pan of the design process. We base our approach on refactoring rules that apply to class structure, and use the rules to implement design patterns. As a motivating example, we introduce a user-interface design that follows the model-view-controller paradigm into an existing specification.

The nomenclature of style: Brutalism, Minimalism, art history and visual style in architecture journals

The naming of styles or movements is a basic mechanism of the architectural journals. The announcement of new tendencies, groups or philosophies, gives a journal its character as ‘news’, and if such terms are taken up in general discourse this demonstrates the prescience of the editor and enhances the repute of the journal. The announcement of phenomenon such as ‘critical regionalism’ or ‘deconstructivism’ referred architectural developments to a context in socio-politics or philosophy, and thus aimed to provide at least an initial resistance to their understanding as the formal styles which they quickly became. A different strategy, or occasion, which this paper will discuss, is where the name of an architectural moment is given in the traditional form of an art historical style. Here the nomenclature of style and a certain attitude to form is introduced as the starting point for a more open ended critical inquiry. Two examples of this strategy will be given. The first is Peter Reyner Banham and the Architecture Review’s promotion of ‘Brutalism’ as an anti-aesthetic which took its conceptual form from early twentieth century art movements, particularly Futurism. The second, identified with Architectural Design in the 1990’s is ‘Minimalism’, a term describing a strand of the visual arts of the 1960’s which can be understood as an attempt to nuance and add seriousness to the present rampant nostalgia for the style of the architecture of the 1960’s.

Oase: Tijdschrift voor Architectuur = Oase: Architecture Journal

In recent years, both architectural historiography and architectural design practice have been characterized by significant shifts. These new perspectives and methodologies did not merely bring about internal changes, but also called into question the boundaries and relations between the two disciplines. This issue of OASE investigates the impact of these changes for both disciplines in a series of dialogues between historians, architects, designers and photographers, exploring themes such as the everyday, the landscape, heritage and visual culture.

A reference architecture for instructional educational software

Our extensive research has indicated that high-school teachers are reluctant to make use of existing instructional educational software (Pollard, 2005). Even software developed in a partnership between a teacher and a software engineer is unlikely to be adopted by teachers outside the partnership (Pollard, 2005). In this paper we address these issues directly by adopting a reusable architectural design for instructional educational software which allows easy customisation of software to meet the specific needs of individual teachers. By doing this we will facilitate more teachers regularly using instructional technology within their classrooms. Our domain-specific software architecture, Interface-Activities-Model, was designed specifically to facilitate individual customisation by redefining and restructuring what constitutes an object so that they can be readily reused or extended as required. The key to this architecture is the way in which the software is broken into small generic encapsulated components with minimal domain specific behaviour. The domain specific behaviour is decoupled from the interface and encapsulated in objects which relate to the instructional material through tasks and activities. The domain model is also broken into two distinct models - Application State Model and Domainspecific Data Model. This decoupling and distribution of control gives the software designer enormous flexibility in modifying components without affecting other sections of the design. This paper sets the context of this architecture, describes it in detail, and applies it to an actual application developed to teach high-school mathematical concepts.