Excellent article!  Thank you for taking the time to write this up :)  A couple of comments:

1) I really like the idea of using Default Settings for application specific configuration ... that ties it in with existing import/export APIs and keeps things stored together nicely ... well done :)

2) The challenging thing with respect to reference / code tables is that directly exporting those will also export the local RowIDs for that data element, which can vary from environment to environment.  InterSystems IRIS provides a new way to handle this using the XML Exchange functionality built into the product.  Basically, when a persistent class extends %XML.Exchange.Adaptor it will ensure that GUIDs automatically get assigned to each data element, and that referenced objects are referenced in the exported XML by GUID rather than ID, which means that on import time it can ensure referential integrity by looking for the intended GUIDs in the imported object relationships.  TrakCare uses this to expose its 1000+ code tables for source control and versioning and we use it in AppServices as well.  Check it out: https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic.... 

Thanks again for this very comprehensive article about an important part of environment management :)

@Yuri Marx  - if you go to https://login.InterSystems.com you will see that we have published new icons for all of our applications which are consistent with the ISC look and feel.  Feel free to pop these into your diagram for consistency.

Any interested in learning more about these services should attend DEV005 at Global Summit where @Pravin Barton and I will discuss the 15 services and applications you can access via your InterSystems Login Account (Wed at 3:30).  Hope to see many of you there!