Eip Diagrams

EIP Diagrams:

Customer Order[pic 1]

Above is the EIP diagram that demonstrates the flow of message when an order is received form a customer. First, the message, which may contain more than one type of product, will be split by a splitter, that the order will be fragmented into small parts by products. Then, the messages will be routed with a content based router, which is helped by a process manager that accesses inventory data from a database. For orders that contains products that’s out of stock, the system notifies the customer and ask them if he/she still want the remaining items that are available.  For ones that are available and the customer wants it, the order message goes to the next stage, the aggregator. The aggregator reassembles the fragmented message and immediately report to the data storage to mark the stock level, recall that the data is used when checking inventory. After a complete message is formed, it’s broadcasted to the shipment ordering system and the customer as invoice.

Shipment order:[pic 2]

After confirming order from customer, the retailer has to request shipment service from the shipping company. The retailer doesn’t have to request shipment every time an order is made, instead, it requests shipment per day. First, the orders are aggregated and filtered out the unnecessary information, only keeping address and name, which are needed. When the combined shipment info for the day is compiled, it’s sent to the shipper. With a splitter, the shipment info is slit according to the address, then they are routed to the departments that handles shipment to those areas, with a content based router. After the package for the customers is dispatched, a message is sent to respective customer by using a content based router. Afterwards, the information from different departments are combined into a report with an aggregator and then send back to the retailer.