Team Everest – SRD Review From:

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

Product Services and Summary

Environments 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

User learning online.

Attention tracking activation dialog

User getting bored…

Attention getter.

External Interface

Data Flows

Customer Requirements 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.

Localization Requirements

Marketing and Sales Requirements

Administrative and Development Requirements Meetings Applicable Constraints Engineering Notebook Member’s role Google Code Coding Standards Code Reviews MS Project

Quality Assurance & Safety Requirements Component Testing Compatibility Testing Acceptance testing No exposed wiring The mind flex equipment must be kept sanitary 536_c3a74a1bc3.jpg

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.

Support Requirements Support Ends Dec 2011 User Manual Design Documentation

Performance Requirements Speedy Limit length of attention getter Prevent Unnecessary Distractions

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

Exception Conditions and Handling Loss of Internet Connectivity Intentional/Unintentional Removal of EEG Webcam/EEG unplugged

Early Subsets and Implementation Priorities Must Have’s Calculate Results in Real Time Low Response Time Minimally Invasive Can Run on an Average Computer Low Amount of Notifications

Foreseeable Modifications and Enhancements RCkuI/AAAAAAAAAKI/cf5ZLTJHPBA/s1600/browsers-icons.png

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

Design Guidelines Weekly meetings to discuss problems Important code Simple Architecture Design

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

Use Cases

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

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

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

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

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

Sources of Information Sponsor Billy Fortenberry Senior Design Doc Library ocument_Library/Senior_Design_Document_L ibrary.htm ocument_Library/Senior_Design_Document_L ibrary.htm – Team Pegasus – Team Defender

Any Questions?