Group 5, Case Analysis PPT, 7-Eleven.pptx

case analysis presentation

1. 7 Eleven

2. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

3. DigiForge’s Company Name:

4. Justification: Digital represents the core focus of the company on technology and innovation. Forge symbolizes the creation and crafting of solutions, highlighting the company's ability to build robust and effective IT systems. Together, DigiForge embodies the essence of our company. By fusing "digital" with "forge," we convey our dedication to crafting innovative technological solutions. This name reflects our commitment to delivering precise and efficient IT services that perfectly align with our clients' needs.

5. Target Retail Company Chosen Retail Company: 7-Eleven (Seven Eleven) Business Objectives: a. Optimize inventory management to reduce stockouts and excess inventory. b. Enhance sales analysis to identify product trends and customer preferences.Implement a customer loyalty program to foster customer retention and increase sales. c. Implement a customer loyalty program to foster customer retention and increase sales.

6. II. REQUIREMENTS ANALYSIS

7. Relationships 1. A customer can place multiple orders. 2. An order can contain multiple order items. 3. A product can be included in multiple orders. 4. Asale is associated with a customer and a salesperson. 5. An inventory record is associated with a product and a store. 6. A store manager manages a store.

8. III. LOGICAL DESIGN

9. 1. Entity-Relationship Diagram (ERD) This image depicts an Entity-Relationship (ER) diagram illustrating the conceptual design of a retail management system. The diagram visualizes the key entities involved in retail operations, such as customers, products, orders, employees, and stores, along with their attributes and relationships.

10. 2. Data Dictionary Creation This data dictionary serves as a reference to ensure consistency and accuracy in the database design. Table name: Customer

11. 2. Data Dictionary Creation Table name: Inventory

12. 7 Eleven

13. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

14. I. PRELIMINARY PHASE

15. 2. Data Dictionary Creation Table name: Store

16. 2. Data Dictionary Creation Table name: Employee

17. IV. Physical Design

18. IV. Physical Design The physical design phase involves translating the logical database structure into a specific implementation. This section presents the physical representation of the inventory table, a core component of the database system. By defining the table's structure, fields, and sample data, we establish a foundation for storing and managing inventory information effectively.

19. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

20. DigiForge’s Company Name:

21. Justification: Digital represents the core focus of the company on technology and innovation. Forge symbolizes the creation and crafting of solutions, highlighting the company's ability to build robust and effective IT systems. Together, DigiForge embodies the essence of our company. By fusing "digital" with "forge," we convey our dedication to crafting innovative technological solutions. This name reflects our commitment to delivering precise and efficient IT services that perfectly align with our clients' needs.

22. Target Retail Company Chosen Retail Company: 7-Eleven (Seven Eleven) Business Objectives: a. Optimize inventory management to reduce stockouts and excess inventory. b. Enhance sales analysis to identify product trends and customer preferences.Implement a customer loyalty program to foster customer retention and increase sales. c. Implement a customer loyalty program to foster customer retention and increase sales.

23. II. REQUIREMENTS ANALYSIS

24. Relationships 1. A customer can place multiple orders. 2. An order can contain multiple order items. 3. A product can be included in multiple orders. 4. Asale is associated with a customer and a salesperson. 5. An inventory record is associated with a product and a store. 6. A store manager manages a store.

25. III. LOGICAL DESIGN

26. 1. Entity-Relationship Diagram (ERD) This image depicts an Entity-Relationship (ER) diagram illustrating the conceptual design of a retail management system. The diagram visualizes the key entities involved in retail operations, such as customers, products, orders, employees, and stores, along with their attributes and relationships.

27. 2. Data Dictionary Creation This data dictionary serves as a reference to ensure consistency and accuracy in the database design. Table name: Customer

28. 2. Data Dictionary Creation Table name: Inventory

29. 7 Eleven

30. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

31. I. PRELIMINARY PHASE

32. 2. Data Dictionary Creation Table name: Store

33. 2. Data Dictionary Creation Table name: Employee

34. IV. Physical Design

35. IV. Physical Design The physical design phase involves translating the logical database structure into a specific implementation. This section presents the physical representation of the inventory table, a core component of the database system. By defining the table's structure, fields, and sample data, we establish a foundation for storing and managing inventory information effectively.

