The system concept has these elements: Sensors (e.g. cameras) are installed in the parking lots. The system has maps of all parking lots and data on the geographical coordinates of all parking spaces. The parking lot has a public wireless network capability. Users have a compatible smartphone with GPS (global positioning system) capability. The smartphone will have an application to be developed by your project that requests the location of nearby empty parking spaces. The system you develop will display the location of the nearby empty parking spaces on the smartphone. (“GPS” means the smartphone knows the geographical coordinates of the smartphone somehow.) Your software development company have subcontracted with a company that specializes in imaging to provide a commercial off the shelf (COTS) software component to use in the parking space locator application. The input to the COTS software component is raw sensor data (e.g. images). The output of the COTS software component is a list of locations (geographical coordinates) that it detects as parking spaces that are occupied. Your application will receive the output (list of locations) every 15 seconds. Page 2 of 3 There are some assumptions and details that you, the database designer, must decide. Be sure to document any assumptions that are not made clear in your design choices.

Additional Requirements:
Your database application does not have to store the raw sensor data. In fact, it does not have access to the raw sensor data. It only receives a list of occupied parking spaces. Each parking space is located in a lot.
Lots are assigned to a zone: Staff, Commuter North, Resident North, etc. Some spaces within a lot have a special status such as reserved, service parking, handicap parking, etc. Most spaces will not have a special status. You have been asked by parking services to save the list of occupied parking spaces every 10 minutes. They will use this data at a later time to decide which parking lots should be expanded. Students and Staff should be available to create an account on the parking space locator application. Their account will hold which type of parking pass they have purchased so that the application can search the appropriate lots without user input.

The ER Diagram must include primary keys, partial keys, key constraints, participation constraints, cardinality ratios in addition to the entities, attributes, and relationships. Define the minimal set of attributes based on the requirements given.