SlideServe
Menu
Préférences
© SlideServe · v2026

Real-Time Concentration Tracking Software Design Review - Team Everest

almira avatar
32 diapositives · 440 Views · Sep 21, 2014

This document presents the architectural design review conducted on September 15, 2011, by Team Everest, which includes members Larry Battle, Chris Brown, Erica Llaca, and Bikash Acharya. The focus is on developing a real-time software product that tracks concentration levels with minimal hardware requirements and near-instant processing times. Key customer requirements emphasize non-invasive hardware, low response times, and usability on average computer systems of that time. Detailed testing plans for sub-layers and logic layers are also outlined.

Real-Time Concentration Tracking Software Design Review - Team Everest - slide 1
01 / 32Real-Time Concentration Tracking Software Design Review - Team Everest
1 / 17

Télécharger la présentation

Real-Time Concentration Tracking Software Design Review - Team Everest
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Team Everest Architectural Design Review September 15, 2011 From: http://www.flickr.com/photos/troyismad/89419822/

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

  3. * Product Summary * Requirements * Layers / Sub-layers * Motivation * Flexibility * Feasibility * Testing Overview

  4. Product Summary

  5. Customer Requirements 1) The product will run in real time and have the results without lag. 2) The software shall process little response time

  6. Customer Requirements 3) The product shall have minimally invasive hardware http://www.blogcdn.com/www.engadget.com/media/2010/09/neurosky-mindwave-01-top.jpg

  7. Customer Requirements 4) The product shall track all ranges of concentration http://static.guim.co.uk/sys-images/Guardian/About/General/2009/6/30/1246373469711/Customers-use-computers-a-001.jpg

  8. Customer Requirements 5) The product shall have little to no notification of concentration awareness http://www.remove-virtumonde.com/wp-content/uploads/2009/04/virtumonde-pop-ups1.jpg

  9. Customer Requirements 6) Must run on an average computer system. http://media.photobucket.com/image/cpu%20magazine%20mods/jordan23james/100_4271.jpg

  10. Question: What are specs for an average computer system in 2011? Image from: http://exonome.com/fj/phkl/open.jpg

  11. Question: What are specs for an average computer system in 2011? Answer:CPU: 2.0GHz dual-core or betterRAM: 2-4GBHard drive: 160GB+Video: 512MB - 1GBOS: Windows XP or better Image from: http://exonome.com/fj/phkl/open.jpg

  12. ADS History

  13. ADS History

  14. ADS History

  15. Overview of Layers

  16. Server Image from: http://www.instablogsimages.com/images/ 2007/01/08/hp-mediasmart-server_48.jpg

  17. Sub Layers

  18. http://hacknmod.com/wp-content/uploads/2009/04/messy-cables.jpghttp://hacknmod.com/wp-content/uploads/2009/04/messy-cables.jpg

  19. Event Handler Sub-layer

  20. Input Sub-layer

  21. Database Sub-layer

  22. Manager Sub-layer

  23. Analyzer Sub-layer

  24. Check Sub-layer

  25. Browser Sub-layer

  26. Question: Which browser do you prefer? http://one7.files.wordpress.com/2010/06/browsers.jpg

  27. Testing for I/O Layer 1) Can the input sub-layer process the input from the external devices within a reasonable amount of time? 2) Can the database sub-layer add, update, delete data from the database? 3) Does the input and database sub-layers sent data to the appropriate location? 4) Does the input simplify the data correctly?

  28. Testing Logic Layer 1) Can the Check Sub-Layer find and report errors? 2) Does the Event Handler send data to the function of the assigned Destination? 3) Do all the sub-layers communicate with the Event Handler correctly? 4) Does the Analyzer sub-layer launch an attention getter event when the user isn’t concentrated for a certain time period?

  29. Testing Controls 1) Can the Browser Sub-Layer communicate with the browser? 2) Are the attention getters appearing on the screen for the designated time? 3) Can the Browser Sub-Layer turn off our program when the browser is closed?

  30. Motivation/ Flexibility

  31. Feasibility http://tamsconcretecanvas.files.wordpress.com/2008/11/obama_yes_we_can.jpg

  32. Any Questions? http://committeeofpublicsafety.files.wordpress.com/2010/02/cute-sad-kitten06.jpg