3.2 Software Design Specification 3.2.1 Introduction 3.2.1.

1 Goals and Objectives This project focus in creating a procurement system that will help the company for easily proposal bidding, purchasing and consume less time in the recordings of data and information. The procurement system will be user friendly software that is easy to understand by the user and the owner. And to construct a system that contains all information and data together with their attributes and to implement a system that can easily search, add and update all the records of the suppliers and items, it also lighten the load for the staff and enhance customer service. To create a procurement system that will take out the inaccuracy in the recordings of the data and give an easy access to the files and data at any given time. 3.2.1.2 Statement of Scope The following are the scope of the proposed Material Management Procurement System: Security Allocation of bidding among different development

sectors/projects. Functioning Commands (ADD, EDIT, VIEW, DELETE, PRINT, SEARCH). Procurement procedure.

3.2.1.3 Software context In Quezon City Hall, they are using Microsoft Access for their system. That is why the proponents where encouraged to develop an automated system to resolve those problems. For the LGU, the proposed study contains functionality will help in the manipulation and modification of records of suppliers and items within the company, through this capability the system is able to generate a more accurate and reliable information needed for different procurement transactions. 3.2.1.4 Major constraints The Material Management Procurement System will use Java NetBeans IDE 7.3 which requires a windows application supporting this technology. 3.2.2 Data Design Application type system with MySql xampp and Java NetBeans IDE 7.3 as front end. 1. Front End Graphical User Interface Java NetBeans IDE 7.3 used for the development of the front GUI. Input by user using a keyboard. 2. Back End data MySqlyog xampp server is the back end of the system. All data input on the GUI by the user of Java NetBeans IDE 7.3 3. Internal functional Procedures The internal functionalities procedures are the logical entities that carry out different tasks of adding, updating, viewing and printing the data in the database.

3.2.2.1 Internal Data Structure There is no data structure available to internal software Architecture. The intermediate information while updating or adding to any table is stored in the administrator form in adding of new Supplier record of the GUI. When add button is pressed the information encoded will be directly added on the database as well as the update button it will change information directly to the database. For accessing or viewing any table data is fetched directly from the database to the Java Netbeans 7.3 database object place, defining the information to be print out, checking availability of the components needed in the printing purpose and then print reports to be done in weekly and monthly Due.

3.2.2.2 Global Data Structure The only kind of data available globally to the whole system is the database itself stored in Mysql server. Any data stored can fetched and update.

3.2.2.3 Temporary Data Structure The Material Management Procurement System does not use any intermediate files of its own. As data being stored in a database system all the intermediate data until the command commit is being executed in MySQL query by the application. Hence no intermediate files or data structure are used. 3.2.2.4 Database Description Table Name: User Account Attributes: Username, Password, Designation

Designation: Each person accesses their user account with a user name and password. Table Name: Supplier Attributes: Username, Password, Designation

Designation: Each person accesses their user account with a user name and password. Table Name: ItemList Attributes: listID, DRnumber, Item, ItemName

Designation: list of item 3.2.3 Architectural and Component Level Design 3.2.3.1 Architectural Diagram The Architectural Diagram should include (on the diagram or on separate attached diagrams) all connectivity, data flow, business flow and supporting functions. Data flow descriptions should include the proposed server, protocols, networks and projected data repositories. The network component diagrams should include, but are not limited to, the following; a. End-user workstations and other applicable devices. b. Server, including hardware type, operating system level, and hosted applications. c. Firewalls, including details on interfaces, ports, proxies, and protocols. d. Routers, including interfaces, access control list, and configurations. e. Switches(VLAN information)

Architectural Context Diagram

Workstation

Admin
Material Management Procurement System Database MySqlyog

Server Xampp

Workstation

User

Figure 13 Architectural Context Diagram There are types of architecture and application the context. Basically the architectures can be divided as system architectures and application architectures. The system architecture is the diagram that the proponent described above. The application architecture is the call and return architecture. In the diagram, the main calls the controller functions, these application call the application and this function return the required data.

3.2.3.2 Description of Components 3.2.3.2.1 Component Supplier 3.2.3.2.1.1 Processing narrative of component Supplier The component supplier contains the class supplier it contains the attributes, which are the basic data of the supplier of the company. It contains the function which sets all the related data into and out of the class supplier contains the data members and function, which are unique to the supplier of the company. The responsibilities of this component is to declaring variables of the data supplier and implementing functions which set data in the database and retrieve from the database. 3.2.3.2.1.2 Interface description of the component Supplier The component supplier has an interface with the class Item from which it inherits attributes and functions. The Item class and functions to set this data into the database and retrieve from the database. The attributes common for supplier are declared in this interface and the functions related to these attributes to set and get from the database are defined in this class the attributes and operations which are unique to the supplied are declared and defined in the component class. 3.2.3.2.1.3 Algorithmic description of component Supplier Component supplier The intent of this component is set basic. Supplier data into database and get data from the database.

Start Declare variables of the basic data Set the basic data of the Supplier in the database Get the data from the database End 1.2.3.2.1.3.1 Design class hierarchy

Supply Supply name Get_supply_name Set_supply_name

Supplier Supplier name Get_supplier_name Set_supplier_name

3.2.3.2.2 Component User 3.2.3.2.2.1 Processing narrative of component User The component user consists of the class user. It contains the attributes which are the basic data of the user of the system. It contains the functions. This set all the related data into and out of the database. The class user contains the data member and functions, which unique to the employee. The responsibility of this component is to declared variables of the basic data in the database and retrieves from database. 3.2.3.2.2.2 Interface description of component user The component user has an interface with the class person from which is inherit attributes and functions. The

