A System of Residence Space Construction Variability, Emergent Properties and Developmental Procedures in an Integrated Building System This presentation.

Slides:



Advertisements
Similar presentations
Understand and appreciate Object Oriented Programming (OOP) Objects are self-contained modules or subroutines that contain data as well as the functions.
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
An Evaluation of MC/DC Coverage for Pair-wise Test Cases By David Anderson Software Testing Research Group (STRG)
Lecture # 2 : Process Models
A cognitive theory for affective user modelling in a virtual reality educational game George Katsionis, Maria Virvou Department of Informatics University.
Substantive environmental provisions Prof. Gyula Bándi.
Geometric aspects of variability. A simple building system could be schematically conceived as a spatial allocation of cells, each cell characterized.
Basic Concepts in Component-Based Software Engineering
OASIS Reference Model for Service Oriented Architecture 1.0
Software Architecture for DSD DSD Team. Overview What is software architecture and why is it so important? The role of architecture in determining system.
Introduction and Overview “the grid” – a proposed distributed computing infrastructure for advanced science and engineering. Purpose: grid concept is motivated.
Unit 251 Implementation and Integration Implementation Unit Testing Integration Integration Approaches.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
The Architecture Design Process
Quality of Service in IN-home digital networks Alina Albu 23 October 2003.
Software Requirements
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
RIZWAN REHMAN, CCS, DU. Advantages of ORDBMSs  The main advantages of extending the relational data model come from reuse and sharing.  Reuse comes.
LÊ QU Ố C HUY ID: QLU OUTLINE  What is data mining ?  Major issues in data mining 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Integration at the urban and the architectural scale
GENERAL CONCEPTS OF OOPS INTRODUCTION With rapidly changing world and highly competitive and versatile nature of industry, the operations are becoming.
Emergent Construction and System Integration The system, as described so far, could be defined by both a set of types of elementary construction modules,
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
An Introduction to Software Architecture
CSE 303 – Software Design and Architecture
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
ITEC 3220M Using and Designing Database Systems
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Lecture 9. The organizational structure of management of enterprise.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Instructor Kostas Kontogiannis.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
SOFTWARE DESIGN.
Module 4: Systems Development Chapter 12: (IS) Project Management.
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
Strategic Human Resource Management Copyright © Texas Education Agency, All rights reserved.
This chapter is extracted from Sommerville’s slides. Text book chapter
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
CSE 303 – Software Design and Architecture LECTURE 4.
Implementing Low-Cost e-Gov Solutions in Europe, in Africa, All over the Globe: Report on Experiences Marios Chatzidimitriou, Adamantios Koumpis ALTEC.
1 Chapter 3 1.Quality Management, 2.Software Cost Estimation 3.Process Improvement.
What’s MPEG-21 ? (a short summary of available papers by OCCAMM)
Individual Decision Making Various type of Consumer Problem Solving By Levi Spencer Caleb Pierce.
Distributed Models for Decision Support Jose Cuena & Sascha Ossowski Pesented by: Gal Moshitch & Rica Gonen.
Software Engineering and Object-Oriented Design Topics: Solutions Modules Key Programming Issues Development Methods Object-Oriented Principles.
OPERATING SYSTEMS CS 3530 Summer 2014 Systems and Models Chapter 03.
Software Engineering Issues Software Engineering Concepts System Specifications Procedural Design Object-Oriented Design System Testing.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
CISB444 - Strategic Information Systems Planning Chapter 3 : Developing an IS/IT Strategy: Establishing Effective Processes Part I.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Systems Analyst (Module V) Ashima Wadhwa. The Systems Analyst - A Key Resource Many organizations consider information systems and computer applications.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
BIMILACI 2007 Partners for Quality Infrastructure: The FIDIC Vision Washington, May 10, 2007 Dr. Jorge Díaz Padilla FIDIC President.
DESIGN PROCESS AND CONCEPTS. Design process s/w design is an iterative process through which requirements are translated into a “blueprint” for constructing.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
AUDIT STAFF TRAINING WORKSHOP 13 TH – 14 TH NOVEMBER 2014, HILTON HOTEL NAIROBI AUDIT PLANNING 1.
Design Engineering 1. Analysis  Design 2 Characteristics of good design 3 The design must implement all of the explicit requirements contained in the.
CompSci 280 S Introduction to Software Development
Design Patterns: MORE Examples
Classifications of Software Requirements
Need for the subject.
Chapter 13 Quality Management
L E A R N I N G O U T L I N E Follow this Learning Outline as you read and study this chapter.
Presentation transcript:

