Towards an integrated design environment for architectural design Prof. Dr. Herman Neuckermans and Dr. Ann Hendricx Dept. of Architecture, Urban Design.

Slides:



Advertisements
Similar presentations
Eindhoven Technische Universiteit An Experimental Design System for the Very Early Design Stage B. de Vries A.J. Jessurun.
Advertisements

Object-Oriented Software Development CS 3331 Fall 2009.
Alternative Approach to Systems Analysis Structured analysis
Analysis Concepts, Principles, and Modeling
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Lecture 13 Revision IMS Systems Analysis and Design.
Requirements Analysis Concepts & Principles
Lecture Fourteen Methodology - Conceptual Database Design
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
© Copyright Eliyahu Brutman Programming Techniques Course.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Modeling & Designing the Database
Course Instructor: Aisha Azeem
Object Oriented Analysis and Design Using the UML
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Traditional Approach to Requirements Data Flow Diagram (DFD)
Chapter 6: The Traditional Approach to Requirements
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 The Traditional Approach to Requirements
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Systems Analysis and Design in a Changing World, Fifth Edition
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
ITEC224 Database Programming
An Introduction to Software Architecture
ITEC 3220M Using and Designing Database Systems
1 ICAS’2008 – Gosier, March 16-21, 2008 A Transformational Approach for Pattern-based Design of User Interfaces Costin Pribeanu Jean Vanderdonckt National.
Improving Design Workflow in Architectural Design Applications Presentation Doctoral Seminar 16/06/2006 Leuven (Belgium)
Methodology - Conceptual Database Design Transparencies
Database Systems: Design, Implementation, and Management Ninth Edition
Methodology Conceptual Databases Design
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
SOFTWARE DESIGN.
Chapter 9 Moving to Design
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
Systems Analysis and Design in a Changing World, 3rd Edition
1 Introduction to Software Engineering Lecture 1.
Methodology - Conceptual Database Design
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
- 1 - Implementation of an Architectural Design Environment Stefan Boeykens Dept. Architecture CAD-Lab K.U.Leuven (Belgium) Stefan Boeykens Dept. Architecture.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Implementation Strategy for an Architectural Design Environment Stefan Boeykens Dept. Architecture CAD-Lab K.U.Leuven (Belgium) Stefan Boeykens Dept. Architecture.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Lecture 3 : Hard Systems Modelling UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Basic Characteristics of Object-Oriented Systems
Process 4 Hours.
Introduction to UML.
Methodology Conceptual Databases Design
Chapter 6 The Traditional Approach to Requirements.
Methodology Conceptual Database Design
An Introduction to Software Architecture
Methodology Conceptual Databases Design
Presentation transcript:

Towards an integrated design environment for architectural design Prof. Dr. Herman Neuckermans and Dr. Ann Hendricx Dept. of Architecture, Urban Design and Planning K.U.Leuven University, Belgium

Design Futures Seminar ° Eindhoven 22/11/ Overview CADLAB K.U.Leuven University about architectural design a conceptual system for CAAD Design methodology and CAAD CADLAB activities the IDEA+ research project core model: starting points and desiderata methodology and presentation current research status

Design Futures Seminar ° Eindhoven 22/11/ CADLAB K.U.Leuven From drafting tool to design system Numerics and logic Characters Graphics Design research area

Design Futures Seminar ° Eindhoven 22/11/ Design >< Problem solving ‘wicked’ problems ‘tame’ problems Original‘known’ Ill-definedsystematic Problem definitionoptimisation // problem solutionstep by step variable(s,pd,ga,sp,es,d,i,f) rational + irrationalrational uncertain

Design Futures Seminar ° Eindhoven 22/11/ Design Most important decisions in early stages of design Not one best design method Open design system

Design Futures Seminar ° Eindhoven 22/11/ Sketch Design Conceptual solution for –Formal issues –Layout –Construction –Equipment

Design Futures Seminar ° Eindhoven 22/11/ Conceptual system for CAAD in the sketch design phase Physical levels: each can be entry point Grids: hierarchical 10/30/60/90 Tests: in development >< post-design appraisal

Design Futures Seminar ° Eindhoven 22/11/ Conceptual system for CAAD in the sketch design phase

