Transcript ppt

Design Exploration of an Electronic
Honor System
Irma Rachmawati
Ann Sakata
Young-Mi Shin
Overview
Operational Concepts
System and Software Architecture
System Requirements
Lifecycle Plan and Feasibility
Elevator Pitch
 Old-You is a CS undergrad. She was working
late into the night in the labs. Her desire for a
Diet Dr. Pepper lures her to the lounge. She
finds to her dismay that she is lacking correct
change. Being an honest student, she digs out
45 pennies and nickel from her pocket and
guiltily puts the coins in the Visual Studio box.
Now, had little Old-You had the option of using
an electronic system, she could have saved both
herself and the ACM treasurers much grief by
tracking her expenditures with her husky card
and placing bills into the box at her convenience.
Operational Concepts: Objectives
 Reduce cash handling
No need for exact change
Desirable for ACM treasurers
 Easier than paper system to
use/maintain
 Convenient for users to track
expenditures
What Will Work?
Card readers?
No
• HFS regulations
Web interface?
No
• Slow and cumbersome
Cue Cats!
Yes!
• Fast & Easy to use
• Anonymous
System and Software Architecture
 Cue Cats
 Client interfaces to database
 Barcode interpreter software
 Database tracking
Anonymous user accounts
Current user balances
System and Software Architecture (cont’)
ACM Officers
Consumer Web
Interface
Consumer Cue Cat
interface
Consumer Web Interface
 Anonymous (only barcode numbers!)
 Users able to check account balance
 Feedback/Food Request form
 Option to request withdraw from system
ACM Officers
Password protected access
Withdraw users from system
Track/update inventory
Consumer Cue Cat Interface
 Station in Lounge
equipped with
Cue Cat
 Users scan card,
product
 User session ends when
scanning card or session times out
 Barcodes available to add funds to account
CCC Interface (…continued)
Who would use it?
Students
The ACM Coke Closet
-wouldn’t be replacing old method,
just existing in parallel
Summary
Electronic system more
efficient/convenient
Complete implementation reasonable
within ~6 weeks