Yes, it makes sense to have the massaging logic there (operations close to the data that used it). This class is basically as dumb as the UserParameters ( i actually copied the concept from there), but only focussed on the AnalysisConstraints data.
We can do these improvements later, not a problem. I'm not very knowledgeable with Spring, so i prefer for now to play safe, and not trying anything 'new and fancy'. Anyway later on we will have to extend the of analysis constraints to the other 5 analysis, and then we can adjust the design again. 

I tested this for all the 10 analysis, and also tested the produced request.json and all work. 
So from now on we can rely on these files, and that was the visible motive for this improvement.