This week in IPPD, we attended the SLDR Event. Prior to the event, we finalized our SLDR report based off feedback from the SLDR draft report submission. Additionally, we had a chance to modify our SLDR presentation based off the feedback received from the SLDR draft presentation event held last week. Overall the event went very well and we were very happy with our presentation. The event served as a fantastic opportunity to meet our liaison face to face and speak about both the project and other conversational topics. Moving forward, we will be working to correct the looming network issue that has prevented us from holding our CTF. We are looking forward to solving this problem in addition to a myriad of others next semester in IPPD 2.

Prior to this week’s IPPD class, team 10 worked to address the feedback received from our prototype. We received a lot of valuable feedback from this event, and believe that our end product will be significantly better as a direct result of the PID event. Beyond this we worked to complete our SLDR Report Draft and SLDR Presentation Draft.

In class this week, we presented our SLDR draft presentations and received feedback from our peers. This event was extremely helpful since we can now target specific problems brought to our attention, improving the overall quality of the presentation. Moving forward, we will be addressing these problems in addition to making other improvements and changes. We will also be practicing our presentation to fully prepare for the SLDR event. Lastly, we will be working to improve, modify, and address the feedback received from our SLDR Report draft so that it will be perfect for next week’s event.

This week in IPPD, we presented a demonstration of our project for Prototype Inspection Day. In preparation for the event, Team 10 generated an interactive low fidelity wireframe to model how we envision users interacting with the system and how the system will respond in turn. We also attempted to write an interactive demonstration of certain program functions using CherryPy, but this ended up proving to be a much larger task than initially anticipated. Overall, the event went well and we were able to receive some useful feedback that will help us refine our design choices and continue making progress on our project.

While our efforts this week were primarily focussed on preparing for Prototype Inspection Day, we did make progress in other areas of need for our project. Since contacting UF IT did not end up helping resolve our CTF campus networking issue, one of the most notable events to occur this week includes getting in touch with an IPPD alumni that worked on this project. The advice we were given over email seems promising, and now needs to be tested. If everything goes smoothly, we can get this issue resolved and host our CTF immediately after Thanksgiving.

This week in IPPD, we attended a Salary Negotiation workshop presented by Dr Erin Lin from  the Career Connections Center. Despite its name, the workshop covered so much more than how to go about negotiating salary. In addition to learning about salary negotiation, Dr Lin provided a lot of useful insight in how to better interview for jobs. Beyond this workshop, we also discussed the importance of engineering ethics and a series of case studies involving ethical issues.

Outside of class, we have primarily set our focus on Prototype Inspection day. Over the course of the past few weeks, we have been developing wireframes that show our envisionment of new features requested to be added to the program. In addition to this, we have also been working on completing a CherryPy tutorial so that we can also show some demo code for prototype inspection day. Other than this, we have been working on resolving a networking issue with the current version of the program not being accessible to users over UF’s network. Because of this issue, our CTF has needed to be pushed back, but we are now in contact with our Coach, Liaison, and UF IT to attempt to resolve the problem asap. Once this is complete and prototype inspection day is behind us, it will finally be time to officially host our initial CTF.

This week in IPPD, we learned about cost estimation, make vs buy analysis, and mainly completed our prototype plan. In this process, we were asked to answer a few questions that would help guide us in both the creation of our prototype and presentation for Prototype Inspection Day. After answering the questions, we have a strong idea of our prototype’s purpose, how we plan to evaluate our prototype’s success, what we plan to be showing and receiving feedback on, a list of necessary materials to construct the prototype, and most importantly a schedule that displays all of the tasks that need to be completed by a specific deadline prior to Prototype Inspection Day.

Outside of class, we have continued in an attempt to ensure that our CTF is held before Thanksgiving Break. Over this past week, we have been in contact with the IPPD coach that worked on this project last year, Dr Newman. Through our communications, we were able to learn that last year’s CTF was held in the Hub over UF’s network. This is critical knowledge, as we now plan to hold a test CTF among our team to test the application and ensure we are able to host the game on UF’s network. Once this is complete, we will have all the available tools and knowledge required to run the CTF. Beyond the CTF, all team members completed the Python beginner course to gain a deeper understanding of the language prior to diving into CherryPy. Moving forward we will be developing our prototype and preparing for Prototype Inspection Day, in addition to completing the CherryPy tutorial found in the CherryPy Github repository.

This week in IPPD, we modified and submitted the final revision of our PDR. Changes made were based on feedback received from Dr Latore, our peers, and our liaison engineer. In class, we held a teamwork prototype planning session in preparation for prototype inspection day. During this meeting we were able to consider various questions that will be prevalent in the development of our prototype plan. 

As we move forward, we intend to begin creating our prototype plan and generating graphics to demonstrate the changes we plan to implement. Currently, the plan is to create wireframes to model what the changes will look like after being implemented. Beyond this, we would also like to create a demo using CherryPy to gain familiarity with the framework and using Python for web development. To aid in this process, team members without prior Python experience will be taking the beginner course on Codeacademy to gain familiarity with Python. In addition to our prototype plan, we are also still in the process of planning our CTF. At this time, we are still seeking participants, however our coach has agreed to assist in this process. Additionally, we are waiting to hear back from our coach regarding the network resources needed to run the CTF and have it accessible on various devices. Our goal is to hold the CTF prior to prototype inspection day (November 16th).

This week in IPPD, we presented our PDR document to our liaison engineer, Randall Brooks, from Raytheon Technologies. Overall the presentation went very well and we were happy with the end result. Prior to the PDR presentation, each member of the team went through their slides and cleaned up any feedback mentioned from our Draft Presentation. Beyond this, we also held a practice session prior to giving the actual presentation. 

Moving forward, our first order of business will be sending a final copy to our liaison today to receive his signature. Beyond this, it is also essential that we hold our initial CTF so that we can make our own assessment of things that will require modification moving forward. Lastly, all team members have begun learning Python so that we can begin implementing changes as soon as next semester.