Our idea is to build an open repository containing a collection of models from a large group of projects (qualitas corpus), where each of these models can be annotated and expanded with analysis results. Analysis results could be anything (i.e. all classes of a certain project can be annotated with a certain metric; two classes can be related by a duplication relationship; etc.. ). The resulting "expanded models" can be queried or downloaded (useful if you want to compare the data against results of an industrial project analysis). MSE files are used as a way to import a simple version (no contributed analysis results annotations) of the project model into moose and enable new analyses.
Ok now what I'm saying is that as soon as you want to do analysis you need also the infrastructure to support partial information.
Yes. You can have reduced models either by:
- (1) exporting a reduced (MSE) version from VerveineJ (I guess this is implemented);
- (2) or, importing your full model in Moose and then exporting the entities you want (this is also implemented, not sure if this integrated);
Distributing reduced MSE models of a project does not make much sense to me.
:) My point is that having a server is something, having an infrastructure to perform analysis is important and this is what we brainstormed.
You have to take in consideration multiple analysis requirements and build a reduced model for each of them. Would it be possible (and would it make sense) to create a web service which interprets moose queries, runs them on the specified target image and returns a serialized representation of the returned objects ?
- keeping source code (and much more) is important because you never know what people would like to do in the future.
It happened to a team in Brazil recently, they correlated some metrics to bugs. So they needed on top of the MSEs: access to a bug-tracking system to identify bug-identifiers; access to SVN commit comments to identify bug-fixing commits; access to the code to know what methods/classes were changed to correct the bug. Anyway, people want to see source code. If something looks strange in a visualization, you want to go back to the code to understand what's happening.
Since qualitascorpus.com already provides and maintains a good collection of java projects, we thought about reusing that valuable source of information and building the MSE repository as a complement to Qualitas Corpus.
I would always version the source code and the mse (as well as the version of the tools used to extracted it). HD is cheap and you always want to get all the information if you can.
This means that MSE files would be generated and hosted by us and source code can be downloaded from qualitascorpus.com.
I would follow an object-oriented approach: project with all data together and encapsulated.
Andrea
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev