[NOTE] 
- We understand that the solutions to this problem could be very subjective and 
  different persons may take very different views on how to model the domain. 
  When marking, we took several solutions we think are "better" designs and give 
  marks on the basis of similarity of your solution with the "better" ones.  
- Similar mistakes are penalized only once
- If more than one of following categories apply, the more specific one is taken

General
--------------------------------------
- Entity (missing or extra) -5
- Relationship (missing or extra) -5
- Attribute (missing or extra or misplaced) -2
- Key (wrong or not showing) -3
- Contraint (wrong) -3
- Assumption (unreasonable) -3

Item (book, cd, video)
------------------------------------
- Model author and/or artist as attributes -6
- Not model different kinds of items -6
- Model borrowed item as a separate entity -5
- Place item's attributes on its children -2
- place item's relationship on its children -2

Collection & Branch
-----------------------
- Miss collection/library branch concept (and associated rels and attrs) -6
- Model collection/library branch as an attribute -3
- Model collection/library branch as an relationship -2 

User
------------------------------------
- Miss user type (age group) concept and associated rels and attrs -6
- Model user type as an attribute on user  -3
- Miss fine-rate and/or loan-period information -2

Borrow/Return
-------------------------------------
- Model borrow as an separate entity -6
- Model borrow as relationship between user and library -3
- Split borrow/checkout concept into multiple entities -2
- Miss fine attribute on borrowing/checkout -1
- Treat condition as an attribute of borrowing/checkout -1