1 / 6

Can’tTouchThis

This update highlights the progress in developing a laptop anti-theft device, including the completion of the desktop interface and ongoing work on RFID communication. Test cases for various use cases, performance tests, and the testing process are discussed. Anticipated difficulties and lessons learned are also mentioned.

ymoore
Télécharger la présentation

Can’tTouchThis

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. Can’tTouchThis JSM Hammer Jun Wei Chuah Shihong Ng Ming Yang Koh

  2. Test Cases • Project Concept: Laptop Anti-theft Device • Status Update: • Currently working on getting the RFID to communicate with the T-mote (certain voltage issues to sort out) • Desktop interface complete (with password screen) • Project Test Cases (Testing the use cases): • Startup (Devices start up without errors) • User moves laptop (Nothing should happen) • User leaves laptop (Arming of device) • Thief moves laptop (Alarm rings) • User returns to laptop (Disarming of device) • Shutdown (Devices shutdown properly)

  3. Performance Tests • Degree of movement • Important to distinguish between subtle movements and theft • Test: Various movements around laptop, check correct identification of theft • Response time before buzzer sounds • When theft is detected, important to sound buzzer in a timely manner • Test: Move laptop in armed mode, check that buzzer sounds in no more than 500ms (500ms X 100m/10s = 5m) • Password security • Password must be resistant to cracking • Test: Look for loopholes in password system (some form of white-box testing) • RFID / Disarming range • User’s presence must be detected from a suitable distance • Test: Tester moves into close proximity with the device (no more than 50cm), check that user’s presence is detected

  4. Testing Process • Usage of checklists for testing • Useful for checking degree of movement and RFID range • Useful for checking password security • Usage of software tools in testing • Software timers for response time calculations (correlate with hardware timers for accurate timings) • Testing under heavy conditions • Testing RFID range in area with several RFID readers or tags • Testing with non-user RFID tags

  5. Looking Ahead • Anticipated Difficulties • Ambiguity with regards to significance of movement • RFID functionality still a blur, might switch to Zigbee modules for authentication • Thankfully, most of our test cases are pretty straightforward • Might include testing with errors to ensure functionality • Lessons learnt in testing • As mentioned before, degree of movement test is still rather shady • Difficult for author of code to check correctness (password security)

  6. Questions? Anyone?

More Related