Inventory Management

System

Arina Ramlee, Bruce Chhay, David Henry

Operational Concepts
 Real-time inventory management
 Provides notification of low stock to managers
 Helps ensure that popular items remain in
stock
 Does not automate restocking
 Does not interpret sales data
Additional Features
 Automatically email stock updates
 Records sales data for export
 Full POS integration
System Requirements
 Database server (MySQL)
 Web server (Tomcat)
 Emulating cash registers (JavaPOS)
Architecture
 Client-Server (2 different clients)
 All data at the server
 Emulated Cash Register Client
 Stock Manager Client web interface
Architecture (cont.)

Database
(MySQL) RMI / HTTPS
Cash Register Client

JDBC Connector / J Web RMI / HTTPS

Server Cash Register Client

(Tomcat) RMI / HTTPS

RMI / HTTPS Cash Register Client

Stock Manager Client

Stakeholders
 Consumers
 Ensures consistent availability
 Stock manager
 Efficiency
 Small stores use single PC or internal network
 Regional franchise uses multiple client
locations connecting to a single server
Schedule
 2 weeks: Design and Core Features
 5 weeks: Testing and Additional Features
 Spiral model
 Prototype
 Beta
 Release
 Each feature is an independent task
Feasibility Rationale
 Emulation of cash registers
 Trusting SSL for encryption

 Loss of connection to server

 Relies on following a restocking procedure
 Theft breaks synchronization between the
inventory and the database
 Similar Products