RTX Gamification Classmate System Webpage

Team Gaming Ed.


Project Description

The goal of Team Gaming Ed. is to create a new learning management system for our client Professor Terry Baxter. The reason for creating a new learning management system is to improve student engagement by having an interactive gamified LMS. A course is gamified by making the course feel more like a video game rather than an actual course. Courses these days usually have a boring layout even though students pay a great deal of money. Courses have the potential of having a unique design and feel giving students a refreshing view of their studies. If we gamified a course students who are interested in games would be more likely to succeed. The initial concept for this project was provided by our sponsor which is located here.

High level requirements

Some of the requirements include a desktop application where teachers can create a course and a website application where students can take the course. We are hoping to have a working desktop application by the end of the Fall 2022 semester. The team addressed risks to the project such as security issues so that information is not compromised. The functional, non-functional, and environmental requirements are discussed in detail in our Requirements Specification Document located inside the Archive tab.

Envisioned Solution

Team Gaming Ed's envisioned solution is to design a more elegant learning system to help improve student motivation. Our course will allow course reconstruction by authorized users and be able to handle gamified and non-gamified courses. We want to development a system that can handle any course but feel like a video game if that is what the administrator wants when designing their course. Our envisioned application will have two parts including a desktop application and a website application. The desktop application will be where the teacher creates a course. The website application will be where the student completes a course.


The desktop application will be developed using Unity Game Engine. The website application will be developed using .NET Frameworks. The team will also be using ASP.NET as well as Blazor. Our database will be accessed using PHP and SQL. GitHub is where our code repository will be located for all team members to have access to. We have created a group Google Drive where all team documents are located. We are currently using draw.io as a graphic editor and have not needed anything more powerful up to this point. Team Gaming Ed. has been informed that ITS will need justification to allow for a budget. The team is currently using a free tier AWS subscription which will need to be further evaluated in the Fall in order to keep the website running.

Schedule, resources, budget

Our current mode of handling assignments include putting the link of the document in its own section on Discord. The deadline is marked on each Discord section and each assignment is located in the teams shared Google Drive. These assignments appear in Discord at least a week ahead of time. The Gantt chart below shows the timeline of our gantt chart progress throughout the second semester of project build.



We will be using GitHub for version control. This account will exist in the future as the owner will not delete it, even on a clean-up binge. GitHub repository will be kept private per the mentors request.

Team Information

Grace Hsieh (gmh256@nau.edu)


Role: Team Leader

Stay in close contact with the team members ensuring all aspects of the project are completed accurately and on time.

Handle internal issues within the team.

Has a planned agenda before the meeting and is expected to manage/run the meeting.

Issues concerning a three way tie will be overruled by the team leader after considerable debate.

Role: Customer Communicator

Confirm that the project meets all sponsor expectations and requirements.

Communicate via email with the sponsor and the mentors.

Relay information from sponsors and mentors to team members via discord or email.

Role: Coder

Writing and reviewing code.

Overseeing all code to make sure it is following team standards and meets project requirements.

Brett Lewerke (bdl85@nau.edu)


Role: Architect

Knowledgeable in usage of SQL/ noSQL databases.

Construct file organization.

Enforce proper coding standards are being followed.

In charge of language and back-end being used.

Role: Release Manager

In charge of releasing code to main branch.

Cleans up old branches to ensure cleanliness.

Role: Coder

Writing and reviewing code.

Will be working more on the back-end of the project.

Role: Recorder

Take down meeting notes every week for each type of meeting: sponsor, mentor, and team.

Upload meeting notes after every meeting on discord in the minutes section.

After uploading notes I will ask team members to review the minutes for accuracy.

Chayson Spigarelli (cds427@nau.edu)


Role: Task Report

Create a task report so the mentors can check our progress.

Task reports should be completed before the team meetings on Sunday

Role: Coder

Contribute to coding the website in order to ensure accuracy and reduce load on other team members.

Will be working more on the front-end of the project.


Research future technologies the team could use in the future.

Final Editor

Goes over document before submission to make sure there are no grammatical mistakes in deliverables.

Makes any last minute suggestions to team to improve document grade by reading entire document before submission.



Mini Intro Presentation

A five minute summary presentation that introduced the project to the rest of the class. Goes over how our client connects to our project. Explains the problems with our clients current system. Introduces a solution and a plan for development.

Design Review 1

A ten minute presentation that communicated the current work status to others within the class. Talks about the problem and our chosen solution. Talks about the key requirements that helped the team understand more about the problem and the functionality the system will provide. Talks about the risks and the feasibility of these risks. Briefly goes over the schedule for the project as it stood when the presentation occurred.

Design Review 3

A twelve minute presentation with Google Slides updating the class on our current progress. Sections included but not limited to a prototype review, testing plan, architecture review, and requirements/spec review.


Team Standards

Shared agreement on the expectation of teammates concerning how the team will function. Standards range from assigning specific roles to each team member, to establishing protocols for conduct and communication, to agreeing on what tools the team will use. Establishes a common understanding of expectations and efficient and effective collaboration. Without these norms the team would have difficulty communicating and cooperating since each individual may have a different interpretation of how things should be done.

Team Inventory

Introduced what talent exists on the team and what gaps there might be in the team's capabilities. Gets to know the team members, including some hobbies or special interests. Provides the client with a preliminary overview of the team working on the project. Allows the client to better understand what the team's strengths and weaknesses are and how our client can best support the team. Also provides the team with some knowledge of its collective strengths and weaknesses. This information is instrumental in assigning tasks, negotiating project specifications, establishing design philosophy and strategy, project scheduling, and overall project management.

Technological Feasibility

Identifies key technological challenges and major design decisions that the project presented very early on. Explored approaches and existing products that might be out there. Makes preliminary decisions on which approach the team is going to choose to solve technological challenges.

Requirements Specification Document

Description of our projects requirements such as the functional requirements, non-functional (performance) requirements, and environmental requirements. Also addresses potential risks to the project. Finally this document discusses the project plan going forward from the point of the document finalization.

Communication Strategy Memo

This document entails the strategies the team will be implementing over the semester in order for the team to be successful. Meeting times and places are also discussed for mentor meeting as well as team meetings.

Software Design Document

Document that details the project's overall architectural design as well as the design of each major module.

Capstone Poster

Poster that was presented at the capstone conference on December 2nd, 2022. Team discusses the projects: problem, technologies, structure, and inspiration.

User Manual

User manual meant to help users manage the project such as the desktop application and the website application. Accounts for possible troubleshooting steps in case a user gets stuck using the project.

Final Project Report

Final project report that highlighted key features of the RTX Gamified Learning Management system. Also discussed future work with the project and the architecture implemented in order to meet project requirements.

Team Reflection Document

End of project development where team reviewed the overall project as a whole.



A 2 minute "elevator pitch" video that introduces and sells our product. This link redirects your web browser to the YouTube video.

Design Review 2

Animated video that details why the team is making this software as well as implementation steps the team has taken in order to design and develop the software.

Mini-Video #2

Animated video that details why the team is making this software as well as implementation steps the team has taken in order to design and develop the software. This is the second time the team has made a mini-video and has made an improved version compared to the first mini-video