Template for DTR Memo

Project: Enigma

Group Member Names: Bao Nguyen and Ben Jacobs

Project Expectations: What does each group member hope to get out of this project?

Ben would like to solve all aspects of problem. I would like to whiteboard and pseudocode the project as well as we can to solve the problem so that less code is written as a whole.

Goals and expectations:

Better implementing TDD, with full test coverage for functionality and correctness. Also coverage of edge cases. Solve every
problem and figure out a calculated approache to decryption after brute force. Share work load and learning benefits.

Team strengths:

Relatively solid knowledge of functionality. Good grasp of basic computer science concepts/fundamentals.

How to overcome obstacles:

Both Ben and I are used to working by ourselves. Ben has worked as a freelancer for the last three years and my last group project was in 2010.

Schedule Expectations (When are we available to work together and individually?):

Generally work before class, lunch if need by, and afternoon up to 1730-1800. Pairing in person only.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
Daily checkins and communication based on project task progress. Spend more time at the beginning and end of project. Do certain tasks individually.

Abilities Expectations (Technical strengths and areas for desired improvement):

Abilities are good for both persons. Desire for improvement in testing and also to improve each other's code based on suggestions and tests.

Workload Expectations (What features do we each want to work on?):

After mapping out tasks, we will decide what we want to do. No expectations on certain tasks at the moment.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

Try to learn git workflow - with pull requests and merging. Be vigilant to work on an alternate branch, rather than make commits to working code in the master branch.

Expectations for giving and receiving feedback:

Communicate about code readability. Be open to new ideas and constructive criticism.

Agenda to discuss project launch:



Ideas:
Update after whiteboard exercise.

Tools:
VSCode, Git.

Additional Notes: