Final Close is a 3 year old company that developed an e-store platform. Their platform allows their brick-and-mortar clients do e-commerce through e-stores and virtual storefronts. What the company developed is more than just a brick-to-click solution. Their framework has automation in place that responds immediate to changes in each client's partnerships and offerings. To achieve this, Final Close builds integrations between their platform and their clients' business management systems. This allows their platform's data be synchronization to their clients' every 24 hours.

Instructions

Complete all the steps. Paste in the document only the work that's requested. When submitting your images make sure you show the complete information along with your name and student number.

E-Store Database Design

 

System Diagram

 

1. Use a drafting or visual modeling tool of your choice
2. Draw the operational system based on diagram examples in the previous steps
3. Add the arrows between your operational system components that best describe the system's behaviour. Label each arrow with at most three words.
4. Repeat steps (ii) and (iii) for the data warehouse system.
5. Repeat steps (ii) and (iii) for the business intelligence system.
6. Add the arrows between the operational, data warehouse, and business intelligence system components that best explains their interactions. Label each arrow with at most three words.
7. Add a separate component called Client to represent customers' systems. Add arrows to and from Client describing how the three systems could interact with that component. Use what you know about Final Close as a guide.
8. Add your name and student number at the bottom left corner of your diagram.

P EntityID F NUMBER (10) VARCHAR2 (20) Company FirstName VARCHAR2 (20) LastName VARCHAR2 (20) OwnerlD NUMBER (10) P AddressID City Province Postal Code ENTITY ApartmentNumber StreetNumber StreetName F* EntityID F CustomerlD ADDRESS P CustomerlD FirstName LastName UserName CUSTOMER NUMBER (10) VARCHAR2 (10) VARCHAR2 (10) VARCHAR2 (30) VARCHAR2 (30) CHAR (3) CHAR (7) NUMBER (10) NUMBER (10) NUMBER (10) VARCHAR2 (20) VARCHAR2 (20) VARCHAR2 (30) ENTITY_PARTNERSHIP_INT * EntityPartnership IntlD F EntityID F PartnershipID PRODUCT P ProductID ProductName Listed Price F EntityID NUMBER (10) NUMBER (10) NUMBER (10) NUMBER (10) VARCHAR2 (20) NUMBER (5,2) NUMBER (10) PARTNERSHIP IP * PartnershipID InitiatedDate DATE TerminationDate DATE OFFERING OfferingID ValidDate OfferedPrice PartnershipID NUMBER (10) F F ProductID NUMBER (10) DATE NUMBER (5,2) NUMBER (10) NUMBER (10) P PurchaselD Purchase Date Purchase Price OfferingID CustomerlD FE_StorelD F F PURCHASE R E_STORE PE_StorelD StoreName Location Code URL F PartnershipID NUMBER (10) DATE NUMBER (5,2) NUMBER (10) NUMBER (10) NUMBER (10) NUMBER (10) VARCHAR2 (20) CHAR (5) VARCHAR2 (255) NUMBER (10)