Final Project

The final project consists of finishing our work on the Pippin Simulator for the semster. I have provided the final version of the Pippin Simulator, as well as a Graphical User Interface to run that simulator. At the beginning of the project, there is only one major missing piece - an Assembler to convert man readable Pippin Assembly files into Pippin Executable files that contain the binary representation of Pippin programs that can be run on the Pippin Simulator.

The final project will be divided into two parts. The first part consists of writing the Java code to implement an Assembler for Pippin. You will have two weeks to work on this project in teams. The second part consists of providing an enhancement to the Graphical User Interface provided with the Pippin simulator. You will again have two weeks to work on the second part of the project with your team.

During the finals week, I will also schedule 5 minute oral exams with each student. One of the goals of the oral exam is to make sure that you understand all of the work your team has done on the project.

The following table summarizes the final project parts

Project Teams

The project may be done in teams of 1, 2, or 3 students.

• Teams should be composed of students from the same lab section because we will be working on the project during the lab times. Students may select their own teams, as long as all members of the team agree to be on the team.
• The team should decide, before accepting the project part 1 invitation, on a team name, and choose a team member to create the team.

  The team creator should accept the Project part 1 invitation first. When accepting the invitation, GitHub Classroom will ask you if you want to join an existing team, or create a new team. The creator should create a new team, using the agreed team name.

  Once the creator has successfully accepted the invitation, the remaining team members can accept the project 1 invitation. The remaining members should join an existing team, and select the team name.

• We will use the same teams for both the project part 1 and the project part 2.
• The Professor has the authority to modify team membership, but it's a pain in the neck especially after some time has passed, so try to get the teams right the first time.
• Once you have joined a team, then you have the authority to view the team's master repository, clone that repository to a local clone, commit on your local clone, and push that commit back to the master. Since multiple people can commit to the same master, there is a real potential for generating git conflicts. It is possible to resolve conflicts, but it's a lot easier to avoid conflicts by agreeing within your team on who is going to perform commits and pushes on the code. Make sure one students changes are committed and pushed, and then pulled into all other students clones before starting the next round of changes.

Project Part 1 Extensions

I realize this is a difficult time of the semester, which lots of papers due and exams to study for and travel plans to organize. The Project Part 1 is due on Wednesday, May 12, 2021 at 11:59 PM. I am willing to be somewhat flexible with this deadline, but this flexibility comes with some responsibility on your part.

• I will grant short extensions only when I get an email from your group. When I grant an extension, I will send an email and copy all the members of the group. If you have not received an email from me confirming your extension, you don't have an extension!
• I will not grant extensions after the due date. If you need an extension, you must ask for it before the project is due.
• Early requests for extensions represent good planning, and will be much easier to get. The closer the due date gets, the harder it will be to get an extension.
• An extension on part 1 of the project *reduces* the time you have to work on part 2 of the project. There will be **no** extensions granted for part 2 of the project because part 2 will be due on the last day of exams (and I need to quickly grade exams and projects to turn in final grades.)

Project Part 2

The project part 2 invitation is available, as of Sunday, May 9. You may start working on part 2 of the project whenever you would like to, but it makes most sense to start working on the project part 2 after submitting your part 1 results.

You will be working on part 2 of the project with the same teams you used for part 1 of the project. A new proj02 repository will be created for your team when the first member of your team accepts the GitHub proj02 invitation. Other team members will get access to that repository when they accept the invitation. All team members must accept the invitation.

Please feel free to ask questions about part 2 of the project during office hours, durling lab sessions, via email, or on Piazza, or any other established communication mechanism.

The second part of the project is due at the very end of the semester, so no extensions can be allowed for the project part 2.