Differences

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

--- courses:cs335:spring2019:chemtutor:workplan [2019/04/27 00:03] – [Student User Login] jint
+++ courses:cs335:spring2019:chemtutor:workplan [2019/04/30 21:02] – wilsonj
@@ Line 1: / Line 1: @@
-==== Project ====
+====== Work Plan ======
+==== Set Up and Registration ====
 === Team ===
+The set up and registration page, in it's first iteration, will not be too complex. The front end web page will be built by team members Alex and Mitch and Carter will handle the back end database integration.
 === Design Outline ===
-====== Work Plan ======
+The set up and registration page will be initially created and potentially improved upon down the road if time and bandwidth allow. The first iteration will be an HTML form that collects user data. This page will be linked to from the user login page by a link to set up an account. This HTML form will include a checkbox indicating that the user accepts the site's terms of service. Once the user submits the form with the checkbox checked, the data from the form will be transferred to the back end database and an entry for a new user will be created. This entry will contain all the information they entered, including; a student's name, email address, student number, the school they attend, phone number, and their expected graduation year. This HTML form will be created as a static mockup before being integrated with the back-end server.
+The second phase of the design process is a lower priority but will make the site more usable. Javascript features can be added such as live error checking for password and student ID dissimilarities. Additionally, we will want to check the student ID the user inputs against the W&L or Rollins database, depending on the school, to verify that the user is actually a student.
 ==== Student User Login ====
 === Team ===
@@ Line 54: / Line 58: @@
 === Team ===
-For now, I (Alex W) am the only person working on the practice modules. Because the Practice Modules are low-priority, it is important for other groups to finishes their features first before moving on to this feature. However, I still divided up the different parts of the project in the design outline:
+For now, I (Alex W) am the only person working on the practice modules. The Practice Modules are high-priority because they will help us understand the design of the application as a whole- thus it is important for other groups to finish their features first so we can put a lot of energy into to this feature. This is how I divided up the different parts of the project in the design outline:
 === Design Outline ===
@@ Line 62: / Line 66: @@
   - User Input/Verification: Includes back-end part of what happens when user clicks on an answer (comparing their answer to the correct one, keeping track of correct answers, etc.) and front-end (the appearance of the green check or red x, the appearance of the next button, the final result slide).
 One thing that we will also need to incorporate is multi-step problems. However, I believe that we should first finish the program for just single-step problems and then go back and modify for multi-step problems if we have time.
+==== Graph Exercises ====
+=== Team ===
+Team members: Chris Surran, Roby Mize, and JD Wilson
+  * Work Allocation (SUBJECT TO CHANGE)
+    * Surran - Work on creating static pages and CSS
+    * Mize - Work on retrieving information from python and displaying data
+    * JD - Work on creating forms to track progress.
+The graph exercises are integral to the functionality of ChemTutor, as they provide the exercises that will help users learn. The graph exercises, along with the practice modules, are the hands-on learning experiences that many users will ultimately visit the page for. We can begin to work on the graph exercises immediately, as we have the Python scripts that can generate the graphs correct graphs and do not really rely on any other group to complete another part first. Our graph exercises can be incorporated into the overall application at almost any point, but must work with the data tracking group to ensure their tracker understands how to follow a user's progress on the graph exercises.
+=== Design Outline ===
+  * First, we will need to decide if we want graphing problems to extend the work done on the other practice modules.
+  * Then, we will work on getting a static version of the page completed.
+    * This will include an example question.
+    * Will also need to use css to style the page.
+  * Next, we will work on getting a dynamic version of the page working.
+    * We will need to decide which of the two types of graph problems we will want to display.
+      * Can be done at random or have some other algorithm for making the decision.
+    * Then we will need to choose from question subtypes associated with that category (ie what happens when you change b vs. what happens when you change m?).
+    * Retrieve the selected question from python script and then display graph from said question.
+      * Need to know more about how these are generated before we can proceed.
+    * Make a form that contains the other answer choices and also display the graphs associated with those choices.
+    * Store user response in order to track their process through the module.
+    * Display the users score at the end of the module.
+      * Can include whatever information here that we wish
+        * Which questions they got wrong
+        * What they put vs what was the right answer
+        * % correct
+        * How this compares to their past test results.