# Project 2

## Part A
For this project, all of my team mates and I were really communicative with each other and wanted to deliver a meaningful, but well-structured and designed plan for the group that would be recieving it, while also meeting the professor's request. In addition, we tried to lay out concepts for the "Bucket" design without using complicated language and provided the team with a UML diagram so that they could get a good gist of the software architecture that needed to be implemented.

I planned out the first "Design Diagrams and Outline" section of our team [document](https://depauledu.sharepoint.com/:w:/s/SE371475-Fall2022-TeamSwift7/EcBXwwOCY91AoLP-ZyG9aHgBuujmQ5ktcE3LDGhm7-7kjQ?e=f63z18) and also created a draft for the UML diagram. Later out project manager Caleb Papay, add new implementations and cleaned it up.

In the end, we tried to make an implementation that was efficient, especially for removing & deleting items or buckets, so the design requires for the next team to code a doubly linked list.


## Part B
For this part of the project, it really made me understand how people can think of the same project in many different implementations. The team that we recieved the instructions from were very communicative on MS Teams and made sure that we were able to recieve all of the instructions. After reviewing Team 6's instructions, we as a team found some issues with the design; however, we made sure to contact Team 6 and they were very helpful and transparent. Overall from this project, we learned the importance of filling in the gaps. In a typical workplace, guidelines aren't going to cover every technical detail, so it's important to make the best and practical descision when it comes to undefined technicalities. After our team discussed the implementations after reading Team 6's design and asking them questions, we had one coder and the rest of us tested it and made sure it abided by the given requirements. There were some gaps that we found, but our team tried our best to bridge these gaps and fulfill every requirement and specification for the Nodes within the SpinList. If there were any things that Team 6 did not mention, we made sure to mention that in the code comments, and if we renamed any methods, we also made sure to mention them in the code comments as well.