Any business visited by customers wants to count footfalls.

This project is about simulating data from a footfall sensor and recording it for reporting.

At a top level, the program runs in two processes - the sender and the receiver.

The Sender is responsible for simulating the footfall sensor. The Receiver stores the data.

The Sender sends data to the Receiver using console redirection. Run them on the command line as follows:

sender-executable | receiver-executable

This would make the console-writes of the sender become the console-reads of the receiver.

The naming of source files within the Sender and within the Receiver give their internal decomposition.

This project follows the practices and tools listed here.

We document the interface between the Sender and the Receiver as test cases.

The Sender and Receiver are testable on their own:

• The Sender is testable without the Receiver - so we can develop for another data-source, test and be confident about integration.
• The Receiver is testable without the Sender - so we can enhance without re-testing against all Receivers again.

To simulate different patterns of footfalls, the Sender reads a CSV file as input.

The Receiver writes aggregates into another CSV file, which a spreadsheet app can load for further processing.

Aggregates are in the form of:

• Average footfalls per hour, shown over a day
• Average daily footfalls in a week
• Peak daily footfall in the last month

Footfall sensors can malfunction. The facility keeps a manual log of footfalls as well. Make it possible to reconcile the records with the manual log, without having to simulate the input again.

See here for the evaluation criteria of this exercise.