Architectural Design Rules Research Articles

The pedagogy of latrines. A kaleidoscopic look at the history of school bathrooms in Argentina, 1880-1930

ABSTRACT School bathrooms are liminal spaces where notions about intimacy and one’s public persona are configured and where issues such as sex and gender are centrally experienced and proved. These learnings are partially scripted by architectural design and pedagogical rules but not fully captured by them. In this article, I intend to historicise these configurations through an analysis of the trajectories of school bathrooms in Argentina from 1880 to 1930. Grounding on sensorial and material histories of schooling and on architectural and cultural histories, I follow the thread of toilets through school plans, state regulations, photographs, architectural treatises and pedagogical reports. I claim that issues such as the height of doors, the quality of floor and wall materials, the preference for squat or flush-down toilets, or the presence or absence of windows and mirrors, became contested arenas and that they can be projected as fragments of a kaleidoscope, as proposed by Sigfried Giedion, and not as a unified narrative of progress. I conclude that educational research would benefit from paying attention to apparently insignificant elements whose refraction visibilises not the history of purity and civilisation but that of impure hybrids that contained different possibilities.

Your Coffee Shop Uses Cloud Computing

IT applications and physical businesses often face similar challenges. Customers have to be served quickly; throughput and availability should increase. Concepts such as redundancy and parallelism are inherent in the architectural design of both worlds. However, the complexity of IT systems can hinder them from following architectural principles and design rules to obtain highly scalable and fault-resilient applications. The authors cover the architectural design phases of a cloud application and describe common best practices relevant in each phase. They use a coffee shop as a real-world analogy to avoid IT complexity.

An Approach for Modeling Architectural Design Rules in UML and its Application to Embedded Software

Current techniques for modeling software architecture do not provide sufficient support for modeling architectural design rules. This is a problem in the context of model-driven development in which it is assumed that major design artifacts are represented as formal or semi-formal models. This article addresses this problem by presenting an approach to modeling architectural design rules in UML at the abstraction level of the meaning of the rules. The high abstraction level and the use of UML makes the rules both amenable to automation and easy to understand for both architects and developers, which is crucial to deployment in an organization. To provide a proof-of-concept, a tool was developed that validates a system model against the architectural rules in a separate UML model. To demonstrate the feasibility of the approach, the architectural design rules of an existing live industrial-strength system were modeled according to the approach.

The Architectural Design Rules of Solar Systems Based on the New Perspective

In this paper I present a new perspective of the birth and evolution of Planetary Systems. This new perspective presents an all encompassing and self consistent Paradigm of the birth and evolution of the solar systems. In doing so it redefines astronomy and rewrites astronomical principles. Kepler and Newton defined a stable and non-evolving elliptical orbits. While this perspective defines a collapsing or expanding spiral orbit of planets except for Brown Dwarfs. Brown Dwarfs are significant fraction of the central star. Hence they rapidly evolve from non-Keplerian state to the end point which is a Keplerian state where it is in stable elliptical orbits. On the basis of the Lunar Laser Ranging Data released by NASA on the Silver Jubilee Celebration of Man’s Landing on Moon on 21st July 1969–1994, theoretical formulation of Earth-Moon tidal interaction was carried out and Planetary Satellite Dynamics was established. It was found that this mathematical analysis could as well be applied to Star and Planets system and since every star could potentially contain an extra-solar system, hence we have a large ensemble of exo-planets to test our new perspective on the birth and evolution of solar systems. Till date 403 exo-planets have been discovered in 390 extra-solar systems by radial velocity method, by transiting planet method, by gravitational lensing method, by direct imaging method and by timing method. I have taken 12 single planet systems, four Brown Dwarf—Star systems and two Brown Dwarf pairs. Following architectural design rules are corroborated through this study of exo-planets. All planets are born at inner Clarke’s Orbit what we refer to as inner geo-synchronous orbit in case of Earth-Moon System. The inner Clarke’s Orbit is an orbit of unstable equilibrium. By any perturbative force such as cosmic particles or radiation pressure, the planet gets tipped long of aG1 or short of aG1. Here aG1 is inner Clarke’s Orbit. If planet is long of aG1 then it is said to be in extra-synchronous orbit. Here Gravitational Sling Shot effect is in play. In gravity assist planet fly-by maneuver in space flights, gravitational sling shot is routinely used to boost the space craft to its destination. The exo-planet can either be launched on death spiral as CLOSE HOT JUPITERS or can be launched on an expanding spiral path as the planets in our Solar System are. In death spiral, exo-planet less than 5 mJ will get pulverized and vaporized in close proximity to the host star. If the mass is between 5 and 7.5 mJ then it will be partially vaporized and partially engulfed by the host star and if it is greater than 7.5 mJ, then it will be completely ingested by the host star. In the process the planet will deposit all its material and angular momentum in the Host Star. This will leave tell-tale imprints of ingestion: in such cases host Star will have higher 7Li, host star will become a rapidly rotating progenitor and the host star will have excess IR. All these have been confirmed by observations of Transiting Planets. It was also found that if the exo-planet are significant fraction of the host star then those exo-planets rapidly migrate from aG1 to aG2 and have very short Time Constant of Evolution as Brown Dwarfs have. But if exo-planets are insignificant fraction of the host star as our terrestrial planets are then they are stay put in their original orbit of birth. By corollary this implies that Giant exo-planets reach nearly Unity Evolution Factor in a fraction of the life span of a solar system. This is particularly true for brown dwarfs orbiting main sequence stars. In this study four star systems hosting Brown Dwarfs, two Brown Dwarf pairs and 12 extrasolar systems hosting Jupiter sized planets are selected. In Brown Dwarfs evolution factor is invariably UNITY or near UNITY irrespective of their respective age and Time Constant of Evolution is very short of the order of year or tens of years. In case of 12 exo-planets system with increasing mass ratio evolution factor increases and time constant of evolution shortens from Gy to My though there are two exceptions. TW Hydrae is a special case. This Solar System is newly born system which is only 9 million years old. Hence its exo-planet has just been born and it is very near its birth place just as predicted by my hypothesis. In fact it is only slightly greater than aG1. This vindicates our basic premise that planets are always born at inner Clarke’s Orbit. This study vindicates the design rules which had been postulated at 35th COSPAR Scientific Assembly in 2004 at Paris, France, under the title “New Perspective on the Birth & Evolution of Solar Systems”.

Linking Model-Driven Development and Software Architecture: A Case Study

A basic premise of model driven development (MDD) is to capture all important design information in a set of formal or semi-formal models which are then automatically kept consistent by tools. The concept however is still relatively immature and there is little by way of empirically validated guidelines. In this paper we report on the use of MDD on a significant real-world project over several years. Our research found the MDD approach to be deficient in terms of modelling architectural design rules. Furthermore, the current body of literature does not offer a satisfactory solution as to how architectural design rules should be modelled. As a result developers have to rely on time-consuming and error-prone manual practices to keep a system consistent with its architecture. To realise the full benefits of MDD it is important to find ways of formalizing architectural design rules which then allow automatic enforcement of the architecture on the system model. Without this, architectural enforcement will remain a bottleneck in large MDD projects.