![\"\"](\"https:\/\/depts.washington.edu\/csclab\/wordpress\/wp-content\/uploads\/image.jpg\")
<\/a>\nContemporary design practice is in flux. It continues to become increasingly collaborative and dependent on a proliferation of software-driven modeling systems. The advent of more affordable and ubiquitous modeling software, especially 3D CAD, in design fields such as\u00a0Architecture\u00a0is causing massive ripple effects on design practice. Each modeling system favors different concerns and ways of working. Engineering friendly Building Information Model (BIM) software has taken many design fields by storm yet recent research has called in to question its effectiveness for supporting conceptual design. In contrast, more accessible modeling systems such as Rhino, designed to be more similar to drawing and their related practices, have also become ubiquitous. Some larger firms find not only both, but multiple systems, in one project. Adding to the collaborative complexity is that traditional, analog modes (e.g. paper sketches, printouts, and scale models) continue to be necessary and useful.
\nWhereas design for the built environment has customary milestones where responsibility is handed off from one stakeholder to another, modeling software is aggressively changing how and by who work is carried out. While the ability of modeling systems to support collaboration is often touted, it is unclear that software development efforts are taking into account both the particular social and technical needs of collaborative conceptual design and how those outputs will be used by fabricators\/builders. More research is needed to holistically study how designers talk around, disagree, negotiate, and work together to mix and match traditional and analog artifacts, 2D and 3D models and modeling systems through the first two stages of the\u00a0architecture\u00a0design process: conceptual design and design development.<\/p>\n
Using observations, semi-structured interviews, and artifact analysis to study\u00a0architects, product designers, infrastructure developers, fabricators, and members of an\u00a0architecture\u00a0software firm, this work proposes a three-year ethnographic study to document and analyze how stakeholder groups communicate and collaborate around different types of iterative analog and digital models to first do conceptual design, move to development\/fabrication, and then iterate. We will study the ecosystem of computational and material artifacts and the practices that they support, enable, or restrict. We examine design collaboration using an infrastructural perspective (tracing overlapping and embedded relationships between people, technologies, and analog artifacts).<\/p>\n
This study will:
\n\u2022 Investigate when and how stakeholder participation changes during and shortly after schematic design
\n\u2022 How and when different modeling software is brought to bear for different design activities
\n\u2022 How and when analog artifacts are used in relation to process, modeling software, and collaborators
\n\u2022 Inform the design of systems that can more purposefully and appropriately support a variety of collaborative design situations and practices including tools for managing how collaboration unfolds<\/p>\n
This research offers broader impacts for education and scholarship in multiple communities. Our study will contribute to a corpus of research on the role of software in collaborative\u00a0architectural\u00a0design, HCI\/CSCW, engineering, and advance education in\u00a0architecture\u00a0and design by providing ways to reflect upon and change practice.<\/p>\n","protected":false},"excerpt":{"rendered":"
Modeling Software and Evolving Collaborative Design Practices in Architecture and Design Contemporary design practice is in flux. It continues to become increasingly collaborative and dependent on a proliferation of software-driven modeling systems. The advent of more affordable and ubiquitous modeling software, especially 3D CAD, in design fields such as\u00a0Architecture\u00a0is causing massive ripple effects on design practice. Each modeling system favors different concerns and ways of working. Engineering friendly Building Information Model (BIM) software has taken many design fields by storm…<\/p>\n","protected":false},"author":19,"featured_media":1737,"parent":7,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-notitle.php","meta":{"footnotes":""},"class_list":["post-1715","page","type-page","status-publish","has-post-thumbnail","hentry","post-has-thumbnail"],"_links":{"self":[{"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/pages\/1715","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/users\/19"}],"replies":[{"embeddable":true,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/comments?post=1715"}],"version-history":[{"count":11,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/pages\/1715\/revisions"}],"predecessor-version":[{"id":1743,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/pages\/1715\/revisions\/1743"}],"up":[{"embeddable":true,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/pages\/7"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/media\/1737"}],"wp:attachment":[{"href":"https:\/\/depts.washington.edu\/csclab\/wp-json\/wp\/v2\/media?parent=1715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}