On 22/08/16 20:32, Anne Etien wrote:

Please find them attached.
Cheers,
Anne
Thanks Anne. A good list. Here are some more:

Name resolving is something we now do custom for each language.
Some more generic tooling for that might be worthwhile too.

Support for systems consisting of multiple languages would be
helpful. Systems using SQL stored procedures and another language,
or XML configuration files are very common.

I also tend to need to model connected artifacts: JIRA tickets,
requirements, releases.

"20mn are currently needed to load a 1 million elements model. "
20 million what? The inheritance depth and #instVars in current FAMIX
are problematic indeed. It is much too easy to run out of memory.

The storage of calculated measurements also needs changes:
mostly I calculate the same measurements for all (or a group of)
methods/classes/units. Storing them in a dictionary for each instance
is very wasteful.

Cheers,
  Stephan




MooseADT