Showing posts with label access. Show all posts
Showing posts with label access. Show all posts

Tuesday, 28 February 2017

Validation, verification, design

Validation, verification, design 

I often find myself entangled in discussions on what a brief is, what it does, how a design is structured with respect to a brief and all kinds of rather unproductive situations. Many of them derive from my own stubborn interest in terminological clarity and consistency, which may conflict with established terms and their use. Nevertheless, I don't intend to stop. I see what happens in other areas and it makes me believe that terminological clarity is a good indication that an area knows what it is doing and why (methodological clarity and relevance). So, I wonder what we are doing in architecture to validate and verify a design.

To be clear about the terms I'm using, validation refers to whether the design solves the original problems and validation to whether the design meets the specifications set up for solving the problem. In other words, it goes like this: we identify a problem, then we set some specifications for the designs that should solve it and then we make designs on the basis of this specification. In architecture the specifications (the brief) are often put aside and designers address the problem itself. This may indicate poor specifications or bad designer attitudes; in either case, it's a sign of a poorly operating field. Both verification and validation are necessary when it comes to testing the utility of a design as well as establishing and extending domain knowledge.

A practical example: accessibility is an undeniably serious issue in architecture. To ensure accessibility in a design we have all kinds of rules and regulations that specify constraints on spaces and building elements like the width of corridors or doors. A design can be evaluated against such constraints and so verified as an adequate solution to accessibility. However, it is also important to see if the building is also accessible by really testing it with respect to the movement of people with disabilities or spatial needs. Validation can make evident that e.g. additional constraints are required or that some constraints contribute little. We shouldn't assume that the ones we have been using are right or sufficient. Just think of Blondel's formula for stair design, which is seldom if ever challenged: 2 x riser + tread = step length. Why do we assume that it suffices for the design of safe and comfortable stairs? My own experience tells me that if a tread is not deep enough for my 46-size shoes, descent can be a problem.

Thursday, 29 December 2016

Rituals of access

Rituals of access

In Andrea Camilleri's Paper Moon, following frustrating experience with a secure bank entrance, inspector Montalbano considers writing a text on the ceremony of access and how it is intended to make you feel secure while there is no guarantee that you actually are. This is something more and more people realising with various security measures, including the demanding ones at airports. However, such rituals predate current security issues and are built in the affordances many entrances. For example, revolving doors are intended to restrict air flow and reduce drafts between indoors and outdoors. They also regulate pedestrian flow, making us slow down and go in or out in small numbers, ensuring that we've paid a ticket or that we don't go in the wrong direction (as with turnstiles). They manage to constrain our behaviour so effectively that we seldom rebel against their tyranny; we accept them as part of the experience and even welcome the adjustment they offer. When I see unobtrusive yet major design successes, I realise how natural the built environment can be.