PowerPoint Presentation

POINT OF SALES SYSTEMBawagan, MatthewFlorendo, CherryfeTugade, Rhea Ann

Chapter 1: INTRODUCTION1.1 BACKGROUND OF THE STUDY1.2 STATEMENT OF THE OBJECTIVES1.3 SIGNIFICANCE OF THE STUDY1.4 SCOPE AND LIMITATIONS1.1 BACKGROUND OF THE STUDYA Point of Sales System is a system which helps customers make payments to the merchant in exchange for goods and services. The history of a Point of Sales System goes way back 40 years ago. In August 1973, IBM released the IBM 3650 and 3660 store systems that were, in essence, a mainframe computer used as a store controller that could control up to 128 IBM 3653/3663 point of sale registers. 1.2 STATEMENT OF THE OBJECTIVESGENERAL OBJECTIVE to be able to accommodate the customers with computerized, systematic, and correlated retail information with regards to the products that they purchase with their respective prices, the quantity they purchase, and with less time burdenSPECIFIC OBJECTIVES to be able to update the system based on the number of products they purchase during their transaction and the reliability and clarity of results by allowing the system to print full-size invoices1.3 SIGNIFICANCE OF THE STUDYADMINISTRATOR it allows them efficiently modify available products and employees by adding new ones and editing and removing existing ones as well as monitor clock-in and clock-out attendance of employeesCASHIER it allows them to easily add and remove purchased products to the receipt as well as compute the total price, the value-added tax, and the change after receiving cash from customers. It also allows them to save, preview, and print well-documented receipts as well as generate company reports such as sales, expenses, and revenue/profit1.4 SCOPE AND LIMITATIONSSCOPEADMINISTRATOR can be able to login the system and access the retail database; can add, update or remove, goods, and employees; and the admin account cannot be accessed by the cashierCASHIER employees login to a separate account but cannot access the retails database; is limited to receiving cash from customers and calculating the change; and is able to print receiptsLIMITATIONSSystem can only be accessed offline.System can only receive cash.System cannot receive amounts on a credit card basis.Chapter 2: METHODOLOGY OF THE STUDYRequirements Gathering and RefinementQuick Design and Building of the PrototypeCustomers Evaluation of the PrototypeRefining of the PrototypeEngineered ProductChapter 3: DATA GATHERING PROCEDURES AND OUTPUTDesk/Internet ResearchSurvey

Table 1.0: SURVEY OUTPUTChapter 4: PROPOSED SYSTEM4.1 SYSTEM OVERVIEW4.2 PROCESS SPECIFICATIONS4.3 DATA SPECIFICATIONS4.4 SCREEN LAYOUT SPECIFICATIONS4.1 SYSTEM OVERVIEWA Point of Sales System is an electronic system that provides businesses with the capability to retain and analyse a wide variety of offered products within an inventory and a day-to-day transaction data on a continuous basis. POS Systems have been touted as valuable tools for a wide variety of business purposes, including refining target marketing strategies; tracking customer purchases and determining its patterns; analysing sales (on a daily, monthly, or annual basis) of each inventory item, department, or supplier; and creating reports for use in making purchases and reorders.

4.2 PROCESS SPECIFICATIONS4.2.1.1 DATA FLOW DIAGRAM (ADMINISTRATOR)4.2.1.2 DATA FLOW DIAGRAM (CASHIER)4.2.2 ACTIVITY DIAGRAM4.2.3 CONTEXT DIAGRAM4.2.4 DATA DICTIONARY4.2.1.1 DATA FLOW DIAGRAM (ADMINISTRATOR)

Figure 1.0: DFD for Admin4.2.1.2 DATA FLOW DIAGRAM (CASHIER)

Figure 1.1: DFD for Cashier4.2.2 ACTIVITY DIAGRAM

Figure 2.0: Activity Diagram for POS4.2.3 CONTEXT DIAGRAM

Figure 3.0: Context Diagram for POS4.2.4 DATA DICTIONARYADMINISTRATOR LOGIN Administrator Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]ADMINISTRATOR PASSWORD CHANGEOld Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]New Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]Confirm Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]

PRODUCT DETAILSProduct Name = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]Product Price = { Legal Character }Legal Character = [ 0 9 | . ]Product Quantity = { Legal Character }Legal Character = [ 0 9 ]EMPLOYEE REGISTRATIONEmployee First Name = { Legal Character }Legal Character = [ A Z | a z ]Employee Middle Name = { Legal Character }Legal Character = [ A Z | a z | . ]Employee Last Name = { Legal Character }Legal Character = [ A Z | a z ]Employee Username = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]Employee Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]Employee Password Confirmation = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]

EMPLOYEE LOGINEmployee Username = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]Employee Password = { Legal Character }Legal Character = [ A Z | a - z | 0 - 9 ]RECEIPTProduct ID = { Legal Character }Legal Character = [ 0 9 ]Purchases = { Legal Character }Legal Character = [ 0 9 ]Amount Received = { Legal Character }Legal Character = [ 0 9 | . ]Calculator = { Legal Character }Legal Character = [ 0 9 ]

4.3 DATA SPECIFICATIONS4.3.1 ENTITY-RELATIONSHIP DIAGRAM4.3.2 ARCHITECTURAL DESIGN4.3.3 TABLES/FILES LAYOUT4.3.1 ENTITY-RELATIONSHIP DIAGRAM

Figure 4.0: ERD for POS4.3.2 ARCHITECTURAL DESIGN

Figure 5.0: Architectural Design for POS 4.3.3 TABLES/FILES LAYOUT

Table 2.0: Database Tables and Fields4.4 SCREEN LAYOUT SPECIFICATIONS

Figure 6.0: POS LoginFigure 6.1: Administrator Login

Figure 6.2: Product ListFigure 6.3: Employee List

Figure 6.4: Password Change (Administrator)Figure 6.5: Product Update

Figure 6.6: Company Sales ReportFigure 6.7: Employee Registration

Figure 6.8: Employee LoginFigure 6.10: CalculatorFigure 6.11: Print Preview

Figure 6.9: System OperationFigure 6.12: Employee AttendanceChapter 5: SYSTEM CODING5.1 PROGRAMMING LANGUAGE Visual Basic (VB.NET)5.2 SPECIAL PURPOSE LANGUAGE TOOLS Visual Basic (a 3rd-generation event-driven high-programming language and integrated development environment developed by Microsoft) and Microsoft Office Access (a database management system from Microsoft that combines the relational Microsoft Jet Database Engine with a graphical user interface and software-development tools)Chapter 6: SYSTEM TESTING (TESTING STAGES & SCHEDULE)TEST CASESTEST PROCEDUREEXPECTED RESULTSSTATUSDATE TESTED (DD-MM-YY)DATE FIXED (DD-MM-YY)Administrator LoginAdministrator provides a valid password.Administrator should be able to access the Admin Window.PASS06-01-1406-01-14Administrator provides an invalid passwordAdministrator should not be able to login.PASS06-01-1406-01-14Administrator provides a blank passwordAdministrator should not be able to login.PASS06-01-1406-01-14Employee LoginEmployee provides a valid username and password.Employee should be able to access the Employee Window.FAIL11-01-1419-01-14Employee provides an invalid username and password.Employee should not be able to login.FAIL11-01-1419-01-14Employee provides a blank username and password.Employee should not be able to login.PASS11-01-1411-01-14Employee RegistrationEmployee provides valid background information of himself/herself.Employee should be able to successfully register his/her account.PASS12-01-1412-01-14Employee provides invalid background information of himself/herself.Employee should not be able to successfully register his/her account.FAIL12-01-1417-01-14Employee provides blank background information of himself/herself.Employee should not be able to successfully register his/her account.FAIL12-01-1417-01-14Administrator Password ChangeAdministrator provides a valid old and new password with a valid password confirmation.Administrator should be able to change Administrator password.PASS18-01-1418-01-14Administrator provides an invalid old and new password with an invalid password confirmation.Administrator should not be able to change Administrator password.PASS18-01-1418-01-14Administrator provides a blank old and new password with a blank password confirmation.Administrator should not be able to change Administrator password.PASS18-01-1418-01-14Add ProductAdministrator provides a valid product name, product price, and product quantity.Administrator should be able to add a product in the database.FAIL20-01-1422-01-14Administrator provides an invalid product name, product price, and product quantity.Administrator should not be able to add a product in the database.PASS20-01-1420-01-14Administrator provides a blank product name, product price, and product quantity.Administrator should not be able to add a product in the database.PASS20-01-1420-01-14Edit ProductAdministrator provides a valid product name, product price, and product quantity.Administrator should be able to edit a product in the database.FAIL23-01-1425-01-14Administrator provides an invalid product name, product price, and product quantity.Administrator should not be able to edit a product in the database.FAIL23-01-1425-01-14Administrator provides a blank product name, product price, and product quantity.Administrator should not be able to edit a product in the database.PASS23-01-1423-01-14Remove ProductAdministrator selects an existing product and removes it.Administrator should be able to delete a product item from the database.PASS26-01-1426-01-14Add EmployeeAdministrator provides valid background information of the employee.Administrator should be able to add employee.FAIL27-01-1431-01-14Administrator provides invalid background information of the employee.Administrator should not be able to add employee.PASS27-01-1427-01-14Administrator provides blank background information of the employee.Administrator should not be able to add employee.PASS27-01-1427-01-14Edit EmployeeAdministrator provides valid background information of the employee.Administrator should be able to edit employee.FAIL01-02-1403-02-14Administrator provides invalid background information of the employee.Administrator should not be able to edit employee.FAIL01-02-1403-02-14Administrator provides blank background information of the employee.Administrator should not be able to edit employee.PASS01-02-1401-02-14Remove EmployeeAdministrator selects an existing employee and removes him/her.Administrator should be able to delete an employee along with his/her background information from the database.PASS03-02-1403-02-14Product SelectionEmployee selects an existing product by entering its corresponding Product ID.Employee should be able to automatically view its corresponding product name, product price, and product quantity.PASS05-02-1405-02-14Employee selects a non-existing product by entering a Product ID.Employee should not be able to automatically view its corresponding product name, product price, and product quantity.PASS05-02-1405-02-14Purchase Number InputEmployee inputs the number of customer purchases that is less than or equal to the number of product quantities available in the inventory database.Employee should be able to successfully update the product quantity.FAIL08-02-1413-02-14Employee inputs the number of customer purchases that is greater than the number of product quantities available in the inventory database.Employee should not be able to successfully update the product quantity.FAIL08-02-1413-02-14Add Receipt ItemEmployee adds the purchased item to the list of purchased products.Employee should be able to add the product to the receipt along with its product name, product price, number of purchases, and total price..FAIL15-02-1416-02-14Remove Receipt ItemEmployee selects the added purchased item and removes it.Employee should be able to delete the purchased product from the receipt.PASS15-02-1415-02-14Print ReceiptEmployee selects a printer and prints the receipt being previewed.Employee should be able to use a printer and print the receipt.FAIL23-02-1427-02-14Cash ComputationsEmployee inputs the amount received from the customer that is greater than or equal to the total price.Employee should be able to automatically compute the change and the value-added tax.PASS15-02-1415-02-14Employee inputs the amount received from the customer that is less than the total price.Employee should not be able to automatically compute the change and the value-added tax.PASS15-02-1415-02-14Save ReceiptEmployee saves the purchase history as well as the products purchased (product information included) along with its cash calculationsEmployee should be able to save the receipt information and the receipt details in the database and generate a receipt preview.FAIL16-02-1423-02-14Display Employee AttendanceEmployees login to their respective accounts as well as logout once they are finished.Administrator should be able to view employee clock-ins and clock-outs with their respective dates.FAIL01-03-1403-03-14Display Company Sales ReportEmployees must save the receipts after every customer purchase transaction.Both Administrator and Employee should be able to display the companys total sales, expenses, and revenues.FAIL04-03-1406-03-14Table 3.0: Test CasesChapter 7: SYSTEM IMPLEMENTATION PLAN (RESOURCE REQUIREMENTS)7.1 HARDWARE REQUIREMENTSAny PC, Desktop, or Laptop with pre-installed Visual Basic and Microsoft Access applications. Printer7.2 SOFTWARE REQUIREMENTSVisual Basic 2012 Express Edition for Windows DesktopMicrosoft Access 2007/Microsoft Office Access 2010Windows 7/Windows 8 Operating System7.3 HUMAN RESOURCE REQUIREMENTSEmployees cashiersAdministrator senior management official/senior human resource official

Chapter 8: GANTT CHART

Figure 7.0: GANTT CHARTSurvey and Table DatabaseSURVEY QUESTIONSYESPERCENTAGENOPERCENTAGETABLEFIELDDATA TYPEFIELD SIZE1. Does your retail store still manage its business manually?640%960%EMPLOYEE BACKGROUNDFirst NameVarchar/Text2552. Is your retail store able to produce daily/weekly/monthly reports?533.33%1066.67%Middle NameVarchar/Text2553. Do you still continue to use a manually-based system?426.67%1173.33%Last NameVarchar/Text2554. Have you experienced using a Point of Sales System?853.33%746.67%StatusVarchar/Text255UsernameVarchar/Text255PasswordVarchar/Text255EMPLOYEE LOGINLogin NumberInteger32 767UsernameVarchar/Text255Login TimeDate/TimeN/AEMPLOYEE LOGOUTLogout NumberInteger32 767UsernameVarchar/Text255Logout TimeDate/TimeN/APRODUCT DETAILSProduct IDInteger32 767Product NameVarchar/Text255Product PriceDecimal/Currency11Product QuantityInteger32 767RECEIPT CONTENTReceipt IDInteger32 767Receipt DateDate/TimeN/AReceipt TotalDecimal/Currency11Receipt AmountDecimal/Currency11Receipt ChangeDecimal/Currency11Receipt VATDecimal/Currency11RECEIPT DETAILSReceipt IDInteger32 767Product IDInteger32 767Product NameVarchar/Text255Product PriceDecimal/Currency11Product QuantityInteger32 767COMPANY REPORTReceipt IDInteger32 767Cashier NameVarchar/Text255Receipt DateDate/TimeN/ACompany SalesDecimal/Currency11Company ExpensesDecimal/Currency11Company ProfitDecimal/Currency11

Gantt ChartWBSTask Name2014JanuaryFebruaryMarchWeek 1 (6 - 11)Week 2 (12 - 18)Week 3 (19 - 25)Week 4 (26 - 31)Week 1 (1 - 8)Week 2 (9 - 15)Week 3 (16 - 22)Week 4 (23 - 28)Week 1 (1 - 8)Week 2 (9 - 15)Week 3 (16 - 22)1Requirements Gathering and Definition1.1Desk Reseach1.2Defining Objectives1.3Determing the Significance1.4Assessing the Scope and Limitations1.5Survey2Designing and Building the Prototype2.1Creating Database Tables and Relationships2.2Connecting Database Servers2.3Creating Process Diagrams2.4System Coding2.5System Trappings3Evaluation of the System3.1Testing of the Prototype3.2Review of the Documentation4Refinement of the Prototype4.1Reassessing the System4.2Addition of Trappings4.3Revision of the Documentation

Sheet3