Add a comment

 

Architecture is lacking/degenerate in software

There seems to be a huge difference between a building and software: buildings are inhabitaed, software is not inhabitated. Users are not "in" the software doing stuff. They are always on the outside. They only have contact with a surface, the user interface. Like with a vending machine or a car.<p/> The "architecture" of a vending machine is of no concern to users. But the layout of the surface is.<p/> What C. Alexander ist talking about is the "interaction surface" where inhabitants are in contact with architecture. When software devs talk about architecture it's (mostly) about what's behind such a surface.<p/> That said, software development at large needs to take a different stance on software architecture. It's still too much hand waving and too little systematic design.<p/> And despite interesting influences from all sorts of other disciplines software dev can learn from... it's at the same time something utterly different. Software does not suffer from wear and tear, software has hardly ever a preset lifetime, software needs to change much, much more and at a higher frequency over an indeterminate timespan than any other human product. We've to keep learning how to deal with that.

Architecture is lacking/degenerate in software


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).