Differences

This shows you the differences between two versions of the page.

--- proj [2017/01/31 17:43] – bil
+++ proj [2018/02/27 15:49] (current) – bil
@@ Line 1: / Line 1: @@
+**EECS 2311 Project**
-For an initial description of the project, see the Introduction slides from Week 1, pages 13-16.
+<html><!--
-Further specification will be added here as the project progresses.
+  To be posted.
-<html><!--
+--></html>
-The most critical part of the Simulator is the API it will present to the Player and Authoring app
+Treasure Box Braille (TBB) is a device that helps kids learn how to read Braille.
-This API must be able to be duplicated by the hardware device (its firmware will include a firmware wrapper)
+TBB presents Braille characters/words to the user who then responds by pressing buttons.
-API must be described in detail with Javadoc
+Educators can load different scenarios to teach different letters and keep the kids entertained.
-The best simulator API from all submissions will be chosen going forward
+We will write a piece of software to help educators create these scenarios. We will call it the Authoring App. The Authoring app will provide facilities to
+  * Create the flow of the scenario (ask questions, receive answers)
+  * Record audio
+  * Save the scenario in the appropriate format
+  * Test the scenario using the provided software
-Rubric posted on the course website
+**Important requirement**: The Authoring App must be usable by visually-impaired users
-Four grade components
-Requirements document
+Since there are not enough TBBs for each group (and also because they are expensive and hard to replace), we provide software that simulates the TBB.
-Testing document
+This way, as an educator is preparing a scenario with your authoring app, they can try it out to see if it works. See the Week 1 slides (click on Course Outline) for instructions on how to get the starter software.
-Simulator API
-Implementation
-Create a .zip or .jar that contains the following:
+The starter software contains example scenarios that you can run to get a feel for what this system does.
-All grade components from the previous slide including the code
+{{:startersoftwaredesign.pdf|Click here}} for a UML diagram of the starter software.
-A README.txt that
-Explains the contents of the zip file
-Describes how to access the API in HTML
-Provides a link to your github repository
-Email the zip file to bil@cse.yorku.ca by 11:59pm on Feb 7
+{{:scenarioformat.pdf|Click here}} for a description of the file format for scenarios.
-Only one email per team
-Include your team number in the subject
-Each student must also send me a private email with an assessment of their teammates’ contributions
+**New requirement (added on Feb 27, 2018)**
+Your system must log all actions the user takes and keep count of how many times each feature is accessed
+Based on the log data, add keyboard shortcuts to the most frequently used features. Such features should be easy to access with a mouse as well
---></html>