Notion Of Architecture Research Articles

Reprogramming Modernism

The advent of digital not only fosters new possibilities in creation but also in conservation. Architectural preservation evoked in the Modern period, when mimicry, a standard method of creation was paused and the intention to preserve past notations of architecture awakened. Now, what is the future of Modernism in the Digital archive?Digital Modern manifests the revival of this objective with actual tools. Digital proposes a new approach to history and the treatment of the past by keeping all records recallable to the present. Cloud computing proposes timeless history, where previous memory stored in algorithms is available at the level of representation. This essay shows how Modern architectural notations are explicitly inherited by the Computational era and introduce the correlation between typology and digital patterns. The period influenced by the industrial revolution and universal solutions prepared the platform for the current era influenced by the digital revolution.To understand the relationship between the two dominant epochs, this essay relies on the notions of mimicry, rules, models and methods as modes of repetition and creation crosslinked with different stages of technological development in history. This will lead to the understanding how virtual copies create a new chapter in mimesis and provokes a new chronological approach. The research methodology does not follow a linear timeline but builds on simultaneous perspectives of the Digital Modern phenomenon.

Architecture as performance

Might architecture be reconceived as a form of performance? I draw upon Nelson Goodman’s writing on architecture—including his account of architectural notation—and David Davies’s performance theory, which claims that artworks should be considered not as products made by generative performances, but rather as the performances themselves. I tie the exemplification that Goodman identifies as the primary way architectural works ‘mean’ to the role of the architectural ‘score’, recast not as a mere ‘constraint’ but as integral to the creative processes by which architecture establishes an ‘artistic statement’ and a distinctive ‘virtual’ realm. In so doing, I reconcile such a position with an aesthetics of reception, whereby the situated encounter with the physical building is seen as essential to the critical retrieval of any given architectural performance. I test this position against a late work by Sigurd Lewerentz, completed when he was in his eighties, and examine the extraordinary lengths necessitated by his idiosyncratic imperative not to cut any bricks, thereby articulating an artwork every bit as radical as contemporaneous works by conceptual artists.

A method for transforming knowledge discovery metamodel to ArchiMate models

Enterprise architecture has become an important driver to facilitate digital transformation in companies, since it allows to manage IT and business in a holistic and integrated manner by establishing connections among technology concerns and strategical/motivational ones. Enterprise architecture modelling is critical to accurately represent business and their IT assets in combination. This modelling is important when companies start to manage their enterprise architecture, but also when it is remodelled so that the enterprise architecture is realigned in a changing world. Enterprise architecture is commonly modelled by few experts in a manual way, which is error-prone and time-consuming and makes continuous realignment difficult. In contrast, other enterprise architecture modelling proposal automatically analyses some artefacts like source code, databases, services, etc. Previous automated modelling proposals focus on the analysis of individual artefacts with isolated transformations toward ArchiMate or other enterprise architecture notations and/or frameworks. We propose the usage of Knowledge Discovery Metamodel (KDM) to represent all the intermediate information retrieved from information systems’ artefacts, which is then transformed into ArchiMate models. Thus, the core contribution of this paper is the model transformation between KDM and ArchiMate metamodels. The main implication of this proposal is that ArchiMate models are automatically generated from a common knowledge repository. Thereby, the relationships between different-nature artefacts can be exploited to get more complete and accurate enterprise architecture representations.

The ramp around the world: the composition of a post-Wolrd War II project atlas

The article proposed here reports on reading the master's student's research object using the iconological method created by the German historian Aby Warburg - the Atlas. The research in question has as the main object the reading of works that have the ramp as an architectural notation, a concept created by the Swiss architect Bernard Tschumi. Starting from a quick elucidation on the theoretical basis of the mother research, the process of building the universe of works is explained through searches in large portals for the dissemination of architectural projects, and those that meet the requirements created by the author are selected. Following the initial clarifications, there is a clarification of the German historian's methodology when composing the method that today is known as Atlas. Even though Atlas is a great help tool, it was concluded that secondary analyzes are necessary to bring the researcher closer to objects so that categories are created and from these object-works are highlighted for a more detailed assessment. All of these analyzes are carried out to find these object-works that will be studied to understand the ramp as architectural notation in post-World War II projects.

