> > > The daemon would notionally be in two sections - the front end whcih is > > > dependent upon the data structure passed to it, > [...] > > > and the back end > > In today's informatics, it is common to distinguish between "Frontend" > (User Interface) and "Backend" (Persistence Mechanism). THIS IS WRONG. > The frontend doesn't "get passed" a data structure, it _is_ a data > structure! All we need to consider is a "System" (Human) having one or > many instances of a "Model" (Brain and special Organs): System --> Model
[...] > Using such an architecture, one can add or delete any data models > (remember: data models also means any kind of user interface!) and > exchange mechanisms without touching any other or changing the whole > system every time. This is true component orientation/modularization. So exactly how does this help us in implementing a reference prescription module ? BTW, Fowler, who happens to be one of the OO gurus, recently published research on how Agile Programming worked well for larger projects _including_ database schema work. http://martinfowler.com/articles/evodb.html Thus I am not entirely convinced that I need to follow your reasoning on why I should not design and use tables before having recomputed 42 as the answer to the world. Regards, Karsten Hilbert -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
