inventory management system
The main goal of Inventory Management System is to ensure consistent availability of supplies for consumers. Thus, Inventory Management System is directed toward owners of small to large stores and stock managers who are responsible of maintaining sufficient goods on hand in a retail or manufacturing business. It can scale from a single computer running both client and server software up to multiple stores and warehouses.
4.2 Schedules The time estimated to complete the Inventory Management System project is fairly short. There will be three major Win-Win Spiral Model cycles through our prototyping stage, beta release, and final release. We will need two weeks of designing the architecture and implementing core features and five weeks of adding functionality and testing. The project can be completed by 6-8 people in at most 7 weeks.
5. Feasibility Rationale
5.1 Assumptions
The above design should works for the Inventory Management System application. However, we are emulating a cash registers interface to work with our software by simulating barcode inputs. A more realistic design of cash register interface can be done to suit the integration, as the interface does not interfere with the data collected. We expect that the cash registers clients are able to update their data to the current point of sale in case of loss of connection to the server. The particular restocking procedure adopted by each store does interfere with the feasibility and accuracy of the application as it does not remind the stock manager to update the data each time they had done any restocking. We also trust that that the Secure Socket Layer (SSL) is reliable in creating a secure connection between a client and a server.
5.2 Risks
One of the major risks covered by this application is theft breaks synchronization between the inventory and the database. The information could be generated by the data stored in this application. The confidence level of trusting
4.2 Schedules The time estimated to complete the Inventory Management System project is fairly short. There will be three major Win-Win Spiral Model cycles through our prototyping stage, beta release, and final release. We will need two weeks of designing the architecture and implementing core features and five weeks of adding functionality and testing. The project can be completed by 6-8 people in at most 7 weeks.
5. Feasibility Rationale
5.1 Assumptions
The above design should works for the Inventory Management System application. However, we are emulating a cash registers interface to work with our software by simulating barcode inputs. A more realistic design of cash register interface can be done to suit the integration, as the interface does not interfere with the data collected. We expect that the cash registers clients are able to update their data to the current point of sale in case of loss of connection to the server. The particular restocking procedure adopted by each store does interfere with the feasibility and accuracy of the application as it does not remind the stock manager to update the data each time they had done any restocking. We also trust that that the Secure Socket Layer (SSL) is reliable in creating a secure connection between a client and a server.
5.2 Risks
One of the major risks covered by this application is theft breaks synchronization between the inventory and the database. The information could be generated by the data stored in this application. The confidence level of trusting