A normative design process for code-based infrastructure design
Keywords: Christian engineering, normative design, design norms, code-based design, infrastructure, civil engineering
Abstract: Design norms for engineering based on Herman Dooyeweerd’s modal aspects were introduced in the landmark book Responsible Technology and revisited in A Christian Field Guide to Technology for Engineers and Designers. While these norms were initially introduced primarily in the context of the prototype-style design most common in fields such as mechanical and electrical engineering, recent work has shown that these design norms are also very applicable to code-based infrastructure design usually most associated with civil engineering. This paper aims to extend this work into the design process, since typical approaches to design methodology often seem to also cater to prototype-style design rather than code-based design.
What should an integrally Christian design process look like? Typical design processes, whether or not they are based on the design norms, often involve an iterative methodology that designs and analyzes, prototypes, tests, re-designs, re-prototypes, and so on. However, infrastructure design typically is based on code requirements, rather than being based on an iterative prototype and testing process. Therefore, it is often difficult to apply design processes that are more geared toward this iterative style. One promising alternative to iterative design that has been briefly explored is the double-diamond model of discovery, definition, development, and delivery. In this paper, we explore this and other similar concepts in the context of the design norms to present a distinctively Christian approach to design that is appropriate for code-based infrastructure design.
Email Sharing: We authorize the sharing of all author emails with Program Chairs.
Data Release: We authorize the release of our submission and author names to the public in the event of acceptance.
Submission Number: 17
Loading