Archive of Affinities Making Architecture from Architecture

AbstractArchive of Affinities is a digital collection and display of architectural objets trouvés, created and curated by Andrew Kovacs, assistant adjunct professor at the University of California Los Angeles. Elements, forms and architectural notations are selected from the Archive's galaxy of possibilities as the prima materia for his practice's projects. The juxtaposition of scale, taxonomies, typologies and colour gives the work of Office Kovacs its own particular flavour.

La mirada y el cuerpo en movimiento: notaciones para el análisis y diseño de la arquitectura

In the last few decades, the diagram has emerged as one of the main themes in the architectural debate, becoming a malleable term which has adopted a myriad of meanings and promoted new ways of designing architecture. This article aims to highlight one of these diagrammatic instruments, namely, notations for the analysis and design of architecture, due to its ability to work with the temporal dimension. It will analyze the notational systems elaborated by Philip Thiel in the mid-1950s and Bernard Tschumi in the late 1970s. These two different proposals for architectural notation, the first one focused on phenomenological questions and the second one on programmatic themes, sought to improve the traditional mechanisms for architectural representation. When introducing the variables of time and experience in the processes of analysis and design of architecture, the notations focus their attention on the dialogue that is established between the act of looking and the physical experience of the user in motion with the architectural space, while leaving out more formal issues. Keywords: diagram, notation, architectural experience, Philip Thiel, Bernard Tschumi.

Expertise and Heritage Ethics in the Middle East

By the time I completed fieldwork in Qatar in 2016, the Msheireb project that aimed to redevelop the heart of Doha was nearing completion of its first phase. The way this development project unfolded during this time was indicative of broader negotiations of Qatari cultural brokers with ideas of indigeneity and expertise: the project was rebranded from Dohaland, “The Heart of Doha,” to Msheireb (after the local wadi) in the first half of 2011, while the iconic Al Kahraba Street—the “spine” of the old city and the first street to be electrified in Qatar—was referred to in architectural notations as the “Champs-Élysées” of Doha. The politics of indigeneity of place-making in these negotiations reflected an unresolved unease with the cosmopolitan nature of expertise. This tension was related not necessarily to the ingenious remixing of traditional and modern concepts of cultural and environmental sustainability, but rather to the active erasure of foreign expertise. We see this, for example, in the active rebranding of the I. M. Pei's Museum (in reference to the Chinese American “starchitect” who designed it) in order to take its rightful “local” name, the Museum of Islamic Art. While these efforts would suggest an intention to localize expertise and build local capacity as part of national objectives, I argue in this essay that this mastering in fact obscures local expertise by dissociating it from the cosmopolitan context in which knowledge production is negotiated in Qatar.

Integrated Human Factors Views in the Unified Architecture Framework

AbstractHuman beings are integral to today's complex systems of systems. Human behaviour, interactions, abilities, complexity, and limitations will have a dramatic effect on the successful realization of system capabilities. Therefore the human factors considerations need to be evaluated in conjunction with the overall systems engineering. Systems engineers need to address them upfront and throughout the system life cycle resulting in effective Human Systems Integration (HSI). Systems engineers are increasingly using Model Based System Engineering (MBSE) techniques to define systems requirements, behaviour, structure, interactions, etc. Typical architecture notations are the Systems Modeling Language (SysML) for modelling systems and the Unified Modeling Language (UML) Profile for DoDAF and MODAF (UPDM). The metamodels defining these notations contain implicit, but not explicit elements for defining how the human fits into the architecture. The Unified Architecture Framework (UAF) has standardized a set of Human Views (called Personnel Views in UAF) into its system of systems framework, allowing the Human aspects to be considered in conjunctions with the rest of the architecture. The UAF Personnel views will not be standalone, but like SysML will allow users to interface with specialty to analyse human aspects in both quantitative and qualitative ways. It is only by taking this integrated approach that systems can be fit for purpose by including the human impact and contribution to overall system performance. This paper will describe these views and how they fit into the overall architecture as well as how they can interact with a spectrum of human factors and architecture tools.

