3.2 Software Design Specification Document 3.2.1. INTRODUCTION 3.2.1.

1 Goals and Objectives A certain product is not as simple as it is. At customers view, there will only be 2 significant factors that matters most: (1) the brand name and (2) the price. However, if one may be given a chance to enter the world of merchandising, he or she would not be satisfied at all for having that two simple data on hand. Although these two data are indispensable for everyones mind (customer or client) most especially for those people covered inside the circle of merchandising and/or marketing firm (employees). Because for every employee inside the supermarket, it is very important to know and to learn on how to classify various merchandise. On what category does a certain product belongs. Where it is located? What are the available brands? Is there any other stock of that certain product? Is it imported? Is it fresh? Then, all of those questions are answerable by having a reliable, accurate, secured and organized stock of information. And it can only be possible by having a simple computer system installed with a stock-keeping unit oriented program. As it offers its various functionalities such as: (1) organizing product information at its utmost way (2) generate SKU codes and barcodes for product coding purposes (3) generating significant reports - list of available products/merchandise, list of outdated products, list of merchandise suppliers, list of merchandise manufacturers, list of merchandise groups and classifications, list of merchandise categories, list of merchandise with stockkeeping unit codes, list of system users and user profile reports, business notes log reports, list of updated merchandise, etc. (4) retrieving product information for less than a minute (5) secures the firm, the user, the customer and the product.

3.2.1.2 Statement of Scope The SKU system will give an emphasis on how to accommodate and organize myriad products available inside the market. As the software goes, there will be an engine that will classify or categorize a certain product in order to meet the market standard of having Food Divisions. Afterwards, it will be possible to easily sort and retrieve product information. And the most efficient part will be the report generation needed by the management.

Major Inputs: Class Products Group Inputs Product Groups Name Product Groups Description Product Groups Image Product Categorys Name Products Category Product Categorys Description Product Categorys Groupings Product Sub-categorys Name Products Sub-category Product Categorys Description Product Categorys Category Product Name Product Distributor/ Supplier Product Descriptions Product Variant, Variety Product Size Product Quantity per Unit Stock Product Quantity per Unit Package Products Information Product Quantity per Unit Item Product Prices; Suggested Retail Price, Food Selling Price Product Duration, Expiry date and Manufactured date. Product rights; Consignor or Outright Product allocation properties; Location, Storage, etc. Name, Position, Contact no. Suppliers Information Email, Company Address

Processing Functionalities Function Product Groupings Product Classifying Product Information Entry Stock-Keeping Unit Coding Barcoding Product Tracking Product Sorting Supplier Information Entry User Information Entry Business Note User Tracking and Monitoring Audit Trailing SKU System Settings; Limited Login Attempts System Lock. Business Note Notifications Outputs: Product Information Report Product profiles; List of available products/merchandise; List of outdated products; List of merchandise suppliers, manufacturers; list of merchandise groups, categories and sub - categories; list of merchandise with stock-keeping unit codes; list of system users, user profile, business notes log reports; list of updated merchandise); Product Division Report; Product SKU Code; Product Barcode; Audit Trail Reports Priority Essential Essential Essential Essential Essential Essential Essential Essential Essential Essential Essential Essential Desirable

3.2.1.4 Major Constraints The SKU module is intended to integrate with the other modules in order to build up a whole high-performance Merchandising Information System. That is why if one module cannot perform its core processes then there will be a domino effect for the rest of the other modules; unless each module can stand on its own. As the SKU systems disposition goes, it is hardly connected with the price management and warehouse inventory. Because it would be inefficient to create a SKU code and barcode without the price and inventory. After the software issues are the hardware, as the computer system will always require high specification of each components inside. Then, for great and reliable performance for entry-level computing, it is better to have at least 160GB of hard disk drive or rather upgrade to a solid state drive or SSD. SSDs deliver faster and are more rugged, reliable and completely quiet. And when it comes to RAM (Random Access Memory), 2GB is ideal for everyday tasks inside the merchandising firm. For the processor, it should be supported by some Turbo Boost Technology that will offer extra performance and will guarantee the quality of the stock-keeping output.

3.2.2 Data Design Through this section, further revelations with regards to the data structure and logic of stock-keeping unit module will be introduced to the future users of this software. But let us first meet the three (3) developing areas of the software: (1) the Front End Graphical User Interface supported by Java Netbeans (2) the Back End Database System supported by MySQL (3) the Internal Functional Procedures supported by CLI. Without those 3 elements, it wouldnt be possible to exist such unique kind of stockkeeping unit system. Graphical User Interface This is the top layer of the software. It covers the back-end data that stores several information unnecessary to disclose for one screen at the same time. With the help of JAVA Netbeans, it became possible to offer a system that will always emphasize the users requests of information. As the Front Ends purpose goes, It covers the unnecessary and uncovers the necessary information and functionalities of a certain application. More Front End GUIs are available in the section 3.2.4.4 of the document. Back End Data The inner layer of the software that drives the entire database is the Back End Data. With the aid of MySQL database server, SKU can now offer its vast and even unlimited amount of storage for data entry . As it contains Product Table, more and

