SE 371 – Project 2

Part 1:
This project involved my team creating a design document with an implementation design and sending it to another team (Team 4) for them to use. Along with receiving a design document from Team 2. We had a meeting the Friday following the reveal of Project 2, where we thought we summarized the necessary elements for Project 3 relatively effectively. Unfortunately come class on Wednesday, we discover that there a lot of flaws within both our design document and wiki. The professor provided a plethora of critiques that we took to heart, and proceeded to immediately work on correcting after class, with a better understanding of the project dependencies we were able to organize things to a great extent after that first class.

Part 2:
Much of the focus during the team meetings in the first week were concerned with future proofing communications and organization for when we had to interact with the other teams. This focus on the communication with the other teams came in handy come the second week, where we had distinct roles assigned to all members of the team, so that people could focus on their assigned tasks without concerning themselves with miscellaneous elements. I was in charge of organizing our communication structure as well as roles, and managing the Team Discord server, which was extremely vital to the success of our team in Part 2. Furthermore, I was the primary communicator between Team 3 and Team 4, since we had the ability to dictate how Team 4 would communicate with us. This culminated in our successful project completion on Wednesday, where Team 4 (and Team 2) described communication with our team as ‘great’ which I can’t help but take some amount of credit for, as I was part of the primary planning process for our organization and scheduling. I was also able to answer questions, or at least acknowledge the questions from Team 4 within 5-10 minutes or even shorter. We had a little struggle in terms of certain people not successfully completing their task assignments at certain points, but we completed everything in the end, with time to spare to allow for any feedback for Team 4 to be given, though none was needed, since my answers allowed them to complete the design without much hassle.

SE 371 – Project 1 – Part 2

Part 2 of Project 1…
This is where we actually made the test cases for our chosen methods, I will say that as I was working I discovered a very poor choice of methods on my part. I had to test the main() method(s) of some of the classes, and this required me to figure out how to check and test System.out.println statements, which took me way longer than I’d like to admit. However, once those were done, everything else was generally pretty easy, and my groupmates came in clutch in terms of helping with some git stuff. Jacob and Jonathan especially were very helpful.

SE 371 – Project 1 – Part 1

Okay, so for this assignment or Project the first part involved me and the rest of my team organizing our git workspace and scheduling what exactly needed to be done and when. Every available group member chose five different methods to create JUnit tests for. This process wasn’t terribly difficult and with the work done by some other group members the rest of the GitHub repository was set up successfully.