A System of Residence Space Construction Variability, Emergent Properties and Developmental Procedures in an Integrated Building System This presentation includes material from the diploma project of L. Virirakis and G. Bourkas, supervisied by Professor S. Charalambides. The project was presented in NTUA, Department of Architecture, in October 1985 The presentation includes pictures originated from the website Each one of these pictures is presented with reference to its original URL. Click your mouse to continue, or use the keyboard arrows to move forward or backward in the slide show

Two different paradigms of built space production

Conventional design considers the user of the built space as an abstract entity derived by averaging over a usually ill defined set of individuals. As a consequence, a set of simplistic easy-to-handle specifications is extracted from rather unreal "user's needs". The designer combines these specifications with general organizational and aesthetic design principles, according to his/her own ability to process design information. As this ability is not unlimited (even for expert designers), the variability of the design—a property intuitively expressing the possibility to reach many different design structures—can be seriously constrained. However high variability is required if the design has to satisfy various small-scale user-specific needs.

Reduced variability—viewed as a response to simplistic specifications—has been considered as an aesthetic principle by the modern movement, and has been expressed by either simplistic architectural forms … Villa Savoye:

Reduced variability—viewed as a response to simplistic specifications—has been considered as an aesthetic principle by the modern movement, and has been expressed by either simplistic architectural forms … Paris 130:

… or simplistically structured repetition of identical modules Unite d’habitation

… or simplistically structured repetition of identical modules La Cite Radieuse:

In many cases low variability constitutes an expression of a linear mechanistic-deterministic approach to design, which has consequences on the level of integration of different systems of a building construction. Different systems of the construction (support, electrical, plumbing system etc), as well as the construction- environment system, are considered as independent to each other. This specifies all processes associated to either the design or the construction or the functionality of different systems as additive or even (in most cases) antagonistic. The failure of the independent systems to work together as an integrated self-consistent system significantly increases the cost of the construction. Respectively, the failure of the construction-environment system increases the dependence of the construction on expensive large scale urban infrastructures. As a consequence, the total cost of the built space can be enlarged by orders of magnitude.

A completely different situation concerns some cases of built space production, occurred under different historical conditions. In these cases the built environment results from asynchronous actions of many different agents. These agents are not design experts but, being usually users themselves, they have a very clear picture of their particular needs. Information processing during the built space construction is localized and distributed. Interactions among construction activities occur as the product of the work of each agent constitutes part of the environment where the work of other agents has to adapt. Larger scale urban properties emerge in a bottom-up mode by smaller scale spatial properties. Santorini, Greece:

The total amount of information processed in this way largely exceeds the potential of any design expert working in isolation, while the result could be a high-complexity built environment satisfying numerous small-scale user-specific needs. Both the construction process and the functionality of the built space are also supported by synergistic procedures evolved during a historical process. Santorini, Greece:

We shall refer to this approach by the term "systemic", emphasizing to net-organization, bottom-up, emergent, synergistic features of the built space production and functionality, as opposing to the centrally controlled, top-down, additive, antagonistic features characterizing the conventional approach. Santorini, Greece:

Unfortunately, present cases of built space production that exhibit "systemic" properties apply under conditions of poverty. Favelas, Brasil:

This is due to historical reasons: poor communities, unable to afford the "expensive" resources of the dominant production system (not only materials and infrastructures, but also designers are included in these resources) have to create their own residence space. Favelas, Brasil:

