2. Design an ER model for a photo-sharing application. Your model needs to allow for the following requirements: The app allows users to log in and upload images. Images belong to one user but may be shared (i.e. accessed) by other users. Each image has a filename, URI (Uniform Resource Identifier, which looks like a URL), and metdata, including a size, type, and description. Users have a userid which is a seven-digit string of characters and numbers. Additionally, they have a name, geographic location, and one or more email addresses. User accounts have an associated plan (for premium paid accounts) and a filespace limit. You should use the notation developed in class or the text for your ER model. You can feel free to use weak entities, aggregation, hierarchies, and higher-order relation- ships, but only where necessary (and, in particular if these refinements simplify the model). Ensure you include sensible cardinality constraints on every relationship. If you make any non-obvious assumptions when developing your model, be sure to state these assumptions and briefly justify why they are reasonable, based on what you know (or have read) about the real world. Start with a simple ER model that captures the basics, then add refinements to it. It is always a good idea to show your work and the thought process that went into your model. Translate the model you made for question 2 into relational schemas. Ensure you capture any constraints that arise from your model, or from what you know (or have read) about the real world. Also make sure you identify primary keys for each relation as well as foreign keys. Are there any constraints given by your model that you cannot capture in the relational model directly? Briefly explain why or why not