Klever

If one runs verification of several requirement specifications within one job and simultaneously requires to use aspects of those requirement specifications for weaving common models, current caching approach can fail since it will cache and then reuse models that are woven in using only one aspect(s) from one requirement specification while other ones can require other aspects being used. I suppose to distinguish not only models but also aspects when caching them.