36. 1. Physical Database Structure - Sample Table: `Inventory` - Fields: `inventory_id` (int(12)), `product_id` (int(12)), `inv_quantity` (varchar(50)) - Sample Tuples: 1. (1, 1001, 'Coca-Cola 1.5L', ‘Beverages’, 25, 50.00) 2. (2, 1002, 'Chips (Classic)', ‘Snacks’, 30, 25.00) 3. (3, 1003, 'Sandwich (Tuna)', ‘Prepared Foods’, 15, 65.00) 4. (4, 1004, 'Battery (AA)', ‘General Merchandise’, 50, 20.00) 5. (5, 1004, 'Chocolate Bar', ‘Confectionery’, 40, 35.00)

37. 1. Physical Database Structure

38. Group 5 Group Leader: Alliah Nicole M. Tolentino Group Members: Lance Joseph R. Arceo Charity Mae DL. Estopil Daniel V. Manalo BSIT 3-H

39. 1. Physical Database Structure - Sample Table: `Inventory` - Fields: `inventory_id` (int(12)), `product_id` (int(12)), `inv_quantity` (varchar(50)) - Sample Tuples: 1. (1, 1001, 'Coca-Cola 1.5L', ‘Beverages’, 25, 50.00) 2. (2, 1002, 'Chips (Classic)', ‘Snacks’, 30, 25.00) 3. (3, 1003, 'Sandwich (Tuna)', ‘Prepared Foods’, 15, 65.00) 4. (4, 1004, 'Battery (AA)', ‘General Merchandise’, 50, 20.00) 5. (5, 1004, 'Chocolate Bar', ‘Confectionery’, 40, 35.00)

40. 1. Physical Database Structure

41. Group 5 Group Leader: Alliah Nicole M. Tolentino Group Members: Lance Joseph R. Arceo Charity Mae DL. Estopil Daniel V. Manalo BSIT 3-H

42. DigiForge’s Company Name:

43. Justification: Digital represents the core focus of the company on technology and innovation. Forge symbolizes the creation and crafting of solutions, highlighting the company's ability to build robust and effective IT systems. Together, DigiForge embodies the essence of our company. By fusing "digital" with "forge," we convey our dedication to crafting innovative technological solutions. This name reflects our commitment to delivering precise and efficient IT services that perfectly align with our clients' needs.

44. Target Retail Company Chosen Retail Company: 7-Eleven (Seven Eleven) Business Objectives: a. Optimize inventory management to reduce stockouts and excess inventory. b. Enhance sales analysis to identify product trends and customer preferences.Implement a customer loyalty program to foster customer retention and increase sales. c. Implement a customer loyalty program to foster customer retention and increase sales.

45. II. REQUIREMENTS ANALYSIS

46. Relationships 1. A customer can place multiple orders. 2. An order can contain multiple order items. 3. A product can be included in multiple orders. 4. Asale is associated with a customer and a salesperson. 5. An inventory record is associated with a product and a store. 6. A store manager manages a store.

47. III. LOGICAL DESIGN

48. 1. Entity-Relationship Diagram (ERD) This image depicts an Entity-Relationship (ER) diagram illustrating the conceptual design of a retail management system. The diagram visualizes the key entities involved in retail operations, such as customers, products, orders, employees, and stores, along with their attributes and relationships.

49. 2. Data Dictionary Creation This data dictionary serves as a reference to ensure consistency and accuracy in the database design. Table name: Customer

50. 2. Data Dictionary Creation Table name: Inventory

51. 7 Eleven

52. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

53. I. PRELIMINARY PHASE

54. 2. Data Dictionary Creation Table name: Store

55. 2. Data Dictionary Creation Table name: Employee

56. IV. Physical Design

57. IV. Physical Design The physical design phase involves translating the logical database structure into a specific implementation. This section presents the physical representation of the inventory table, a core component of the database system. By defining the table's structure, fields, and sample data, we establish a foundation for storing and managing inventory information effectively.

