Blog Posts

Week 18 Post

Chart made in Chart.js made to match the one in the prototype

This week we’ve gone further with the planning the CTF and gathering data from it, we brought this up with both our coach and our liaison to get there thoughts on the details we confirmed so far. We got some excellent suggestions on incentives we could use to get a sizeable number of people to come. We’ll be using these alongside the suggestion from our coach to reach out towards certain UF clubs to ask to both use their space and get their members to compete.

We also have begun testing and implementation of the Chart.js library with the features we are adding to Hacker Jeopardy. The library was exactly what was needed to make the analysis pages work and display the data including the custom icons for each type of data point. This test was done separately from the overall system of Hacker Jeopardy, but the code for the activity log graph is mostly complete. We just need to create a page to hold it and the other analysis graphs which will be our focus.

Week 17 Post

The team just outside the room where we had our QRB

This was the week of our first QRB, focusing on on our plan for the remaining semester. We prepared well for this presentation, gathering all the work we have done so far from planning poker results to the login system being improved. Just gathering all the information together really put in perspective what our next plans should be, and what we’ve accomplished so far. After the presentation we got a lot of good questions on our plans and feedback for the project as a whole, which we will be taking into account during the following months.
In particular we got feedback on the scale of our project, and the feasibility of completing all the requirements, and increasing the degree to which we assign roles in the project. These will definitely be considered and talked about during our next meeting with our liaison. Overall, however, it seems we are on track which is great to know and we’ll be sure to continue researching, developing, and testing to the best of our abilities!

Week 16 Post

Logo for PyCharm the IDE we’re using to make changes and look at the program files

As January reaches its end, we are preparing to showcase our progress in QRB 1. We’ve made great progress already with the project and our objectives. This will include our work on the login systems of Hacker Jeopardy, which has seen some improvements since the blog post, and further research and documentation work. We have made further progress on how we are going to handle the peer testing portion of the project, and how to gather people for it.

The in-class assignment on Designing for X also helped us really find and refine the ideas what we’re working on overall and how to visualize what our goals are. In particular we want to design our parts such that they are easy to further work on and elaborate on. We want to make sure that Hacker Jeopardy continues to be worked on and improved as needed.

Week 15 Post

Cover Page for the “Paper” Documentation of the code

This week we’ve started to get back into the swing of things and begin working on the project more. This includes refining our plans for the semester that we made back in the Fall. We’ve been making plans to get user feedback on both a full session of Capture the Flag/Cyber Jeopardy, and specifically on the login system.  

We’re also gathering data from the source code to make in-depth documentation, that started in the fall. This will include details on imports, exports, variables, what each method and class does. This should make working on the system easier for both us and whoever wishes to work for it in the future. 

Finally, we have also implemented one change to the login system, that being to automatically log someone in after they create an account for the session. This should, of course, make logins much less painless and much faster. 

Week 14 Post – First Week of Spring

The first day in the new classroom

We’re back from Winter Break, ready to begin full development on the project. We’ll be working in a through a multitude of sprints using Agile methodology. We met up in the new classroom for the class and worked on getting reacquainted with what needs to be done this semester, and the schedule. We also have set up a new time for our liaison meetings and our meetings. We hope we’ll be able to fulfill all the requirements and finish the project.

Week 13 Post – Final Post of the Fall

Here we are at the final post of this semester. We’ve made it through all the challenges and problems to showcase at the SLDR. We refined the aspects of our presentation that needed refining and expanded on the report. As the day arrived, we felt prepared to present our ideas to the mixed group of peers and liaisons, even our own liaison Randall. 

Team Cyber Jeopardy after our presentation with our liaison

Ultimately everything went incredibly well! There were some minor technical issues with the clicker for the presentation, but besides that we did our best to provide a good demonstration of our progress so far with our planning for the spring semester and our prototype that uses Figma with the changes made since Prototype Inspection Day. The other groups presentations were amazing as well and there was plenty of interesting information within them. 

