1 / 36

Team Everest – SRD Review

Team Everest – SRD Review. From: http://www.flickr.com/photos/troyismad/89419822/. Team Members. Larry Battle (CSE). Chris Brown (SE). Erica Llaca (SE). Bikash Acharya (CS). http://www.visualphotos.com/image/2x4561402/bored_college_students_sleeping_in_lecture_hall.

jaser
Download Presentation

Team Everest – SRD Review

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. Team Everest – SRD Review From: http://www.flickr.com/photos/troyismad/89419822/

  2. Team Members Larry Battle (CSE) Chris Brown (SE) Erica Llaca (SE) Bikash Acharya (CS)

  3. http://www.visualphotos.com/image/2x4561402/bored_college_students_sleeping_in_lecture_hallhttp://www.visualphotos.com/image/2x4561402/bored_college_students_sleeping_in_lecture_hall

  4. Product Services and Summary

  5. Software side: • Processing • C/C++ • HTML / CSS / JS • XUL • Firefox • Notepad++ • Eclipse IDE • OpenCV • Microsoft Word • Microsoft Project • Google Code • Hardware side: • EEG (such as Mindflex) • Webcam • PC • Microcontroller Environments

  6. User learning online.

  7. Attention tracking activation dialog

  8. User getting bored…

  9. Attention getter.

  10. External Interface

  11. Data Flows

  12. 1) The product will run in real time and have the results without lag. • 2) The software shall process little response time • 3) The product shall have minimally invasive hardware • 4) The product shall track all ranges of concentration • 5) The product shall have little to no notification of concentration awareness • 6) Must run on an average computer system. Customer Requirements

  13. Localization Requirements

  14. Marketing and Sales Requirements

  15. Administrative and Development Requirements • Meetings • Applicable Constraints • Engineering Notebook • Member’s role • Google Code • Coding Standards • Code Reviews • MS Project http://www.slice.ca/BLOG/photos/survival_guide/images/14124/original.aspx

  16. Quality Assurance & Safety Requirements • Component Testing • Compatibility Testing • Acceptance testing • No exposed wiring • The mind flex equipment must be kept sanitary http://farm3.static.flickr.com/2327/2418509536_c3a74a1bc3.jpg http://www.flickr.com/photos/oskay/2418509536/

  17. Standards Compliance and Maintenance Requirements • Senior Design Project Standard • IEEE Std. Source: • Dr. Manfred Huber • Mr. Bill Fortenbery • Previous Senior Design Documents • Senior Design document templates. http://ronsquailityhomecare.webs.com/maintenance.jpg

  18. Support Requirements • Support Ends Dec 2011 • User Manual • Design Documentation

  19. Performance Requirements http://t2.ftcdn.net/jpg/00/10/44/03/400_F_10440370_nOqmQIYQ6eVvabIAlr5ZRPTjCfhBJRlx.jpg • Speedy • Limit length of attention getter • Prevent Unnecessary Distractions

  20. System Constraint Requirements • One Browser • Sufficient Readings from EEG • 2 USB Ports

  21. Exception Conditions and Handling http://www.masternewmedia.org/images/unplugged.jpg • Loss of Internet Connectivity • Intentional/Unintentional Removal of EEG • Webcam/EEG unplugged

  22. Early Subsets and Implementation Priorities http://churmura.com/wp-content/uploads/2010/01/dual-core.jpg • Must Have’s • Calculate Results in Real Time • Low Response Time • Minimally Invasive • Can Run on an Average Computer • Low Amount of Notifications

  23. Foreseeable Modifications and Enhancements http://4.bp.blogspot.com/-zCJJh-eQn4s/TVQcf-RCkuI/AAAAAAAAAKI/cf5ZLTJHPBA/s1600/browsers-icons.png

  24. Acceptance Criteria • Satisfy customer requirements • Approved under CSE 4316 requirements • Customer Accepts final product!

  25. Design Guidelines • Weekly meetings to discuss problems • Important code • Simple Architecture Design

  26. Assumptions • User knows how to operate the application • User reads instructions carefully • Application will never fail • External components will operate without failure

  27. Use Cases

  28. Use Cases (Cont.) Use Case 2: Actor: User TUCBW: User Clicks button TUCEW: Dialog Box appears to user asking to monitor concentration

  29. Use Cases (Cont.) Use Case 3: Actor: User TUCBW: User Clicks “Yes” TUCEW: A changed icon will appear and user will setup user profile.

  30. Use Cases(Cont.) Use Case 4: Actor: User TUCBW: User Clicks “No” TUCEW: Displays dialog box telling the user the application is deactivated.

  31. Use Cases (Cont.) Use Case 5: Actor: User TUCBW: User can click “stop” while attention getter is running in the window TUCEW: User returns to their content

  32. Use Cases(Cont.) Use Case 6: Actor: User TUCBW: User exiting the system TUCEW: Brings them back to home page

  33. Sources of Information • Sponsor Billy Fortenberry • Senior Design Doc Library http://ranger.uta.edu/~odell/Senior_Design_Document_Library/Senior_Design_Document_Library.htm • Team Pegasus • Team Defender

  34. Any Questions?

More Related