This week, we completed both the PDR report and presentation. We have both in state that we are all happy with. Using that we traveled down to a Raytheon Facility in Largo, Florida to present alongside the other team. There was a bit of a change in schedule since the Interstate highway was closed earlier that morning, but we still arrived close to the intended time. Once we arrived, we got prepared and gave the presentation in front of various Raytheon employees, including our liaison. The presentation went well, and we received a good amount of feedback for both the presentation, and things we should consider for the future. 

Afterwards, we ate lunch that was generously provided to us by Raytheon, and watched the other Raytheon team’s presentation, which was great. Then finally we took an in-depth tour of the site with both our team and the other team going through parts of the hardware and process of engineering and construction. Unfortunately, no photos were allowed to be taken inside the site, so there are no photos of PDR, but we did take a picture outside with the Raytheon Logo. 

This week, we have used our time to continue the PDR report refinement. We have prepared our plans for the PDR and when we will meet up with Raytheon. We have also prepared the form to get a rental car for the drive down. The driver will be one of our team members most likely. During the meeting with our liaison, we also work out the preferred method of implement the multiple answers per question request. 

We also attended some guest lectures in class, one of which included an employee of Raytheon. In the first lecture we were given advice for after IPPD and the types of attitudes we should strive to have. In one of the other lectures we were given information on scrum and how scrum works, which will be very important for the next stage of the project where implementation will take place. 

This week we have been mostly focusing on preparing the PDR document to be the best it can be. This includes preparing documentation, writing, and revising the document. As part of this we have created and included an analysis of the source code and its internal connections. This is visualized through a flow chart that we included in our PDR Peer Review presentation.  

Also included in the list of items we have done this week is the PDR Peer Review Presentation. This was done on Tuesday, and we are happy with the results. We did realize that there are some things we needed to add to the presentation, and we got some good peer review comments which were mostly positive. Following this, we are using our completed PDR Document graded and commented for more polish. We will then use that to present to our liaison at Raytheon itself. 

This week, we’ve continued work on the learning the source code for Hacker Jeopardy. We’ve gotten the code into a GitHub Repo to both save our work and allow us to all work on the project at the same time. In our meeting with Raytheon, we’ve gone over more of the information such as the IDE we should use for the software. The recommended one was PyCharm by JetBrains.  We are also using our First Month Report as a building ground for the upcoming PDR report Peer review. Since we’ve gotten some feedback from the First Month Report, we’ll use these to improve any less than satisfactory sections and add more through content.

For the software itself, there is the unfortunate lack of documentation of what each part does and when. For the time being we are still exploring the source code and trying to learn what each file does. We are trying to build up documentation as we go and will make sure to add to the documentation as we make changes. Finally, we have already made one change, that being moving the chat to the right side of the screen instead of the left. This allows for less visual clutter on the gameboard, and it fits better under the leaderboard. 

This week, unfortunately Hurricane Ian passed through South to Central Florida which caused a lot of damage in those areas and we, as a team, hope recovery efforts go well. Fortunately for our team Gainesville wasn’t heavily hit despite early forecasts showing that it would pass through.

Before the hurricane, we were able to meet with our liaison and discussing the roadmap and future of our project. We got approval for our roadmap as our liaison thought it generally fit well with what they hoped. We also learned more information about how we should run the test game to get more information on what we think could be improved. The most important thing to happen from the meeting is that we were able to get source code for the existing Hacker Jeopardy, which means we can now analyze and run the code as need be.

This week we consolidated our information in order to draft a Product Design Specification. In this document we used information from our meeting with our liaison to order the product needs, and the specifications we’ll use to meet those specific needs. After completing that, we began brainstorming some ideas on how we will tackle some of the needs. This included brainstorming graphs for user analytics, and some ideas for the User interface and selecting questions for the CTF. 

We are currently working on the projects overall schedule to prepare for the upcoming months of work. We also decided on using Sprints and Agile methodology to keep track of the work that has and will be done. The number of weeks between sprints will change as we shift from design to implementation. 

Finally, we went to the White Belt Team Workshop together. There we learned about processes and how to improve upon them by finding the root causes of problems and then improving upon them. We did this work alongside another team, GatorRepo, and simulated a car dealership and then improved on that process. 

This week, we continued organizing ourselves in this group. We started our work by deciding on a team name and logo. It took much deliberation, but we ultimately decided on the name Cyber Jeopardy, and we have for the most part decided on a final design for our logo. Then using the Scope of Work that Raytheon provided us we have begun analyzing the needs and wants of the project as a whole. This work should help us understand what we should attempt to do and in what order. This analysis also includes understanding who the major stakeholders in our project are. 

This Friday we were able to meet with our liaison for the first time, through this meeting we were able to get clarity on parts of the Scope of Work that were unclear and get further thoughts on features that they would like to see in the program. We also were able to get more information on how we would be able to access the existing program to begin analysis. 

Hello! We are one of two teams working for Raytheon during this academic year of IPPD. Our team is working on a continuation of the Hacker Jeopardy project from last year. Welcome to our first blog post for the year! 

This week we met up for the first-time during class. During the class we got to know one another and began planning for how the rest of the year would work. We decided on the number of times to meet per week and recorded what times we would be available to meet during the week. Later, we connected our liaison and scheduled a day to meet. During this next week we will be thoroughly studying the scope of work to begin planning for the rest of the year.