Your SlideShare is downloading. ×
0
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Point of Sales System
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Point of Sales System

8,723

Published on

Published in: Software, Business, Technology
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
8,723
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
530
Comments
0
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Bawagan, Matthew Florendo, Cherryfe Tugade, Rhea Ann
  • 2. • 1.1 BACKGROUND OF THE STUDY • 1.2 STATEMENT OF THE OBJECTIVES • 1.3 SIGNIFICANCE OF THE STUDY • 1.4 SCOPE AND LIMITATIONS
  • 3. • A 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.
  • 4. • GENERAL 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 burden • SPECIFIC 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 invoices
  • 5. • ADMINISTRATOR – 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 employees • CASHIER – 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/profit
  • 6. • SCOPE i. ADMINISTRATOR – 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 cashier ii. CASHIER – employees login to a separate account but cannot access the retail’s database; is limited to receiving cash from customers and calculating the change; and is able to print receipts • LIMITATIONS i. System can only be accessed offline. ii. System can only receive cash. iii. System cannot receive amounts on a credit card basis.
  • 7. • Requirements Gathering and Refinement • Quick Design and Building of the Prototype • Customers’ Evaluation of the Prototype • Refining of the Prototype • Engineered Product
  • 8. • Desk/Internet Research • Survey SURVEYQUESTIONS YES PERCENTAGE NO PERCENTAGE 1.Doesyourretail storestill manageitsbusinessmanually? 6 40% 9 60% 2.Isyourretail storeabletoproducedaily/weekly/monthlyreports? 5 33.33% 10 66.67% 3.Doyoustill continuetouseamanually-basedsystem? 4 26.67% 11 73.33% 4.HaveyouexperiencedusingaPointofSalesSystem? 8 53.33% 7 46.67% Table 1.0: SURVEY OUTPUT
  • 9. • 4.1 SYSTEM OVERVIEW • 4.2 PROCESS SPECIFICATIONS • 4.3 DATA SPECIFICATIONS • 4.4 SCREEN LAYOUT SPECIFICATIONS
  • 10. • A 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.
  • 11. • 4.2.1.1 DATA FLOW DIAGRAM (ADMINISTRATOR) • 4.2.1.2 DATA FLOW DIAGRAM (CASHIER) • 4.2.2 ACTIVITY DIAGRAM • 4.2.3 CONTEXT DIAGRAM • 4.2.4 DATA DICTIONARY
  • 12. Figure 1.0: DFD for Admin
  • 13. Figure 1.1: DFD for Cashier
  • 14. Figure 2.0: Activity Diagram for POS
  • 15. Figure 3.0: Context Diagram for POS
  • 16. • ADMINISTRATOR LOGIN i. Administrator Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] • ADMINISTRATOR PASSWORD CHANGE i. Old Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] ii. New Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] iii. Confirm Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ]
  • 17. • PRODUCT DETAILS i. Product Name = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] ii. Product Price = { Legal Character } Legal Character = [ 0 – 9 | . ] iii. Product Quantity = { Legal Character } Legal Character = [ 0 – 9 ] • EMPLOYEE REGISTRATION i. Employee First Name = { Legal Character } Legal Character = [ A – Z | a – z ] ii. Employee Middle Name = { Legal Character } Legal Character = [ A – Z | a – z | . ] iii. Employee Last Name = { Legal Character } Legal Character = [ A – Z | a – z ] iv. Employee Username = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] v. Employee Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] vi. Employee Password Confirmation = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ]
  • 18. • EMPLOYEE LOGIN i. Employee Username = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] ii. Employee Password = { Legal Character } Legal Character = [ A – Z | a - z | 0 - 9 ] • RECEIPT i. Product ID = { Legal Character } Legal Character = [ 0 – 9 ] ii. Purchases = { Legal Character } Legal Character = [ 0 – 9 ] iii. Amount Received = { Legal Character } Legal Character = [ 0 – 9 | . ] iv. Calculator = { Legal Character } Legal Character = [ 0 – 9 ]
  • 19. • 4.3.1 ENTITY-RELATIONSHIP DIAGRAM • 4.3.2 ARCHITECTURAL DESIGN • 4.3.3 TABLES/FILES LAYOUT
  • 20. Figure 4.0: ERD for POS
  • 21. Figure 5.0: Architectur al Design for POS
  • 22. TABLE FIELD DATA TYPE FIELD SIZE First Name Varchar/Text 255 Middle Name Varchar/Text 255 Last Name Varchar/Text 255 Status Varchar/Text 255 Username Varchar/Text 255 Password Varchar/Text 255 Login Number Integer 32 767 Username Varchar/Text 255 Login Time Date/Time N/A Logout Number Integer 32 767 Username Varchar/Text 255 Logout Time Date/Time N/A Product ID Integer 32 767 Product Name Varchar/Text 255 Product Price Decimal/Currency 11 Product Quantity Integer 32 767 Receipt ID Integer 32 767 Receipt Date Date/Time N/A Receipt Total Decimal/Currency 11 Receipt Amount Decimal/Currency 11 Receipt Change Decimal/Currency 11 Receipt VAT Decimal/Currency 11 Receipt ID Integer 32 767 Product ID Integer 32 767 Product Name Varchar/Text 255 Product Price Decimal/Currency 11 Product Quantity Integer 32 767 Receipt ID Integer 32 767 Cashier Name Varchar/Text 255 Receipt Date Date/Time N/A Company Sales Decimal/Currency 11 Company Expenses Decimal/Currency 11 Company Profit Decimal/Currency 11 COMPANY REPORT RECEIPT DETAILS EMPLOYEE BACKGROUND EMPLOYEE LOGIN EMPLOYEE LOGOUT PRODUCT DETAILS RECEIPT CONTENT Table 2.0: Database Tables and Fields
  • 23. Figure 6.0: POS Login Figure 6.1: Administrator Login Figure 6.2: Product List Figure 6.3: Employee List
  • 24. Figure 6.4: Password Change (Administrator) Figure 6.5: Product Update Figure 6.6: Company Sales Report Figure 6.7: Employee Registration
  • 25. Figure 6.8: Employee Login Figure 6.10: Calculator Figure 6.11: Print Preview Figure 6.9: System Operation Figure 6.12: Employee Attendance
  • 26. • 5.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)
  • 27. TEST CASES TEST PROCEDURE EXPECTED RESULTS STATUS DATE TESTED (DD-MM-YY) DATE FIXED (DD-MM-YY) Administrator Login Administrator provides a valid password. Administrator should be able to access the Admin Window. PASS 06-01-14 06-01-14 Administrator provides an invalid password Administrator should not be able to login. PASS 06-01-14 06-01-14 Administrator provides a blank password Administrator should not be able to login. PASS 06-01-14 06-01-14 Employee Login Employee provides a valid username and password. Employee should be able to access the Employee Window. FAIL 11-01-14 19-01-14 Employee provides an invalid username and password. Employee should not be able to login. FAIL 11-01-14 19-01-14 Employee provides a blank username and password. Employee should not be able to login. PASS 11-01-14 11-01-14 Employee Registration Employee provides valid background information of himself/herself. Employee should be able to successfully register his/her account. PASS 12-01-14 12-01-14 Employee provides invalid background information of himself/herself. Employee should not be able to successfully register his/her account. FAIL 12-01-14 17-01-14 Employee provides blank background information of Employee should not be able to successfully register his/her FAIL 12-01-14 17-01-14
  • 28. Administrator Password Change Administrator provides a valid old and new password with a valid password confirmation. Administrator should be able to change Administrator password. PASS 18-01-14 18-01-14 Administrator provides an invalid old and new password with an invalid password confirmation. Administrator should not be able to change Administrator password. PASS 18-01-14 18-01-14 Administrator provides a blank old and new password with a blank password confirmation. Administrator should not be able to change Administrator password. PASS 18-01-14 18-01-14 Add Product Administrator provides a valid product name, product price, and product quantity. Administrator should be able to add a product in the database. FAIL 20-01-14 22-01-14 Administrator provides an invalid product name, product price, and product quantity. Administrator should not be able to add a product in the database. PASS 20-01-14 20-01-14 Administrator provides a blank product name, product price, and product quantity. Administrator should not be able to add a product in the database. PASS 20-01-14 20-01-14
  • 29. Edit Product Administrator provides a valid product name, product price, and product quantity. Administrator should be able to edit a product in the database. FAIL 23-01-14 25-01-14 Administrator provides an invalid product name, product price, and product quantity. Administrator should not be able to edit a product in the database. FAIL 23-01-14 25-01-14 Administrator provides a blank product name, product price, and product quantity. Administrator should not be able to edit a product in the database. PASS 23-01-14 23-01-14 Remove Product Administrator selects an existing product and removes it. Administrator should be able to delete a product item from the database. PASS 26-01-14 26-01-14 Add Employee Administrator provides valid background information of the employee. Administrator should be able to add employee. FAIL 27-01-14 31-01-14 Administrator provides invalid background information of the employee. Administrator should not be able to add employee. PASS 27-01-14 27-01-14 Administrator provides blank background information of the employee. Administrator should not be able to add employee. PASS 27-01-14 27-01-14
  • 30. Edit Employee Administrator provides valid background information of the employee. Administrator should be able to edit employee. FAIL 01-02-14 03-02-14 Administrator provides invalid background information of the employee. Administrator should not be able to edit employee. FAIL 01-02-14 03-02-14 Administrator provides blank background information of the employee. Administrator should not be able to edit employee. PASS 01-02-14 01-02-14 Remove Employee Administrator 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. PASS 03-02-14 03-02-14 Product Selection Employee 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. PASS 05-02-14 05-02-14 Employee selects a non-existing product by Employee should not be able to automatically view its corresponding product name, product PASS 05-02-14 05-02-14
  • 31. Purchase Number Input Employee 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. FAIL 08-02-14 13-02-14 Employee 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. FAIL 08-02-14 13-02-14 Add Receipt Item Employee 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.. FAIL 15-02-14 16-02-14 Remove Receipt Item Employee selects the added purchased item and removes it. Employee should be able to delete the purchased product from the receipt. PASS 15-02-14 15-02-14 Print Receipt Employee selects a printer and prints the receipt being Employee should be able to use a printer FAIL 23-02-14 27-02-14
  • 32. Cash Computations Employee 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. PASS 15-02-14 15-02-14 Employee 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. PASS 15-02-14 15-02-14 Save Receipt Employee saves the purchase history as well as the products purchased (product information included) along with its cash calculations Employee should be able to save the receipt information and the receipt details in the database and generate a receipt preview. FAIL 16-02-14 23-02-14 Display Employee Attendance Employees 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. FAIL 01-03-14 03-03-14 Display Company Sales Report Employees must save the receipts after every customer purchase transaction. Both Administrator and Employee should be able to display the company’s total sales, expenses, and revenues. FAIL 04-03-14 06-03-14 Table 3.0: Test Cases
  • 33. • 7.1 HARDWARE REQUIREMENTS i. Any PC, Desktop, or Laptop with pre-installed Visual Basic and Microsoft Access applications. ii. Printer • 7.2 SOFTWARE REQUIREMENTS i. Visual Basic 2012 Express Edition for Windows Desktop ii. Microsoft Access 2007/Microsoft Office Access 2010 iii. Windows 7/Windows 8 Operating System • 7.3 HUMAN RESOURCE REQUIREMENTS i. Employees – cashiers ii. Administrator – senior management official/senior human resource official
  • 34. Week1(6-11) Week2(12-18) Week3(19-25) Week4(26-31) Week1(1-8) Week2(9-15) Week3(16-22) Week4(23-28) Week1(1-8) Week2(9-15) Week3(16-22) 1 RequirementsGatheringandDefinition 1.1 DeskReseach 1.2 DefiningObjectives 1.3 DetermingtheSignificance 1.4 AssessingtheScopeandLimitations 1.5 Survey 2 DesigningandBuildingthePrototype 2.1 CreatingDatabaseTablesandRelationships 2.2 ConnectingDatabaseServers 2.3 CreatingProcessDiagrams 2.4 SystemCoding 2.5 SystemTrappings 3 EvaluationoftheSystem 3.1 TestingofthePrototype 3.2 ReviewoftheDocumentation 4 RefinementofthePrototype 4.1 ReassessingtheSystem 4.2 AdditionofTrappings 4.3 RevisionoftheDocumentation WBS TaskName January February March 2014 Figure 7.0: GANTT CHART

×