Final Project!

The Final Project Repository!

Welcome to the final project repository!

Here is a welcome video showing the repository organization--be sure to read carefully through the instructions (Consuming a large spec and breaking it down is part of engineering!).

https://youtu.be/F0XVOL1zQHM

Repository Organization

1. There are no more individual assignments.
2. You will complete your final project in the final project directory. The organization is partially up to you on the file structure and organization, just make sure you organize it logically and against any requirements.

Team

Team Name: DRaw

Team Member Names:

1. Steven Abbott
2. Elizabeth Williams
3. Andrew Briasco-Stewart
4. Ben Mallett

Team Spreadsheet

• Your team members and project manager are listed on the following spreadsheet here.
• Your project manager will be your first point of contact for various project deliverables and questions. Though you may continue to attend office hours with whomever you like, your project manager will be your primary contact.

Team Logistics

• Work with your team to ensure everyone has a way to work on this codebase with a common set of tools
• Everyone should make code contributions to the repository (i.e. everyone should have some commits in the commit history -- even if you pair program, that means you need to switch who is in control!)
• See the project timeline
• Note: In semesters where I have a 'token system' for late days, you cannot use any tokens for the final project

Notes on working in teams

• Four Ways to Lead Your Software Team to Success
• The 3 C's of being a captain
• Etiquette for Pair Programming

Rubric

Points	Description
10% (Milestone Check-in #1)	Did you complete your check-in #1? Was a timeline present? Were there at least 10 tasks created in the 'Projects' tab?

Points	Description
10% (Milestone Check-in #2)	Did you complete your check-in #2?

Points	Description
5% (Youtube Video)	Did you upload a YouTube Video and test out opening it incognito mode, so we could also access it?

Points	Description
10% (Team Assessment)	Did you complete the assessment form which earns you 2%? -- the other 8% is determined by your team members responses. Note: In rare instances the instructor reserves the right to weigh the Team assessment more heavily. In the instance that a team member scores very low, the instructor will individually evaluate that students grade for the project.

Points	Description
25% (Polish and completion)	How polished are your materials (timeline, documentation, presentation)? Does your software work? Does it compile? Does it crash, segfault?

Points	Description
10% (Feature of your choice)	Does your feature work? Do you have at least 1 test case?

Points	Description
20% (Networking)	Does your networking work?

Points	Description
10% (Testing)	Do you have at least 8 unit test cases? Are they properly integrated with a GitHub Action?

Note: To be 100% clear, every team member gets the same grade except for the peer assessment.