.json и .csv в C++

---

Your task is to provide a working application that processes the input files, normalizes them and write merged and normalized data to the output file.

Application requirements:
•	The application must receive two command-line arguments with names of the two input files.
•	Input files must be processed concurrently to save processing time.
•	Input files must be parsed and normalized before writing to the output files.
•	The input files will be provided in CSV and JSON formats.
•	Reading input files must be measured in milliseconds and the result must be written to the log file or console output.
•	Writing to the output file must be done simultaneously from all input files, in a thread-safe manner.
•	Every line in the input file will produce exactly one line in the output file.
•	Input files:
There are two input files, one in CSV and the other in JSON format.
Each file contains three (3) fields:
•	some id (string),
•	quantity (integer)
•	price (double).

CSV line examples with semi-colon (;) as the delimiter, from the file called inputA.csv:
"cfd001";4000;132.50
"afe322";125;678.22

Similar JSON line examples, from the file called inputB.json:
{ "id": "afa072", "quantity": 3000, "price": 22.15 }
{ "id": "bba893", "quantity": 4, "price": 3455.10 }

•	Output file:
The output file must contain mixed lines in CSV format (as they are processed in parallel by each parser) with semi-colon (;) as the delimiter.
Each line contains four (4) fields that represent exactly one input line:
•	input file name (string),
•	id (string),
•	quantity (integer),
•	price (double).

Output file example (using the example lines above):
"inputB";"afa072";3000;22.15
"inputA";"cfd001";4000;132.50
"inputA";"afe322";125;678.22
"inputB";"bba893";4;3455.10

Development requirements:
•	Provide the solution using OOP techniques.
•	Write unit tests wherever you find appropriate.

Task deliverables:

•	Basic development and runtime environment specifications (compiler version, IDE used, target OS);
•	Activity and class diagrams (UML);
•	The source code;
•	The unit tests code;
•	The project files (solution/project files, makefile or similar)
•	The working application;
•	Any additional documentation or explanation you find necessary.

Что я уже пробовал:

Я не знаю, как оштрафовать решение проблемы ?

---