1. Capstone Project Vista Game Logs Sponsor: Jerald Block John Van Drasek Tony Kautz Priya Pitla Desiree Mijares Ryan Hieber

2. Overview Dr. Jerald Block The study of compulsive computer use. Vista creates logs of game use. Our program –Collects this log information. –Sends it to the researcher. –Puts the information into a database.

3. Background Current research data gathered is inaccurate. Currently data is gathered by: –Recall –Self Diary Our software increases data accuracy. It is: – Automatic – Accurate to the second

4. Game Log Information Information we gather: –Game start and end times –Game ESRB rating –Game Name –System startup and shutdown times –Screen saver start and duration

5. Vista Game Logging Features –Game Logs – New Windows Parental Control(WPC) features in Vista –Upload Game Logs – Send log file to researcher server –IIS – Web server –ASP.NET – Server side scripting –SSL – Security –Upload.aspx – Server side script –MS Access – Database, UI, Reports

6. The Architecture of the System Researcher Application Participant Application SSL Access Database Upload.as px SSL IIS ASP.NET Internet Researcher Participant

7. File Edit View Settings Participant Application Game Logs –WPC crimson channel –WPC event system logs –Events. GameStartEvent()... WPC Crimson Channel WPC Event System Log Event Viewer GameStartEvent(): Game started at 11:00pm 10100011001100

8. Participant Application Upload Game Logs –Upload file to server without user interaction/confirmation –WebClient object supports HTTPS –UploadFile(uri,”POST”,logFile)

9. Researcher Application Internet Information Server(IIS) –Allows remote users ability to POST files –Firewall settings configured to allow SSL traffic on port 443 How to get it to work: –Default IIS installation and configuration

10. Researcher Application ASP.NET : –Allows remote users ability to execute server side scripts Server side file input and output Database operations open, update, etc. How to get it to work: –Register IIS as program to use ASP.NET –Register the aspnet_isapi.dll

11. Researcher Application SSL –Allows the ability for data to be sent over a secure channel. How to get it to work: –Generate CSR from IIS –Submit CSR to certificate provider to get a.cer file –Configure IIS to use the certificate

12. Researcher Application upload.aspx script –Archive incoming log file to server file system –Load data from log file into database How to get it to work: –Put script in web folder on server

13. Researcher Application MS Access –Database –User Interface –Report Generation

14. Database Create a new study project. Add/remove new families and family member for studies. Schema

15. schema

16. Generate reports Subject categories for the statistic: Criteria: age (high/low), sex, start date, end date, period of time, and game hours, Compute Average and variance for the following Variables: 1.Computer Start up time (daily) 2.Computer shut down / hibernation time (daily) 3.First game start up time (daily) 4.Last game shut down time (daily) 5.Total time gaming (daily)* 6.Total game launches (daily)* Cutoff time and metric time

17. Product Demo Now we are going to Demonstrate the Application

18. Sponsor Feedback Generally happy with the resulting application and its functionality –While we were unable to add all the hoped features many of the features (easy install) were implemented Could have used him as a source earlier in the process –As we ran into difficulty, consulted him and used his influence to unblock barriers

19. Development Process Create The Two Core Solutions –Build the sln file for the researcher and participant applications –Create stubs for planned functionality Begin Building Applications –Create Access Database 120 hours –Implement communication 60 hours –Update participant application with features 60 hours –Gather WPC information to populate database 60 hours Estimated hours of effort –120 hours for the database –60 hours for communication –60 hours to complete participant application –60 hours to prepare data for transmission to researcher Actual effort –120 hours for database –90 hours for communication –90 hours to complete participant application –120 hours for data

20. Future Features Automate the uninstall process of the application –One of the few alternate features time did not allow to be implemented Encode/Encrypt Data on Client Machines –Plain text data may allow undesired functionality that might disrupt the study

21. Project Load Divided Priya Pitla –Build Database/Schema –Create Reports Desiree Mijares –Build Database/Schema –Create Reports Ryan Hieber –Database propagation script John Van Drasek –Communication –Client Installers Tony Kautz –Researcher Installers –Report Compilation

22. Lessons Learned The use of a source control –Thought we would not need one –Helped to better organize our information Difficulty of seemingly easy tasks –Enough work-hours or personnel on particular parts Assume information/tools available work without verifying –Verify tools meet our needs early in the development

23. End Thank You