search

G915-2-Data-Modeling-381 / Project-1-eStreamingMovies

Collaborate and use the best from each of the group member's individual project and create the modernized YourName-eStreamingMoviesSqlServer2019-yyyymmdd. Highlighting the individual's contributions for the best solution. Read the Project one Specification Read the Project plan
0 stars 0 forks source link

Individual Project comments #7

Closed adrianmnh closed 2 years ago

adrianmnh commented 2 years ago

Comment on individual group members' Conceptual, Logical and Physical models

adrianmnh commented 2 years ago

Provide constructive feedback on models per team member (Positives & Negatives) Suggest potential feature to be incorporated on project Submit work as an .md file or text comment on your issue

Oliver Vidal

− no model images uploaded

Amber Garcia

✓ Improved conceptual model with different payment methods ✓ Maintains most of the original eMovies model structure ✓ Use of user defined data types and domains ✓ Normalized tables − PaymentType on logical model not in Physical model, unable to link CustomerPaymentMethod to different payment methods, all use different PKs − MovieRental rate is an integer − Some tables do not have have a surrogate primary key

Jasmider Garcha

✓ Lots of subcategories add depth to the model ✓ Bitcoin as a payment method ✓ Grouping of customers and movie stars into one entity in conceptual model ✓ Subscription service added to conceptual model that can be used as a Streaming Hub ✓ Good use of data types for attributes on physical model ✓ Bridge table for Movie and Stars for multi-value "star" link to movie − Streaming Service multi tier subscription model can be reworked − Customer require 2 surrogate keys

Wade Li

✓ Addition of 3 different payment methods to model ✓ Addition of streaming option − Lack of depth and dimensions on logical and conceptual models − eStreams do not require a store, movie copies or employees − Attributes use unconstrained data types