We’re working with a LIMS application right now, and the vendor has a
tool which allows the client to ‘configure’ the application thru a
gui. by ‘configure,’ the tool is actually allowing us to add database
tables, database fields in addition to writing custom code…all we see
in the front end is the new feature (but it really it may be a new
database table in the backend).
some people here are insisting that because the vendor intends you to
change the system, and they provide a tool to do it,
it’s ‘configuration.’ i’d argue that if you: 1. add/remove/modify
database tables 2. add/remove/modify database fileds or 3.
create/modify code, that this is all customization, regardless of how
easy or seamless it was to do it.
what have your experiences been?
also, other than obvious testing implications for customized
functionality, is there a regulatory implication as well? in other
words, would any of you be comfortable telling an inspector that adding
new database tables to an application is configuration?