Sunday, February 9, 2014

Round tripping and other IT fairy stories

IT should recognise that round tripping seldom takes places automatically in mature domains. Design are not normally round tripped. If the data passed in is changed those  changes are usually dealt with by a specific process i.e.
- a cadastral function defines boundaries and other features of the land may be recorded e.g. trees, streams, walls etc.
- a town plan has a map showing plots of land which is used by Architect. Walls, foundations, services etc. may be placed relative to the boundaries. If the Architect changes something that was on the town plan i.e. the data passed to the architect - there is usually some process of notifying the owner of the town plan/map (so they know of the change- as it may affect others)
- an architect defines a walls to be built by a carpenter. The carpenter works out where the studs, braces etc. and nails will go (these details are not normally passed back). If the location of the wall varies from the plan for some reason then dealt with by a process of notifying the owner of the building plan (it isn't just feed back into the plan - because the implications are not known).

IT frequently asked about round-tripping. Which may be possible - but I suspect seldom makes sense because as one descends down from business and conceptual objectives through to implementation and technical details - it is very hard to know what makes sense to feed upwards.

No comments: