Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
start [2019/05/22 11:12] adminstart [2020/06/25 13:12] admin
Line 1: Line 1:
-====== Welcome to the Documentation of TAD ®======+====== Welcome to the Documentation of TAD®======
  
 TAD stands for "The Architect's Desktop"  TAD stands for "The Architect's Desktop" 
Line 11: Line 11:
  
 //Architects need to have a system to flesh out a design iteratively, explore alternatives, capture and communicate intentions clearly, be ready to handle any just-in-time situation during design, construction and usage, and in the end leave behind one central holistic model that captures all the knowledge of the project// //Architects need to have a system to flesh out a design iteratively, explore alternatives, capture and communicate intentions clearly, be ready to handle any just-in-time situation during design, construction and usage, and in the end leave behind one central holistic model that captures all the knowledge of the project//
 +
  
 Our mission is to provide the aforementioned context for architectural design, construction and usage Our mission is to provide the aforementioned context for architectural design, construction and usage
Line 19: Line 20:
  
 Architectural knowledge should no longer remain in silos. The knowledge that we produce MUST be left behind for objective analysis and understanding by anyone concerned or affected. This can be only done if we express our work in an objectively understandable form -- with least controversy of interpretations Architectural knowledge should no longer remain in silos. The knowledge that we produce MUST be left behind for objective analysis and understanding by anyone concerned or affected. This can be only done if we express our work in an objectively understandable form -- with least controversy of interpretations
 +
 +**//Architects should not leave behind just the __what__ that was designed but also the __why__ for future generations. That is the only way knowledge can break out of silos//**
  
 **Road map** **Road map**

Press F1 inside the application to read context-sensitive help directly in the application itself
Last modified: le 2023/04/22 20:59