Summer 2019 SYSC3303A: Trivial File Transfer Protocol Project

A file transfer system based on the TFTP specification (RFC 1350). The TFTP program will contain three programs: Client, Error Simulation, and Server. The goal of the project is to be able to run all of the programs separately and transfer files from or to Client and Server.

Members

Sirak Berhane - 101030433

Samuel Baumann - 101033635

Henri Umba - 101022562

Gen Li - 100967203

Iteration 1 - Submitted On: Tuesday, May 21, 2019

Note: This iteration also includes Iteration 0.

Deliverables:

• README (this document)
• UML Class Diagram
• State Machine Diagrams (Client, Host/Err. Simulator, Server)
• Use Case Document
• Code for each component + supplementary classes & constants

Breakdown:

• Code - Sirak (adapted from his Assignment 1 and further expanded to include file transfer + helper classes)
• Supporting Documentation, UML and Use Case: Sam
• State Machine diagrams and added verbose/quit user input code to Client: Ruchi

Setup:

To run our first iteration, a user must have an instance of the client and server on the same machine, and must also run the connection handler and error simulator if they wish to run tests. Once all of these consoles are open and the threads are running, follow the steps outlined in the Client's main() function to select your mode, file locations and other customizable options. To quit, again follow the instruction in Client to send a shutdown command to the system.

Iteration 2 - Submitted On: Tuesday, May 28, 2019

Note: Group 5 has merged its remaining 3 members with Group 9's remaining 2 members

Deliverables:

• README (this document)
• UML Class Diagram
• State Machine Diagrams (Client, Host/Err. Simulator, Server)
• Use Case Document
• UML Sequence Diagram
• Updated Code for each component + supplementary classes & constants

Breakdown:

• Code - Sirak, Henri (modified with group 9's iteration 1 + addition of testing in Error simulator)
• Supporting Documentation, UML Class and Use Case: Sam
• UML Sequence and State Machine Diagrams: Gen

Setup:

Running the second iteration is similar to the first in that a user must have an instance of the client, error simulator and server open on the same machine, and run the connection handler to log testing, a crucial part of iteration 2. In this case however, though the client is still responsible for accepting user input to select mode, file locations and other options, the Error simluator can be customized to intentionall delay, duplicate or lose packets in order to record how the server behaves when presented with irregular messages.

Known issue

Server can't shutdown by custom command.

Iteration 3 - Submitted on Tuesday, June 4, 2019

Deliverables:

• README (This document)
• UML Class Diagram
• State Machine Diagrams (Client, Error Simulator, Server)
• Use Case Document
• UML Sequence Diagram
• Updated code for each component + supplementary classes & constants

Breakdown:

• Code - Sirak, Henri and Sam (Client/Server by Sirak & Henri, Error Simulator Updates by all 3)
• Supporting Documentation, Use Cases and State Machine Updates - Sam
• Updated UML Class and Squence Diagrams - Gen

Iteration 4 - Submitted on Tuesday, June 11, 2019

note - essentially unchanged from iteration 3

Deliverables:

• README (This document)
• Detailed Setup instructions
• UML Class Diagram
• State Machine Diagrams (Client, Error Simulator, Server)
• Use Case Document
• UML Sequence Diagram
• Updated code for each component + supplementary classes & constants

Breakdown:

• Code - Sirak, Henri and Sam (Client/Server by Sirak & Henri, Error Simulator Updates by all 3)
• Supporting Documentation, Use Cases, setup instructions and State Machine Updates - Sam
• Updated UML Class and Squence Diagrams - Gen