Improving megaproject briefing through enhanced collaboration with ICT

Requirements processing for building design: a systematic review

“…The focus is on integrating requirements' information over the project life cycle, but the authors themselves say that, although many CIC systems have been developed, they usually do not go beyond the limits of technology transfer (Arayici et al, 2006). In general, it can be seen that even in the most recent research, few authors in this group use IT resources (Arayici et al, 2006;Sheer et al, 2007;Chung et al, 2009;Bluyssen et al, 2010).…”

“…These authors propose an integrated model to guide the execution of RM activities, based on the continuous requirement identification, a requirement web-based repository and a requirement change management system. In this sense, the use of web-based collaborative environments was recognized in studies about work plans (Sheer et al, 2007) and extranet network systems (Chung et al, 2009). These structures complement the informal registration and face-to-face meetings, and can improve efficiency in communication and trust in the work of those involved and.…”

“…Most of the guidelines identified are prescriptive and are associated to the well-known problems in the design process, such as difficulties in generating value (Chinyio et al, 1998;Kamara et al, 2001;Leung et al, 2002;Othman et al, 2004;Shen et al, 2004;Yu et al, 2005;Sterry & Sutrisna, 2007;Thyssen et al, 2010;Chandra & Loosemore, 2011;Jay & Bowen, 2011; and in communication (Ryd, 2004;Arayici et al, 2006;Luck & McDonnell, 2006;Sheer et al, 2007;Chung et al, 2009;Bluyssen et al, 2010).…”

“…Guidelines for the Requirements Processing (Chinyio et al, 1998;Kamara et al, 1999;2002;Luck et al, 2001;Hyams, 2001;Leung et al, 2002;Kelly & Duerk, 2002;Othman et al, 2004;Shen et al, 2004;Ryd, 2004;Yu et al, 2005;2007;Arayici et al, 2006;Yu, 2006;Luck & McDonnell, 2006;Sheer et al, 2007;Sterry & Sutrisna, 2007;Chung et al, 2009;Thyssen et al, 2010;Chandra & Loosemore, 2011;Zarooni et al, 2011;Jay & Bowen, 2011;.…”

“…(Luo & Shen, 2008). The brief, which is the main product of briefing, is a document defining at any point in time the relevant needs, aims, and resources of the clients and users, the context of the project and any project requirements (Chung et al, 2009). The outcome of the briefing process is a brief, a document detailing the information about client requirements (Jallow et al, 2014).…”