Skip to content

anushadatta/PizzaRush

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

98 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

PizzaRush

Pizza Rush is a native mobile (iOS & Android) application that aims to allow students and teachers to be able to socialize teaching and learning of courses through an enjoyable game.

It provides a platform that allows students to learn and compete with one another through challenging educational content. Teachers will also be able to assess mastery of the course via data analytics and automated grading obtained through the player’s history of accomplishments in the game, in a comprehensive and continuous way.

Features Overview

Pizza Rush is designed as a dual user application, with its targeted users being students and teachers. It provides different functionalities to each of its users accordingly, as has been elaborated below.

STUDENTS

View Player History

  • The student can view their past performance in each math section in the form of a line chart (Y axis: points, X axis: Time).
  • The student can view current point accumulation and upcoming grading deadlines for each math topic.
  • The student can view their past grades for each section for each past deadline.
  • The student can access the grading rubric, using which the points to grades conversion is determined.

Select Math Topic The student can select the any math section they would like to solve questions from. Currently PizzaRush supports 3 topics (Algebra, Trigonometry and Geometry).

Select Level of Difficulty The student can solve questions of varying difficulty levels (Easy, Medium, Hard) within any chosen math section. The following levels can only be unlocked when played in order: Easy -> Medium -> Hard.

Buy Hints While playing the game a student may buy a hint using points, to help solve a particular question. The number of points required to buy a hint is variable, and depends on the points per hints scheme as below.

Difficulty Level Points Deducted per Hint
Easy -30
Medium -60
Hard -90

View Leaderboard The student can view all students enrolled in each Math topic category (Algebra, Trigonometry or Geometry), in descending order based on their points’ scores. The leaderboard is dynamically updated as students progress through the game - by solving questions or buying hints.

Challenge Friend The student can challenge a friend, as long as they too are players on this platform. The challenge can be specific to a math section (Algebra, Trigonometry or Geometry) and selected level of difficulty (Easy, Medium, Hard).

TEACHERS

Add Questions The teacher can upload questions for the students to solve according to a pre-designed questionnaire template.

View Course Performance Summary The teacher can view the summary statistics generated by the application in the specific math topic categories (Algebra, Trigonometry or Geometry) for the entire class. The data analytics performed on students' performances will include:

  • A line chart with the Progression of the Average Score of the class over time.
  • Mean, Median and Standard Deviation of class scores on each assignment, with assignment date.

View Leaderboard The teachers can view the same leaderboard that is available to the students, but are not allowed to modify or influence it.

COMMON FUNCTIONALITIES

Authentication The Student or Teacher can login to the PizzaRush application by entering their username and password. The user domain (student/teacher) shall be automatically determined upon login, and does not need to be explicitly stated.

Grading System

  • The student shall be graded based on the active involvement in playing the game - which will be quantitatively measured by the points accumulated, individually for each section.
  • There shall be a grading deadline set for each math topic, which is entitely upto the discretion of the teacher.
  • The points accumulated in that math section by that deadline shall determine the grade based on the grading rubric available to the student.
  • The points accumulated in that math section shall be reset to 0 once the deadline has elapsed, and the grade has been decided. After which, a new deadline may be introduced.
  • The deadline shall be renewed regularly at the teacher’s discretion.

Solving Questions

  • The student is able to select the math topic and difficulty level for which they wants to solve questions for.
  • The difficulty levels must only be accessed sequentially, and are locked from access until a certain point threshold for that section is reached.
  • The student will see a story context for the question before the question is displayed, which will introduce the game aspect.
  • There is a story context for each individual question.
  • The story context shall consist of a game world and character, which is randomly assigned to a user, and changes with every question.
  • The user must then be directed to the question screen, which consists of a question, 4 answers and a hint option. The question shall build on the sotry context and may be MCQ, interactive numerical or interactival area based.

The points earned per questions answered by the user shall be determined by the points ruberic below:

Difficulty Level Points Awarded per Correct Answer Points Deducted for using Hint Points Deducted for Incorrect Answer
Easy +10 -30 0
Medium +20 -60 0
Difficult +30 -90 0

Challenging Friends

Sending challenge

  • The student can challenge another user in a specific math section and at a specific difficulty level of their choice.
  • A custom challenge is created for the player to attempt.
  • The challenge questions must be answered with a running timer, and without any hints.
  • The student can view their score and time for the challenge once the challenge is completed.
  • The student can then choose to send the same challenge(identical set of challenge questions) to another player by selecting the user from a drop down menu.

Accepting challenge

  • The student can view the challenges received from other players.
  • The student can choose to accept or decline received challenges.
  • If a challenge is accepted, the student is presented with the same challenge questions to solve as those solved by his/her challenger.
  • At challenge completion, the student is presented with his/her score and time for the accepted challenge, and the challenge outcome - WIN/LOSS.
  • The WIN/LOSS outcome is determined by a points/time ratio of his/her performance as compared to that of the challenger’s.
  • The challengee’s score and outcome of the challenge automatically be shared with the challenger.
  • The student can further challenge another player if he/she wishes to do so.

View sent challenges

  • The student can view all previously sent challenges.
  • The student can view whether the challenges have been accepted or declined.
  • If the challenge has been accepted, the student can able to see the challenged user’s score and WIN/LOSS outcome of the challenge.

ADD QUESTION

The teacher can upload questions for the students to solve according to a pre-designed questionnaire template. The questionnaire template consists of the following components:

  • Select math topic
  • Select difficulty level
  • Select game world
  • Select Characters
  • Write context story
  • Write questions (Option available to add media attachment)

Usability Requirements

Based on Shneiderman's Eight Golden Rules of Interface Design, the key considerations to enhance usability of the application are:

  • Reduce short term memory load: The implementation of navigation bar helps users navigate seamlessly through the features.
  • Permit easy reversal of actions: The user can return to their previous state through the use of a back button.
  • Internal Locus of Control: Defined buttons and titles for each feature of the system help make navigation and task activation clear for users.
  • Strive for consistency: A consistent layout of the features is achieved using similar font, color and search buttons.

Documentation

Component Diagram

Data Flow Diagram

Dialog Map

For more reference and deeper understanding of the project process, feel free to check out the following documentation:

Authors

  • Anusha Datta
  • Mehul Kumar
  • Divvij Chandna
  • Palak Somani

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages