3.

2 Software Design Specification

3.2.1 Introduction 3.2.1.1 Goals and Objectives To make a secured, convinient, flexible, cost less and user friendy system, these are the goals and objectives of developing the proposed system. Secured because the system can only access by the authorized user.Convinient for a reason that the company dont have to purchase manually instead the user will just used the system in the office area and can perform purchasing without spending fare for transportation so it also cost less.Flexible because the system software can operate many operations.User friendly because the system was developed in a simple user interface so it can easy understand.

3.2.1.2 Statement of Scope Major Inputs Purchase Order ID, Purchase Ordercode, Price, Delivery Date, Product Name, Quantity, OR# Product ID, Product Name, Price, Quantity Bad Order ID, OrderCode, Product Name, Quantity, Package Supplier Information Company Name Agreement period Return to Supplier Information Function Purchase Order Entry Product Information Entry Bad Order Information Entry Supplier Information Company Name Agreement period Return to Supplier Priority Essential Essential Essential Essential Essential Essential Essential

3.2.1.3 Software context This Purchase Order Management Software is a Very efficient one, which maintains database of Purchase Order, Product Information, Supplier Information, Return to Supplier, Bad Order & Transaction table. And this Software is less expensive and also reduces complexity. In this software proponents used JAVA netbeans & SQLyog for the database connectivity. 3.2.1.4 Major Constraints The Purchase Order is runnable with using SQLyog as a back end and with using netbeans as a front end.The system is good enough to perform all the transactions that must be perpform by a Purchase Order. ` 3.2.2 Data Design 1.Front End Netbeans IDE 2.Back End Data

3.2.2.1 Internal Data Structure Any Information that has been inputted will store in the system database, when the user add or updates an information in the text fields, it is directly go to the database for adding and updating.While for viewing, the desire table will display on the screen for the system is created in easier accession. 3.2.2.2 Global Data Structure To complete the function of the system, globally its need database to store data and to creates queries function.The Proponent choose SQLYOG as back end and Netbeans as front end. To function the stored data in the database there must have JDBS connection so that data stored can be fetched, update and delete. 3.2.2.3Temporary Data Structure The Purchase Order Management system does not use any temporary data structure.The data that has been inputted will store to its database which is the MySQL. 3.2.2.4 Database Description

The following mentioned are the tables and their corresponding attributes.

Table Name 1. Product

Attributes Prod_ID, Prod_SRP Prod_Name,Prod_Supplier,Prod_Manufacturer, Po_ordercode, Prod_qtyperbox, Prod_qtyperpiece, Prod_type, Prod_qtypermeasurement PO_ Code,Prod_ID,Sup_ID,Prod_Name,Delivery Date,Contract,Time, Po_payment, Po_suptotalamount Supplier_ID,Supplier_Name,Supplier_Address,Supplier_Contact, Supplier_email User_ID,User_Name,User_password BO_No.,Delivery Date,Prod_ID,Prod_Name,Supplier_ID, Rts_ID, PO_ordercode, Product_ID, Supplier_ID, Rtv_Qty

2. Purchase order 3. Supplier 4. Login 5. Bad Order 6. Return to Supplier

3.2.3 Architectural and Component level Design 3.2.3.1 Architectural Diagram 3.2.3.2 Description of components