Execution Plan - ntopper/MD5AwSum GitHub Wiki

Table of Contents

Teams

The project will be divided into 3 teams, who will each be responsible for two related modules. By dividing the project into 3 parts of related classes and methods, we can make sure our teams are highly specialized and apply the best personnel for the task at hand.

Team 1, Hashing and Searching

Team one will be responsible for creating and testing the md5lib, and the RainbowTable modules.

Team 2 File Management

Team two will be responsible for the RepositoryManagement and Config modules.

Team 3 Implementation

Team 3 will be responsible for parsing the input arguments, and the main function(s).

Deadlines

First Unit Tests

The first unit tests for each team will be due on November 14th. These unit tests will be designed to test each class and its methods individually. These unit tests will bring forth the bulk of the internal logic errors in each individual class. They will fully flush every method and property of each class to ensure that the implementations are ready to be run together in a cohesive unit.

Second Unit Tests

The second unit tests will be due on November 21, giving one week to correct any bugs found in the first round and to prepare the project as a whole to run the classes together. These unit tests will be more concerned with how the project as a whole interacts rather than the individual classes and methods (as most, if not all, of the bugs should be handled in the first round of unit testing).

Final Submission

Our goal is to submit the project on November 28th, before the week of final exams.

⚠️ **GitHub.com Fallback** ⚠️