Design Futures Seminar ° Eindhoven 22/11/ CADLAB Didactics Conceptual model Object modelling for IDEA+ Case-based design Integrated testing: daylight, sunshine, shading Documentation and visualisation of archeological sites

Design Futures Seminar ° Eindhoven 22/11/ Historical reconstruction of Leuven Thesis work 00-01: sunshading intelligent zoom / objects detailing:2D/3D animation + test visual keys for CBD CADLAB (2)

Design Futures Seminar ° Eindhoven 22/11/ The IDEA+ research project Aim: an Integrated Design Environment for Architect designers. Research topics include: A central building model Software tools using the central model A swift data management system

Design Futures Seminar ° Eindhoven 22/11/ The IDEA+ research project modelling tools evaluation tools building partnersarchitectural cases digital model architect designer integrated environment

Design Futures Seminar ° Eindhoven 22/11/ Product modelling Product modelling: ‘The use of computers to represent the designer’s (or designers’) evolving idea of an artefact of design during the design process’ (Galle 1998) architect ownercontractorsengineersinhabitants town planning office

Design Futures Seminar ° Eindhoven 22/11/ = fit the model in a workable design environment = a static description of the architectural and geometrical objects capable of describing architectural design objects + ensuring the possibility of evolution and modelling (complex) behaviour + model the communication between the model and the surrounding tools Product modelling

Design Futures Seminar ° Eindhoven 22/11/ The core object model: Starting points and desiderata premises: –pursue qualitative architecture –support the early design phases –allow different design approaches –respect the evolutionary nature of design –ensure the core model’s neutral position case studies, test implementations methodological approach - MERODE

Design Futures Seminar ° Eindhoven 22/11/ Hogenheuvelcollege - Leuven Paul Van Aerschot / Poponcini & Lootens

Design Futures Seminar ° Eindhoven 22/11/ The MERODE methodology Model-driven Existence-dependency Relationship Object-oriented Development conceptual modelling: distinction between specification and implementation model driven development  distinction between enterprise objects and functionality objects

Design Futures Seminar ° Eindhoven 22/11/ Resulting model: objects describing the partitioning parts of an architectural project (basic behaviour included in an object’s methods) + objects describing all kinds of functionality i.e. operations on and interactions between the partitioning parts a core object model for architectural design

Design Futures Seminar ° Eindhoven 22/11/ Stepwise development of the core object model 1. enterprise model enterprise objects and events static relationships between the enterprise objects object-event table elaborated class definitions: attributes, contraints, functions methods layer atomic events layer functionality layer user interface implementation strategy for an OO environment 2. functionality model

Design Futures Seminar ° Eindhoven 22/11/ MERODE and the conceptual framework enterprise submodel functio- nality submodel integrated design environment

Design Futures Seminar ° Eindhoven 22/11/ Enterprise objects 1. generic principle layer 3. specialisation or library layer 2. architectural aspects layer enterpise objects project model instantiation

Design Futures Seminar ° Eindhoven 22/11/ Generic principle layer General principles, for instance: PROJECT ELEMENT CAAD ENTITY GRAPHICAL ENTITY staircase 1. stair 2. banisters

Design Futures Seminar ° Eindhoven 22/11/ Architectural aspects layer CAAD ENTITY: PHYSICAL ELEMENT, SPACE, USER ACTIVITY, GRID … and related objects bathroom bedroom dining room day area night area

Design Futures Seminar ° Eindhoven 22/11/ Architectural aspects layer PHYSICAL ELEMENT TYPE COMPOSITION PHYSICAL ELEMENT information independent from typological information typological information PHYSICAL ELEMENT TYPE typological information independent from composition composition information PHYSICAL ELEMENT COMPOSITION composition information “kitchen wall” cavity wall 14/7/9 wall with overall thickness 30 cm unraveling physical elements to enhance their capability of change:

Design Futures Seminar ° Eindhoven 22/11/ Specialisation or library layer Specialisations of objects defined in the generic principle or architectural aspects layer e.g.GRAPHICAL ENTITY PHYSICAL ELEMENT TYPE PHYSICAL ELEMENT TYPE TERRAIN PRIMARY ELEMENT SECONDARY ELEMENT HVAC ELEMENT INTERIOR DESIGN ELEMENT FOUNDATION PLANAR ELEMENT SKELETON ELEMENT STAIRS WALL ROOF FLOOR OPENING ELEMENT...

