Payment methods conceptual and logical model I need to create a conceptual and logical (normalized) models of parking house according to the requirements below. It looks to me as a very simple concept that doesn't need all tables to have relationships - but then they could not be modelled as entities.
I tried asking this on stackoverflow but got no feedback for couple of days now.


Three possible methods of payment:


a ticket paid on leave,
prepaid card with cash credit,
prepaid card with "time credit",

Price of ticket depends on time:


1-2hrs = $0,
3hrs = $2,
4hrs = $4,
afterwards x hrs = $(x+1), but max. $20 for 24hrs (... easiest to put these to 24 rows, right?).

A ticket (a) may be allowed a 20% discount (ie. for shopping in the mall).
Cash credit card uses same prices as tickets but with 40% discount.
Cash credit card can be reloaded.
Time card is paid once and allows parking while valid.


The problem is I don't know how to put those highlighted relations to the logical db model and whether event to put them there. Is it ok-practice to have isolated tables in the design?
In a transactional system you will want to record the values that applied to the transaction at the time it happened.

It is a mistake to try to use relationships to connect a transaction to a date-depenendent lookup data.  The reason for this is that changes to the date-dependent data that happen after the transaction will restate what should have happened to the transaction.  This will cause confusion and errors.

The way to handle this type of situation is to denormalize the actual value applied to the payment transaction.  Your model doesn't reflect this, but if you had named categories for your discounts and timespan rates, you could keep a relationship from the transaction to the category name while still denormalizing the actual (time sensitive) rate/percent.



EDIT: What should the logical model look like?

In your logical model, the issue is that you need multiple discount (or price) rates because they change over time - or just because there may be multiple rules, for example one price for regular customers and one for special customers, etc.

What is missing is the notion of a rate table.  This is like a header which then has rate details attached to it.  What you have in your model now is really just the rate detail.  You need to insert the rate table header in between the transaction and the rate detail.  In your logical model, the relationship is between the transaction and the rate table header.  This is OK because the rate table is more stable than the details which change over time.

In your physical model you still need to denormalize make a point in time snapshot of the actual rate used into your transaction because that is the only reliable way to make sure that editing the rates won't restate history.