1 / 40

Computer Tracking and Managing Software for Matrix Computer Shop

Computer Tracking and Managing Software for Matrix Computer Shop. June 8,2011 Gumaca City, Quezon Province Games and I nternet surfing. June 8,2011 Gumaca City, Quezon Province Games and I nternet surfing. June 8,2011 Gumaca City, Quezon Province

keelia
Download Presentation

Computer Tracking and Managing Software for Matrix Computer Shop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Computer Tracking and Managing Software for Matrix Computer Shop

  2. June 8,2011 • GumacaCity, Quezon Province • Games and Internet surfing

  3. June 8,2011 • GumacaCity, Quezon Province • Games and Internet surfing

  4. June 8,2011 • GumacaCity, Quezon Province • Games and Internet surfing

  5. Org Chart

  6. Customer avails to the current employee for a computer to rent. Business Process

  7. Employee takes note if the user is open time or limited. Business Process

  8. Employee directs customer to the computer. Business Process

  9. Employee records the starting time when the customer starts using the computer. • When time limit is reached or customer declares his/her use to end, employee computes the amount of money to be charged based on the time. Business Process

  10. Customer pays the employee. • Employee records the time and amount of money received. Business Process

  11. Inconsistency of time tracking Problems

  12. Non-technological recording keeping Problems

  13. To monitor the time usage of a customer on each computer. Objectives

  14. To generate the subtotal amount that a customer should pay. Objectives

  15. To record the income of the shop daily for backtracking and referencing. Objectives

  16. Rental agreements - Open Time and Fixed Scope and Limitations

  17. Network connections Scope and Limitations

  18. MD01 – Services Recording Module Register Customer to a Terminal Monitor Terminals Stop Terminal Use Register Additional Service Delete/Edit Service Customer Checkout Modules

  19. MD02 - Price Management Module Edit Cost of Services View Current Cost of Services Generate Text File Modules

  20. MD03– Data Parse Module. Backtrack Generate Text File Modules

  21. Manager/Owner • Terminal and Service Controllers Users

  22. Binary File Data Files

  23. Prices Database • Price Version • Date Revised • Terminal Rental • Black and White Printing • ColoredPrinting • CD Burning • DVD Burning Data Files

  24. Income and Computer Usage Database • Customer Number • Terminal Number • Type of Rental • Time • Additional Services • Price of Unregistered Additional Services • Total Amount of Payables • Price Version Data Files

  25. Financial Report • Frequency of generation • Contents • Price Revision Tracking Report • Frequency of generation • Contents Reports

  26. Use Case

  27. Use Case

  28. Register Customer to Terminal • Precondition: • Main Flow of Events: • User selects which terminal will be rented and determines the rental type. • System will register the customer to the database • System will start the timer, corresponding to the desired terminal, according to the rental type. • Exception Flow: • None Use Case

  29. Monitor Terminal • Precondition: • Main Flow of Events: • System displays the occupied and unoccupied terminals. • System displays the time lapse of each occupied terminal. • System informs the user if a customer's time limit has been reached. • Exception Flow: • None Use Case

  30. Stop Terminal Use • Precondition: Terminal has a registered customer • Main Flow of Events: • User stops terminal usage time • System records time duration of customer usage in database. • Exception Flow: • None Use Case

  31. Register Additional Service • Precondition: • Main Flow of Events: • User adds additional service that a customer avails. • System adds services to the database. • System confirms the user that the service has been successfully been added. • Exception Flow: • None Use Case

  32. Register Additional Service • Precondition: • Alternative Flow: • User chooses a service that is not in the price database. • User inputs the price of the service availed. • System records the service into the database. • Exception Flow: • User Inputs invalid price. • The system informs the user of the error. • The system goes back to the alternative flow. Use Case

  33. Edit/Delete Service • Precondition: There is a registered service availed by a customer in the database. • Main Flow of Events: • User chooses a service to edit or delete. • System does the same revisions in the database. • Exception Flow: • None Use Case

  34. Customer Checkout • Precondition: Terminal has a registered customer • Main Flow of Events: • User checks out the customer from the shop • System generates total amount of payables of the customer. • System records data in income database. • Exception Flow: • None Use Case

  35. View Price • Precondition: Price Database contains at least 1 data regarding a service. • Main Flow of Events: • System shows list of services currently in the database • User chooses from the list of services • System accesses price database and lists • User checks the price description • Exception Flow: • Price database is empty. • System informs user that there is currently no price information in the database. • System goes back to main menu. Use Case

  36. Change Price • Precondition: Price Database contains at least 1 data regarding a service. • Main Flow of Events: • User chooses a service price to change • System accesses database by showing the price • User changes the price of the service • System verifies if the user is sure about the change that is to be made • System confirms the change. • Exception Flow: • None Use Case

  37. Generate Text File for Price Database • Precondition: Price Database contains at least 1 data regarding a service. • Main Flow of Events: • System generates the text file for the price database. • Exception Flow: • None Use Case

  38. View Income • Precondition: There is at least 1 transaction made and recorded in the database • Main Flow of Events: • User inputs the desired sorting criteria (daily, weekly, monthly) • System sorts the income data based on sorting criteria • Based on sorting criteria the user can further sort the data into specific time frames (still based on search criteria) • System outputs desired data corresponding to the specific search criteria Use Case

  39. View Income • Precondition: There is at least 1 transaction made and recorded in the database • Exception Flow: • The income database is empty • System informs user that there is no income to show yet. • System directs user back to main menu Use Case

  40. Generate Text File for Income • Precondition: There is at least 1 transaction made and recorded in the database • Main Flow of Events: • System generates a text file at the end of the day and on-demand • Exception Flow: • The income database is empty • System informs user that there is no income to show yet. • System directs user back to main menu Use Case

More Related