58. 1. Physical Database Structure - Sample Table: `Inventory` - Fields: `inventory_id` (int(12)), `product_id` (int(12)), `inv_quantity` (varchar(50)) - Sample Tuples: 1. (1, 1001, 'Coca-Cola 1.5L', ‘Beverages’, 25, 50.00) 2. (2, 1002, 'Chips (Classic)', ‘Snacks’, 30, 25.00) 3. (3, 1003, 'Sandwich (Tuna)', ‘Prepared Foods’, 15, 65.00) 4. (4, 1004, 'Battery (AA)', ‘General Merchandise’, 50, 20.00) 5. (5, 1004, 'Chocolate Bar', ‘Confectionery’, 40, 35.00)

59. 1. Physical Database Structure

60. Group 5 Group Leader: Alliah Nicole M. Tolentino Group Members: Lance Joseph R. Arceo Charity Mae DL. Estopil Daniel V. Manalo BSIT 3-H

61. I. PRELIMINARY PHASE

62. DigiForge’s Company Name:

63. Justification: Digital represents the core focus of the company on technology and innovation. Forge symbolizes the creation and crafting of solutions, highlighting the company's ability to build robust and effective IT systems. Together, DigiForge embodies the essence of our company. By fusing "digital" with "forge," we convey our dedication to crafting innovative technological solutions. This name reflects our commitment to delivering precise and efficient IT services that perfectly align with our clients' needs.

64. Target Retail Company Chosen Retail Company: 7-Eleven (Seven Eleven) Business Objectives: a. Optimize inventory management to reduce stockouts and excess inventory. b. Enhance sales analysis to identify product trends and customer preferences.Implement a customer loyalty program to foster customer retention and increase sales. c. Implement a customer loyalty program to foster customer retention and increase sales.

65. Justification: 7-Eleven , as a global convenience store leader, possesses a vast customer base and a diverse product range. Optimizing inventory management and extracting actionable insights from customer data is pivotal to sustaining its market dominance. Our database solution can empower 7-Eleven to achieve unprecedented levels of efficiency, profitability, and customer satisfaction. a. Optimize inventory management to reduce stockouts and excess inventory. b. Enhance sales analysis to identify product trends and customer preferences. c. Implement a customer loyalty program to foster customer retention and increase sales.

66. II. REQUIREMENTS ANALYSIS

67. 1. Stakeholder Identification a. Management: Responsible for overall business strategy and financial performance. b. Store Managers: Oversee daily operations, inventory management, and customer service. c. Sales Department: Handles customer transactions and product sales. d. Marketing Department: Responsible for promotions, advertising, and customer loyalty programs. e. IT Department: Manages the company's technology infrastructure and systems.

68. 2. Requirement Gathering Understanding the information needs of each department is crucial for designing an effective information system. This section outlines the specific data requirements of Management, Store Managers, Sales Department, and Marketing Department. By analyzing these needs, we can identify essential data entities, attributes, and relationships to form the foundation for a robust and informative system.

69. 1. Management a. Comprehensive sales reports: Overall sales performance, sales by product, sales by region, sales by time period. b. Inventory turnover analysis: Rate at which inventory is sold and replaced, identifying slow-moving and fast-moving items. c. Customer demographics: Customer age, gender, location, purchasing behavior.

70. 2. Store Managers a. Real-time inventory data: Product availability, stock levels, reorder points. b. Sales performance metrics: Sales by product, sales by employee, sales by day/week/month. c. Efficient product ordering processes: Product demand forecasting, supplier information, order history.

71. 3. Sales Department a. Customer information: Contact details, purchase history, preferences, order status. b. Product information: Product details, pricing, availability. c. Sales performance metrics: Individual sales, team sales, commission calculations.

72. 4. Marketing Department a. Customer purchase history: Products purchased, purchase frequency, spending patterns. b. Customer preferences: Product preferences, brand loyalty, customer segmentation. c. Customer demographics: Customer age, gender, location, income.

73. 5. IT Department a. Customer purchase history: Products purchased, purchase frequency, spending patterns. b. Customer preferences: Product preferences, brand loyalty, customer segmentation. c. Customer demographics: Customer age, gender, location, income.

74. Data Entities and Attributes Based on these requirements, we can identify potential data entities and their attributes: 1. Customer: customer_id, name, contact_info, demographics, purchase_history, preferences 2. Product: product_id, name, description, price, category, inventory_level 3. Order: order_id, order_date, customer_id, order_totalprice, order_quantity 4. Order_Item: order_item_id, order_id, product_id, order_quantity, price 5. Sales: sale_id, sale_date, salesperson_id, customer_id, total_amount 6. Inventory: inventory_id, product_id, inv_quantity, reorder_point 7. Store: store_id, location, manager_id 8. Employee: employee_id, name, role, store_id

