1 / 18

Design Exploration of an Electronic Honor System

Design Exploration of an Electronic Honor System. Mary Dang Kira Lehtomaki Tanya Peters Irma Rachmawati Ann Sakata Young-Mi Shin. Overview. Operational Concepts System and Software Architecture System Requirements Lifecycle Plan Feasibility. Operational Concepts: Objectives.

candice-bowers
Download Presentation

Design Exploration of an Electronic Honor System

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. Design Exploration of an Electronic Honor System Mary Dang Kira Lehtomaki Tanya Peters Irma Rachmawati Ann Sakata Young-Mi Shin

  2. Overview • Operational Concepts • System and Software Architecture • System Requirements • Lifecycle Plan • Feasibility

  3. Operational Concepts: Objectives • Reduce cash handling Right now, people pay with pennies, nickels, dimes, quarters, and dollar bills for food. It takes around 2 hours for 10 people to count 3 weeks worth of donations. A lot of precious time is wasted in this tedious task. • Easier than paper system to use/maintain

  4. Operational Concepts (…continued) • Convenient for users to track expenditures No need to carry your wallet with you (just your card is needed!) Curious about how many bytes you have left? Just check online! • Provide ACM officers an estimate of inventory and statistics of how fast items go Will ease decision making of ordering products Desirable products, happier people!

  5. System and Software Architecture • Cue Cats • Hardware: cue cat • Software: Implemented in .NET with C# • ACM officers and web service interfaces • .NET with C# • Database tracking • Anonymous user accounts showing current balance • ACM officers showing inventory estimate • Implemented using SQL

  6. System and Software Architecture (cont’) ACM Officers Consumer Cue Cat interface Consumer Web Interface Kiosk

  7. Consumer Web Interface • Users can create and/or login to their anonymous, password-protected account (using Husky Card number and chosen password) Login Create an account

  8. Consumer Web Interface (cont) • Users can check account balance, change their password, leave anonymous feedback to the ACM Officers, or log out of the system.

  9. Consumer Web Interface (cont) • Screenshots Check current balance Change password

  10. Consumer Web Interface (cont) • UMail (a Catalyst tool) will be used as the Anonymous Feed Form

  11. ACM Officers • Password protected access • Withdraw users from system • Track/update inventory • Backup data from database • Send out forgotten passwords

  12. Consumer Cue Cat Interface • Station in Lounge equipped with Cue Cat • Users scan card to begin a new transaction • Barcodes available to add funds to account • Users have options to either add bytes to their account or scan a products • User session ends when scanning card for a second time, session times out, or a different card is scanned

  13. CCC Interface (…continued)

  14. States “s”, “hello”, “byte”, and “UPC”

  15. Error states

  16. Who would use it? • Students • The ACM Coke Closet -wouldn’t be replacing old method, just existing in parallel

  17. What the System doesn’t Do • Does not guarantee the accuracy of of products quantity • Does not guarantee cash donation recorded equal to the actual cash donated • Does not guarantee elimination of counting lower currency denominations (but will most likely reduce time sink)

  18. Summary • Electronic system more efficient/ convenient • Complete the initial development in ~4 weeks • Use the remaining days for testing and any additional features

More Related