7.1 Architectural Design
7.1.1 Entity-Relationship Diagram
Fig. 7.1.1 Database model
On the figure above, the table “item_description” contains information about the items in the inventory. This is where the data for new items will be stored and updating of information of existing items takes place. Notice that, the table “critical_items” has only two attribute which is “status” that identifies the critical item if it is low or not. The “transaction” table is where the system stores data regarding individual transaction while “item_trans” table focuses on list of items and its total price.
7.2 System Function
7.2.1 Physical Data Flow Diagram
Fig. 7.2.1 Physical DFD
The system mainly consists of functions for sales and inventory management. A customer orders an item and the system checks the inventory by accessing the master item table. New items can be added by the management and the master item record is updated as such. A process computes the total price for the items ordered by using the input from the customer and data(prices) from the inventory master table. After the transaction, receipt will be given to the customer and both the inventory record and sales record are updated. If the system detects any item to be at critical level, a notification will be sent to the management.
7.2.2 User Interface
Fig. 184.108.40.206 Main Menu
This is the interface where the user has access to all function of the system (Fig. 220.127.116.11). The first thing that will show up when the user runs the system is the button with a text of “V”. When the user clicks the “V” button the five buttons and upon clicking the inventory and report button their sub items will also appear and when the user clicks one of these buttons (Point of Sale, View Inventory, Update Inventory, Add Inventory, Critical Items, View Sales Report, and View Inventory report) the visibility of all buttons will be disabled and then the desired form of the user will appear on the gray space....
Please join StudyMode to read the full document