Automated updating of space design requirements connecting user activities and space types

Abstract Architects need to update design requirements whenever user information changes during project development. However, they often do so manually because current theories do not effectively capture the rationale behind the generation of requirements, which is often related to the activities of building users. In this paper, we formalized the relationship between design requirements and the user information in support of automated updating of the requirements. We then developed an automated requirements updating method comprising three phases: updating of user information, updating of the requirements for each space type, and adjustment of the numbers of space types to satisfy target utilization. We validated our method by comparing, for the same case example, the performance of a prototype system with that of experienced architects with respect to updating design requirements according to user information changes. Deployment of this method would allow architects to update design requirements quickly and accurately during project development.

[1]  William Peña,et al.  Problem Seeking: An Architectural Programming Primer , 1977 .

[2]  Martin Fischer,et al.  A knowledge-based framework for automated space-use analysis , 2013 .

[3]  Ipek Ozkaya,et al.  Tool support for computer-aided requirement traceability in architectural design: The case of DesignTrack , 2007 .

[4]  Martin Fischer,et al.  Method to produce field instructions from product and process models for cast-in-place concrete operations , 2009 .

[5]  Stuart D. Green,et al.  Modelling client business processes as an aid to strategic briefing , 1999 .

[6]  Halil I. Erhan,et al.  Interactive computational support for modeling and generating building design requirements , 2003 .

[7]  Bauke de Vries,et al.  Simulation and Validation of Human Movement in Building Spaces , 2010 .

[8]  Simon Wiedemann,et al.  Requirements Management , 2008 .

[9]  Arto Kiviniemi,et al.  Requirements management interface to building product models , 2005 .

[10]  Chimay J. Anumba,et al.  ClientPro: a prototype software for client requirements processing in construction , 2001 .

[11]  David Garlan,et al.  Documenting software architectures: views and beyond , 2002, 25th International Conference on Software Engineering, 2003. Proceedings..

[12]  Edith Cherry,et al.  Programming for Design: From Theory to Practice , 1998 .

[13]  N. F. Noy,et al.  Ontology Development 101: A Guide to Creating Your First Ontology , 2001 .

[14]  Qiping Shen,et al.  Building Information Modeling-based user activity simulation and evaluation method for improving designer–user communications , 2012 .

[15]  Mehul Bhatt,et al.  Ontological modelling of form and function for architectural design , 2012, Appl. Ontology.

[16]  Burcu Akinci,et al.  Representing Work Spaces Generically in Construction Method Models , 2002 .

[17]  Raymond E. Levitt,et al.  OARPLAN: Generating project plans by reasoning about objects, actions and resources , 1988, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.

[18]  Omer Akin SEED-PRO: Computer AssistedArchitectural Programming inSEED , 1995 .

[19]  Arthur J Willis,et al.  The Architect in Practice , 1970 .

[20]  Joseph A. Demkin The architect's handbook of professional practice , 2002 .

[21]  Ekambaram Palaneeswaran,et al.  Improving megaproject briefing through enhanced collaboration with ICT , 2009 .