Modeling a domain using an entity-relational diagram

These conditions determine "minimum" requirements. I recommend trying to do rather more than less (or minimum). You can add more entities, relationships, define more attributes and so on. Thanks to more advanced model it will be much easier for you later to create more and meaningful queries.

In a classical way, the analysis is done with a customer who defines what he needs. In this approach the right model of domain is what the customer needs and want. Your approach will be a little bit different as you don't have a customer, therefore you can be your own customer or you can ask your instructor for help defining model. This means that you must specify what you want to store in the specified domain - for example if you have domain for managing student assignments, you need to think if it is required for you to store students entities in database or not. Will you create student entity, will you create assignment entity?