Now we’re getting prepared for the Spring Semester where the majority of the work will begin. We’ve already completed two of the requirements, but the upcoming working will go more in-depth into the source code and making the documentation for it. Regardless we’ll be refreshed and ready to take on the challenge provided to make the users of Cyber Jeopardy and Raytheon happy with the overall product. 

Week 12 Post

This is one of the last weeks in this semester, so as part of wrapping up we have been working on the System Level Design Review. This includes both the presentation and the report itself. We’ve done great work on both aspects of the SLDR, including covering the prototype we created for the PID. We also worked on planning aspects for the spring semester. We planned out our Sprints now that we can take into account the progress we’ve made so far. We also got further insight into how we will handle the graphs within the program by using some JavaScript modules such as either “Chart.js” or “d3.js”. There were, of course, other aspects we covered in the presentation and report that we submitted for review this Tuesday.

First slide of the SLDR Presentation

We also presented in the peer review on Tuesday. We were matched up with other software based teams, and they gave us a good amount of review in our presentation style, and were given very interesting questions for our project. All of this is extremely helpful for the upcoming SLDR next Tuesday. 

Week 11 Post

Individual Statistics Page shown at PID
Question Statistics Page shown at PID

The week of the Prototype Inspection Day has arrived! We continued working on the prototype through Figma on Monday after getting some feedback from our Liaison. We added more potential solutions including a user interface for having multiple questions on one point value and selecting between them, statistics based on the questions rather than the teams, and a graph of the team scores over time. We also added statistics on the analysis page that showed how well a student was doing in contributing to their team.  

Ultimately, the prototype inspection day went well with all of us getting a good amount of feedback on places we need to improve. This also included feedback on how we presented the prototype and the pitch we gave, which were greatly appreciated. There are a couple things we can’t change, like the colors in relation to the existing theme in cyber jeopardy but we will do our best to keep these in mind as we keep working on and improving this program. We are all glad that we managed to get this many designs into our prototype and thus get feedback on them. A huge thank you to the judges for helping us improve.

The Team at Prototype Inspection Day

Week 10 Post

During this week of the 11th of November, we’ve been hard at work preparing visuals and in-depth concepts for next Tuesday’s Prototype Inspection Day. Most of this work has gone in to two areas that we will focus on during that day: the student analysis page (which we mentioned in last week’s blog post), and a walkthrough of the Hacker Jeopardy system.

First Mockup of the Analysis Graph

To make analysis simple and easy for admins, we would have to pick a chart for the page that would be easy to read and easy to draw analysis from. We went over many different types of charts, including bar and line graphs, but we settled on a modified dot plot to both show the number of attempts on a particular question, but also the time between attempts. Since the X axis would be in order, it could also show trends within categories. We then made a mockup of this idea as pictured here, which we have further refined into something we will show off specifically on Tuesday.

From there we needed to create a concept for the analysis page as a whole, in order to do this, we used the website Figma which allows for functional prototypes with interactive elements. This will allow us to showcase our designs for the analysis page smoothly with the judges on Tuesday and get feedback on overall design. The important part about using Figma is that we can get feedback on how it “feels” to use rather than just how it looks, since people can actually test out the design.

Screenshot of Figma and it’s connections

Week 9 Post

Now that the Design Review has been approved, we have begun work on the prototype. This prototype will include a mock-up design for the data analysis page of the program. We’ll make sure to keep the original intent of this analysis page in mind. The original intent of course being to monitor individual students to see how well they’re doing; separate from the teams they are a part of.

We’re hoping our designs get a good amount of feedback during prototype inspection day so we can keep adding and building to make this the best program it can be.

As part of entering the implementation/design phase, we’re starting to build upon the functional decomposition to create true documentation for the software going over each function or method in each class of the source code. We can then use this both for presentations and working on the source code.

This doesn’t mean we won’t be adding in-text documentation to the source code though, we’ll all work on those once we get into actually implementing our changes beyond the text chat movement. We’ll also be adding comments to our own code to make it easier for future teams of Raytheon themselves to work on and improve Hacker Jeopardy.

Previous nonfunctional analysis page, hidden in the program