SOFTWARE DESIGN SPECIFICATION

3.2.1 Introduction 3.2.1.1 Goals and Objective Developing the software is an attempt to make the process effective, simple and efficient. The software can perform operations like monitoring the Stock / Item available in Selling Area, because efficient stock control allows you to have the right amount of stock in the right place at the right time, monitor the fast and slow moving products in store and has a warning notification for expired and critical item so there is no need for manual checking of items in store. It provides reports for the availability of stocked items within the store, so that the inventory would be effective and helps to avoid having an out of stock and missing products. 3.2.1.2 Statement of Scope The software allows registering new users accessible by admin, inputting the quantity of products before displaying in selling area, monitoring of products. The software allows generate reports indicated in outputs. Major Inputs Quantity per piece Quantity per pack Date Receive Pull out Date Product loss Date Processing Functionalities Function Priority

Add receive item

Outputs Fast and slow moving product report, Critical Item report, Summary product report, Report for expired products, Pull out or change product report, Sales report for check and balance, consigners report. 3.2.1.3 Software context The software is integrated with other sub-system. In this software the proponents use Java programming language and MySql for the database connectivity. 3.2.1.4 Major constraints The software is to run on a system, with SQL, Therefore the system should be properly connected to server to access database. 3.2.2 Data Design To understand the data design of store inventory control system its important to have a look at the overall design of the application it completely define the application's data characteristics and processes. As the application build in Java, MySql and JDBC. Front end and GUI Back End Data 3.2.2.1 Internal Software Data Structure 3.2.2.2 Global Data Structure

The data available globally to the whole system is the database itself stored in MySql. After the JDBC connection any data stored can be fetched, updated, or deleted. 3.2.2.3 Temporary Data Structure There are no temporary files in the software because data is being stored in DBM system all the data are being stored by the DBMS until the command commit is being executed in the SQL query by the application. 3.2.2.4 Database Description Below are the list of all tables, their corresponding attributes and meaning of each. Table Name: Product_Table Attributes: prod_id, prod_name, prod_cat, prod_subcat, prod_qtyperpack,

prod_qtyperpiece, prod_expdate, prod_maxlevel, prod_reorderlevel, prod_srp, prod_fsp, prod_location, prod_barcode, skucode, prod_type, prod_description. Description: It holds all the information of the products of store inventory. Primary key of this table is prod_id. Table Name: Consigner_Table Attributes: prod_id, prod_name, prod_cat, prod_expdate, prod_maxlevel, prod_srp, prod_fsp, prod_location, prod_description. Description: It holds all the information of consigner products of store inventory. Primary key of this table is prod_id. Table Name: Pullout_Table Attributes: prod_id, prod_name, prod_cat, prod_subcat, prod_qtyperpack,

prod_qtyperpiece, prod_expdate, prod_maxlevel, prod_reorderlevel, prod_srp, prod_fsp,

prod_location, prod_barcode, skucode, prod_type, prod_description. pullout_date, comment. Description: It holds all the information of pullout products of store inventory. Primary key of this table is prod_id. Table Name: Prodloss_Table Attributes: prod_id, prod_name, prod_cat, prod_subcat, prod_qtyperpack,

prod_qtyperpiece, prod_expdate, prod_maxlevel, prod_reorderlevel, prod_srp, prod_fsp, prod_location, prod_barcode, skucode, prod_type, prod_description. loss_date, loss_num. Description: It holds all the information of loss products of store inventory. Primary key of this table is prod_id. Table Name: History_Table Attributes: user_id, username, position, date, prod_name, prod_cat, prod_subcat, prod_qtyperpack, prod_qtyperpiece, prod_expdate, prod_maxlevel, prod_reorderlevel, prod_srp, prod_fsp, prod_location, prod_barcode, skucode, prod_type, prod_description. pullout_date, comment. Description: It holds all the history information of store inventory. Table Name: Transaction_Table Attributes: user_id, username, prod_name, prod_cat, prod_subcat, prod_qtyperpack, prod_qtyperpiece, prod_location, prod_description. Description: It holds all the information of transaction of store inventory. Primary key of this table is (User_id).

3.2.3 Architectural and Component level Design 3.2.3.1 Architectural Diagram

The architectural diagram for the software is shown below. As it is clear from the diagram, various actors are admin and inventory staff which uses the system. The subordinate systems that will be used by the software are the database (MySql) and Java. Also JDBC driver is required to connect java to database. Data Maintenance is for testing and maintenance purposes.

Data Maintenance

Uses

Admin

Store Inventory Control System

Inventory Staff
Uses

Java and JDBC Drivers

Database (MySql)

Main Store Inventory Control System software executive User information

External Staff Management

Add/Modify New User information

Monitor Fast, Slow, Critical, Expired products

Print or Display reports

Inventory Staff information

Product information

Graphical User Interface

Inventory Staff Sign in and sign out

3.2.3.2 Description of Components 3.2.3.2.1 Component Parent ` 3.2.3.2.2 Component Employee 3.2.3.2.3 Component Child 3.2.3.2.4 Component Teacher 3.2.3.2.5 Component Admin staff

3.2.3.2.6 Component Manager 3.2.3.2.7 Component Reports 3.2.3.3 Dynamic Behavior for component 3.2.3.4 Interaction Diagram 3.2.4 User Interface Design 3.2.4.1 Description of the User Interface 3.2.4.2 Interface Design rules 3.2.4.3 Components Available 3.2.4.4 UIDS Description 3.2.5 Restrictions, Limitations and Constraints 3.2.6 Testing Issues