Architectural notation and design process

The paper tackles the specific nature of relations between architectural notations and design process from the aspect of architectural media, viewed as the place of articulation of architectural opinion. Creative process of thinking is possible to notate via various architectural media. Each medium has its own specific internal mechanism of abstraction inciting imagination and creativity. The paper tackles specific practice of architectural design in the contemporary research through the project. This issue is of great importance having in mind the access to methodology of architectural design within education system.

Integrating behavior analysis into architectural modeling

Architectural modeling and behavior analysis are two important concerns in the software development. They are often implemented separately, and specified by their own supporting notations. Architectural modeling helps to guarantee the system design to satisfy the requirement, and behavior analysis can ensure the interaction correctness. To improve the trustworthiness, methods trying to combine architectural modeling and behavior analysis notations together have been proposed, e.g., establishing a one-way mapping relation. However, the one-way relation cannot ensure updating one notation specifications in accordance with the other one, which results in inconsistency problems. In this paper, we present an approach to integrating behavior analysis into architectural modeling, which establishes the interoperability between architectural modeling notation and behavior analysis notation by a bidirectional mapping. The architecture is specified by the modeling language, architecture analysis and design language (AADL), and then mapped to behavior analysis notation, Darwin/FSP (finite state process) through the bidirectional transformation. The bidirectional transformation provides traceability, which makes behavior analysis result provided by a model checker can be traced and reflected back to the original AADL specifications. In this way, the behavior analysis is integrated into architectural modeling. The feasibility of our approach is shown by a control system example.

Generating CAM aspect-oriented architectures using Model-Driven Development

Aspect-Oriented Software Development promotes the separation of those concerns that cut across several components and/or are tangled with the base functionality of a component, through all phases of the software lifecycle. The benefit of identifying these crosscutting concerns ( aspects) at the architectural level in particular is to improve the architecture design and its subsequent evolution, before moving onto detailed design and implementation. However, software architects are not usually experts on using specific AO architecture notations. Therefore, the aim of this paper is to provide support to define and specify aspect-oriented (AO) architectures using non-AO ones as the source. We will use the Model-Driven Development approach to transform a component-based architecture model into an AO architecture model. The CAM (component and aspect model) model and the DAOP–ADL language are the proposals used for modelling and specifying AO architectures. We will show how we automated part of the process and the tool support.

A framework for visual notation exchange

A wide range of software tools provide software engineers with different views (static and dynamic) of software systems. Much recent work has focused on software information model exchange. However, most software tools lack support for exchange of information about visualisation notations (both definitions of notations and instances of them). Some basic converters have been developed to support the exchange of notation information between software tools but almost all are custom-built to support specific notations and difficult to maintain. We describe the development of several notation exchange converters for tools supporting software architecture notations. This has lead to the development of a unified converter generator framework for notation exchange.

Reconciling the needs of architectural description with object-modeling notations

Complex software systems require expressive notations for representing their software architectures. Two competing paths have emerged. One is to use a specialized notation for architecture, an architecture description language (ADL). The other is to adapt a general-purpose modeling notation, such as UML. The latter has a number of benefits, including familiarity to developers, close mapping to implementations, and commercial tool support. However, it remains an open question as to how best to use object-oriented notations for architectural description, and, indeed, whether they are sufficiently expressive, as currently defined. In this paper, we take a systematic look at these questions, examining the space of possible mappings from ADLs into UML. Specifically, we describe (a) the principal strategies for representing architectural structure in UML; (b) the benefits and limitations of each strategy; and (c) aspects of architectural description that are intrinsically difficult to model in UML using the strategies.

