OP asked,
Do these entities even make sense if you look at this conceptual design?
Yes, it does. From your conceptual diagram we are able to understand how entities are related to each other and their cardinality.
Is it smart to evolve this database around the program that they present to the public?
I interpret your question as "Is this design able to represent various real scenarios for which it is created?" To answer this question, I will really need to know all of those possible cases that may occur in future. From what I gathered by asking questions above, I believe the model can sustain your requirements quite well. Still, I would request you to consider following points:
Booking
should ideally be linked with yourProgram
and not to yourAccount
. If you link booking to Account and try to create a 3NF model, you will lose the correspondence between booking and programAccount
andRole
both can (and should) exist as they are two fundamentally different entities. But if you can not (or need not) capture data forAccount
in the system, you may as well do away with yourAccount
entity. You can still relate roles with the program as desired.If
Program
s are composed ofItem
s, items should be linked withProgram
rather thanRole
Is there any inherent relation with
Equipment
andStudio
? Like, certain equipments are only available in certain Studios? If yes, you may want to link equipment directly with studio.
I believe one of the goals of your conceptual model is to capture the business information in detail. Ensure that you have done so correctly in this level and everything will look great in the later part of the design!