what pootleflump meant (I think) is ignore his first post here #3, as when he was posting that you were posting the link.
so havign doen your initial ERD, in your opinion does it match the requirments of the real world you are trying to model. to a certain extent thats alwasy a personal choice, and for coursework its a very personal choive.. providing your accompaning text matches the ERD it deosn't matter to much if it does match the real world. its coursework, its made up, so you can have any ERD you like.. providing it and your assumptions are compatable.
If you are happy with the ERD, then Id sugegst you fleash out the ERD into a data model creating attributes for your entities
eg
a golf club has the following attributes
presumably a name, an address, a contact point
a golf course belongs to a club (you may have to watch that, as in the real world a golf course may not belong to a club at all... it may be owned by the local authority)
it will have the following attributes
number of holes, a standard scratch score
you have a porential problem with courses that have say 27 holes arranged in blocks of 9 holes, is that 3 courses (A+B, A+B & B+C)....
a player has the following attributes
presuambly a name, an address, a handicap, a phone, and a bad sense of fashion
once you have fleshed out the data model then you are capable of building your SQL. Im assuming your course will want some queries using joins, different where clauses, different sort orders and the like. the best way of doing that in my books is to create your datamodel, put it into what ever SQL engine you have access to , putting in some test data and then drun some queries.. the test data and the output of the queries shoudl satisfy your lecturer/teacher/whoever that you have met the requirement of the course. IE your pathway from ERD, to data model, using normalisation (if you must) to data model to test db & data to queries and results