PROG8651-FALL 2023-SECTION 3-Lakshay Bhati (1)

pdf

School

Conestoga College *

*We aren’t endorsed by this school

Course

8750

Subject

Computer Science

Date

Feb 20, 2024

Type

pdf

Pages

4

Uploaded by MasterWallabyPerson940

Report
Date: 6 th October 2023 Course: PROG8651 Name: Lakshay Bhati College Name: Conestoga College Program Code: 1372 Course Code: PROG8651 Course: Information Technology Business Analysis Course Section: Section 3 Assignment Title: Task 2 – Functional Dependencies (A) Student Name: Lakshay Bhati Date: October 6, 2023
Date: 6 th October 2023 Course: PROG8651 Name: Lakshay Bhati SECTION - A 1. Functional dependencies for the CustomerOrder table (OrderID, PaymentID) → (Tax, SubTotal, TotalPaid, DatePaid) (OrderID,OrderStatusID) → (EstDateShipped,ActualDateShipped) (Tax, SubTotal) → TotalPaid (OrderID) → (CustomerID,PaymentID,OrderStatusID,ShipmentMethodID,ShippingAddressID,DateModified) (ShippingAddressID, OrderID, CustomerID) → EstDateShipped (ShippingAddressID, OrderID, CustomerID) → ActualDateShipped 2. Primary key(s), foreign key(s) and candidate key(s) for the CustomerOrder table are as follows: OrderID → Primary Key and Candidate key OrderStatusID → Foreign Key, referencing the primary key of the table Order Status ShipmentMethodID → Foreign Key, referencing the primary key of the table Shipment Method PaymentID → Foreign Key, referencing the primary key of the payment table. ShippingAddressID → Foreign Key, referencing the primary key of ShippingAddress table. CustomerID → Foreign Key, referencing the primary key of customer information. OrderID,PaymentID→Candidate Key 3. Multivalued dependencies within the CustomerOrder table are: Attribute -> Attribute CustomerID -> PaymentID CustomerID -> OrderID ShippingAddressID-> CustomerID ShippingAddressID-> OrderID 4. Transform the CustomerOrder entity [table] into the 4th Normal Form utilizing the following format: CustomerOrder(OrderID ,CustomerID,PaymentID,OrderStatusID,ShipmentMethodID,Shipment AdressI D,DateModified) Shipment (ShippingAdressID, OrderID, CustomerID, EstDateShipped, ActualDateShipped) Payments(PaymentID,SubTotal,Tax,TotalPaid,DatePaid) Customer(CustomerID, OrderID )
Date: 6 th October 2023 Course: PROG8651 Name: Lakshay Bhati SECTION – B 1. If you were to take on the task of updating the organization database, and enforcing the entity [table] structure changes you indicated in the previous question (s), what questions would you want to ask the resident Database Administrator, or Business Manager, for clarification? Keep the following concepts in mind while drafting your questions: Ans: To ensure an amazing transition and meet the organization's demand, it's important to gain each piece of information, The questions I want to ask to a resident Database Administrator or Business Manager are as follows: Questions (Scope) 1. What are the major goals we are trying to achieve with the updating of this database? 2. Do The tables we are enforcing, have any relationship with the dependencies that we should know? 3. What benefits will we achieve after updating the organization database and enforcing the entity table structure? Questions (Audience ) 1. What is the perspective of the sales manager on the database and its implications on business processes? 2. The database administrator meet our technical requirements or not? 3. What data do you currently track for each customer order? Questions (Language) 1. Are there any rules and regulations, that should be followed to handle the records in the entity format? 2.. Is there any document design or basic format to handle database updates? 3. Will there be any language barriers, while communicating with the stakeholders regarding the changes? 2. Identify at least two (2) potential issues found within any of the 4 tables of the Orders schema (CustomerOrder, ShipmentMethod, OrderStatus, ProductSelection). Be sure to clearly state what the issue is and how you would address these issues . Ans: The potential issues found within any of the 4 tables of the Orders schema are: Issue 1 (CustomerOrder ): Necessary for key fields to uniquely differentiate each other. Addressing : Having a modern key, makes it different and creates strides in data honesty. Issue 2 (ShipmentMethod ): Stolen information with respect to shipment methods. Addressing : Analysing all shipment methods strategies is found within the table.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Date: 6 th October 2023 Course: PROG8651 Name: Lakshay Bhati Issue 3(OrderStatus Table ): Unnecessary statuses that are not applicable. Addressing : Removing all the statuses that are repeated and maintaining them in a precise manner. Issue 4(ProductSelection Table ): Squabble data passages for item selection in orders. Addressing: Add restrictions or review to avoid disagreement or incorrect information from being included in the table.