To expand on the above comment because it's so true:
Prototyping is usually done at an 'Architectural' scale like urban design, international airports, 'Gigafactory', or very large apartment buildings in cities. It's just not affordable or practical (time or money) for the single-family home.
Examples of client costs which must be passed on to the consumer may include 3d rendering/animations at the very simplest. U.L. Certification for any un-listed building product OR assembly (e.g. how a wall is put together with your new material) is somewhat common - like living in a reclaimed steel shipping container building in the past or using a airplane fuselage/boat hull now. Fire ratings are also often required and that's almost always a destructive test - the cost is double or triple for that new tent roof design assuming it passes the first time. Be prepared for the insanity of earthquake tests if you design a new transparent block you want to use in your wall - even if it's not load bearing. A simple custom rubber gasket will require water/air pressure tests in many cases and that's pretty common for glazing systems.
Every building design is an MVP - it must comply with with the 'Building Codes' (IBC/NFPA/AISC/etc.) which by definition is a set of rules for building a safe MVP. Beyond the MVP you hire a specialist like interior designer/landscape arch/audio specialist and even then there are laws which must be followed (smoke/flame spread, permeable land usage, etc). No extra information is ever added to the construction docs (blueprints) because they're a contract too. And every element either graphic or textual will incur a liability and/or expense within the set of drawings and written specifications.
AEC's work out designs in their heads and translate them to paper for legal approval - that's how they avoid premature optimization. That applies to the schedule too.
When you look at a blueprint and you see 'the cloud' around part of the drawing it's a revision - something has changed - and so the graphic notation for iterative design is built into the conventions for conveying important information.
Take another look at architecture beyond Alexanders 'Pattern Language' books[0] and Frank Ching's awesome sketches[1] used as inspiration for the GoF books[2]. You'll find that there's a lot of applicable ideas for software starting before Imhotep and continuing through today. Philosophically speaking, both disciplines are reflections of the current society at the time of their construction.
Prototyping is usually done at an 'Architectural' scale like urban design, international airports, 'Gigafactory', or very large apartment buildings in cities. It's just not affordable or practical (time or money) for the single-family home.
Examples of client costs which must be passed on to the consumer may include 3d rendering/animations at the very simplest. U.L. Certification for any un-listed building product OR assembly (e.g. how a wall is put together with your new material) is somewhat common - like living in a reclaimed steel shipping container building in the past or using a airplane fuselage/boat hull now. Fire ratings are also often required and that's almost always a destructive test - the cost is double or triple for that new tent roof design assuming it passes the first time. Be prepared for the insanity of earthquake tests if you design a new transparent block you want to use in your wall - even if it's not load bearing. A simple custom rubber gasket will require water/air pressure tests in many cases and that's pretty common for glazing systems.
Every building design is an MVP - it must comply with with the 'Building Codes' (IBC/NFPA/AISC/etc.) which by definition is a set of rules for building a safe MVP. Beyond the MVP you hire a specialist like interior designer/landscape arch/audio specialist and even then there are laws which must be followed (smoke/flame spread, permeable land usage, etc). No extra information is ever added to the construction docs (blueprints) because they're a contract too. And every element either graphic or textual will incur a liability and/or expense within the set of drawings and written specifications.
AEC's work out designs in their heads and translate them to paper for legal approval - that's how they avoid premature optimization. That applies to the schedule too.
When you look at a blueprint and you see 'the cloud' around part of the drawing it's a revision - something has changed - and so the graphic notation for iterative design is built into the conventions for conveying important information.
Take another look at architecture beyond Alexanders 'Pattern Language' books[0] and Frank Ching's awesome sketches[1] used as inspiration for the GoF books[2]. You'll find that there's a lot of applicable ideas for software starting before Imhotep and continuing through today. Philosophically speaking, both disciplines are reflections of the current society at the time of their construction.
[0] https://www.patternlanguage.com [1] http://www.frankching.com/ [2] https://www.amazon.com/Design-Patterns-Elements-Reusable-Obj...