Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
courses:cs335:spring2019:chemtutor:workplan [2019/04/26 22:30] – [Student User Login] liur | courses:cs335:spring2019:chemtutor:workplan [2019/05/01 02:43] – [Student User Login] pany | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Project ==== | ||
+ | ====== Work Plan ====== | ||
+ | ==== Set Up and Registration ==== | ||
=== Team === | === 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 === | === 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' |
+ | |||
+ | 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, | ||
==== Student User Login ==== | ==== Student User Login ==== | ||
=== Team === | === Team === | ||
Line 13: | Line 17: | ||
- My Progress Page (Ruinan) | - My Progress Page (Ruinan) | ||
- | Ruinan will explore the various ways ChemTutor can display the progress. He will first look at how other website does the my progress page (self-service, | + | Pan will make the appearance of the login form enjoyable using HTML and CSS. Ruinan will explore the various ways ChemTutor can display the progress. He will first look at how other website does the my progress page (self-service, |
=== Design Outline === | === Design Outline === | ||
- | - **Phase 1: Research** During the first phase, Ruinan will research ways to create pie charts (javaScript pi charts, maybe?). How to connect to the database, and communicating with the registration team to make sure all the information needed is in the database. | + | - **Phase 1: Research** During the first phase, |
- | - **Phase 2: Mock up** In the second phase, Ruinan will create the static mock up for his my progress page. This process includes a static web page that have the various clickable modules. And within each modules, there will be problem set questions. The problem sets are also clickable, but they will only show how a static webpage since it is not connected to the database yet. Ruinan will also create a static pie chart or other displaying tools in this phase. | + | - **Phase 2: Mock up** In the second phase, |
+ | - **Phase 3: Implementation** In the last phase, Ruinan will implement the static mock up pages he has created. And Pan will join to help after her parts. Ruinan will connect the static webpage with the database and display the correct information that is needed. Ruinan will also test the webpage to see whether the information displayed is accurate and correct. | ||
==== Math Formula Presentation ==== | ==== Math Formula Presentation ==== | ||
Line 37: | Line 42: | ||
=== Team === | === Team === | ||
- | We divided | + | Since our project heavily relies on the appearance |
- | * Connor: He will be working on the appearance | + | |
- | * Abhi and Utkrist: Since the back end of the project | + | |
Lastly, all three of us are going to work on improving the final appearance of the periodic table. We will review and analyze everything at the end together as a team. | Lastly, all three of us are going to work on improving the final appearance of the periodic table. We will review and analyze everything at the end together as a team. | ||
Line 46: | Line 48: | ||
=== Design Outline === | === Design Outline === | ||
Our design involves the appearance of the periodic table in the webpage and the integration of the periodic table with various different exercises along with other minor adjustments. We will also be adding the options of user color selection, partial view of the periodic table (individual elements, a single category of elements, or the entire periodic table). Furthermore, | Our design involves the appearance of the periodic table in the webpage and the integration of the periodic table with various different exercises along with other minor adjustments. We will also be adding the options of user color selection, partial view of the periodic table (individual elements, a single category of elements, or the entire periodic table). Furthermore, | ||
- | Our project does not have an exploratory phase since we already have a base to work on. Therefore, for the most part, we will be adding, updating and adjusting the HTML and CSS codes for adding/ | + | Our project does not have an exploratory phase since we already have a base to work on. Therefore, for the most part, we will be adding, updating and adjusting the HTML and CSS codes for adding/ |
+ | |||
+ | |||
+ | |||
+ | ==== Practice Modules ==== | ||
+ | |||
+ | === Team === | ||
+ | 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 === | ||
+ | - HTML/CSS of a slide: Just working on the front-end looks of an individual slide to make sure it matches the examples on the Chem Tudor mock-up. | ||
+ | - Storing Questions/ | ||
+ | - Attaching Question to Slide: Assigning questions to slides, and making sure that they are in random order. | ||
+ | - User Input/ | ||
+ | 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, | ||
+ | |||
+ | === 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. |