Design Futures Seminar ° Eindhoven 22/11/ Setting relationships  Simplified E-R scheme generic principle layer architectural aspects layer

Design Futures Seminar ° Eindhoven 22/11/ A catalogue of object class definitions 1. enterprise model enterprise objects and events static relationships between the enterprise objects object-event table elaborated class definitions: attributes, constraints, functions methods layer atomic events layer functionality layer user interface 2. functionality model

Design Futures Seminar ° Eindhoven 22/11/ relation with other object classes attributes and constraints object methods A catalogue of object class definitions

Design Futures Seminar ° Eindhoven 22/11/ Hogenheuvelcollege case study core objects and relationships in relational database entrance forms relation- ships tables

Design Futures Seminar ° Eindhoven 22/11/ modelling in several phases: masterplan - physical elements - spaces - user activities Hogenheuvelcollege case study

Design Futures Seminar ° Eindhoven 22/11/ modelling in several phases: masterplan - physical elements - spaces - user activities Hogenheuvelcollege case study

Design Futures Seminar ° Eindhoven 22/11/ modelling in several phases: masterplan - physical elements - spaces - user activities building rooms subspaces floors vertical circulation letter box corner Hogenheuvelcollege case study

Design Futures Seminar ° Eindhoven 22/11/ The functionality model 1. enterprise model enterprise objects and events static relationships between the enterprise objects object-event table elaborated class definitions: attributes, contraints, functions methods layer atomic events layer functionality layer user interface 2. functionality model implementation strategy for an OO environment

Design Futures Seminar ° Eindhoven 22/11/ modelling tools evaluation tools building partnersarchitectural cases digital model architect designer integrated environmententerprise model functionality model class definitions The functionality model

Design Futures Seminar ° Eindhoven 22/11/ Layering functionality User Interface Functionality Layer Atomic Event Layer Methods Layer complex workflows input output services tasks consistent events event broadcast core object model higher functionality

Design Futures Seminar ° Eindhoven 22/11/ Class definitions of functionality objects Class TRANSFORM-ENTITY Attributes -- references to participating object types: … -- additional attributes: … Methods initiate_transform_entity (Input_graphical_entity: GRAPHICAL-ENTITY) is... check_validity is... run is Different options: if solitary graphical-entity: perform transform operation on graphical-entity else: define caad-entity and all connected caad-entities (via dependence-link, mandatory boundary-link) if physical-element: perform operation on physical-element-type else: perform operation on caad-entity The transform operation is conducted on the appropriate graphical-primitive, after which the geometry_topology attribute is set in accordance with the new situation. This setting triggers the VISUALIZE service. class definition of Input output service TRANSFORM-ENTITY

Design Futures Seminar ° Eindhoven 22/11/ Final state machine Service Specification Diagram Class definitions of functionality objects

Design Futures Seminar ° Eindhoven 22/11/ The IDEA+ research project Future: elaboration and implementation of the functionality required for the IDEA- l design tool Elaborated description of the enterprise objects and events Testing on actual design cases Example elaboration of the functionality model Development and prototype implementation of a geometrical modeller and the IDEA- l design tool for natural lighting

Design Futures Seminar ° Eindhoven 22/11/ Current research activities at the CADLAB: core object model sunshading visual keys evaluation tools building partners architectural cases digital model architect designer integrated environment modelling tools architectural details- builder 2D-3D Intelligent objects Idea-l : daylighting tool Dynamo: architectural database on-line

Design Futures Seminar ° Eindhoven 22/11/ Thank you for your attention!

Design Futures Seminar ° Eindhoven 22/11/ DESIGN METHODOLOGY & CAAD PART 1 Design theory: epistemology of design design activity design process programming structuring info coping with complexity sketch design generation of ideas selection of solutions

Design Futures Seminar ° Eindhoven 22/11/ DESIGN METHODOLOGY & CAAD PART 2 Design methods: a critical study notation methods decomposition patterns masterplanning morphological box brainstorming synectics

Design Futures Seminar ° Eindhoven 22/11/ DESIGN METHODOLOGY & CAAD PART 3 History of HW / SW / CAAD HW & SW for CAAD Modeling: conceptual physical Application: actual prospective