Management Information Systems - IoT Project
Bryce Rose
Q365C992
Project Part #3
Description: The company that I will use in this project is a fictional online marketplace for buying and reselling shoes. The company will employ 50 people and will include a management structure along with divisions for shipping/fulfillment, sales, cataloging and a small developing force to handle the online platform. The issue this company has is managing their sales pipeline from the customer purchasing shoes to the shoes getting delivered and also the process for people trying to list their shoes for consignment. That involves receiving the shoe shipment, checking for authenticity and cataloging, then making sure the shoes get delivered to the buyer thus completing the sales pipeline.
Event Table for Online Shoe Sales System:
|
ID |
Event |
System State |
System Response |
|
1 |
Purchase order received |
Online |
1. Send information to Authenticator to verify the shoe is available 2. Collect Payment Information and verify sale 3. Store Shipping Information for fulfillment services |
|
2 |
|
|
|
|
3 |
|
|
|
|
4 |
|
|
|
|
5 |
|
|
|
|
6 |
|
|
|
|
7 |
|
|
|
|
8 |
|
|
|
|
9 |
|
|
|
|
10 |
|
|
|
Business Events:
· Customer Purchase Order
· Customer Sell Order
· Customer Uses Database to Compare Prices
· Authenticator Sends Verified Shoe Information to Database (ex. Price, Color, Size)
· Authenticator Uses Database to Update Price Information
· Fulfillment Uses Database to Get Customer Information for Shipping
Temporal Events:
· Database compares prices of available shoes every 5 minutes to allow competitive offers from potential buyers
Signal Events:
· Database sends out information to Authenticators on if a shoe has been sold
· Database sends out fulfillment information once a shoe has been sold
·