Yelp.com has recently started a project to develop a new DB system for collecting and processing its online reviews. As a new project member, you are asked to write out the database requirements based on the relational schema below. In this way, the project manager can compare your DB requirements with the original ones and evaluate whether the relational schema has accurately captured all the requirements. Please go over the relational schema and write out all the DB requirements. If you make any assumptions that are not indicated in the relational schema, please write out these assumptions along with your answer.

*1 Hint: Game Record should have a composite PK.

*2 Hint: A M:N relationship calls for an additional relation with a composite PK.

*Please follow the eg format: For each xxx, Yelp.com needs to keep track of...

Review ReviewID Rating Comment ReviewerD (FK BusinessID (FO ReviewDate Business BusinessID Business Name Address (U) Phone Number (4) Business Hours PriceRange BusinessFeature BusinessID (FIO Featurell (FK Reviewer Reviewerlo Reviewer Name Email () Password Yelp Elite Status (0) City State Feature Featurell Feature Type FeatureDescription Task tips: Step 1: Identify relations in the relational schema and write out a DB requirement for each of them and its own attributes. (Note: in this step, omit the relation BusinessFeature and omit all foreign key(s) in the relations). E.g., for each reviewer, Yelp.com needs to keep track of the unique reviewer ID, ... Step 2: Identify the two foreign keys in the relations Review and write out a DB requirement for each of them. E.g., each review must be submitted by reviewer Step 3: Write out the maximum and minimum cardinality constraints that are not reflected in the relational schema as additional DB requirements/assumptions. E.g., can a reviewer make more than one review? Must a reviewer submit at least one review? Hint: the relation BusinessFeature is created as an additional relation to depict the many-to-many relationship between Business and Feature. In Step 3, you can omit the relation BusinessFeature and write out the maximum and minimum cardinality constraints for the relationship between Business and Feature based on your own assumptions. E.g., can a business have multiple features (e.g., operation hours, payment methods, reservation options)? Must a feature be associated with at least one business