Regular hotels include restaurants, entertainment places and hotels.

Hotels should only be for accommodation, check-out, etc.

If you change it, just remove the module of hotel catering and entertainment.

You think of yourself as a customer. For example, after you enter a hotel, you don't have to stay overnight, and you don't have to entertain for dinner. So are the others.

I don't know about the hotel business, it should be just the accommodation business.

Therefore, the catering and entertainment sub-modules in the hotel system can be deleted.

If your hotel also has other businesses, then your hotel's business will be retained.

As for the background database, the objects in the database include tables on catering business (box table, menu table, order table and bill table) and tables on entertainment business (box table, consumption record table, entertainment activity table, etc. ), and the integrity constraints (rules) of views, stored procedures, indexes and other tables associated with these tables should also be modified or deleted.

This system is relatively easy to change, because the hotel business happens to be relatively easy to change with a part of the hotel business, but if the hotel only has a meal business, it is another matter …

In fact, you change the system, make clear the business relationship and requirements of the two systems, and then change the original program and database.