I routinely develop small data collection systems for a variety of purposes. One issue I frequently encounter is what to refer to the front-end as to users. They're just about tech-savvy enough to know that the database is the actual data storage and not the form they input into, and there's some separation between the two, but not quite tech-savvy enough to understand what is meant by 'front-end' vs 'back-end'. 'Database' is frequently used to describe either.
Thus, there's real ambiguity over usage of the term 'database' - a question frequently raised by both sides of communication is whether 'database' is presently being used to refer to the "forms where you/we type things in", the "place where the data is stored", or the whole system in general. It gets even worse when users insist on referring to Excel workbooks as databases too (and even, once or twice, the stack of paper on their desk - it's happened!). Confusion and/or heavy-handed explanation ensues.
So what's a nice, entry-level and generally understandable term to be able to say "these are the changes I've made to the front-end" and "these are the changes I've made to the back-end"?
Edit: I've tried using "form" to refer to the front-end, but that also leads to overlap, as users often think of the "form" as being the physical paper sheet they're copying into the system. So if I say I've made a change to the form, users tend to think I mean the paper form, not the front-end.