Looking at the logical architecture for hms_sys, and allowing for a local data store for the Artisan Application that wasn't in the original diagram, there are three databases that development needs to be concerned with:
The Web-Store Database is attached to the Web-Store Application, and cannot be modified as a result. The current expectation is that modifications to data in that database will be handled by a call to the API that the Web-Store Application makes available. At this point, then, data access to and from this database can be set aside.
The artisan Database, on the other hand, doesn't exist yet at all, and will have to be created as part of the development of hms_sys. It feels safe to assume, given the artisan-level, installation-related stories from the first iteration, that keeping the number of software installations they...