1 / 9

Implementation Strategy for an Architectural Design Environment

Implementation Strategy for an Architectural Design Environment. Issues in the development of IDEA+. Stefan Boeykens Dept. Architecture CAD-Lab K.U.Leuven (Belgium). 1 – Introduction. Ongoing transition from traditional to digital architectural practice

hada
Download Presentation

Implementation Strategy for an Architectural Design Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementation Strategy for an Architectural Design Environment Issues in the development of IDEA+ Stefan Boeykens Dept. Architecture CAD-Lab K.U.Leuven (Belgium)

  2. 1 – Introduction • Ongoing transition from traditional to digital architectural practice • Most CAAD-tools focused on construction documentation • Lack of early-design phase evaluation tools

  3. 2 – What is IDEA+ • Conceptual Model (1992) • Design Phases • Scale Levels • Transitions • Evaluation tests • Core Object Model (2000) • MERODE • Entity Relationship Diagram • Object-Event Table

  4. 3 – Data Structure • Abstraction, Interface & Independency • CAAD Entities • Representations • Commands & Events • Transitions • Tests/Evaluation

  5. 3 – Data Structure (part 2) • Abstraction, Interface & Independency • The CAAD Entities Physical Elements walls, floors, roofs, beams, columns, openings, stairs, ... Spaces Masterplan Elements Activity

  6. 3 – Data Structure (part 3) • Representations • Connection between CAAD & Graphic • Amount of representations • Share graphical entities • Interface to the data • Commands & Events • Object Event Table(from Core Object Model) • Create, Remove, Modify, Select, Import/Export

  7. 3 – Data Structure (part 4) • Transitions • Between design phases • Between scale levels • Tests/Evaluations • Daylighting (IDEA-l) • Cost Estimation

  8. 4 – Prototype Application Platform-dependency Issues • Data structure = C++ only • Portability & vendor-independency • Some common program functionality (administration, commands, evaluation tools) is kept part of the data-structure • Prototype = Win32/MFC/OpenGL • Ease of developing an interface (GUI) • Diminish development time

  9. 5 – Conclusions • IDEA+ is a work-in-progress • Data structure is not finalised yet • Prototype aims to be suitable for further development • Not the intention to make a commercial-class application END OF PRESENTATION

More Related