They have to do so by making best use of available low-quality resources, where "best use" means covering basic residence needs by minimizing the consumption of resources. This makes a "systemic" approach necessary. Favelas, Brasil:

It is an interesting question whether the present technological framework could support a "systemic" approach to the design, the construction and the use of built space. This approach could promote social values, such as satisfaction of user-specific small- scale needs, reduction of the cost and improvement of the quality of the built space, adaptability, sociality, and user participation in the formation of his/her own space.

Modular industrial building systems, which aim to the rapid construction of large scale building projects, are known to exhibit very low variability, while they provide poor integration of different systems of a building construction. In addition, they depend on specialized factories, which seriously affects their cost. Prefabricated buildings:

Modular industrial building systems, which aim to the rapid construction of large scale building projects, are known to exhibit very low variability, while they provide poor integration of different systems of a building construction. In addition, they depend on specialized factories, which seriously affects their cost. Key Worker Housing:

Modularity does not necessarily result in low variability. A relatively small number of module types combined under appropriate rules could exhibit remarkable variability producing complex built space. Habitat 67:

Variability is only one aspect of the "systemic" approach. A building system that adopts the "systemic" principles should satisfy the following specifications: Habitat 67:

- Reduce the informational cost - Support high variability of the design of the built space - Allow variability to apply in different design scales - Retain integration of different systems of the construction - Promote emergence of desired properties of the built space through interactions of the system's units - Promote "developmental" production procedures based on information reusability - Reduce the social cost of the built space - Reduce the material and energy resources consumption - Make built space modifications easy - Exploit existing industrial production possibilities - Offer high quality architectural space Specifications of a "systemic" building system design Variability could be defined as the size of the set of possible system-consistent designs, given a project’s specifications. The distinction between different system-consistent designs depends on scale-dependent criteria (e.g. designs having different small scale features may be considered as similar in a larger scale). As a consequence variability tends to decrease with the design scale. The possibility to maintain high variability in different design scales makes possible for the system to satisfy needs and specifications concerning these scales. Variability at a design scale should not be heavily reduced due to constraints posed at a larger design scale. However such constraints are needed if they represent design knowledge that affects the system’s efficiency. Different systems of a construction (e.g. support, electromechanical, plumbing or energy system) should work together in a synergistic mode: the performance of each system should be enhanced by the function of the other systems. Desired properties should occur rather as a consequence of the system’s function than as a result of project-specific design. This can be achieved through the proper design of the system’s units, which also includes their interactions. The particular approach promotes also user participation in the production procedure, as the role of the expert designer degrades. This allows a distributed production procedure which makes possible various forms of emergence. The "developmental" paradigm specifies a recursive bottom-up creation process where larger-scale, complex, specialized structures are composed from lower-scale, simpler, less specialized ones. During this process information is reused as different specialized structures inherit the same information produced at a previous composition phase. The social cost could be defined as the total amount of human time that has to be spent in work concerning either the creation or the use of the built space. This also includes the work necessary to obtain all the construction and use resources. The informational cost constitutes part of the social cost: it concerns the information production work performed during either the creation or the use of the built space, as well as the obtainment of the respective resources. The creation and the use of the built space consume both material and energy resources. Reduction of the necessary resources of this kind results in reduction of both the social cost and the environmental implications. The built space should be easy to modify. This would make the system adaptable to versatile conditions, while would encourage user-made modifications resulting in satisfaction of small-scale dynamic needs. Even the best possible building system would be unattainable if it could not be implemented in the current technological framework at a cost lower than the cost saved due to the system’s application. Ideally, a building system should make best use of existing production possibilities which otherwise would remain partially or totally idle. The quality of the architectural space depends on both the quality of the material resources provided by the system and general spatial attributes characteristic of the system. To a large degree, architectural quality constitutes an emergent property.

Continued in Section_2_EN.PPS