Refine
Document Type
- Conference Proceeding (123)
- Article (66)
- Doctoral Thesis (25)
- Master's Thesis (5)
- Diploma Thesis (1)
Institute
- Professur Informatik im Bauwesen (177)
- Professur Baubetrieb und Bauverfahren (10)
- Professur Grundbau (4)
- Professur Holz- und Mauerwerksbau (4)
- Professur Allgemeine Baustoffkunde (2)
- Professur Entwerfen und Architekturtheorie (2)
- Professur Informatik in der Architektur (2)
- Professur Massivbau I (2)
- Institut für Strukturmechanik (ISM) (1)
- Junior-Professur Computational Architecture (1)
- Junior-Professur Europäische Medienkultur (1)
- Professur Angewandte Mathematik (1)
- Professur Aufbereitung von Baustoffen und Wiederverwertung (1)
- Professur Bauaufnahme und Baudenkmalpflege (1)
- Professur Bauchemie und Polymere Werkstoffe (1)
- Professur Bauformenlehre (1)
- Professur Bauphysik (1)
- Professur Baustatik und Bauteilfestigkeit (1)
- Professur Bodenmechanik (1)
- Professur Darstellungsmethodik (1)
- Professur Entwerfen und Industriebau (1)
- Professur Entwerfen und ländliches Bauen (1)
- Professur Planung von Ingenieurbauten (1)
- Professur Raumplanung und Raumforschung (1)
- Professur Stahlbau (1)
- Professur Verkehrsplanung und Verkehrstechnik (1)
- Professur Wasserbau (1)
Keywords
- Verteiltes System (37)
- Bautechnik (30)
- Bauwerk (27)
- Produktmodell (25)
- Simulation (23)
- Architektur (21)
- Modellierung (21)
- Mehragentensystem (19)
- Ingenieurbau (17)
- Planungsprozess (17)
Year of publication
- 2004 (220) (remove)
In current AEC practice client requirements are typically recorded in a building program, which, depending on the building type, covers various aspects from the overall goals, activities and spatial needs to very detailed material and condition requirements. This documentation is used as the starting point of the design process, but as the design progresses, it is usually left aside and changes are made incrementally based on the previous design solution. These incremental small changes can lead to a solution that may no longer meet the original requirements. In addition, design is by nature an iterative process and the proposed solutions often also cause evolution in the client requirements. However, the requirements documentation is usually not updated accordingly. Finding the latest updates and evolution of the requirements from the documentation is very difficult, if not impossible. This process can lead to an end result, which is significantly different from the documented requirements. Some important requirements may not be satisfied, and even if the design process was based on agreed-upon changes in the scope and requirements, differences in the requirements documents and in the completed building can lead to well-justified doubts about the quality of the design and construction process...