Document about Fitting Workflow

Side-Conditions
1. Code will go to exclusive ownership of ... and they want to have it commercializable
2. Thus we can only build on top of pre-existing software, which is under a commercial-friendly license.
3. We need to calculate for User-documentation and Source-Code documentation
4. We need to calculate for automated tests and test-coverage
5. We can build on top of the iPython-notebook as provided by Meysam and which Lia will further inspect now
6. We need to have a „requirements“-description from Marseille-side, which we can refer to in our offer. It is mandatory, that this requerement also ourlines the involvment of INS into the work, as this is crucial for ... to have that defined in the contract (as it is a lever for codebox to excuse if not delivering…). Thus that needs to be described as precise as possible.
7. We will refer to the requirements mentioned above in our offer and assure the points (documentation, ownership etc.) mentioned before to be delivered for a flat-fee. Alongside we will need a bit of text for the work-offer „how“ we will implement the requirements (programming-language etc.)
8. Reconstruction-Pipeline is out of scope

Lia is aware (and expecting) to be contacted by Viktor on this for further details. Potentially there will be a further contact useful with Meysam (however, Lia will indicate necessaty based on the analysis of the iPython notebook). Our focus now is to understand the delta from the current existing implementation to what is necessary for ... to give a contract.