Job Fair Pervasive Computing System http://seniord.ece.iastate.edu/dec0912/ Members: Adam Lee, Kartik Subbu, Nick Oakman, and Gabriel Semonis Advisor: Professor Daji Qiao

What We Will be Covering Purpose Proposed Solution Design Layouts Hardware Software Interface Risks and Challenges

Purpose “How many people here actually know where they’re going?”

Purpose “Are you making the most of your time at the career fair?”

Purpose To develop a pervasive system to help students managing their time better while at the job fair by picking out the best booth to go to based on Line length/Congestion Employer/Student requirements Student job preferences/filters

Proposed Solution Create a system where students can “check in” at booths to inform system that he/she is waiting in that booth’s respective queue Inform students in which order they should visit booths if they want to save time

How do we go about this? We design a system where each employer uses their laptop which is connected to our server through the internet. Each booth will receive a card reader for which students will swipe and “check-in”. Students query the server through either a terminal or by phone message to determine where they should go next. Other features that may be implemented for check in include pulling information about the student onto the employer's laptop such as their resume etc.

Original Idea –Terminal System This is the coliseum, you will scan your card to get your tag, use the that tag at the employer booths to indicate you are checked in to those terminals. To access data you scan cards/tags at terminals which print out a list of where to go next.

The Problems/ Benefits of Terminal System Updating is not real-time, each person has to physically go back to a terminal to update his list Using paper May get crowded Available to everyone in the coliseum Easier to implement

Second Idea Update through text messaging instead of terminals

The Problems/ Benefits Disruptive (how to make sure everyone’s phone isn’t making noise) Cost on the receiver side Each person would have to give their cell information Both active/passive systems possible Pervasive as almost everyone has a cell phone More dynamic and real-time

Tentative Solution A mix of terminals and text messaging service. In this way we lower congestion at the terminals while allowing paperless real-time notification

The “Check-In” Quandary What will we use to identify students ISU Card RFID Card/Tag

The Problems/Benefits of ISU Card Security issues ISU Card services is “doubtful” whether we can use the cards or not More physical effort to swipe and re-swipe if errors Employers need to use our software (more security risk) Pervasive as students using our system has an ISU Card Cheaper to implement than RFID Card already needed to get information at Career Fair

Biggest Problem of All Proprietary System run by Simplicity Blocked by ISU Card services based on legal / privacy issues

The Problems/Benefits of RFID Card Everyone needs a one, not as pervasive as ISU Card Expensive to buy readers for each booth Only contains information we need (less security risk) Easier to check in Possibility to detect multiple RFIDs in certain range ISU Lab available for use

Software Client/Server system for check-in/out and text messaging Best fit algorithm for deciding employer visit order Employer’s interface for use on their laptops On-board program Web-interface Terminal printing *Note not all of these will necessarily be implemented in the system

Interface Interfacing between the hardware and software components will need use of a certain protocol Possible options include TCP/IP, SMS Protocols come at a later stage of the design process once the basic hardware and software components are figure out. Employer – Card Reader interface

Plan Decide components we should/can use Research topics Topics will depend on which implementation scheme we can go with Design the system Verify system meets clients demands Assess financial feasibility Get Expert Feedback Create prototype system

Risks and Challenges Overcoming cost Implementing the system Coordination Team member leaves Too much work Time management