75. Relationships 1. A customer can place multiple orders. 2. An order can contain multiple order items. 3. A product can be included in multiple orders. 4. Asale is associated with a customer and a salesperson. 5. An inventory record is associated with a product and a store. 6. A store manager manages a store.

76. III. LOGICAL DESIGN

77. 1. Entity-Relationship Diagram (ERD)

78. 1. Entity-Relationship Diagram (ERD) This image depicts an Entity-Relationship (ER) diagram illustrating the conceptual design of a retail management system. The diagram visualizes the key entities involved in retail operations, such as customers, products, orders, employees, and stores, along with their attributes and relationships.

79. 2. Data Dictionary Creation This data dictionary serves as a reference to ensure consistency and accuracy in the database design. Table name: Customer

80. 2. Data Dictionary Creation Table name: Product

81. 2. Data Dictionary Creation Table name: Order

82. 2. Data Dictionary Creation Table name: Order_Item

83. 2. Data Dictionary Creation Table name: Sales

84. 2. Data Dictionary Creation Table name: Inventory

85. 7 Eleven

86. Database Life Cycle (DBLC) for 7-Eleven's Retail Management System as a Benchmark for DigiForge's Retail Operations Case Analysis IT IM-01 | Advanced Database Systems

87. I. PRELIMINARY PHASE

88. 2. Data Dictionary Creation Table name: Store

89. 2. Data Dictionary Creation Table name: Employee

90. IV. Physical Design

91. IV. Physical Design The physical design phase involves translating the logical database structure into a specific implementation. This section presents the physical representation of the inventory table, a core component of the database system. By defining the table's structure, fields, and sample data, we establish a foundation for storing and managing inventory information effectively.

92. 1. Physical Database Structure - Sample Table: `Inventory` - Fields: `inventory_id` (int(12)), `product_id` (int(12)), `inv_quantity` (varchar(50)) - Sample Tuples: 1. (1, 1001, 'Coca-Cola 1.5L', ‘Beverages’, 25, 50.00) 2. (2, 1002, 'Chips (Classic)', ‘Snacks’, 30, 25.00) 3. (3, 1003, 'Sandwich (Tuna)', ‘Prepared Foods’, 15, 65.00) 4. (4, 1004, 'Battery (AA)', ‘General Merchandise’, 50, 20.00) 5. (5, 1004, 'Chocolate Bar', ‘Confectionery’, 40, 35.00)

93. 1. Physical Database Structure

94. Group 5 Group Leader: Alliah Nicole M. Tolentino Group Members: Lance Joseph R. Arceo Charity Mae DL. Estopil Daniel V. Manalo BSIT 3-H

95. 2. Data Dictionary Creation Table name: Store

96. 2. Data Dictionary Creation Table name: Employee

97. IV. Physical Design

98. IV. Physical Design The physical design phase involves translating the logical database structure into a specific implementation. This section presents the physical representation of the inventory table, a core component of the database system. By defining the table's structure, fields, and sample data, we establish a foundation for storing and managing inventory information effectively.

99. 1. Physical Database Structure - Sample Table: `Inventory` - Fields: `inventory_id` (int(12)), `product_id` (int(12)), `inv_quantity` (varchar(50)) - Sample Tuples: 1. (1, 1001, 'Coca-Cola 1.5L', ‘Beverages’, 25, 50.00) 2. (2, 1002, 'Chips (Classic)', ‘Snacks’, 30, 25.00) 3. (3, 1003, 'Sandwich (Tuna)', ‘Prepared Foods’, 15, 65.00) 4. (4, 1004, 'Battery (AA)', ‘General Merchandise’, 50, 20.00) 5. (5, 1004, 'Chocolate Bar', ‘Confectionery’, 40, 35.00)

100. 1. Physical Database Structure

101. Group 5 Group Leader: Alliah Nicole M. Tolentino Group Members: Lance Joseph R. Arceo Charity Mae DL. Estopil Daniel V. Manalo BSIT 3-H

102. Thank You For Listening!