Saturday, June 02, 2007

 

Architecture vs Design vs Code

How do you draw the line between architecture, design and code? What does it mean that an architecture can engage all potential scenarios?



Let's say that you are coding an application which uses check-out register data as a basis for reordering and supplying inventory for a chain of grocery stores. The architecture allows for all the registers and stocking configurations which might be possible in an existing store as well as for future or expanded stores in the chain. The code deals with what exists now, the registers, the stockable shelves, the reserve storage space in each store and warehouse, the existing delivery options including trucks and drivers, wharehousemen, etc. In other words, code deals with the operational details, the architectural deals with potentialities.




Links to this post:

Create a Link



<< Home
| | View blog reactions


This page is powered by Blogger. Isn't yours?