CS4760 Team 5: 5upply Lads Database Schema

Our application does not require the use of a database. Rather, we will be using a JavaScript data store to track the configurations that are entered by the User. The data stored by the application depends on the types of nodes that the user configures. Here is the breakdown of such data:

Supply Node

• rate: <integer>( the amount of product produced (per ‘tick’). Once this value is configured, it cannot be changed on a per supply node basis )
• speed: <integer> ( the amount of ‘ticks’ it takes for a product to travel from a supply node to any other node)

Demand Node

• rate: <integer> (the amount of product demanded (per ‘tick’). Once this value is configured, it cannot be changed on a per demand node basis)

Distribution Node

• rate: <integer> (the amount of product shipped (per ‘tick’). Once this value is configured, it cannot be changed on a per distribution node basis)
• speed: <integer> (the amount of ‘ticks’ it takes for a product to travel from a distribution node to any other node)

When the user runs the simulation, they will receive information about each of the four factors defined in our updated app description. The information will be stored / displayed as follows:

Budget

• cost: <Number> (the total cost of supporting all supply / distribution nodes) (costs are configured by the application and shown to the user (aka, the user cannot change how much a distribution node costs))

Environmental Impact

• emissions: <Number> (the total amount (in parts per million by volume) of CO2 emissions produced by supply and distribution nodes) (emissions are configured / calculated by the application and shown to the user (aka, the user cannot change how much emissions are given by a supply / distribution node))

Supply

• amount: <Number> (the total amount of supply of product available. Determined by the number of supply nodes configured on the map)

Demand

• amount: <Number> (the total amount of product that is being demanded at the point the simulation is stopped. Determined by the number of demand nodes configured on the map)