item class has attributes, which are the basic data common to supplier class and user class and function to set this data into the database and retrieve. The attributes common for supplier and employee are declared in this interface and the related to their attributes to set and get from the database are defined in this class. The attributes and operations which are component class, the user are declared and defined in this component class. 3.2.3.2.2.3 Algorithmic description of components user Component user The inherit of the components user is to set basic data of employee into database and get the data from the database Start Declared variables of the data of the user Set values into the database Get the data from the database End

3.2.3.2.2.3.1 Design class hierarchy

Supply Supply name Category Description Quantity Price Supplier Ponumber Date GetSupply() SetDate() Display User First name Last name MI Address Contact User name Password Designation Check order Get order Print receipt Get receipt

3.2.3.2.2 Component Admin 3.2.3.2.2.1 Processing narrative of component Admin Component admin consist of the class admin, it contains the attributes, which are basic responsibilities of the bids of item regarding check, update, edit, account get reports add bidders save data. It contains the operations to set related data to database, it also compute the bidding of item 3.2.3.2.2.2 Interface description of component admin The component admin has a interface with the classes, checking the bids of item, the admin of procurement department. It inherit the attributes and functions from the class user.

3.2.3.2.2.3 Algorithmic description of components admin Component admin The intent of his component is the check the data of admin, check update, edit account, get reports, add item and save item into the database and get the same from the database. Start Set the data of admin into the database Set the data of check update into the database Set the data of edit account into the database Set the data of get reports into the database Set the data of add item and supplier into the database Set the data of save item and supplier into the database Get the date of save item and supplier into the database End

3.2.3.2.2.3.1 Design class hierarchy

Supply Supply name Category Description Quantity Price Supplier Ponumber Date GetSupply() SetDate() Display Supplier Company name Contact person Contact number Supplier product Invoice number GetInvoice no() Setclass()

Admin Username Password Designation Check update() Edit account()

User First name Last name MI Address Contact User name Password Designation Check order Get order Print receipt Get receipt

3.2.3.2.3 Component Supply 3.2.3.2.3.1 Processing narrative of component supply The component supply consist of the supply, it contains the attributes, which are the unique basic data of the supply. It contains the functions which set all the related data to database. The class supply contains the data

members and functions, which are the unique to the user. The responsibility of this component is to declare variable of basic of the user and implementing functions which set data in the database and retrieve from the database 3.2.3.2.3.2 Interface description of component supply The component item has an interface with the class admin from which it inherits attributes and functions. The admin class has attributes, which are the class admin class and item and function to set this data into the database and retrieve from the database. The attributes common for common for admin and supply declared in this interface and the function related to this attributes which are unique to the item are declared and defined in the component class. 3.2.3.2.3.3 Algorithmic description of components supply Component supply The intent of this components produced is to set basic data of supply into the database and get the data from the database. Start Declared variables f the basic data of the supply Set schedule in to the database Set supply from the database Get supply from the database

3.2.3.2.3.3.1 Design class hierarchy

Supply Supply name Category Description Quantity Price Supplier Ponumber Date GetSupply() SetDate() Display

Admin Username Password Designation Check update() Edit account()

3.2.3.2.4 Component Reports 3.2.3.2.3.1 Processing narrative of component reports The component reports consist of the class user. The responsibilities of this component are to summarize and print reports of log-in, log-out, user info. 3.2.3.2.3.2 Interface description of component supply The component reports have an interface with the class user, admin, supplier and other users. It inherits the data members and functions from the class user generate reports, it inherits the data members and functions from class admin to generate reports. It inherits the data members and functions from the class supplier to generate reports, from class of all users to prints reports.

3.2.3.2.3.3 Algorithmic description of components supply Component reports; The intent if this component reports is to print reports Start Set the Set the data of administrator Set the data of user Set the data of supplier Get data of administrator Get the data of user Get the data of supplier Get the data of reports Print reports Set the user of 3.2.3.2.3.3.1 Design class hierarchy

Reports Reports Set_reports() Get_reports()

Admin Username Password Designation Check update() Edit account()

3.2.3.3 Dynamic behavior for component 3.2.3.3.1 Interaction Diagrams

Administrator

Monitor

Material Management Procurement System Software

Printer

Log-in

Verifying

Logged-in Password=correct Successfully logged-in Attempts=3

Blocked Give access to the admin Administrator add/edit/delete data For Display For printing data Prints Data

Display Data

Figure 14 Interaction diagram for Administrator

This is diagram were the use case components is administrator. The first event, system ready, is derived from the external environment and behavior to administrator object. The administrator enters the password. Are the request look-up event is passed to system that looks up event is passed to system that looks up the password into software system and return a result (found or not found) to monitor a valid password result in valid password=correct event to software event which then gives access to the manager and the manager can add/update/delete the data of all other employees. And this data can be displayed on the monitor or printed from the printer upon request. 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 This component can only be called when the user requires the data of the administrator and The Material Management Procurement System will use Java NetBeans IDE 7.3 which requires a windows application supporting this technology. 3.2.6 Testing Issues Test strategy and preliminary test case specification are presented in this section. The various test to be conducted to validate the software developed are login test, updating new records, checking suppliers status, viewing reports, adding information, displaying of result, saving purchasing records and maintain purchasing records.

TABLE OF FIGURES Figure 1.Architecture Context Diagram Figure 2.Call and Return Architecture Diagram Figure 3.Object Oriented Architecture Diagram Figure 4.Sequential Diagram