The Real-Time Process Algebra (RTPA)

The real-time process algebra (RTPA) is a set of new mathematical notations for formally describing system architectures, and static and dynamic behaviors. It is recognized that the specification of software behaviors is a three-dimensional problem known as: (i) mathematical operations, (ii) event/process timing, and (iii) memory manipulations. Conventional formal methods in software engineering were designed to describe the 1-D (type (i)) or 2-D (types (i) and (iii)) static behaviors of software systems via logic, set and type theories. However, they are inadequate to address the 3-D problems in real-time systems. A new notation system that is capable to describe and specify the 3-D real-time behaviors, the i>real-time process algebra (RTPA), is developed in this paper to meet the fundamental requirements in software engineering. RTPA is designed as a coherent software engineering notation system and a formal engineering method for addressing the 3-D problems in software system specification, refinement, and implementation, particularly for real-time and embedded systems. In this paper, the RTPA meta-processes, algebraic relations, system architectural notations, and a set of fundamental primary and abstract data types are described. On the basis of the RTPA notations, a system specification method and a refinement scheme of RTPA are developed. Then, a case study on a telephone switching system is provided, which demonstrates the expressive power of RTPA on formal specification of both software system architectures and behaviors. RTPA elicits and models 32 algebraic notations, which are the common core of existing formal methods and modern programming languages. The extremely small set of formal notations has been proven sufficient for modeling and specifying real-time systems, their architecture, and static/dynamic behaviors in real-world software engineering environment.

Architectural Notation and Computer Aided Design

Architectural Notation and Computer Aided Design

Architectural Notation and Computer Aided Design

Architectural Notation and Computer Aided Design

Pictures that play: Design notations for real‐time and distributed systems

Abstract‘Pictures that play’ are design diagrams that give enough visual cues to enable a person to trace causality sequences that cut across them, without referring to (or even knowing) the kind of details that would enable a tool to execute the design or to generate executable code. Playing design diagrams is particularly important while exploring alternative solutions during the early stages of designing all kinds of systems. It is done either by mentally tracing sequences across diagrams on paper or a computer screen, or physically tracing them on whiteboards with a pointer or finger during design meetings. Two complementary pictorial design notations are described and used together in an example to illustrate the concept of play and to show how to do it: timethreads, a new notation for causality sequences that cut across many components and across the system end‐to‐end, and machine charts, an older notation for architecture presented here from a new angle. These notations are specifically designed to support play during the design process, not just record the end result. The focus is on real‐time and distributed (RTD) systems, but the approach has wider applicability.

Reconceiving Notation and Performance

Nelson Goodman likes to elucidate his theory of notation reference to musical scores and performances. That theory, first presented as chapter four of Goodman's Languages of Art, specifies five requirements for notational systems: unambiguity and syntactic and semantic disjointness and finite differentiation (LA, p. 156).1 To extent that standard notational system of Western music meets those technical requirements, it permits the authoritative identification of a work from to performance (LA, p. 128). Simply stated, all (and only) performances that with and are in turn (LA, p. 144) a given score can count as performances of a given work (Beethoven's Fifth Symphony, for example). Notational compliance vouchsafes work identity in some other arts as well. In literature, for example, a particular recitation is of My Last Duchess if and only if it complies with, and is denoted by, text of Robert Browning's poem. Dance performances, too, execute a choreographic design that has been or could have been inscribed in Labanotation or some other scheme governed by notational principles. Outside realm of performable arts, a construction crew's execution of ground plans is expected to comply specifications couched in architectural notation (cf. LA, p. 219). In their strictest form, Goodman's requirements for notational systems are not fully met in any of arts. No musical performance, for instance, will comply a score as unequivocally as handling of mail, to use Catherine Elgin's example, complies unambiguous notational