You will first design an EER schema diagram based upon the BOOKSTORE MANAGEMENT database requirements specified below, and create an EER schema diagram and documentation report describing your design choices. You should identify any missing or incomplete requirements, and explicitly state them in your documentation. You should also explicitly state any assumptions you made that were not part of the requirements listed above.

1. The database keeps track of CUSTOMERs, STAFFs, ITEMs (eBooks, Movies, periodicals), SUBJECTs, AUTHORs, PUBLISHERs, DIRECTORs, and etc.

2. Each CUSTOMER has a unique IdNo (assume this is a unique integer generated by the system for each new CUSTOMER, such as 1, 2, 3, ), a Name (assume this is string consisting of an single initial and last name only for simplicity, such as J.Smith or R.Wong), a PhoneNo (a string of 12 characters such as 817-333-6000), an Address (a string of MAX 256 characters), an Email (a UNIQUE string of MAX 100 characters), an UserName (a UNIQUE string of between 8-12 characters), a Password (a string of between 8-12 characters), and CreatedDate (Datetime), and etc.

3. The database keeps track of ITEMs available for CUSTOMERs, which are categorized based on their type. There are several types: BOOK, PERIODICALS (publication), FILM, etc.

4. Each ITEM (e.g. eBOOK) has an ITEM_ID (a unique number for each item assume it is a number 1001, 1002, 1003, ), Subject (Science, Romance, fiction, Art, History, Recipes, Travel, etc.), Description (a description for each item), Item_Image (e.g. an image for each Book or periodical).

5. The database will keep track of the current (active) ORDERS as well as available ITEMS. For each ORDER, the information will include the specific ITEM and CUSTOMER as well as the CUSTOMER_PAYMENTS. OrderDate, and total price, which is a derived value that can be calculated from the other information.