Project architecture¶

The application consists of two parts

• Server
• Client application

Server architecture¶

In the following text will be specified the communication between parts of the server application.

In the simple visualisation below are displayed the relevant classes and requests that take place between packages.

• Model asks parser for information acquired from data
• Parser asks data downloader for path to folder containing data

The path to data folder itself is specified from user as a command line argument upon launching the application.

Model architecture¶

Interface model-parser¶

Handing over information in lists containing separate entries.

Method Parse() enables specifying the interval by which to divide the days. By default parses one day as one entry.

- example of dividing into intervals

Parser architecture¶

- csv loader -> can be swapped w/ different one

- parsers for all separate files -> can be swapped w/ different ones

- TagInfo with used tags -> can be swapped / edited

- output relatively universal, just building tags -> could be replaced by different tags

Interface parser-downloader¶

Parser asks for folder with data files.

Loader architecture¶

Has to be able to handle request signaling dowload of new data, and requests for path to folder with data.

Client application architecture¶

Communication server-client¶