Blog Posts

Blog Post #27

FDR Video
Double Jeopardy FDR Poster

Last week marked the IPPD’s final event, the Final Design Review. The event was very well planned and included interesting panelists and lost of fantastic food. Beyond this, the event allowed us to showcase our work in front of representatives from Raytheon Technologies. It was very satisfying to hear how excited they were to see our progress. In addition to giving our project presentation, we also had a fantastic time demoing our program with FDR attendees and watching all of the other teams’ videos. Since this is our final blog post, we’d like to thank you for following us through our IPPD journey! We hope you enjoy the final versions of our project’s poster and video attached above.

Blog Post #26

Screenshot of a Scene from Our FDR Draft Video

This week in IPPD, we listened to guest speaker Mark Sanders from our project sponsor,  Raytheon Technologies. The talk was titled “From College to Career – Success Tips for the New Engineer” and discussed a variety of tips for new college graduates like ourselves. The talk was extremely interesting and Mark served as an excellent resource for asking career related questions. Beyond this, we created a draft video for our Final Design Review, which is now right around the corner. We presented our video in class and received valuable feedback that will be used in the finalization of our video. The event itself was a lot of fun and all of the other team’s videos were fantastic and very entertaining. Moving forward we will continue wrapping up our project and preparing for FDR. Stay tuned for more progress!

Blog Post #25

Modified User Registration for Better User Experience

This week in IPPD we listened to guest speaker Dr Elif Akçali, Associate Professor in Industrial & Systems Engineering, who talked about storytelling. The presentation was extremely engaging, interactive, and did a great job at teaching us to tell stories better. Beyond this, we made great progress in the development of Hacker Jeopardy. First ,we completed the implementation of custom theme changes for the game board. Additionally, we were able to implement some of the feedback received during Prototype Inspection Day to make our user and team registration process more user friendly (pictured above). With this new change, users registering accounts for themselves and for teams can see whether or not their password will be accepted by the game. This is a massive upgrade and will severely reduce the number of times users fail to register accounts and teams. Lastly, we were able to conduct in person user testing using students from our coach’s class. The feedback received during this event will help us make final refinements to the game before focussing our efforts on our FInal Design Review. Stay tuned for more progress!

Blog Post #24

Main View for Demo
Working Team Chat

This week in IPPD, we presented a demo of Hacker Jeopardy at Prototype Inspection & Test Evaluation Day. The event was extremely useful and helped us identify a few key areas that can easily be modified to greatly improve user experience. Beyond this, we received valuable feedback and many fantastic suggestions we are strongly considering implementing. One such change would be implementing a mechanism to let users know if their password meets the game’s requirements in real time. This will make account registration substantially more user friendly, solving one of our most annoying user experience problems. Moving forward, we are looking forward to continuing work on our project and beginning to prepare for FDR. Stay tuned for more progress!

Blog Post #23

First Iteration of Custom Theme/Background Change (Mario Bros Theme)

This week in IPPD, we began preparing for Prototype Inspection & Test Evaluation Day. Our current plan for this event is to show off our progress on Hacker Jeopardy 2.0 and demo all of the new features we have been implementing over the course of the semester. More specifically, we will primarily be showing off our completed User & Team login and working in game team chat. Additionally, we have been tasked by our liaison to implement custom game themes and backgrounds as an admin setting in Hacker Jeopardy. As we near completion on these two major milestones, we are excited to show off our work and receive useful feedback that will help in the successful completion of our project. Stay tuned for more progress!

Blog Post #22

Finished Team Joining / Registration Page

This week in IPPD, we listened to guest speaker Dr Denise R SImmons who discussed leadership in engineering. The talk was very informative and discussed various valuable topics such as the distinction between leadership and management. Outside of class, we have continued making progress with the augmentation of Hacker Jeopardy. This week, we have finalized the design for the team joining and registration page (pictured above). Moving on, our next major area of focus will be the implementation of game chat. This week, we have also made progress with implementing backend message reading for game chat. Stay tuned for more progress!

Blog Post #21

Team Chat Box Early Development (1/2)
Team Chat Box Early Development (1/2)

This week in IPPD, we presented our progress at the QRB2 event. The presentation went smoothly and this event provided us with insightful feedback. Outside of QRB2, we have made great progress on Hacker Jeopardy 3.0. First, we have finished styling the team joining page using CSS. As a result this page is now completely finished and we can focus all our attention on completing the implementation of tema chat functionality. Additionally, we have begun implementing the front end of our chat box, as is pictured above. Moving forward we will be continuing the development of both the frontend and backend for the team chat in addition to looking into implementing suggestions from our liaison. Stay tuned for more progress.

Blog Post #20

Final Screen of Team Joining Page (Team Join Without Password)

This week in IPPD, we listened to guest speaker Yvette Carter, who serves as the Chief Inclusion Officer at Gainesville Regional Utilities. The focus of the discussion was on implicit bias or biases that we didn’t even know we had. Thanks to Mrs Carter, we were able to learn different types of biases and how to identify some of our own. Beyond this, we have completed all of the HTML and Backend functionality of the team joining page. As it currently stands, the application now allows the creation and login of both individual users and teams. Additionally, we have also begun working on implementing our team chat functionality. Lastly we have been preparing for QRB2 and are excited to showcase our progress and receive feedback on our work.

Blog Post #19

Team Login Page Wireframe

This week in IPPD we continued working on implementing our new team joining page and began researching the implementation of an in-game chat box. The concept above pictures a wireframe prototype for the team joining page generated earlier this week. While the backend for this page is completed in its entirety, we are still working on combining this with our frontend. Beyond this, we have been researching how to implement a chat room inside of an existing web application. This feature will prove to be the most difficult to implement as the resources pertaining to writing a web based chat room using CherryPy are extremely sparse. Lastly, we ran a security analysis on our code using PyCQA/Bandit. The results showed us specific in-line functions that could be maliciously targeted. With this information, we can now look at those functions and make changes to improve program security.

Blog Post #18

*Very* Early Look Into the Development of New Team Joining Page

This week in IPPD we continued working on implementing our new team joining page. The concept above pictures a raw html prototype for this page generated earlier this week. The new page will contain a team name and password login option as well as the ability for users to join existing teams by clicking a button next to that team. Beyond this, we have implemented a unit testing framework in our project. This will allow us to write unit tests that will be used to ensure the integrity of data being pushed or pulled from the database. Additionally, we are researching the use of PyCQA/Bandit for code security analysis. While useful in finding potential security issues, we will need to deduce whether or not the tool will help our project specifically. If we find that there is benefit in the tool’s use, we will begin using it immediately.