Databases Reference
In-Depth Information
• Invoice
• Enterprise: Wholesale seller
• Who: A retail seller selecting products to be purchased
• What: A p urchase transaction of pallets of product delivered
via truck
• When: A truck delivers the pallets of product at an agreed date
and time.
• Where: A truck delivers the pallets of product to a receiving dock.
• How: A receiving clerk signs the invoice declaring the product
matches the line items of the invoice, which then obligates the
customer (i.e., the retail seller) to pay the price listed in the invoice.
• Manufactured Products during Second Shit
• Enterprise: Manufacturing plant
• Who: Laborers in the second shit
• What: he manufacture of inished goods
• When: A speciic date during the second shit
• Where: Inside the manufacturing plant
• How: Laborers assemble raw goods and assembly parts into in-
ished goods.
• Dinner in a Restaurant
• Enterprise: A restaurant
• Who: A customer selecting the menu items to be purchased
• What: A restaurant sales transaction
• When: he date and time when a customer visits the restaurant
• Where: All the selected menu items are prepared and presented
to the customer in the restaurant.
• How: he customer eats the prepared menu items and then pays
for them in one transaction.
In Market Basket Analysis, these bounded units of work are each an
Itemset. This discussion of Market Basket Analysis would bog down to
a repetitive and tedious discussion if each mention of an Itemset had to
include each of the above examples. For a g iven enterprise transaction,
the Itemset concept may apply, but not in the form of the examples listed
above. Therefore, all subsequent discussions of Itemsets as the analytic
focus of Market Basket Analysis will inherently assume we are discussing
a unit of work, bounded and complete in and of itself, which is relevant to
