I need some help with this Java project.. It freaks me out... Can any one help m
ID: 3570334 • Letter: I
Question
I need some help with this Java project.. It freaks me out... Can any one help me??? I'll appreciate a lot!You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
widget1 will have a price (i.e. selling price vs buying cost above) that is 2 x cost as well as a color (orange or blue) that is a string.
widget2 will have a price that is 3 x cost as well as a weight that is an int, either 20lbs or 50lbs.
widget3 will have a price that is 4 x cost as well as a serial number (unrelated to stock number) that is a string.
The main menu will contain the following:
1. add inventory
2. ship inventory
3. inquire inventory
4. quit
Both add and ship will use bulk numbers (i.e. no one will buy 1 of widget2...more like 20-100). Since the floor manager is intelligent you don't have to add in checks on the menu items (he won't enter -732 for instance).
But, when he chooses ship inventory, he needs to know that the product is available. For example, if he needs 80 of widget1 in orange...he should have inquired that it is available...if not, he needs to add (same as order here for simplicity) more...then ship.
In each case a class-level number (or two, depending on implementation) is needed to keep up with stock and it can be added to or subtracted from as new objects are added or deleted.
You can assume when ordering products, they are the same. For example, an order of 50 widget2 (30 of 20lbs and 20 of 50lbs) will be processed as two orders to make it easier as far as methods and such.
Please include comments. I need some help with this Java project.. It freaks me out... Can any one help me??? I'll appreciate a lot!
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
widget1 will have a price (i.e. selling price vs buying cost above) that is 2 x cost as well as a color (orange or blue) that is a string.
widget2 will have a price that is 3 x cost as well as a weight that is an int, either 20lbs or 50lbs.
widget3 will have a price that is 4 x cost as well as a serial number (unrelated to stock number) that is a string.
The main menu will contain the following:
1. add inventory
2. ship inventory
3. inquire inventory
4. quit
Both add and ship will use bulk numbers (i.e. no one will buy 1 of widget2...more like 20-100). Since the floor manager is intelligent you don't have to add in checks on the menu items (he won't enter -732 for instance).
But, when he chooses ship inventory, he needs to know that the product is available. For example, if he needs 80 of widget1 in orange...he should have inquired that it is available...if not, he needs to add (same as order here for simplicity) more...then ship.
In each case a class-level number (or two, depending on implementation) is needed to keep up with stock and it can be added to or subtracted from as new objects are added or deleted.
You can assume when ordering products, they are the same. For example, an order of 50 widget2 (30 of 20lbs and 20 of 50lbs) will be processed as two orders to make it easier as far as methods and such.
Please include comments.
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
widget1 will have a price (i.e. selling price vs buying cost above) that is 2 x cost as well as a color (orange or blue) that is a string.
widget2 will have a price that is 3 x cost as well as a weight that is an int, either 20lbs or 50lbs.
widget3 will have a price that is 4 x cost as well as a serial number (unrelated to stock number) that is a string.
The main menu will contain the following:
1. add inventory
2. ship inventory
3. inquire inventory
4. quit
Both add and ship will use bulk numbers (i.e. no one will buy 1 of widget2...more like 20-100). Since the floor manager is intelligent you don't have to add in checks on the menu items (he won't enter -732 for instance).
But, when he chooses ship inventory, he needs to know that the product is available. For example, if he needs 80 of widget1 in orange...he should have inquired that it is available...if not, he needs to add (same as order here for simplicity) more...then ship.
In each case a class-level number (or two, depending on implementation) is needed to keep up with stock and it can be added to or subtracted from as new objects are added or deleted.
You can assume when ordering products, they are the same. For example, an order of 50 widget2 (30 of 20lbs and 20 of 50lbs) will be processed as two orders to make it easier as far as methods and such.
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
widget1 will have a price (i.e. selling price vs buying cost above) that is 2 x cost as well as a color (orange or blue) that is a string.
widget2 will have a price that is 3 x cost as well as a weight that is an int, either 20lbs or 50lbs.
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
widget1 will have a price (i.e. selling price vs buying cost above) that is 2 x cost as well as a color (orange or blue) that is a string.
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
Every widget will have a stock number and a cost (hint: that's the base class)
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The warehouse will stock three products: widget1, widget2, widget3.
You will design an inventory system for a warehouse (imagine the floor manager with a computer running the application).
The main menu will contain the following:
1. add inventory
2. ship inventory
3. inquire inventory
4. quit
Both add and ship will use bulk numbers (i.e. no one will buy 1 of widget2...more like 20-100). Since the floor manager is intelligent you don't have to add in checks on the menu items (he won't enter -732 for instance).
But, when he chooses ship inventory, he needs to know that the product is available. For example, if he needs 80 of widget1 in orange...he should have inquired that it is available...if not, he needs to add (same as order here for simplicity) more...then ship.
In each case a class-level number (or two, depending on implementation) is needed to keep up with stock and it can be added to or subtracted from as new objects are added or deleted.
You can assume when ordering products, they are the same. For example, an order of 50 widget2 (30 of 20lbs and 20 of 50lbs) will be processed as two orders to make it easier as far as methods and such.
The main menu will contain the following:
1. add inventory
2. ship inventory
3. inquire inventory
4. quit
Both add and ship will use bulk numbers (i.e. no one will buy 1 of widget2...more like 20-100). Since the floor manager is intelligent you don't have to add in checks on the menu items (he won't enter -732 for instance).
But, when he chooses ship inventory, he needs to know that the product is available. For example, if he needs 80 of widget1 in orange...he should have inquired that it is available...if not, he needs to add (same as order here for simplicity) more...then ship.
In each case a class-level number (or two, depending on implementation) is needed to keep up with stock and it can be added to or subtracted from as new objects are added or deleted.
You can assume when ordering products, they are the same. For example, an order of 50 widget2 (30 of 20lbs and 20 of 50lbs) will be processed as two orders to make it easier as far as methods and such.
Please include comments.
Explanation / Answer
contact on timacs12@gmail.com