more product information can be preserved inside the computer system and still with a strong and quick response upon retrieving , updating and adding new item. Moreover, the database system is also accessible locally or remotely. Because as the firm expands, the software must also be flexible to propagate its nature. Internal Functional Procedures Running the softwares core processes are made possible through the help of internal functional procedures. These are the logical means needed to drive a software in adding, updating, viewing, searching, sorting and even printing varoius stockkeeping unit information. These procedures have been defined through the JAVA Database Connection (JDBC) which also create a link between the Front and the Back End of the Stock-Keeping Unit System.

Database Description Here are the tables with their corresponding attributes and descriptions as covered by the module of stock-keeping unit system:
Category table: Defines the Category of each merchandise products. Field Type Description gid int(2) Category's group ID no. catno int(4) Product category unique ID no. catname varchar(25) Product category name catdes varchar(50) Category description

Product Group table: Defines the Group of merchandise Categories, these groups serves as division to classify Each product merchandise. Field gid ghex gdes updated pic Type int(2) varchar(2) varchar(100) datetime longblob Description Product group id in hex code. ('Refer from hypermarket sap inventory') Product group Name Product group descriptions. Product group's modification date Product group's Image

Sub-category table: Defines the Sub-category of Product Merchandise. Field subcatno subcatname catno subcatdes Type int(4) varchar(35) int(4) varchar(50) Description Product Sub-category Number. Product Sub-category Name Product Sub-category's Category ID Product Sub-category description

Product table: Stores information of Merchandise/ Product Profiles. Field Type Comment prod_id int(15) Product's Unique Identification no. prod_skucode int(15) Product's SKU Code Product's Barcode(Universal Product prod_prodbarcode int(15) Code) no. prod_type varchar(50) Product's Rights; Consignor or Outright prod_name varchar(100) Product's Name prod_desc varchar(100) Product's Description prod_cat varchar(100) Product's Category prod_subcat varchar(100) Product's Sub-category prod_size varchar(100) Product's Size prod_qtyperbox varchar(100) Product's Quantity per unit Stock prod_qtyperpack prod_qtypermeasure prod_variants prod_variety prod_mfgdate prod_xpdate prod_shelfdue prod_promodue prod_reorderlevel prod_ordercode prod_location prod_srp prod_fsp varchar(100) varchar(100) varchar(50) varchar(50) date date varchar(100) varchar(100) varchar(100) varchar(100) varchar(100) varchar(100) varchar(100) Product's Quantity per unit packaging Product's Quantity per unit Item Product's variant. Product's variety Product's Manufactured Date Product's Expiration date Product's Shelf life Duration Product's Promo Duration Product's Reorder Level Product's Order Code Product's location Product's Suggested Retail Price Product's Selling Price

Product Packages table: Defines the packaging of product merchandise. Field Type Comment packages varbinary(20) Merchandise packaging unit.

Product Variation table: Defines the variants and varieties of merchandise. Field Type Comment variants varchar(20) Merchandise Product variants. varieties varchar(20) Merchandise Product variant's varieties.

Supplier table: Stores the information related to merchandise supplier's profile. Field Type Comment sid int(8) Supplier's ID scomp varchar(200) Supplier's Company Name. sctele varchar(35) Supplier Company's Phone Number Supplier Company's Address or saddress varchar(200) Location. slaname varchar(35) Supplier's LastName sfname varchar(35) Supplier's Firstname scontact varchar(35) Supplier's Contact numbers. email varchar(75) Supplier's Email Address sposition varchar(200) Supplier's Position or Title. status varchar(200) Supplier's Status, ie: Active, InActive Supplier's Mechantile Type, ie: Outright, stype char(200) Consignor. Business notes table: Stores the information on business notes. Field Type Comment int(4) Business Note's message no. longtext Business Note's message. varchar(90) The author of the message. The Datetime when the message is datetime written.

nid notes author date

History table: Stores information on system's overall activity for Audit Trailing. Field Type Comment scode int(1) SKU System setting's no. lattempt int(1) SKU_Module Login Attempt SKU_Module Business Note's switch varchar(25) Notification switch ltime int(4) SKU_Module Lock time author varchar(50) SKU_Module System settings modifier. SKU_Module System settings date date datetime modified

Users table: Stores information related to the modules user profile. Field Type Comment uid int(8) SKU_User's ID username varchar(35) SKU_User's User Name fname varchar(35) SKU_User's Fists Name mname varchar(35) SKU_User's Middle Name lname varchar(35) SKU_User's Last Name position varchar(35) SKU_User's Position password varchar(35) SKU_User's Password email varchar(35) SKU_User's E-mail Address role varchar(35) SKU_User's user level status varchar(35) SKU_User's Status; Active or Inactive SKU_User's Modification entry updated datetime datetime. author varchar(90) SKU_User's Modifier SKU_Settings table: Stores information related to SKU_Module System settings . Field Type Comment scode int(1) SKU System setting's no. lattempt int(1) SKU_Module Login Attempt SKU_Module Business Note's switch varchar(25) Notification switch ltime int(4) SKU_Module Lock time author varchar(50) SKU_Module System settings modifier. SKU_Module System settings date date datetime modified