CMIS$564$ Database Design Project: Antique Oddities, Inc. Antique Oddities is an Edwardsville based business that sells antiques. The company is a small family business. The owners over time have grown the business to high five figures in sales over the years. As the business has grown larger, the use of spreadsheets to manage the business doesn$$t fit the business anymore. The owners want a database application be developed for this purpose. Assume you are hired for this job. As an initial step to this development effort, your task is to come up with a conceptual schema $($Entity$-$Relationship model$)$ based on the information provided below. Antique Oddities product line is categorized in several distinct categories: Breweriana, Americana, Vintage Photos and as expected, Oddities. Sales should capture this categorization. Of course sales data should capture the sales price, shipping cost as $80\%$ of items sold are online. Online sales are comprised of three channels: Etsy, eBay and direct contact $($email etc$).$ There is one bricks and mortar location. But this fluctuates; at one point there were $12$ locations. Sales are tracked by location as well. Purchases are also tracked: cost, source and if online, the order number. Sources for purchases mirror the sales channel but are not limited to those. Additional expenses are tracked as well: booth rental fees, Etsy fees, eBay fees $($this are monthly$),$ food and entertainment, office supplies, computers, cell phones, etc. The data should lend it self to some type of future reporting on sales and expenses. Project Requirements: Based on the afore$-$mentioned narrative, design a relational database schema for Antique Oddities. I. Draw an E$/$R Diagram following the modeling conventions discussed in the course. $1.$ Use nouns to name entities and verbs to name relationships. $2.$ Identify attributes and assign them to entities. If you are not able to show all the attributes $($for all the entities$)$ in the diagram on one single page, indicate the identifier and one or two non$-$identifying attributes for each entity in your diagram and list the other relevant attributes on a separate page. $3.$ Avoid many$-$to$-$many relationships. Express them as Associate Entities. $4.$ Specify cardinality $($maximum and minimum$)$ for each relationship. $5.$ Create a data dictionary for your E$/$R Diagram. Define each entity, relationship, and attribute in your diagram which are not self$-$explanatory $($see class notes for examples$).6.$ Clearly state any assumptions you make. However, make sure your assumptions are realistic. Do not make any assumptions just to suit your answer. $7.$ You do not have to use any ER Diagramming software tools. You may use standard MS$-$Word or PP tools to draw your diagrams. $8.$ What you need to turn in: Your ERD. II$.$ Transform your E$/$R model into a relational structure. $1.$ Map your ERD to a Relational structure $($schema$).2.$ Split your tables if necessary to make sure that all your tables are at least in $3$NF$.3.$ Clearly indicate all Foreign Keys in each table. $4.$ Clearly indicate the $$required$$ attributes in each table, i$.$e$.,$ the attributes where NULLS will not be allowed. $5.$ Draw a normalized $(3$NF$)$ relational structure diagram. $6.$ What you need to turn in: A normalized $(3$NF$)$ relational structure diagram AND ERD Diagram from Part I.