What are the most significant risks that could jeopardize the success of the project?
One of the major risks that we are having right now is not getting the UDP part of the project integrated with the GUI and the rest of the protocols. Additionally, because the original GUI library that we were using was not well documented, we’ve quickly made the transition to using a different GUI library to implement the GUI, making it (so far) a lot easier to integrate our protocols.
How are these risks being managed? What contingency plans are ready?
The UDP integration risk is being mitigated by making small changes to the UDP simulator in order for it to work with the GUI. Sam is dedicating time to make sure this gets done before we have to make our video.
Because the new library that we are using to implement the GUI is a lot easier to use, there has been less issues since debugging is a lot easier due to the more extensive documentation online.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)?
No changes to any requirements or design. We’ve changed the library that we were previously using to implement the GUI, but besides that, everything is the same.
Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
The change was necessary since we were having difficulties displaying an image with the previous implementation of the GUI. Because many of the functions were already created to call the protocols, integrating into a new and similar GU library wasn’t difficult; therefore, there are no additional moving forward. If anything, it may be easier to understand the GUI library since it’s better documented.
Provide an updated schedule if changes have occurred.
The schedule has not changed.