The reality of the problem domain _will_ change over 
> time, and must be reflected in software somewhere, somehow.

Not directly in the software. The following types of logic can be represented 
formally outside the software:
- many kinds of business rules, often expressed in a special language
- workflow specifications, e.g. in languages like XPDL or BPEL
- computerised guidelines, in languages like GLIF, Arden
- structural specifications like archetypes
- terminology, like Snomed


Changing any of these artefacts does not require changes to the database or 
software in general; of course, if someone decides to build say a GUI or 
application specific to a given guideline then this will be affected. But 
normally 
this is t be avoided.

- thomas beale



Reply via email to